[web] Added the Deployment Guide for Fedora 14.
Jaromir Hradilek
jhradile at fedoraproject.org
Sun Nov 14 23:51:38 UTC 2010
commit 3e9599c670862991a761c911a56d5f57d960f628
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Mon Nov 15 00:47:19 2010 +0100
Added the Deployment Guide for Fedora 14.
fedoradocs.db | Bin 490496 -> 490496 bytes
public_html/Sitemap | 24 +
public_html/as-IN/Site_Statistics.html | 4 +-
public_html/as-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Core.xml | 2 +-
.../as-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/as-IN/opds.xml | 10 +-
public_html/as-IN/toc.html | 9 +
public_html/bg-BG/Site_Statistics.html | 4 +-
public_html/bg-BG/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Core.xml | 2 +-
.../bg-BG/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bg-BG/opds.xml | 10 +-
public_html/bg-BG/toc.html | 9 +
public_html/bn-IN/Site_Statistics.html | 4 +-
public_html/bn-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Core.xml | 2 +-
.../bn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bn-IN/opds.xml | 10 +-
public_html/bn-IN/toc.html | 9 +
public_html/bs-BA/Site_Statistics.html | 4 +-
public_html/bs-BA/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Core.xml | 2 +-
.../bs-BA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bs-BA/opds.xml | 10 +-
public_html/bs-BA/toc.html | 9 +
public_html/ca-ES/Site_Statistics.html | 4 +-
public_html/ca-ES/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Core.xml | 2 +-
.../ca-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ca-ES/opds.xml | 10 +-
public_html/ca-ES/toc.html | 9 +
public_html/cs-CZ/Site_Statistics.html | 4 +-
public_html/cs-CZ/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Core.xml | 2 +-
.../cs-CZ/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/cs-CZ/opds.xml | 10 +-
public_html/cs-CZ/toc.html | 9 +
public_html/da-DK/Site_Statistics.html | 4 +-
public_html/da-DK/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Core.xml | 2 +-
.../da-DK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/da-DK/opds.xml | 10 +-
public_html/da-DK/toc.html | 9 +
public_html/de-DE/Site_Statistics.html | 4 +-
public_html/de-DE/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Core.xml | 2 +-
.../de-DE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/de-DE/opds.xml | 10 +-
public_html/de-DE/toc.html | 9 +
public_html/el-GR/Site_Statistics.html | 4 +-
public_html/el-GR/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Core.xml | 2 +-
.../el-GR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/el-GR/opds.xml | 10 +-
public_html/el-GR/toc.html | 9 +
.../Fedora-14-Deployment_Guide-en-US.epub | Bin 0 -> 9642869 bytes
.../Deployment_Guide/Common_Content/css/common.css | 1474 +++
.../Common_Content/css/default.css | 3 +
.../Deployment_Guide/Common_Content/css/lang.css | 2 +
.../Common_Content/css/overrides.css | 51 +
.../Deployment_Guide/Common_Content/css/print.css | 16 +
.../Deployment_Guide/Common_Content/images/1.png | Bin 0 -> 710 bytes
.../Deployment_Guide/Common_Content/images/1.svg | 27 +
.../Deployment_Guide/Common_Content/images/10.png | Bin 0 -> 985 bytes
.../Deployment_Guide/Common_Content/images/10.svg | 31 +
.../Deployment_Guide/Common_Content/images/11.png | Bin 0 -> 810 bytes
.../Deployment_Guide/Common_Content/images/11.svg | 31 +
.../Deployment_Guide/Common_Content/images/12.png | Bin 0 -> 1012 bytes
.../Deployment_Guide/Common_Content/images/12.svg | 31 +
.../Deployment_Guide/Common_Content/images/13.png | Bin 0 -> 1048 bytes
.../Deployment_Guide/Common_Content/images/13.svg | 31 +
.../Deployment_Guide/Common_Content/images/14.png | Bin 0 -> 914 bytes
.../Deployment_Guide/Common_Content/images/14.svg | 31 +
.../Deployment_Guide/Common_Content/images/15.png | Bin 0 -> 989 bytes
.../Deployment_Guide/Common_Content/images/15.svg | 31 +
.../Deployment_Guide/Common_Content/images/16.png | Bin 0 -> 1047 bytes
.../Deployment_Guide/Common_Content/images/16.svg | 31 +
.../Deployment_Guide/Common_Content/images/17.png | Bin 0 -> 888 bytes
.../Deployment_Guide/Common_Content/images/17.svg | 31 +
.../Deployment_Guide/Common_Content/images/18.png | Bin 0 -> 1075 bytes
.../Deployment_Guide/Common_Content/images/18.svg | 31 +
.../Deployment_Guide/Common_Content/images/19.png | Bin 0 -> 1049 bytes
.../Deployment_Guide/Common_Content/images/19.svg | 31 +
.../Deployment_Guide/Common_Content/images/2.png | Bin 0 -> 896 bytes
.../Deployment_Guide/Common_Content/images/2.svg | 27 +
.../Deployment_Guide/Common_Content/images/20.png | Bin 0 -> 1151 bytes
.../Deployment_Guide/Common_Content/images/20.svg | 31 +
.../Deployment_Guide/Common_Content/images/21.png | Bin 0 -> 994 bytes
.../Deployment_Guide/Common_Content/images/21.svg | 31 +
.../Deployment_Guide/Common_Content/images/22.png | Bin 0 -> 1162 bytes
.../Deployment_Guide/Common_Content/images/22.svg | 31 +
.../Deployment_Guide/Common_Content/images/23.png | Bin 0 -> 1207 bytes
.../Deployment_Guide/Common_Content/images/23.svg | 31 +
.../Deployment_Guide/Common_Content/images/24.png | Bin 0 -> 1081 bytes
.../Deployment_Guide/Common_Content/images/24.svg | 31 +
.../Deployment_Guide/Common_Content/images/25.png | Bin 0 -> 1173 bytes
.../Deployment_Guide/Common_Content/images/25.svg | 31 +
.../Deployment_Guide/Common_Content/images/26.png | Bin 0 -> 1208 bytes
.../Deployment_Guide/Common_Content/images/26.svg | 31 +
.../Deployment_Guide/Common_Content/images/27.png | Bin 0 -> 1080 bytes
.../Deployment_Guide/Common_Content/images/27.svg | 31 +
.../Deployment_Guide/Common_Content/images/28.png | Bin 0 -> 1225 bytes
.../Deployment_Guide/Common_Content/images/28.svg | 31 +
.../Deployment_Guide/Common_Content/images/29.png | Bin 0 -> 1196 bytes
.../Deployment_Guide/Common_Content/images/29.svg | 31 +
.../Deployment_Guide/Common_Content/images/3.png | Bin 0 -> 958 bytes
.../Deployment_Guide/Common_Content/images/3.svg | 27 +
.../Deployment_Guide/Common_Content/images/30.png | Bin 0 -> 1250 bytes
.../Deployment_Guide/Common_Content/images/30.svg | 31 +
.../Deployment_Guide/Common_Content/images/31.png | Bin 0 -> 1078 bytes
.../Deployment_Guide/Common_Content/images/31.svg | 31 +
.../Deployment_Guide/Common_Content/images/32.png | Bin 0 -> 1241 bytes
.../Deployment_Guide/Common_Content/images/32.svg | 31 +
.../Deployment_Guide/Common_Content/images/33.png | Bin 0 -> 1268 bytes
.../Deployment_Guide/Common_Content/images/33.svg | 31 +
.../Deployment_Guide/Common_Content/images/34.png | Bin 0 -> 1175 bytes
.../Deployment_Guide/Common_Content/images/34.svg | 31 +
.../Deployment_Guide/Common_Content/images/35.png | Bin 0 -> 1224 bytes
.../Deployment_Guide/Common_Content/images/35.svg | 31 +
.../Deployment_Guide/Common_Content/images/36.png | Bin 0 -> 1281 bytes
.../Deployment_Guide/Common_Content/images/36.svg | 31 +
.../Deployment_Guide/Common_Content/images/37.png | Bin 0 -> 1140 bytes
.../Deployment_Guide/Common_Content/images/37.svg | 31 +
.../Deployment_Guide/Common_Content/images/38.png | Bin 0 -> 1300 bytes
.../Deployment_Guide/Common_Content/images/38.svg | 31 +
.../Deployment_Guide/Common_Content/images/39.png | Bin 0 -> 1294 bytes
.../Deployment_Guide/Common_Content/images/39.svg | 31 +
.../Deployment_Guide/Common_Content/images/4.png | Bin 0 -> 849 bytes
.../Deployment_Guide/Common_Content/images/4.svg | 27 +
.../Deployment_Guide/Common_Content/images/40.png | Bin 0 -> 1130 bytes
.../Deployment_Guide/Common_Content/images/40.svg | 31 +
.../Deployment_Guide/Common_Content/images/5.png | Bin 0 -> 900 bytes
.../Deployment_Guide/Common_Content/images/5.svg | 27 +
.../Deployment_Guide/Common_Content/images/6.png | Bin 0 -> 929 bytes
.../Deployment_Guide/Common_Content/images/6.svg | 27 +
.../Deployment_Guide/Common_Content/images/7.png | Bin 0 -> 807 bytes
.../Deployment_Guide/Common_Content/images/7.svg | 27 +
.../Deployment_Guide/Common_Content/images/8.png | Bin 0 -> 962 bytes
.../Deployment_Guide/Common_Content/images/8.svg | 27 +
.../Deployment_Guide/Common_Content/images/9.png | Bin 0 -> 936 bytes
.../Deployment_Guide/Common_Content/images/9.svg | 27 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 623 bytes
.../Deployment_Guide/Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../Common_Content/images/green.png | Bin 0 -> 176 bytes
.../Common_Content/images/h1-bg.png | Bin 0 -> 565 bytes
.../Common_Content/images/image_left.png | Bin 0 -> 1114 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 2260 bytes
.../Common_Content/images/important.png | Bin 0 -> 2080 bytes
.../Common_Content/images/important.svg | 106 +
.../Common_Content/images/logo.png | Bin 0 -> 1114 bytes
.../Common_Content/images/note.png | Bin 0 -> 1241 bytes
.../Common_Content/images/note.svg | 111 +
.../Deployment_Guide/Common_Content/images/red.png | Bin 0 -> 163 bytes
.../Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 760 bytes
.../Common_Content/images/stock-home.png | Bin 0 -> 808 bytes
.../Common_Content/images/title_logo.png | Bin 0 -> 13399 bytes
.../Common_Content/images/title_logo.svg | 61 +
.../Common_Content/images/warning.png | Bin 0 -> 1340 bytes
.../Common_Content/images/warning.svg | 89 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../Deployment_Guide/images/ABRT-Main_Window.png | Bin 0 -> 62743 bytes
.../images/ABRT-Notification_Area_alarm_icon.png | Bin 0 -> 1187 bytes
.../Deployment_Guide/images/ABRT-plugins.png | Bin 0 -> 72790 bytes
...ion_Configuration-authconfig-Authentication.png | Bin 0 -> 37767 bytes
...entication_Configuration-authconfig-Options.png | Bin 0 -> 30139 bytes
...tion_Configuration-authconfig-SSSD_Settings.png | Bin 0 -> 22607 bytes
...n_Configuration-authconfig-User_Information.png | Bin 0 -> 31426 bytes
.../images/Change_Runtime_Boolean.png | Bin 0 -> 29894 bytes
.../images/FirefoxWithKerberosSSO.png | Bin 0 -> 25826 bytes
...ical_Package_Management-Software_Log_Viewer.png | Bin 0 -> 160350 bytes
...kage_Management-Software_Update_Preferences.png | Bin 0 -> 19454 bytes
...ical_Package_Management-add_remove_software.png | Bin 0 -> 37858 bytes
...hical_Package_Management-additional_updates.png | Bin 0 -> 54900 bytes
.../Graphical_Package_Management-authenticate.png | Bin 0 -> 19596 bytes
...l_Package_Management-filters-only_available.png | Bin 0 -> 32640 bytes
...al_Package_Management-filters-only_end_user.png | Bin 0 -> 32876 bytes
.../images/Graphical_Package_Management-htop.png | Bin 0 -> 58033 bytes
.../Graphical_Package_Management-install.png | Bin 0 -> 55559 bytes
...ckage_Management-installing_a_package_group.png | Bin 0 -> 85446 bytes
...ical_Package_Management-removal_in_progress.png | Bin 0 -> 79297 bytes
.../images/Graphical_Package_Management-remove.png | Bin 0 -> 66023 bytes
...hical_Package_Management-removing_a_package.png | Bin 0 -> 49512 bytes
...raphical_Package_Management-software_update.png | Bin 0 -> 74684 bytes
...phical_Package_Management-updates_available.png | Bin 0 -> 17792 bytes
.../Deployment_Guide/images/Load_New_Policy.png | Bin 0 -> 19739 bytes
.../Network_Configuration-NM-All_applet_states.png | Bin 0 -> 11378 bytes
...ork_Configuration-NM-Available_to_all_users.png | Bin 0 -> 4464 bytes
...work_Configuration-NM-Connect_automatically.png | Bin 0 -> 19915 bytes
...iguration-NM-Edit_System_eth0-IPv4_Settings.png | Bin 0 -> 33802 bytes
...ork_Configuration-NM-Edit_System_eth0-Wired.png | Bin 0 -> 21595 bytes
...Configuration-NM-Editing_Wired_Connection_1.png | Bin 0 -> 56373 bytes
...figuration-NM-Editing_Wireless_Connection_1.png | Bin 0 -> 76055 bytes
...rk_Configuration-NM-IPv4_Settings-Addresses.png | Bin 0 -> 9790 bytes
...nfiguration-NM-IPv4_Settings-DHCP_Client_ID.png | Bin 0 -> 1829 bytes
..._Configuration-NM-IPv4_Settings-DNS_Servers.png | Bin 0 -> 2573 bytes
...twork_Configuration-NM-IPv4_Settings-Method.png | Bin 0 -> 2816 bytes
...twork_Configuration-NM-IPv4_Settings-Routes.png | Bin 0 -> 1557 bytes
...nfiguration-NM-IPv4_Settings-Search_domains.png | Bin 0 -> 3152 bytes
.../Network_Configuration-NM-IPv4_Settings.png | Bin 0 -> 25414 bytes
...etwork_Configuration-NM-Network_Connections.png | Bin 0 -> 19394 bytes
...Network_Configuration-NM-System_eth0-Routes.png | Bin 0 -> 13495 bytes
...iguration-NM-Wireless_Auto_Connections_List.png | Bin 0 -> 83527 bytes
...uration-NM-Wireless_authentication_required.png | Bin 0 -> 70411 bytes
.../Network_Configuration-NM-applet_states.png | Bin 0 -> 2912 bytes
.../Network_Configuration-NM-left-click_menu.png | Bin 0 -> 30200 bytes
.../Network_Configuration-NM-right-click_menu.png | Bin 0 -> 9311 bytes
..._Configuration-NM_applet-signal_strength_75.png | Bin 0 -> 2292 bytes
.../Deployment_Guide/images/PS2port.png | Bin 0 -> 574 bytes
.../Deployment_Guide/images/SCLogin.png | Bin 0 -> 8088 bytes
.../Deployment_Guide/images/SCLoginEnrollment.png | Bin 0 -> 14924 bytes
.../images/SELinux_Decision_Process.png | Bin 0 -> 15530 bytes
.../Deployment_Guide/images/Screenshot-1.png | Bin 0 -> 11434 bytes
.../Deployment_Guide/images/Screenshot-2.png | Bin 0 -> 15784 bytes
.../images/Users_Groups-Create_New_User.png | Bin 0 -> 123723 bytes
.../images/Users_Groups-User_Manager.png | Bin 0 -> 44516 bytes
.../images/apache-mod_ssl-genkey-01.png | Bin 0 -> 139602 bytes
.../images/apache-mod_ssl-genkey-02.png | Bin 0 -> 145185 bytes
.../images/apache-mod_ssl-genkey-03.png | Bin 0 -> 91440 bytes
.../images/apache-mod_ssl-genkey-04.png | Bin 0 -> 147106 bytes
.../images/apache-mod_ssl-genkey-05.png | Bin 0 -> 137555 bytes
.../images/apache-mod_ssl-genkey-06.png | Bin 0 -> 148690 bytes
.../images/apache-mod_ssl-genkey-07.png | Bin 0 -> 144241 bytes
.../Deployment_Guide/images/apol-DIF.png | Bin 0 -> 8924 bytes
.../images/apol-TE-rule-search.png | Bin 0 -> 8384 bytes
.../Deployment_Guide/images/apol-plain.png | Bin 0 -> 6980 bytes
.../html-single/Deployment_Guide/images/arrow.png | Bin 0 -> 117 bytes
.../Deployment_Guide/images/auth-panel.png | Bin 0 -> 9257 bytes
.../Deployment_Guide/images/authconfig-auth.png | Bin 0 -> 7034 bytes
.../Deployment_Guide/images/authconfig-options.png | Bin 0 -> 24477 bytes
.../images/authconfig-user-info.png | Bin 0 -> 27946 bytes
.../images/authconfig_LDAP_kerb.png | Bin 0 -> 52573 bytes
.../images/authconfig_advanced.png | Bin 0 -> 44688 bytes
.../images/authentication_configuration.png | Bin 0 -> 24892 bytes
.../Deployment_Guide/images/authicon.png | Bin 0 -> 1163 bytes
.../Deployment_Guide/images/bugworkflow_new4.png | Bin 0 -> 102130 bytes
.../Deployment_Guide/images/bugworkflow_old8.png | Bin 0 -> 102408 bytes
...ntrolling-access-to-services-authentication.png | Bin 0 -> 19489 bytes
.../controlling-access-to-services-ntsysv.png | Bin 0 -> 110269 bytes
...ng-access-to-services-service_configuration.png | Bin 0 -> 146999 bytes
...rolling-access-to-services-service_disabled.png | Bin 0 -> 864 bytes
...trolling-access-to-services-service_enabled.png | Bin 0 -> 912 bytes
...trolling-access-to-services-service_running.png | Bin 0 -> 707 bytes
...rolling-access-to-services-service_selected.png | Bin 0 -> 617 bytes
...trolling-access-to-services-service_stopped.png | Bin 0 -> 734 bytes
...trolling-access-to-services-service_unknown.png | Bin 0 -> 725 bytes
...ontrolling-access-to-services-service_wrong.png | Bin 0 -> 697 bytes
.../images/date-and-time-authentication.png | Bin 0 -> 15591 bytes
.../images/date-and-time-date_and_time.png | Bin 0 -> 165347 bytes
.../images/date-and-time-network_time_protocol.png | Bin 0 -> 173179 bytes
.../images/date-and-time-time_zone.png | Bin 0 -> 209964 bytes
.../Deployment_Guide/images/devicemngr.png | Bin 0 -> 12743 bytes
.../Deployment_Guide/images/display-dualhead.png | Bin 0 -> 28093 bytes
.../Deployment_Guide/images/display-hardware.png | Bin 0 -> 17525 bytes
.../Deployment_Guide/images/display-settings.png | Bin 0 -> 25249 bytes
.../Deployment_Guide/images/flask-arch.png | Bin 0 -> 4352 bytes
.../Deployment_Guide/images/flow-diagram.png | Bin 0 -> 29692 bytes
.../images/gnome-print-manager-list.png | Bin 0 -> 3998 bytes
.../images/gnome-print-manager.png | Bin 0 -> 7676 bytes
.../Deployment_Guide/images/gnome-print-queue.png | Bin 0 -> 7088 bytes
.../images/gnome-system-monitor-filesystems.png | Bin 0 -> 65650 bytes
.../images/gnome-system-monitor-memory.png | Bin 0 -> 139795 bytes
.../images/gnome-system-monitor-processes.png | Bin 0 -> 110184 bytes
.../Deployment_Guide/images/group-new.png | Bin 0 -> 20994 bytes
.../Deployment_Guide/images/group-properties.png | Bin 0 -> 50829 bytes
.../images/httpd-directories-add.png | Bin 0 -> 21244 bytes
.../Deployment_Guide/images/httpd-directories.png | Bin 0 -> 18407 bytes
.../Deployment_Guide/images/httpd-environment.png | Bin 0 -> 23538 bytes
.../images/httpd-general-options.png | Bin 0 -> 25484 bytes
.../Deployment_Guide/images/httpd-listen.png | Bin 0 -> 4524 bytes
.../Deployment_Guide/images/httpd-logging.png | Bin 0 -> 23846 bytes
.../Deployment_Guide/images/httpd-main.png | Bin 0 -> 12153 bytes
.../Deployment_Guide/images/httpd-server.png | Bin 0 -> 21350 bytes
.../Deployment_Guide/images/httpd-siteconfig.png | Bin 0 -> 28545 bytes
.../Deployment_Guide/images/httpd-tuning.png | Bin 0 -> 24496 bytes
.../images/httpd-virtualhosts-ssl.png | Bin 0 -> 26935 bytes
.../Deployment_Guide/images/httpd-virtualhosts.png | Bin 0 -> 9212 bytes
.../Deployment_Guide/images/hwbrowser.png | Bin 0 -> 20897 bytes
.../images/icon-greencheck-pkgs.png | Bin 0 -> 483 bytes
.../Deployment_Guide/images/icon-install-prep.png | Bin 0 -> 537 bytes
.../Deployment_Guide/images/icon-removal-prep.png | Bin 0 -> 425 bytes
.../Deployment_Guide/images/image_needed.png | Bin 0 -> 2477 bytes
.../Deployment_Guide/images/individual-pkgs.png | Bin 0 -> 13977 bytes
.../images/install-depend-prep.png | Bin 0 -> 14059 bytes
.../Deployment_Guide/images/install-prep.png | Bin 0 -> 12771 bytes
...p-kernel_dump_configuration-expert_settings.png | Bin 0 -> 103326 bytes
...ernel_dump_configuration-filtering_settings.png | Bin 0 -> 81998 bytes
...kernel_dump_configuration-not_enough_memory.png | Bin 0 -> 8602 bytes
...p-kernel_dump_configuration-target_settings.png | Bin 0 -> 82693 bytes
.../images/kdump-kernel_dump_configuration.png | Bin 0 -> 85823 bytes
.../keyboard-configuration-applet-addition.png | Bin 0 -> 18519 bytes
.../keyboard-configuration-applet-observation.png | Bin 0 -> 15341 bytes
.../keyboard-configuration-applet-selection.png | Bin 0 -> 115084 bytes
.../images/keyboard-configuration-break-take.png | Bin 0 -> 75595 bytes
.../images/keyboard-configuration-break.png | Bin 0 -> 171411 bytes
.../keyboard-configuration-layouts-default.png | Bin 0 -> 3446 bytes
.../images/keyboard-configuration-layouts-new.png | Bin 0 -> 29253 bytes
.../keyboard-configuration-layouts-prioritize.png | Bin 0 -> 5071 bytes
.../keyboard-configuration-layouts-separate.png | Bin 0 -> 6495 bytes
.../images/keyboard-configuration-layouts-test.png | Bin 0 -> 45470 bytes
.../images/keyboard-configuration-layouts.png | Bin 0 -> 154144 bytes
.../14/html-single/Deployment_Guide/images/lvg.png | Bin 0 -> 27939 bytes
.../Deployment_Guide/images/lvm-auto-config.png | Bin 0 -> 25658 bytes
.../Deployment_Guide/images/lvm-main1.png | Bin 0 -> 9761 bytes
.../Deployment_Guide/images/lvm-main10.png | Bin 0 -> 8497 bytes
.../Deployment_Guide/images/lvm-main12.png | Bin 0 -> 8161 bytes
.../Deployment_Guide/images/lvm-main13.png | Bin 0 -> 12158 bytes
.../Deployment_Guide/images/lvm-main14.png | Bin 0 -> 13559 bytes
.../Deployment_Guide/images/lvm-main15.png | Bin 0 -> 14775 bytes
.../Deployment_Guide/images/lvm-main16.png | Bin 0 -> 9029 bytes
.../Deployment_Guide/images/lvm-main17.png | Bin 0 -> 16327 bytes
.../Deployment_Guide/images/lvm-main18.png | Bin 0 -> 12662 bytes
.../Deployment_Guide/images/lvm-main2.png | Bin 0 -> 10383 bytes
.../Deployment_Guide/images/lvm-main21.png | Bin 0 -> 11896 bytes
.../Deployment_Guide/images/lvm-main23.png | Bin 0 -> 15371 bytes
.../Deployment_Guide/images/lvm-main26.png | Bin 0 -> 12412 bytes
.../Deployment_Guide/images/lvm-main27.png | Bin 0 -> 17553 bytes
.../Deployment_Guide/images/lvm-main28.png | Bin 0 -> 14745 bytes
.../Deployment_Guide/images/lvm-main3.png | Bin 0 -> 10968 bytes
.../Deployment_Guide/images/lvm-main30.png | Bin 0 -> 10820 bytes
.../Deployment_Guide/images/lvm-main31.png | Bin 0 -> 11317 bytes
.../Deployment_Guide/images/lvm-main32.png | Bin 0 -> 23900 bytes
.../Deployment_Guide/images/lvm-main33.png | Bin 0 -> 24557 bytes
.../Deployment_Guide/images/lvm-main34.png | Bin 0 -> 17170 bytes
.../Deployment_Guide/images/lvm-main36.png | Bin 0 -> 18375 bytes
.../Deployment_Guide/images/lvm-main7.png | Bin 0 -> 15207 bytes
.../Deployment_Guide/images/lvm-manual-boot.png | Bin 0 -> 16845 bytes
.../Deployment_Guide/images/lvm-manual-done.png | Bin 0 -> 23338 bytes
.../Deployment_Guide/images/lvm-manual-free.png | Bin 0 -> 22912 bytes
.../Deployment_Guide/images/lvm-manual-lv.png | Bin 0 -> 8151 bytes
.../Deployment_Guide/images/lvm-manual-lvdone.png | Bin 0 -> 19276 bytes
.../images/lvm-manual-postboot.png | Bin 0 -> 23466 bytes
.../Deployment_Guide/images/lvm-manual-pv01.png | Bin 0 -> 17835 bytes
.../Deployment_Guide/images/lvm-manual-pvdone.png | Bin 0 -> 23269 bytes
.../Deployment_Guide/images/lvm-manual-vg.png | Bin 0 -> 16031 bytes
.../Deployment_Guide/images/lvm/lvg.svg | 684 +
.../Deployment_Guide/images/lvm/lvols.svg | 286 +
.../html-single/Deployment_Guide/images/lvols.png | Bin 0 -> 18880 bytes
.../Deployment_Guide/images/mouseconfig.png | Bin 0 -> 14610 bytes
.../images/n-t-n-ipsec-diagram.png | Bin 0 -> 33470 bytes
.../Deployment_Guide/images/n-to-n-ipsec-local.png | Bin 0 -> 12987 bytes
.../images/n-to-n-ipsec-remote.png | Bin 0 -> 15159 bytes
.../Deployment_Guide/images/neat-aliases.png | Bin 0 -> 16584 bytes
.../Deployment_Guide/images/neat-dns.png | Bin 0 -> 19916 bytes
.../images/neat-ethernet-settings.png | Bin 0 -> 21296 bytes
.../Deployment_Guide/images/neat-ethernet.png | Bin 0 -> 14810 bytes
.../Deployment_Guide/images/neat-home-profile.png | Bin 0 -> 17085 bytes
.../Deployment_Guide/images/neat-hosts.png | Bin 0 -> 14239 bytes
.../Deployment_Guide/images/neat-isdn-settings.png | Bin 0 -> 14132 bytes
.../Deployment_Guide/images/neat-isdn.png | Bin 0 -> 18341 bytes
.../images/neat-modem-settings.png | Bin 0 -> 14411 bytes
.../Deployment_Guide/images/neat-modem.png | Bin 0 -> 18513 bytes
.../images/neat-office-profile.png | Bin 0 -> 17939 bytes
.../images/neat-tokenring-settings.png | Bin 0 -> 13866 bytes
.../Deployment_Guide/images/neat-tokenring.png | Bin 0 -> 18540 bytes
.../Deployment_Guide/images/neat-tonline1.png | Bin 0 -> 9220 bytes
.../images/neat-tonlineAcctsetup.png | Bin 0 -> 15775 bytes
.../images/neat-tonlineProvidertab.png | Bin 0 -> 16620 bytes
.../images/neat-wireless-settings.png | Bin 0 -> 11287 bytes
.../Deployment_Guide/images/neat-wireless.png | Bin 0 -> 18246 bytes
.../images/neat-xdsl-selectdevicetype.png | Bin 0 -> 9044 bytes
.../Deployment_Guide/images/neat-xdsl-settings.png | Bin 0 -> 24033 bytes
.../Deployment_Guide/images/neat-xdsl.png | Bin 0 -> 18410 bytes
.../html-single/Deployment_Guide/images/neat.png | Bin 0 -> 19286 bytes
.../Deployment_Guide/images/nfs-add.png | Bin 0 -> 7087 bytes
.../images/nfs-general-options.png | Bin 0 -> 19847 bytes
.../images/nfs-server-settings.png | Bin 0 -> 14176 bytes
.../Deployment_Guide/images/nfs-user-access.png | Bin 0 -> 13845 bytes
.../Deployment_Guide/images/oprof-start-config.png | Bin 0 -> 8206 bytes
.../Deployment_Guide/images/oprof-start-setup.png | Bin 0 -> 13238 bytes
...raphical_Package_Management-software_update.xcf | Bin 0 -> 223150 bytes
.../Deployment_Guide/images/package-selections.png | Bin 0 -> 26001 bytes
.../Deployment_Guide/images/pam-icon.png | Bin 0 -> 1515 bytes
.../Deployment_Guide/images/print-manager-menu.png | Bin 0 -> 12069 bytes
.../images/printconf-add-printer.png | Bin 0 -> 17231 bytes
.../Deployment_Guide/images/printconf-config1.png | Bin 0 -> 14695 bytes
.../Deployment_Guide/images/printconf-config2.png | Bin 0 -> 10585 bytes
.../Deployment_Guide/images/printconf-config3.png | Bin 0 -> 11450 bytes
.../Deployment_Guide/images/printconf-config4.png | Bin 0 -> 12218 bytes
.../Deployment_Guide/images/printconf-config5.png | Bin 0 -> 11020 bytes
.../images/printconf-default-icon.png | Bin 0 -> 210 bytes
.../Deployment_Guide/images/printconf-edit.png | Bin 0 -> 13674 bytes
.../Deployment_Guide/images/printconf-ipp.png | Bin 0 -> 19642 bytes
.../images/printconf-jetdirect.png | Bin 0 -> 20083 bytes
.../Deployment_Guide/images/printconf-local.png | Bin 0 -> 21888 bytes
.../Deployment_Guide/images/printconf-lpd.png | Bin 0 -> 9083 bytes
.../Deployment_Guide/images/printconf-main.png | Bin 0 -> 19412 bytes
.../Deployment_Guide/images/printconf-ncp.png | Bin 0 -> 10463 bytes
.../images/printconf-queue-name.png | Bin 0 -> 11538 bytes
.../images/printconf-select-model.png | Bin 0 -> 18461 bytes
.../images/printconf-sharing-general.png | Bin 0 -> 6501 bytes
.../images/printconf-sharing-hosts.png | Bin 0 -> 8209 bytes
.../images/printconf-sharing-queue.png | Bin 0 -> 7478 bytes
.../Deployment_Guide/images/printconf-smb.png | Bin 0 -> 29262 bytes
.../images/printconf-test-page.png | Bin 0 -> 16481 bytes
.../images/printer-notification-icon.png | Bin 0 -> 15022 bytes
.../images/raid-manual-boot-error.png | Bin 0 -> 4714 bytes
.../Deployment_Guide/images/raid-manual-final.png | Bin 0 -> 24250 bytes
.../Deployment_Guide/images/raid-manual-free.png | Bin 0 -> 22912 bytes
.../images/raid-manual-lvm-final.png | Bin 0 -> 24916 bytes
.../Deployment_Guide/images/raid-manual-mntpt.png | Bin 0 -> 10266 bytes
.../images/raid-manual-part-add.png | Bin 0 -> 17771 bytes
.../images/raid-manual-part-bootready.png | Bin 0 -> 23946 bytes
.../images/raid-manual-part-opt.png | Bin 0 -> 21060 bytes
.../images/raid-manual-part-opt2.png | Bin 0 -> 16558 bytes
.../images/redhat-config-packages.png | Bin 0 -> 10457 bytes
.../images/redhat-config-users.png | Bin 0 -> 17101 bytes
.../images/redhat-filter-enable.png | Bin 0 -> 194249 bytes
.../images/redhat-filter-sample.png | Bin 0 -> 16132 bytes
.../Deployment_Guide/images/redhat-filters.png | Bin 0 -> 9495 bytes
.../images/redhat-logviewer-add.png | Bin 0 -> 147036 bytes
.../images/redhat-logviewer-monitoring.png | Bin 0 -> 159116 bytes
.../Deployment_Guide/images/redhat-logviewer.png | Bin 0 -> 166037 bytes
.../images/redhat-optional-packages.png | Bin 0 -> 14208 bytes
.../Deployment_Guide/images/registering.png | Bin 0 -> 25879 bytes
.../Deployment_Guide/images/relevant-errata.png | Bin 0 -> 25777 bytes
.../Deployment_Guide/images/removal-prep.png | Bin 0 -> 14152 bytes
.../Deployment_Guide/images/remove-depend-prep.png | Bin 0 -> 14088 bytes
.../Deployment_Guide/images/rh-securitylevel.png | Bin 0 -> 17203 bytes
.../networkconfig/n-t-n-ipsec-diagram.svg | 658 +
.../Deployment_Guide/images/s-c-samba-basic.png | Bin 0 -> 3358 bytes
.../images/s-c-samba-create-share.png | Bin 0 -> 7734 bytes
.../Deployment_Guide/images/s-c-samba-security.png | Bin 0 -> 9223 bytes
.../Deployment_Guide/images/s-c-samba-users.png | Bin 0 -> 2275 bytes
.../Deployment_Guide/images/s-c-samba.png | Bin 0 -> 22881 bytes
.../images/samba-nautilus-machines.png | Bin 0 -> 17926 bytes
.../Deployment_Guide/images/samba-nautilus.png | Bin 0 -> 19767 bytes
.../images/seaudit-Edit-filter.png | Bin 0 -> 12933 bytes
.../images/seaudit-Query-policy.png | Bin 0 -> 21946 bytes
.../seaudit-Select-target-type-filtering.png | Bin 0 -> 12826 bytes
.../images/seaudit-View-filtering.png | Bin 0 -> 13075 bytes
.../Deployment_Guide/images/seaudit-plain.png | Bin 0 -> 12414 bytes
.../images/sec-ipsec-host2host.png | Bin 0 -> 16970 bytes
.../images/security-intro-to-mls.png | Bin 0 -> 19654 bytes
.../images/security-mls-data-flow.png | Bin 0 -> 14986 bytes
.../Deployment_Guide/images/serialport.png | Bin 0 -> 752 bytes
.../Deployment_Guide/images/serv-config.png | Bin 0 -> 23731 bytes
.../images/ssh-passphrase-prompt.png | Bin 0 -> 13186 bytes
.../images/ssh-startup-applications-add.png | Bin 0 -> 14508 bytes
.../images/ssh-startup-applications-check.png | Bin 0 -> 148890 bytes
.../images/ssh-startup-applications.png | Bin 0 -> 146484 bytes
.../Deployment_Guide/images/switchmail-gui.png | Bin 0 -> 14414 bytes
.../Deployment_Guide/images/system-config-nfs.png | Bin 0 -> 12666 bytes
.../Deployment_Guide/images/tcp_wrap_diagram.png | Bin 0 -> 25775 bytes
.../Deployment_Guide/images/usbport.png | Bin 0 -> 277 bytes
.../Deployment_Guide/images/user-new.png | Bin 0 -> 15984 bytes
.../Deployment_Guide/images/user-properties.png | Bin 0 -> 70120 bytes
.../Deployment_Guide/images/user_pass_groups.png | Bin 0 -> 5635 bytes
.../Deployment_Guide/images/user_pass_info.png | Bin 0 -> 45963 bytes
.../Deployment_Guide/images/your-rhn.png | Bin 0 -> 20572 bytes
.../14/html-single/Deployment_Guide/index.html |13155 ++++++++++++++++++++
.../14/html/Deployment_Guide/Acknowledgements.html | 14 +
.../Deployment_Guide/Common_Content/css/common.css | 1474 +++
.../Common_Content/css/default.css | 3 +
.../Deployment_Guide/Common_Content/css/lang.css | 2 +
.../Common_Content/css/overrides.css | 51 +
.../Deployment_Guide/Common_Content/css/print.css | 16 +
.../Deployment_Guide/Common_Content/images/1.png | Bin 0 -> 710 bytes
.../Deployment_Guide/Common_Content/images/1.svg | 27 +
.../Deployment_Guide/Common_Content/images/10.png | Bin 0 -> 985 bytes
.../Deployment_Guide/Common_Content/images/10.svg | 31 +
.../Deployment_Guide/Common_Content/images/11.png | Bin 0 -> 810 bytes
.../Deployment_Guide/Common_Content/images/11.svg | 31 +
.../Deployment_Guide/Common_Content/images/12.png | Bin 0 -> 1012 bytes
.../Deployment_Guide/Common_Content/images/12.svg | 31 +
.../Deployment_Guide/Common_Content/images/13.png | Bin 0 -> 1048 bytes
.../Deployment_Guide/Common_Content/images/13.svg | 31 +
.../Deployment_Guide/Common_Content/images/14.png | Bin 0 -> 914 bytes
.../Deployment_Guide/Common_Content/images/14.svg | 31 +
.../Deployment_Guide/Common_Content/images/15.png | Bin 0 -> 989 bytes
.../Deployment_Guide/Common_Content/images/15.svg | 31 +
.../Deployment_Guide/Common_Content/images/16.png | Bin 0 -> 1047 bytes
.../Deployment_Guide/Common_Content/images/16.svg | 31 +
.../Deployment_Guide/Common_Content/images/17.png | Bin 0 -> 888 bytes
.../Deployment_Guide/Common_Content/images/17.svg | 31 +
.../Deployment_Guide/Common_Content/images/18.png | Bin 0 -> 1075 bytes
.../Deployment_Guide/Common_Content/images/18.svg | 31 +
.../Deployment_Guide/Common_Content/images/19.png | Bin 0 -> 1049 bytes
.../Deployment_Guide/Common_Content/images/19.svg | 31 +
.../Deployment_Guide/Common_Content/images/2.png | Bin 0 -> 896 bytes
.../Deployment_Guide/Common_Content/images/2.svg | 27 +
.../Deployment_Guide/Common_Content/images/20.png | Bin 0 -> 1151 bytes
.../Deployment_Guide/Common_Content/images/20.svg | 31 +
.../Deployment_Guide/Common_Content/images/21.png | Bin 0 -> 994 bytes
.../Deployment_Guide/Common_Content/images/21.svg | 31 +
.../Deployment_Guide/Common_Content/images/22.png | Bin 0 -> 1162 bytes
.../Deployment_Guide/Common_Content/images/22.svg | 31 +
.../Deployment_Guide/Common_Content/images/23.png | Bin 0 -> 1207 bytes
.../Deployment_Guide/Common_Content/images/23.svg | 31 +
.../Deployment_Guide/Common_Content/images/24.png | Bin 0 -> 1081 bytes
.../Deployment_Guide/Common_Content/images/24.svg | 31 +
.../Deployment_Guide/Common_Content/images/25.png | Bin 0 -> 1173 bytes
.../Deployment_Guide/Common_Content/images/25.svg | 31 +
.../Deployment_Guide/Common_Content/images/26.png | Bin 0 -> 1208 bytes
.../Deployment_Guide/Common_Content/images/26.svg | 31 +
.../Deployment_Guide/Common_Content/images/27.png | Bin 0 -> 1080 bytes
.../Deployment_Guide/Common_Content/images/27.svg | 31 +
.../Deployment_Guide/Common_Content/images/28.png | Bin 0 -> 1225 bytes
.../Deployment_Guide/Common_Content/images/28.svg | 31 +
.../Deployment_Guide/Common_Content/images/29.png | Bin 0 -> 1196 bytes
.../Deployment_Guide/Common_Content/images/29.svg | 31 +
.../Deployment_Guide/Common_Content/images/3.png | Bin 0 -> 958 bytes
.../Deployment_Guide/Common_Content/images/3.svg | 27 +
.../Deployment_Guide/Common_Content/images/30.png | Bin 0 -> 1250 bytes
.../Deployment_Guide/Common_Content/images/30.svg | 31 +
.../Deployment_Guide/Common_Content/images/31.png | Bin 0 -> 1078 bytes
.../Deployment_Guide/Common_Content/images/31.svg | 31 +
.../Deployment_Guide/Common_Content/images/32.png | Bin 0 -> 1241 bytes
.../Deployment_Guide/Common_Content/images/32.svg | 31 +
.../Deployment_Guide/Common_Content/images/33.png | Bin 0 -> 1268 bytes
.../Deployment_Guide/Common_Content/images/33.svg | 31 +
.../Deployment_Guide/Common_Content/images/34.png | Bin 0 -> 1175 bytes
.../Deployment_Guide/Common_Content/images/34.svg | 31 +
.../Deployment_Guide/Common_Content/images/35.png | Bin 0 -> 1224 bytes
.../Deployment_Guide/Common_Content/images/35.svg | 31 +
.../Deployment_Guide/Common_Content/images/36.png | Bin 0 -> 1281 bytes
.../Deployment_Guide/Common_Content/images/36.svg | 31 +
.../Deployment_Guide/Common_Content/images/37.png | Bin 0 -> 1140 bytes
.../Deployment_Guide/Common_Content/images/37.svg | 31 +
.../Deployment_Guide/Common_Content/images/38.png | Bin 0 -> 1300 bytes
.../Deployment_Guide/Common_Content/images/38.svg | 31 +
.../Deployment_Guide/Common_Content/images/39.png | Bin 0 -> 1294 bytes
.../Deployment_Guide/Common_Content/images/39.svg | 31 +
.../Deployment_Guide/Common_Content/images/4.png | Bin 0 -> 849 bytes
.../Deployment_Guide/Common_Content/images/4.svg | 27 +
.../Deployment_Guide/Common_Content/images/40.png | Bin 0 -> 1130 bytes
.../Deployment_Guide/Common_Content/images/40.svg | 31 +
.../Deployment_Guide/Common_Content/images/5.png | Bin 0 -> 900 bytes
.../Deployment_Guide/Common_Content/images/5.svg | 27 +
.../Deployment_Guide/Common_Content/images/6.png | Bin 0 -> 929 bytes
.../Deployment_Guide/Common_Content/images/6.svg | 27 +
.../Deployment_Guide/Common_Content/images/7.png | Bin 0 -> 807 bytes
.../Deployment_Guide/Common_Content/images/7.svg | 27 +
.../Deployment_Guide/Common_Content/images/8.png | Bin 0 -> 962 bytes
.../Deployment_Guide/Common_Content/images/8.svg | 27 +
.../Deployment_Guide/Common_Content/images/9.png | Bin 0 -> 936 bytes
.../Deployment_Guide/Common_Content/images/9.svg | 27 +
.../Common_Content/images/bkgrnd_greydots.png | Bin 0 -> 157 bytes
.../Common_Content/images/bullet_arrowblue.png | Bin 0 -> 177 bytes
.../Common_Content/images/documentation.png | Bin 0 -> 623 bytes
.../Deployment_Guide/Common_Content/images/dot.png | Bin 0 -> 98 bytes
.../Common_Content/images/dot2.png | Bin 0 -> 98 bytes
.../Common_Content/images/green.png | Bin 0 -> 176 bytes
.../Common_Content/images/h1-bg.png | Bin 0 -> 565 bytes
.../Common_Content/images/image_left.png | Bin 0 -> 1114 bytes
.../Common_Content/images/image_right.png | Bin 0 -> 2260 bytes
.../Common_Content/images/important.png | Bin 0 -> 2080 bytes
.../Common_Content/images/important.svg | 106 +
.../Common_Content/images/logo.png | Bin 0 -> 1114 bytes
.../Common_Content/images/note.png | Bin 0 -> 1241 bytes
.../Common_Content/images/note.svg | 111 +
.../Deployment_Guide/Common_Content/images/red.png | Bin 0 -> 163 bytes
.../Common_Content/images/shade.png | Bin 0 -> 101 bytes
.../Common_Content/images/shine.png | Bin 0 -> 146 bytes
.../Common_Content/images/stock-go-back.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-forward.png | Bin 0 -> 828 bytes
.../Common_Content/images/stock-go-up.png | Bin 0 -> 760 bytes
.../Common_Content/images/stock-home.png | Bin 0 -> 808 bytes
.../Common_Content/images/title_logo.png | Bin 0 -> 13399 bytes
.../Common_Content/images/title_logo.svg | 61 +
.../Common_Content/images/warning.png | Bin 0 -> 1340 bytes
.../Common_Content/images/warning.svg | 89 +
.../Common_Content/images/watermark-draft.png | Bin 0 -> 25365 bytes
.../Common_Content/images/yellow.png | Bin 0 -> 175 bytes
.../14/html/Deployment_Guide/Users_and_Groups.html | 80 +
.../14/html/Deployment_Guide/abrt-plugins.html | 24 +
.../Deployment_Guide/app-Revision_History.html | 19 +
.../ch-Authentication_Configuration.html | 424 +
.../html/Deployment_Guide/ch-Automated_Tasks.html | 151 +
.../ch-Controlling_Access_to_Services.html | 64 +
...h-Dynamic_Host_Configuration_Protocol_DHCP.html | 16 +
.../ch-Gathering_System_Information.html | 121 +
...ackage_Management-sec-Additional_Resources.html | 16 +
.../ch-Keyboard_Configuration.html | 38 +
.../14/html/Deployment_Guide/ch-Log_Files.html | 146 +
.../ch-Manually_Upgrading_the_Kernel.html | 42 +
.../Deployment_Guide/ch-Network_Configuration.html | 29 +
.../Deployment_Guide/ch-Network_Interfaces.html | 40 +
.../14/html/Deployment_Guide/ch-OpenSSH.html | 96 +
.../14/html/Deployment_Guide/ch-PackageKit.html | 51 +
.../Fedora/14/html/Deployment_Guide/ch-RPM.html | 54 +
.../ch-The_Apache_HTTP_Server.html | 54 +
.../Deployment_Guide/ch-The_BIND_DNS_Server.html | 40 +
.../ch-The_sysconfig_Directory.html | 332 +
.../ch-Working_with_Kernel_Modules.html | 81 +
.../Fedora/14/html/Deployment_Guide/ch-abrt.html | 32 +
.../Fedora/14/html/Deployment_Guide/ch-email.html | 103 +
.../Fedora/14/html/Deployment_Guide/ch-intro.html | 40 +
.../Fedora/14/html/Deployment_Guide/ch-kdump.html | 197 +
.../Fedora/14/html/Deployment_Guide/ch-proc.html | 65 +
.../Fedora/14/html/Deployment_Guide/ch-yum.html | 102 +
.../14/html/Deployment_Guide/ch06s02s03.html | 39 +
.../Fedora/14/html/Deployment_Guide/ch21s02.html | 34 +
.../Fedora/14/html/Deployment_Guide/ch21s05.html | 32 +
.../14/html/Deployment_Guide/ch21s05s02.html | 23 +
.../14/html/Deployment_Guide/ch21s05s03.html | 14 +
.../chap-Date_and_Time_Configuration.html | 52 +
.../chap-SSSD_User_Guide-Configuring_Domains.html | 269 +
.../chap-SSSD_User_Guide-Configuring_Services.html | 74 +
.../chap-SSSD_User_Guide-Introduction.html | 18 +
.../chap-SSSD_User_Guide-Setting_Up_SSSD.html | 185 +
.../chap-SSSD_User_Guide-Troubleshooting.html | 122 +
.../configuring-centralized-crash-collection.html | 68 +
.../configuring-plugins-in-the-gui.html | 70 +
.../14/html/Deployment_Guide/configuring.html | 52 +
.../14/html/Deployment_Guide/dhcp-relay-agent.html | 18 +
.../Deployment_Guide/generating-backtrace.html | 84 +
.../Deployment_Guide/images/ABRT-Main_Window.png | Bin 0 -> 62743 bytes
.../images/ABRT-Notification_Area_alarm_icon.png | Bin 0 -> 1187 bytes
.../html/Deployment_Guide/images/ABRT-plugins.png | Bin 0 -> 72790 bytes
...ion_Configuration-authconfig-Authentication.png | Bin 0 -> 37767 bytes
...entication_Configuration-authconfig-Options.png | Bin 0 -> 30139 bytes
...tion_Configuration-authconfig-SSSD_Settings.png | Bin 0 -> 22607 bytes
...n_Configuration-authconfig-User_Information.png | Bin 0 -> 31426 bytes
.../images/Change_Runtime_Boolean.png | Bin 0 -> 29894 bytes
.../images/FirefoxWithKerberosSSO.png | Bin 0 -> 25826 bytes
...ical_Package_Management-Software_Log_Viewer.png | Bin 0 -> 160350 bytes
...kage_Management-Software_Update_Preferences.png | Bin 0 -> 19454 bytes
...ical_Package_Management-add_remove_software.png | Bin 0 -> 37858 bytes
...hical_Package_Management-additional_updates.png | Bin 0 -> 54900 bytes
.../Graphical_Package_Management-authenticate.png | Bin 0 -> 19596 bytes
...l_Package_Management-filters-only_available.png | Bin 0 -> 32640 bytes
...al_Package_Management-filters-only_end_user.png | Bin 0 -> 32876 bytes
.../images/Graphical_Package_Management-htop.png | Bin 0 -> 58033 bytes
.../Graphical_Package_Management-install.png | Bin 0 -> 55559 bytes
...ckage_Management-installing_a_package_group.png | Bin 0 -> 85446 bytes
...ical_Package_Management-removal_in_progress.png | Bin 0 -> 79297 bytes
.../images/Graphical_Package_Management-remove.png | Bin 0 -> 66023 bytes
...hical_Package_Management-removing_a_package.png | Bin 0 -> 49512 bytes
...raphical_Package_Management-software_update.png | Bin 0 -> 74684 bytes
...phical_Package_Management-updates_available.png | Bin 0 -> 17792 bytes
.../Deployment_Guide/images/Load_New_Policy.png | Bin 0 -> 19739 bytes
.../Network_Configuration-NM-All_applet_states.png | Bin 0 -> 11378 bytes
...ork_Configuration-NM-Available_to_all_users.png | Bin 0 -> 4464 bytes
...work_Configuration-NM-Connect_automatically.png | Bin 0 -> 19915 bytes
...iguration-NM-Edit_System_eth0-IPv4_Settings.png | Bin 0 -> 33802 bytes
...ork_Configuration-NM-Edit_System_eth0-Wired.png | Bin 0 -> 21595 bytes
...Configuration-NM-Editing_Wired_Connection_1.png | Bin 0 -> 56373 bytes
...figuration-NM-Editing_Wireless_Connection_1.png | Bin 0 -> 76055 bytes
...rk_Configuration-NM-IPv4_Settings-Addresses.png | Bin 0 -> 9790 bytes
...nfiguration-NM-IPv4_Settings-DHCP_Client_ID.png | Bin 0 -> 1829 bytes
..._Configuration-NM-IPv4_Settings-DNS_Servers.png | Bin 0 -> 2573 bytes
...twork_Configuration-NM-IPv4_Settings-Method.png | Bin 0 -> 2816 bytes
...twork_Configuration-NM-IPv4_Settings-Routes.png | Bin 0 -> 1557 bytes
...nfiguration-NM-IPv4_Settings-Search_domains.png | Bin 0 -> 3152 bytes
.../Network_Configuration-NM-IPv4_Settings.png | Bin 0 -> 25414 bytes
...etwork_Configuration-NM-Network_Connections.png | Bin 0 -> 19394 bytes
...Network_Configuration-NM-System_eth0-Routes.png | Bin 0 -> 13495 bytes
...iguration-NM-Wireless_Auto_Connections_List.png | Bin 0 -> 83527 bytes
...uration-NM-Wireless_authentication_required.png | Bin 0 -> 70411 bytes
.../Network_Configuration-NM-applet_states.png | Bin 0 -> 2912 bytes
.../Network_Configuration-NM-left-click_menu.png | Bin 0 -> 30200 bytes
.../Network_Configuration-NM-right-click_menu.png | Bin 0 -> 9311 bytes
..._Configuration-NM_applet-signal_strength_75.png | Bin 0 -> 2292 bytes
.../14/html/Deployment_Guide/images/PS2port.png | Bin 0 -> 574 bytes
.../14/html/Deployment_Guide/images/SCLogin.png | Bin 0 -> 8088 bytes
.../Deployment_Guide/images/SCLoginEnrollment.png | Bin 0 -> 14924 bytes
.../images/SELinux_Decision_Process.png | Bin 0 -> 15530 bytes
.../html/Deployment_Guide/images/Screenshot-1.png | Bin 0 -> 11434 bytes
.../html/Deployment_Guide/images/Screenshot-2.png | Bin 0 -> 15784 bytes
.../images/Users_Groups-Create_New_User.png | Bin 0 -> 123723 bytes
.../images/Users_Groups-User_Manager.png | Bin 0 -> 44516 bytes
.../images/apache-mod_ssl-genkey-01.png | Bin 0 -> 139602 bytes
.../images/apache-mod_ssl-genkey-02.png | Bin 0 -> 145185 bytes
.../images/apache-mod_ssl-genkey-03.png | Bin 0 -> 91440 bytes
.../images/apache-mod_ssl-genkey-04.png | Bin 0 -> 147106 bytes
.../images/apache-mod_ssl-genkey-05.png | Bin 0 -> 137555 bytes
.../images/apache-mod_ssl-genkey-06.png | Bin 0 -> 148690 bytes
.../images/apache-mod_ssl-genkey-07.png | Bin 0 -> 144241 bytes
.../14/html/Deployment_Guide/images/apol-DIF.png | Bin 0 -> 8924 bytes
.../images/apol-TE-rule-search.png | Bin 0 -> 8384 bytes
.../14/html/Deployment_Guide/images/apol-plain.png | Bin 0 -> 6980 bytes
.../14/html/Deployment_Guide/images/arrow.png | Bin 0 -> 117 bytes
.../14/html/Deployment_Guide/images/auth-panel.png | Bin 0 -> 9257 bytes
.../Deployment_Guide/images/authconfig-auth.png | Bin 0 -> 7034 bytes
.../Deployment_Guide/images/authconfig-options.png | Bin 0 -> 24477 bytes
.../images/authconfig-user-info.png | Bin 0 -> 27946 bytes
.../images/authconfig_LDAP_kerb.png | Bin 0 -> 52573 bytes
.../images/authconfig_advanced.png | Bin 0 -> 44688 bytes
.../images/authentication_configuration.png | Bin 0 -> 24892 bytes
.../14/html/Deployment_Guide/images/authicon.png | Bin 0 -> 1163 bytes
.../Deployment_Guide/images/bugworkflow_new4.png | Bin 0 -> 102130 bytes
.../Deployment_Guide/images/bugworkflow_old8.png | Bin 0 -> 102408 bytes
...ntrolling-access-to-services-authentication.png | Bin 0 -> 19489 bytes
.../controlling-access-to-services-ntsysv.png | Bin 0 -> 110269 bytes
...ng-access-to-services-service_configuration.png | Bin 0 -> 146999 bytes
...rolling-access-to-services-service_disabled.png | Bin 0 -> 864 bytes
...trolling-access-to-services-service_enabled.png | Bin 0 -> 912 bytes
...trolling-access-to-services-service_running.png | Bin 0 -> 707 bytes
...rolling-access-to-services-service_selected.png | Bin 0 -> 617 bytes
...trolling-access-to-services-service_stopped.png | Bin 0 -> 734 bytes
...trolling-access-to-services-service_unknown.png | Bin 0 -> 725 bytes
...ontrolling-access-to-services-service_wrong.png | Bin 0 -> 697 bytes
.../images/date-and-time-authentication.png | Bin 0 -> 15591 bytes
.../images/date-and-time-date_and_time.png | Bin 0 -> 165347 bytes
.../images/date-and-time-network_time_protocol.png | Bin 0 -> 173179 bytes
.../images/date-and-time-time_zone.png | Bin 0 -> 209964 bytes
.../14/html/Deployment_Guide/images/devicemngr.png | Bin 0 -> 12743 bytes
.../Deployment_Guide/images/display-dualhead.png | Bin 0 -> 28093 bytes
.../Deployment_Guide/images/display-hardware.png | Bin 0 -> 17525 bytes
.../Deployment_Guide/images/display-settings.png | Bin 0 -> 25249 bytes
.../14/html/Deployment_Guide/images/flask-arch.png | Bin 0 -> 4352 bytes
.../html/Deployment_Guide/images/flow-diagram.png | Bin 0 -> 29692 bytes
.../images/gnome-print-manager-list.png | Bin 0 -> 3998 bytes
.../images/gnome-print-manager.png | Bin 0 -> 7676 bytes
.../Deployment_Guide/images/gnome-print-queue.png | Bin 0 -> 7088 bytes
.../images/gnome-system-monitor-filesystems.png | Bin 0 -> 65650 bytes
.../images/gnome-system-monitor-memory.png | Bin 0 -> 139795 bytes
.../images/gnome-system-monitor-processes.png | Bin 0 -> 110184 bytes
.../14/html/Deployment_Guide/images/group-new.png | Bin 0 -> 20994 bytes
.../Deployment_Guide/images/group-properties.png | Bin 0 -> 50829 bytes
.../images/httpd-directories-add.png | Bin 0 -> 21244 bytes
.../Deployment_Guide/images/httpd-directories.png | Bin 0 -> 18407 bytes
.../Deployment_Guide/images/httpd-environment.png | Bin 0 -> 23538 bytes
.../images/httpd-general-options.png | Bin 0 -> 25484 bytes
.../html/Deployment_Guide/images/httpd-listen.png | Bin 0 -> 4524 bytes
.../html/Deployment_Guide/images/httpd-logging.png | Bin 0 -> 23846 bytes
.../14/html/Deployment_Guide/images/httpd-main.png | Bin 0 -> 12153 bytes
.../html/Deployment_Guide/images/httpd-server.png | Bin 0 -> 21350 bytes
.../Deployment_Guide/images/httpd-siteconfig.png | Bin 0 -> 28545 bytes
.../html/Deployment_Guide/images/httpd-tuning.png | Bin 0 -> 24496 bytes
.../images/httpd-virtualhosts-ssl.png | Bin 0 -> 26935 bytes
.../Deployment_Guide/images/httpd-virtualhosts.png | Bin 0 -> 9212 bytes
.../14/html/Deployment_Guide/images/hwbrowser.png | Bin 0 -> 20897 bytes
.../images/icon-greencheck-pkgs.png | Bin 0 -> 483 bytes
.../Deployment_Guide/images/icon-install-prep.png | Bin 0 -> 537 bytes
.../Deployment_Guide/images/icon-removal-prep.png | Bin 0 -> 425 bytes
.../html/Deployment_Guide/images/image_needed.png | Bin 0 -> 2477 bytes
.../Deployment_Guide/images/individual-pkgs.png | Bin 0 -> 13977 bytes
.../images/install-depend-prep.png | Bin 0 -> 14059 bytes
.../html/Deployment_Guide/images/install-prep.png | Bin 0 -> 12771 bytes
...p-kernel_dump_configuration-expert_settings.png | Bin 0 -> 103326 bytes
...ernel_dump_configuration-filtering_settings.png | Bin 0 -> 81998 bytes
...kernel_dump_configuration-not_enough_memory.png | Bin 0 -> 8602 bytes
...p-kernel_dump_configuration-target_settings.png | Bin 0 -> 82693 bytes
.../images/kdump-kernel_dump_configuration.png | Bin 0 -> 85823 bytes
.../keyboard-configuration-applet-addition.png | Bin 0 -> 18519 bytes
.../keyboard-configuration-applet-observation.png | Bin 0 -> 15341 bytes
.../keyboard-configuration-applet-selection.png | Bin 0 -> 115084 bytes
.../images/keyboard-configuration-break-take.png | Bin 0 -> 75595 bytes
.../images/keyboard-configuration-break.png | Bin 0 -> 171411 bytes
.../keyboard-configuration-layouts-default.png | Bin 0 -> 3446 bytes
.../images/keyboard-configuration-layouts-new.png | Bin 0 -> 29253 bytes
.../keyboard-configuration-layouts-prioritize.png | Bin 0 -> 5071 bytes
.../keyboard-configuration-layouts-separate.png | Bin 0 -> 6495 bytes
.../images/keyboard-configuration-layouts-test.png | Bin 0 -> 45470 bytes
.../images/keyboard-configuration-layouts.png | Bin 0 -> 154144 bytes
.../Fedora/14/html/Deployment_Guide/images/lvg.png | Bin 0 -> 27939 bytes
.../Deployment_Guide/images/lvm-auto-config.png | Bin 0 -> 25658 bytes
.../14/html/Deployment_Guide/images/lvm-main1.png | Bin 0 -> 9761 bytes
.../14/html/Deployment_Guide/images/lvm-main10.png | Bin 0 -> 8497 bytes
.../14/html/Deployment_Guide/images/lvm-main12.png | Bin 0 -> 8161 bytes
.../14/html/Deployment_Guide/images/lvm-main13.png | Bin 0 -> 12158 bytes
.../14/html/Deployment_Guide/images/lvm-main14.png | Bin 0 -> 13559 bytes
.../14/html/Deployment_Guide/images/lvm-main15.png | Bin 0 -> 14775 bytes
.../14/html/Deployment_Guide/images/lvm-main16.png | Bin 0 -> 9029 bytes
.../14/html/Deployment_Guide/images/lvm-main17.png | Bin 0 -> 16327 bytes
.../14/html/Deployment_Guide/images/lvm-main18.png | Bin 0 -> 12662 bytes
.../14/html/Deployment_Guide/images/lvm-main2.png | Bin 0 -> 10383 bytes
.../14/html/Deployment_Guide/images/lvm-main21.png | Bin 0 -> 11896 bytes
.../14/html/Deployment_Guide/images/lvm-main23.png | Bin 0 -> 15371 bytes
.../14/html/Deployment_Guide/images/lvm-main26.png | Bin 0 -> 12412 bytes
.../14/html/Deployment_Guide/images/lvm-main27.png | Bin 0 -> 17553 bytes
.../14/html/Deployment_Guide/images/lvm-main28.png | Bin 0 -> 14745 bytes
.../14/html/Deployment_Guide/images/lvm-main3.png | Bin 0 -> 10968 bytes
.../14/html/Deployment_Guide/images/lvm-main30.png | Bin 0 -> 10820 bytes
.../14/html/Deployment_Guide/images/lvm-main31.png | Bin 0 -> 11317 bytes
.../14/html/Deployment_Guide/images/lvm-main32.png | Bin 0 -> 23900 bytes
.../14/html/Deployment_Guide/images/lvm-main33.png | Bin 0 -> 24557 bytes
.../14/html/Deployment_Guide/images/lvm-main34.png | Bin 0 -> 17170 bytes
.../14/html/Deployment_Guide/images/lvm-main36.png | Bin 0 -> 18375 bytes
.../14/html/Deployment_Guide/images/lvm-main7.png | Bin 0 -> 15207 bytes
.../Deployment_Guide/images/lvm-manual-boot.png | Bin 0 -> 16845 bytes
.../Deployment_Guide/images/lvm-manual-done.png | Bin 0 -> 23338 bytes
.../Deployment_Guide/images/lvm-manual-free.png | Bin 0 -> 22912 bytes
.../html/Deployment_Guide/images/lvm-manual-lv.png | Bin 0 -> 8151 bytes
.../Deployment_Guide/images/lvm-manual-lvdone.png | Bin 0 -> 19276 bytes
.../images/lvm-manual-postboot.png | Bin 0 -> 23466 bytes
.../Deployment_Guide/images/lvm-manual-pv01.png | Bin 0 -> 17835 bytes
.../Deployment_Guide/images/lvm-manual-pvdone.png | Bin 0 -> 23269 bytes
.../html/Deployment_Guide/images/lvm-manual-vg.png | Bin 0 -> 16031 bytes
.../14/html/Deployment_Guide/images/lvm/lvg.svg | 684 +
.../14/html/Deployment_Guide/images/lvm/lvols.svg | 286 +
.../14/html/Deployment_Guide/images/lvols.png | Bin 0 -> 18880 bytes
.../html/Deployment_Guide/images/mouseconfig.png | Bin 0 -> 14610 bytes
.../images/n-t-n-ipsec-diagram.png | Bin 0 -> 33470 bytes
.../Deployment_Guide/images/n-to-n-ipsec-local.png | Bin 0 -> 12987 bytes
.../images/n-to-n-ipsec-remote.png | Bin 0 -> 15159 bytes
.../html/Deployment_Guide/images/neat-aliases.png | Bin 0 -> 16584 bytes
.../14/html/Deployment_Guide/images/neat-dns.png | Bin 0 -> 19916 bytes
.../images/neat-ethernet-settings.png | Bin 0 -> 21296 bytes
.../html/Deployment_Guide/images/neat-ethernet.png | Bin 0 -> 14810 bytes
.../Deployment_Guide/images/neat-home-profile.png | Bin 0 -> 17085 bytes
.../14/html/Deployment_Guide/images/neat-hosts.png | Bin 0 -> 14239 bytes
.../Deployment_Guide/images/neat-isdn-settings.png | Bin 0 -> 14132 bytes
.../14/html/Deployment_Guide/images/neat-isdn.png | Bin 0 -> 18341 bytes
.../images/neat-modem-settings.png | Bin 0 -> 14411 bytes
.../14/html/Deployment_Guide/images/neat-modem.png | Bin 0 -> 18513 bytes
.../images/neat-office-profile.png | Bin 0 -> 17939 bytes
.../images/neat-tokenring-settings.png | Bin 0 -> 13866 bytes
.../Deployment_Guide/images/neat-tokenring.png | Bin 0 -> 18540 bytes
.../html/Deployment_Guide/images/neat-tonline1.png | Bin 0 -> 9220 bytes
.../images/neat-tonlineAcctsetup.png | Bin 0 -> 15775 bytes
.../images/neat-tonlineProvidertab.png | Bin 0 -> 16620 bytes
.../images/neat-wireless-settings.png | Bin 0 -> 11287 bytes
.../html/Deployment_Guide/images/neat-wireless.png | Bin 0 -> 18246 bytes
.../images/neat-xdsl-selectdevicetype.png | Bin 0 -> 9044 bytes
.../Deployment_Guide/images/neat-xdsl-settings.png | Bin 0 -> 24033 bytes
.../14/html/Deployment_Guide/images/neat-xdsl.png | Bin 0 -> 18410 bytes
.../14/html/Deployment_Guide/images/neat.png | Bin 0 -> 19286 bytes
.../14/html/Deployment_Guide/images/nfs-add.png | Bin 0 -> 7087 bytes
.../images/nfs-general-options.png | Bin 0 -> 19847 bytes
.../images/nfs-server-settings.png | Bin 0 -> 14176 bytes
.../Deployment_Guide/images/nfs-user-access.png | Bin 0 -> 13845 bytes
.../Deployment_Guide/images/oprof-start-config.png | Bin 0 -> 8206 bytes
.../Deployment_Guide/images/oprof-start-setup.png | Bin 0 -> 13238 bytes
...raphical_Package_Management-software_update.xcf | Bin 0 -> 223150 bytes
.../Deployment_Guide/images/package-selections.png | Bin 0 -> 26001 bytes
.../14/html/Deployment_Guide/images/pam-icon.png | Bin 0 -> 1515 bytes
.../Deployment_Guide/images/print-manager-menu.png | Bin 0 -> 12069 bytes
.../images/printconf-add-printer.png | Bin 0 -> 17231 bytes
.../Deployment_Guide/images/printconf-config1.png | Bin 0 -> 14695 bytes
.../Deployment_Guide/images/printconf-config2.png | Bin 0 -> 10585 bytes
.../Deployment_Guide/images/printconf-config3.png | Bin 0 -> 11450 bytes
.../Deployment_Guide/images/printconf-config4.png | Bin 0 -> 12218 bytes
.../Deployment_Guide/images/printconf-config5.png | Bin 0 -> 11020 bytes
.../images/printconf-default-icon.png | Bin 0 -> 210 bytes
.../Deployment_Guide/images/printconf-edit.png | Bin 0 -> 13674 bytes
.../html/Deployment_Guide/images/printconf-ipp.png | Bin 0 -> 19642 bytes
.../images/printconf-jetdirect.png | Bin 0 -> 20083 bytes
.../Deployment_Guide/images/printconf-local.png | Bin 0 -> 21888 bytes
.../html/Deployment_Guide/images/printconf-lpd.png | Bin 0 -> 9083 bytes
.../Deployment_Guide/images/printconf-main.png | Bin 0 -> 19412 bytes
.../html/Deployment_Guide/images/printconf-ncp.png | Bin 0 -> 10463 bytes
.../images/printconf-queue-name.png | Bin 0 -> 11538 bytes
.../images/printconf-select-model.png | Bin 0 -> 18461 bytes
.../images/printconf-sharing-general.png | Bin 0 -> 6501 bytes
.../images/printconf-sharing-hosts.png | Bin 0 -> 8209 bytes
.../images/printconf-sharing-queue.png | Bin 0 -> 7478 bytes
.../html/Deployment_Guide/images/printconf-smb.png | Bin 0 -> 29262 bytes
.../images/printconf-test-page.png | Bin 0 -> 16481 bytes
.../images/printer-notification-icon.png | Bin 0 -> 15022 bytes
.../images/raid-manual-boot-error.png | Bin 0 -> 4714 bytes
.../Deployment_Guide/images/raid-manual-final.png | Bin 0 -> 24250 bytes
.../Deployment_Guide/images/raid-manual-free.png | Bin 0 -> 22912 bytes
.../images/raid-manual-lvm-final.png | Bin 0 -> 24916 bytes
.../Deployment_Guide/images/raid-manual-mntpt.png | Bin 0 -> 10266 bytes
.../images/raid-manual-part-add.png | Bin 0 -> 17771 bytes
.../images/raid-manual-part-bootready.png | Bin 0 -> 23946 bytes
.../images/raid-manual-part-opt.png | Bin 0 -> 21060 bytes
.../images/raid-manual-part-opt2.png | Bin 0 -> 16558 bytes
.../images/redhat-config-packages.png | Bin 0 -> 10457 bytes
.../images/redhat-config-users.png | Bin 0 -> 17101 bytes
.../images/redhat-filter-enable.png | Bin 0 -> 194249 bytes
.../images/redhat-filter-sample.png | Bin 0 -> 16132 bytes
.../Deployment_Guide/images/redhat-filters.png | Bin 0 -> 9495 bytes
.../images/redhat-logviewer-add.png | Bin 0 -> 147036 bytes
.../images/redhat-logviewer-monitoring.png | Bin 0 -> 159116 bytes
.../Deployment_Guide/images/redhat-logviewer.png | Bin 0 -> 166037 bytes
.../images/redhat-optional-packages.png | Bin 0 -> 14208 bytes
.../html/Deployment_Guide/images/registering.png | Bin 0 -> 25879 bytes
.../Deployment_Guide/images/relevant-errata.png | Bin 0 -> 25777 bytes
.../html/Deployment_Guide/images/removal-prep.png | Bin 0 -> 14152 bytes
.../Deployment_Guide/images/remove-depend-prep.png | Bin 0 -> 14088 bytes
.../Deployment_Guide/images/rh-securitylevel.png | Bin 0 -> 17203 bytes
.../networkconfig/n-t-n-ipsec-diagram.svg | 658 +
.../Deployment_Guide/images/s-c-samba-basic.png | Bin 0 -> 3358 bytes
.../images/s-c-samba-create-share.png | Bin 0 -> 7734 bytes
.../Deployment_Guide/images/s-c-samba-security.png | Bin 0 -> 9223 bytes
.../Deployment_Guide/images/s-c-samba-users.png | Bin 0 -> 2275 bytes
.../14/html/Deployment_Guide/images/s-c-samba.png | Bin 0 -> 22881 bytes
.../images/samba-nautilus-machines.png | Bin 0 -> 17926 bytes
.../Deployment_Guide/images/samba-nautilus.png | Bin 0 -> 19767 bytes
.../images/seaudit-Edit-filter.png | Bin 0 -> 12933 bytes
.../images/seaudit-Query-policy.png | Bin 0 -> 21946 bytes
.../seaudit-Select-target-type-filtering.png | Bin 0 -> 12826 bytes
.../images/seaudit-View-filtering.png | Bin 0 -> 13075 bytes
.../html/Deployment_Guide/images/seaudit-plain.png | Bin 0 -> 12414 bytes
.../images/sec-ipsec-host2host.png | Bin 0 -> 16970 bytes
.../images/security-intro-to-mls.png | Bin 0 -> 19654 bytes
.../images/security-mls-data-flow.png | Bin 0 -> 14986 bytes
.../14/html/Deployment_Guide/images/serialport.png | Bin 0 -> 752 bytes
.../html/Deployment_Guide/images/serv-config.png | Bin 0 -> 23731 bytes
.../images/ssh-passphrase-prompt.png | Bin 0 -> 13186 bytes
.../images/ssh-startup-applications-add.png | Bin 0 -> 14508 bytes
.../images/ssh-startup-applications-check.png | Bin 0 -> 148890 bytes
.../images/ssh-startup-applications.png | Bin 0 -> 146484 bytes
.../Deployment_Guide/images/switchmail-gui.png | Bin 0 -> 14414 bytes
.../Deployment_Guide/images/system-config-nfs.png | Bin 0 -> 12666 bytes
.../Deployment_Guide/images/tcp_wrap_diagram.png | Bin 0 -> 25775 bytes
.../14/html/Deployment_Guide/images/usbport.png | Bin 0 -> 277 bytes
.../14/html/Deployment_Guide/images/user-new.png | Bin 0 -> 15984 bytes
.../Deployment_Guide/images/user-properties.png | Bin 0 -> 70120 bytes
.../Deployment_Guide/images/user_pass_groups.png | Bin 0 -> 5635 bytes
.../Deployment_Guide/images/user_pass_info.png | Bin 0 -> 45963 bytes
.../14/html/Deployment_Guide/images/your-rhn.png | Bin 0 -> 20572 bytes
.../Fedora/14/html/Deployment_Guide/index.html | 35 +
.../Fedora/14/html/Deployment_Guide/ix01.html | 10 +
.../14/html/Deployment_Guide/lease-database.html | 18 +
.../Fedora/14/html/Deployment_Guide/pr01.html | 95 +
.../Deployment_Guide/pt-kernel-configuration.html | 12 +
.../pt-network-related-config.html | 12 +
.../html/Deployment_Guide/pt-pkg-management.html | 12 +
.../14/html/Deployment_Guide/pt-sysconfig.html | 12 +
.../Deployment_Guide/pt-system-monitoring.html | 12 +
.../14/html/Deployment_Guide/reporter-plugins.html | 24 +
.../14/html/Deployment_Guide/s1-apache-dso.html | 16 +
.../html/Deployment_Guide/s1-apache-editing.html | 949 ++
.../html/Deployment_Guide/s1-apache-mod_ssl.html | 40 +
.../html/Deployment_Guide/s1-apache-resources.html | 18 +
.../html/Deployment_Guide/s1-apache-running.html | 23 +
.../Deployment_Guide/s1-apache-virtualhosts.html | 28 +
.../s1-autotasks-additional-resources.html | 24 +
.../Deployment_Guide/s1-autotasks-at-batch.html | 42 +
.../s1-bind-additional-resources.html | 36 +
.../14/html/Deployment_Guide/s1-bind-dig.html | 36 +
.../14/html/Deployment_Guide/s1-bind-features.html | 20 +
.../14/html/Deployment_Guide/s1-bind-mistakes.html | 22 +
.../html/Deployment_Guide/s1-bind-namedconf.html | 290 +
.../14/html/Deployment_Guide/s1-bind-rndc.html | 41 +
.../14/html/Deployment_Guide/s1-bind-zone.html | 51 +
.../14/html/Deployment_Guide/s1-check-rpm-sig.html | 38 +
.../s1-dhcp-additional-resources.html | 24 +
.../s1-dhcp-configuring-client.html | 34 +
.../s1-dhcp-configuring-server.html | 123 +
.../Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.html | 26 +
.../s1-email-additional-resources.html | 36 +
.../14/html/Deployment_Guide/s1-email-mda.html | 66 +
.../14/html/Deployment_Guide/s1-email-mta.html | 85 +
.../14/html/Deployment_Guide/s1-email-mua.html | 67 +
.../14/html/Deployment_Guide/s1-email-types.html | 22 +
.../14/html/Deployment_Guide/s1-kdump-crash.html | 93 +
.../html/Deployment_Guide/s1-kdump-resources.html | 20 +
.../Deployment_Guide/s1-kernel-boot-loader.html | 93 +
.../html/Deployment_Guide/s1-kernel-download.html | 18 +
.../s1-kernel-modules-additional-resources.html | 29 +
.../s1-kernel-perform-upgrade.html | 19 +
.../html/Deployment_Guide/s1-kernel-preparing.html | 56 +
.../html/Deployment_Guide/s1-keyboard-break.html | 20 +
.../Deployment_Guide/s1-keyboard-indicator.html | 22 +
.../s1-log-files-additional-resources.html | 20 +
.../html/Deployment_Guide/s1-logfiles-adding.html | 18 +
.../Deployment_Guide/s1-logfiles-examining.html | 14 +
.../Deployment_Guide/s1-logfiles-locating.html | 79 +
.../html/Deployment_Guide/s1-logfiles-viewing.html | 52 +
.../s1-networkscripts-control.html | 56 +
.../s1-networkscripts-functions.html | 16 +
.../s1-networkscripts-interfaces.html | 107 +
.../s1-networkscripts-resources.html | 16 +
.../s1-networkscripts-static-routes.html | 69 +
.../s1-openssh-additional-resources.html | 26 +
.../s1-proc-additional-resources.html | 24 +
.../html/Deployment_Guide/s1-proc-directories.html | 119 +
.../14/html/Deployment_Guide/s1-proc-sysctl.html | 31 +
.../14/html/Deployment_Guide/s1-proc-topfiles.html | 24 +
.../s1-rpm-additional-resources.html | 16 +
.../html/Deployment_Guide/s1-rpm-impressing.html | 88 +
.../14/html/Deployment_Guide/s1-rpm-using.html | 32 +
.../Deployment_Guide/s1-rsyslog-performance.html | 12 +
.../s1-services-additional-resources.html | 18 +
.../Deployment_Guide/s1-services-configuring.html | 87 +
.../html/Deployment_Guide/s1-services-running.html | 39 +
.../html/Deployment_Guide/s1-ssh-beyondshell.html | 23 +
.../14/html/Deployment_Guide/s1-ssh-clients.html | 35 +
.../Deployment_Guide/s1-ssh-configuration.html | 97 +
.../s1-sysconfig-additional-resources.html | 14 +
.../s1-sysconfig-etcsysconf-dir.html | 34 +
.../s1-sysinfo-additional-resources.html | 27 +
.../Deployment_Guide/s1-sysinfo-filesystems.html | 38 +
.../html/Deployment_Guide/s1-sysinfo-hardware.html | 29 +
.../Deployment_Guide/s1-sysinfo-memory-usage.html | 28 +
.../s1-users-groups-additional-resources.html | 44 +
.../s1-users-groups-private-groups.html | 47 +
.../s1-users-groups-shadow-utilities.html | 32 +
.../s1-users-groups-standard-groups.html | 339 +
.../s1-users-groups-standard-users.html | 1502 +++
.../14/html/Deployment_Guide/s1-users-tools.html | 206 +
.../Deployment_Guide/s2-apache-dso-writing.html | 18 +
.../s2-apache-mod_ssl-enabling.html | 14 +
.../Deployment_Guide/s2-apache-mod_ssl-genkey.html | 71 +
.../s2-apache-mod_ssl-keypair.html | 31 +
.../Deployment_Guide/s2-apache-mpm-common.html | 56 +
.../Deployment_Guide/s2-apache-resources-web.html | 16 +
.../s2-apache-running-stopping.html | 17 +
.../Deployment_Guide/s2-apache-sslconf-common.html | 53 +
.../s2-autotasks-at-batch-controlling-access.html | 18 +
.../s2-autotasks-at-batch-service.html | 12 +
.../s2-autotasks-at-batch-viewing.html | 12 +
.../s2-autotasks-batch-configuring.html | 20 +
.../s2-autotasks-commandline-options.html | 28 +
.../14/html/Deployment_Guide/s2-bind-dig-a.html | 35 +
.../14/html/Deployment_Guide/s2-bind-dig-x.html | 46 +
.../Deployment_Guide/s2-bind-features-dnssec.html | 14 +
.../Deployment_Guide/s2-bind-features-ipv6.html | 12 +
.../Deployment_Guide/s2-bind-features-ixfr.html | 14 +
.../Deployment_Guide/s2-bind-features-tsig.html | 16 +
.../Deployment_Guide/s2-bind-namedconf-comm.html | 18 +
.../s2-bind-namedconf-state-other.html | 48 +
.../Deployment_Guide/s2-bind-related-books.html | 14 +
.../Deployment_Guide/s2-bind-rndc-querylog.html | 14 +
.../html/Deployment_Guide/s2-bind-rndc-reload.html | 25 +
.../html/Deployment_Guide/s2-bind-rndc-sign.html | 19 +
.../html/Deployment_Guide/s2-bind-rndc-status.html | 24 +
.../Deployment_Guide/s2-bind-rndc-validation.html | 16 +
.../Deployment_Guide/s2-bind-useful-websites.html | 12 +
.../html/Deployment_Guide/s2-bind-zone-comm.html | 12 +
.../Deployment_Guide/s2-bind-zone-examples.html | 93 +
.../Deployment_Guide/s2-email-mta-fetchmail.html | 116 +
.../Deployment_Guide/s2-email-mta-sendmail.html | 131 +
.../s2-email-procmail-recipes.html | 147 +
.../Deployment_Guide/s2-email-related-books.html | 20 +
.../html/Deployment_Guide/s2-email-switchmail.html | 16 +
.../html/Deployment_Guide/s2-email-types-mda.html | 14 +
.../html/Deployment_Guide/s2-email-types-mua.html | 14 +
.../Deployment_Guide/s2-email-useful-websites.html | 26 +
.../Deployment_Guide/s2-kdump-crash-backtrace.html | 35 +
.../Deployment_Guide/s2-kdump-crash-files.html | 22 +
.../Deployment_Guide/s2-kdump-crash-memory.html | 40 +
.../Deployment_Guide/s2-kdump-crash-processes.html | 25 +
.../s2-kdump-resources-online.html | 14 +
.../s2-kernel-boot-loader-iseries.html | 20 +
.../s2-kernel-boot-loader-pseries.html | 27 +
.../14/html/Deployment_Guide/s2-keys-checking.html | 18 +
.../s2-log-files-useful-websites.html | 14 +
.../s2-networkscripts-interfaces-alias.html | 28 +
.../s2-networkscripts-interfaces-chan.html | 43 +
.../s2-networkscripts-interfaces-other.html | 20 +
.../s2-networkscripts-interfaces-ppp0.html | 74 +
.../s2-openssh-useful-websites.html | 16 +
.../14/html/Deployment_Guide/s2-proc-cmdline.html | 22 +
.../14/html/Deployment_Guide/s2-proc-cpuinfo.html | 48 +
.../14/html/Deployment_Guide/s2-proc-crypto.html | 23 +
.../14/html/Deployment_Guide/s2-proc-devices.html | 47 +
.../14/html/Deployment_Guide/s2-proc-dir-bus.html | 34 +
.../html/Deployment_Guide/s2-proc-dir-driver.html | 32 +
.../14/html/Deployment_Guide/s2-proc-dir-fs.html | 12 +
.../14/html/Deployment_Guide/s2-proc-dir-irq.html | 18 +
.../14/html/Deployment_Guide/s2-proc-dir-net.html | 54 +
.../14/html/Deployment_Guide/s2-proc-dir-scsi.html | 97 +
.../14/html/Deployment_Guide/s2-proc-dir-sys.html | 333 +
.../html/Deployment_Guide/s2-proc-dir-sysvipc.html | 12 +
.../14/html/Deployment_Guide/s2-proc-dma.html | 14 +
.../html/Deployment_Guide/s2-proc-execdomains.html | 16 +
.../14/html/Deployment_Guide/s2-proc-fb.html | 14 +
.../html/Deployment_Guide/s2-proc-filesystems.html | 38 +
.../html/Deployment_Guide/s2-proc-interrupts.html | 50 +
.../14/html/Deployment_Guide/s2-proc-iomem.html | 30 +
.../14/html/Deployment_Guide/s2-proc-ioports.html | 38 +
.../14/html/Deployment_Guide/s2-proc-kcore.html | 16 +
.../14/html/Deployment_Guide/s2-proc-kmsg.html | 12 +
.../14/html/Deployment_Guide/s2-proc-loadavg.html | 18 +
.../14/html/Deployment_Guide/s2-proc-locks.html | 24 +
.../14/html/Deployment_Guide/s2-proc-mdstat.html | 22 +
.../14/html/Deployment_Guide/s2-proc-meminfo.html | 88 +
.../14/html/Deployment_Guide/s2-proc-misc.html | 16 +
.../14/html/Deployment_Guide/s2-proc-modules.html | 41 +
.../14/html/Deployment_Guide/s2-proc-mounts.html | 30 +
.../14/html/Deployment_Guide/s2-proc-mtrr.html | 19 +
.../html/Deployment_Guide/s2-proc-partitions.html | 29 +
.../14/html/Deployment_Guide/s2-proc-pci.html | 45 +
.../14/html/Deployment_Guide/s2-proc-pid.html | 58 +
.../14/html/Deployment_Guide/s2-proc-slabinfo.html | 67 +
.../14/html/Deployment_Guide/s2-proc-stat.html | 49 +
.../14/html/Deployment_Guide/s2-proc-swaps.html | 17 +
.../Deployment_Guide/s2-proc-sysrq-trigger.html | 14 +
.../14/html/Deployment_Guide/s2-proc-tty.html | 30 +
.../14/html/Deployment_Guide/s2-proc-uptime.html | 16 +
.../14/html/Deployment_Guide/s2-proc-version.html | 16 +
.../s2-redhat-config-users-process.html | 81 +
.../html/Deployment_Guide/s2-rpm-freshening.html | 24 +
.../14/html/Deployment_Guide/s2-rpm-querying.html | 36 +
.../Deployment_Guide/s2-rpm-related-books.html | 14 +
.../html/Deployment_Guide/s2-rpm-uninstalling.html | 27 +
.../Deployment_Guide/s2-rpm-useful-websites.html | 14 +
.../14/html/Deployment_Guide/s2-rpm-verifying.html | 52 +
.../s2-services-additional-resources-books.html | 12 +
.../Deployment_Guide/s2-services-chkconfig.html | 62 +
.../html/Deployment_Guide/s2-services-ntsysv.html | 41 +
.../Deployment_Guide/s2-ssh-beyondshell-tcpip.html | 32 +
.../html/Deployment_Guide/s2-ssh-clients-scp.html | 30 +
.../html/Deployment_Guide/s2-ssh-clients-sftp.html | 51 +
.../s2-ssh-configuration-keypairs.html | 150 +
.../s2-ssh-configuration-requiring.html | 19 +
.../s2-ssh-configuration-sshd.html | 29 +
.../s3-apache-running-restarting.html | 28 +
.../Deployment_Guide/s3-apache-running-status.html | 15 +
.../14/html/Deployment_Guide/s3-bind-zone-rr.html | 130 +
.../Deployment_Guide/sec-Additional_Resources.html | 14 +
.../sec-Configuration_File_Changes.html | 24 +
.../sec-Configuring_Connection_Settings.html | 16 +
...uring_New_and_Editing_Existing_Connections.html | 21 +
.../sec-Configuring_Yum_and_Yum_Repositories.html | 112 +
.../sec-Connecting_to_a_Network_Automatically.html | 20 +
.../sec-Creating_a_Yum_Repository.html | 24 +
.../sec-Displaying_Information_About_a_Module.html | 72 +
.../sec-Finding_Packages_with_Filters.html | 58 +
.../14/html/Deployment_Guide/sec-Installing.html | 64 +
.../sec-Installing_More_Yum_Plugins.html | 14 +
...sec-Installing_and_Removing_Package_Groups.html | 16 +
...ing_and_Removing_Packages_and_Dependencies.html | 31 +
.../sec-Installing_and_Upgrading.html | 90 +
.../sec-Interacting_with_NetworkManager.html | 33 +
.../Deployment_Guide/sec-Loading_a_Module.html | 28 +
.../sec-PackageKit_Architecture.html | 94 +
.../sec-Packages_and_Package_Groups.html | 133 +
.../sec-Persistent_Module_Loading.html | 25 +
.../Deployment_Guide/sec-Plugin_Descriptions.html | 49 +
.../14/html/Deployment_Guide/sec-Removing.html | 38 +
.../sec-Setting_Module_Parameters.html | 47 +
.../sec-Setting_repository_Options.html | 46 +
.../sec-Specific_Kernel_Module_Capabilities.html | 16 +
.../Deployment_Guide/sec-Unloading_a_Module.html | 41 +
.../sec-User_and_System_Connections.html | 34 +
.../sec-Using_Add_Remove_Software.html | 27 +
.../sec-Using_Channel_Bonding.html | 192 +
.../Deployment_Guide/sec-Using_Yum_Variables.html | 20 +
.../sec-Verifying_the_Initial_RAM_Disk_Image.html | 70 +
.../sec-Viewing_the_Transaction_Log.html | 21 +
.../14/html/Deployment_Guide/sec-Yum_Plugins.html | 42 +
.../sect-Configuring_a_Multihomed_DHCP_Server.html | 131 +
...d_Line_Configuration-Network_Time_Protocol.html | 49 +
...e_Configuration-Command_Line_Configuration.html | 28 +
.../sect-RedHat-We_Need_Feedback.html | 28 +
...Domains-Setting_up_Kerberos_Authentication.html | 39 +
...SSSD_User_Guide-Introduction-SSSD_Features.html | 58 +
...ation_Files-SSSD_Configuration_File_Format.html | 71 +
.../Deployment_Guide/testing-upload-method.html | 23 +
.../Fedora-14-Deployment_Guide-en-US.pdf | Bin 0 -> 6439541 bytes
public_html/en-US/Site_Statistics.html | 4 +-
public_html/en-US/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Core.xml | 2 +-
.../en-US/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/en-US/opds.xml | 10 +-
public_html/en-US/toc.html | 9 +
public_html/es-ES/Site_Statistics.html | 4 +-
public_html/es-ES/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Core.xml | 2 +-
.../es-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/es-ES/opds.xml | 10 +-
public_html/es-ES/toc.html | 18 +
public_html/fa-IR/Site_Statistics.html | 4 +-
public_html/fa-IR/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Core.xml | 2 +-
.../fa-IR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fa-IR/opds.xml | 10 +-
public_html/fa-IR/toc.html | 9 +
public_html/fi-FI/Site_Statistics.html | 4 +-
public_html/fi-FI/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Core.xml | 2 +-
.../fi-FI/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fi-FI/opds.xml | 10 +-
public_html/fi-FI/toc.html | 9 +
public_html/fr-FR/Site_Statistics.html | 4 +-
public_html/fr-FR/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Core.xml | 2 +-
.../fr-FR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fr-FR/opds.xml | 10 +-
public_html/fr-FR/toc.html | 9 +
public_html/gu-IN/Site_Statistics.html | 4 +-
public_html/gu-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Core.xml | 2 +-
.../gu-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/gu-IN/opds.xml | 10 +-
public_html/gu-IN/toc.html | 9 +
public_html/he-IL/Site_Statistics.html | 4 +-
public_html/he-IL/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Core.xml | 2 +-
.../he-IL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/he-IL/opds.xml | 10 +-
public_html/he-IL/toc.html | 9 +
public_html/hi-IN/Site_Statistics.html | 4 +-
public_html/hi-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Core.xml | 2 +-
.../hi-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hi-IN/opds.xml | 10 +-
public_html/hi-IN/toc.html | 9 +
public_html/hu-HU/Site_Statistics.html | 4 +-
public_html/hu-HU/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Core.xml | 2 +-
.../hu-HU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hu-HU/opds.xml | 10 +-
public_html/hu-HU/toc.html | 9 +
public_html/id-ID/Site_Statistics.html | 4 +-
public_html/id-ID/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Core.xml | 2 +-
.../id-ID/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/id-ID/opds.xml | 10 +-
public_html/id-ID/toc.html | 9 +
public_html/it-IT/Site_Statistics.html | 4 +-
public_html/it-IT/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Core.xml | 2 +-
.../it-IT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/it-IT/opds.xml | 10 +-
public_html/it-IT/toc.html | 9 +
public_html/ja-JP/Site_Statistics.html | 4 +-
public_html/ja-JP/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Core.xml | 2 +-
.../ja-JP/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ja-JP/opds.xml | 10 +-
public_html/ja-JP/toc.html | 9 +
public_html/kn-IN/Site_Statistics.html | 4 +-
public_html/kn-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Core.xml | 2 +-
.../kn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/kn-IN/opds.xml | 10 +-
public_html/kn-IN/toc.html | 9 +
public_html/ko-KR/Site_Statistics.html | 4 +-
public_html/ko-KR/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Core.xml | 2 +-
.../ko-KR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ko-KR/opds.xml | 10 +-
public_html/ko-KR/toc.html | 9 +
public_html/ml-IN/Site_Statistics.html | 4 +-
public_html/ml-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Core.xml | 2 +-
.../ml-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ml-IN/opds.xml | 10 +-
public_html/ml-IN/toc.html | 9 +
public_html/mr-IN/Site_Statistics.html | 4 +-
public_html/mr-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Core.xml | 2 +-
.../mr-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/mr-IN/opds.xml | 10 +-
public_html/mr-IN/toc.html | 9 +
public_html/nb-NO/Site_Statistics.html | 4 +-
public_html/nb-NO/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Core.xml | 2 +-
.../nb-NO/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nb-NO/opds.xml | 10 +-
public_html/nb-NO/toc.html | 9 +
public_html/nl-NL/Site_Statistics.html | 4 +-
public_html/nl-NL/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Core.xml | 2 +-
.../nl-NL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nl-NL/opds.xml | 10 +-
public_html/nl-NL/toc.html | 18 +
public_html/opds.xml | 86 +-
public_html/or-IN/Site_Statistics.html | 4 +-
public_html/or-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Core.xml | 2 +-
.../or-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/or-IN/opds.xml | 10 +-
public_html/or-IN/toc.html | 9 +
public_html/pa-IN/Site_Statistics.html | 4 +-
public_html/pa-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Core.xml | 2 +-
.../pa-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pa-IN/opds.xml | 10 +-
public_html/pa-IN/toc.html | 9 +
public_html/pl-PL/Site_Statistics.html | 4 +-
public_html/pl-PL/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Core.xml | 2 +-
.../pl-PL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pl-PL/opds.xml | 10 +-
public_html/pl-PL/toc.html | 9 +
public_html/pt-BR/Site_Statistics.html | 4 +-
public_html/pt-BR/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Core.xml | 2 +-
.../pt-BR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-BR/opds.xml | 10 +-
public_html/pt-BR/toc.html | 9 +
public_html/pt-PT/Site_Statistics.html | 4 +-
public_html/pt-PT/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Core.xml | 2 +-
.../pt-PT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-PT/opds.xml | 10 +-
public_html/pt-PT/toc.html | 9 +
public_html/ru-RU/Site_Statistics.html | 4 +-
public_html/ru-RU/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Core.xml | 2 +-
.../ru-RU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ru-RU/opds.xml | 10 +-
public_html/ru-RU/toc.html | 9 +
public_html/sk-SK/Site_Statistics.html | 4 +-
public_html/sk-SK/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Core.xml | 2 +-
.../sk-SK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sk-SK/opds.xml | 10 +-
public_html/sk-SK/toc.html | 9 +
public_html/sr-Latn-RS/Site_Statistics.html | 4 +-
public_html/sr-Latn-RS/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora_Core.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sr-Latn-RS/opds.xml | 10 +-
public_html/sr-Latn-RS/toc.html | 9 +
public_html/sr-RS/Site_Statistics.html | 4 +-
public_html/sr-RS/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Core.xml | 2 +-
.../sr-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sr-RS/opds.xml | 10 +-
public_html/sr-RS/toc.html | 9 +
public_html/sv-SE/Site_Statistics.html | 4 +-
public_html/sv-SE/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Core.xml | 2 +-
.../sv-SE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sv-SE/opds.xml | 10 +-
public_html/sv-SE/toc.html | 9 +
public_html/ta-IN/Site_Statistics.html | 4 +-
public_html/ta-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Core.xml | 2 +-
.../ta-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ta-IN/opds.xml | 10 +-
public_html/ta-IN/toc.html | 9 +
public_html/te-IN/Site_Statistics.html | 4 +-
public_html/te-IN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Core.xml | 2 +-
.../te-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/te-IN/opds.xml | 10 +-
public_html/te-IN/toc.html | 9 +
public_html/toc.html | 15 +
public_html/uk-UA/Site_Statistics.html | 4 +-
public_html/uk-UA/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Core.xml | 2 +-
.../uk-UA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/uk-UA/opds.xml | 10 +-
public_html/uk-UA/toc.html | 9 +
public_html/zh-CN/Site_Statistics.html | 4 +-
public_html/zh-CN/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Core.xml | 2 +-
.../zh-CN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-CN/opds.xml | 10 +-
public_html/zh-CN/toc.html | 9 +
public_html/zh-TW/Site_Statistics.html | 4 +-
public_html/zh-TW/opds-Fedora.xml | 21 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Core.xml | 2 +-
.../zh-TW/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-TW/opds.xml | 10 +-
public_html/zh-TW/toc.html | 9 +
1378 files changed, 40278 insertions(+), 505 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index be64548..25840d1 100644
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 84d9900..3da0dc9 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -1483,6 +1483,30 @@
<priority>0.8</priority>
</url>
<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</loc>
+ <lastmod>2010-11-14</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/14/html/Deployment_Guide/index.html</loc>
+ <lastmod>2010-11-14</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/14/html-single/Deployment_Guide/index.html</loc>
+ <lastmod>2010-11-14</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf</loc>
+ <lastmod>2010-11-14</lastmod>
+ <changefreq>monthly</changefreq>
+ <priority>0.8</priority>
+</url>
+<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</loc>
<lastmod>2010-10-20</lastmod>
<changefreq>monthly</changefreq>
diff --git a/public_html/as-IN/Site_Statistics.html b/public_html/as-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/as-IN/Site_Statistics.html
+++ b/public_html/as-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/as-IN/opds-Fedora.xml b/public_html/as-IN/opds-Fedora.xml
index 018f67e..5f6c351 100644
--- a/public_html/as-IN/opds-Fedora.xml
+++ b/public_html/as-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:05</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>as-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
index df6d690..4ea241e 100644
--- a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:05</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Core.xml b/public_html/as-IN/opds-Fedora_Core.xml
index dbf97cb..e5b0089 100644
--- a/public_html/as-IN/opds-Fedora_Core.xml
+++ b/public_html/as-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:05</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
index ee22eef..4a0d027 100644
--- a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:05</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds.xml b/public_html/as-IN/opds.xml
index 650f69e..ba28f59 100644
--- a/public_html/as-IN/opds.xml
+++ b/public_html/as-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/as-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:05</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:05</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:05</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:05</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:05</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/as-IN/toc.html b/public_html/as-IN/toc.html
index 8127374..c9d31b1 100644
--- a/public_html/as-IN/toc.html
+++ b/public_html/as-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/bg-BG/Site_Statistics.html b/public_html/bg-BG/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/bg-BG/Site_Statistics.html
+++ b/public_html/bg-BG/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/bg-BG/opds-Fedora.xml b/public_html/bg-BG/opds-Fedora.xml
index 9359463..76e1142 100644
--- a/public_html/bg-BG/opds-Fedora.xml
+++ b/public_html/bg-BG/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>bg-BG</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
index 287ff8d..775295b 100644
--- a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Core.xml b/public_html/bg-BG/opds-Fedora_Core.xml
index 639cc0a..c53949f 100644
--- a/public_html/bg-BG/opds-Fedora_Core.xml
+++ b/public_html/bg-BG/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
index 68f37f1..3098219 100644
--- a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds.xml b/public_html/bg-BG/opds.xml
index 041d0f9..cf6b563 100644
--- a/public_html/bg-BG/opds.xml
+++ b/public_html/bg-BG/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bg-BG/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bg-BG/toc.html b/public_html/bg-BG/toc.html
index 746deba..d36ac89 100644
--- a/public_html/bg-BG/toc.html
+++ b/public_html/bg-BG/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/bn-IN/Site_Statistics.html b/public_html/bn-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/bn-IN/Site_Statistics.html
+++ b/public_html/bn-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/bn-IN/opds-Fedora.xml b/public_html/bn-IN/opds-Fedora.xml
index f1d8833..09abdbe 100644
--- a/public_html/bn-IN/opds-Fedora.xml
+++ b/public_html/bn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>bn-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
index c71732c..e3b9b79 100644
--- a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Core.xml b/public_html/bn-IN/opds-Fedora_Core.xml
index adfe016..f5775f8 100644
--- a/public_html/bn-IN/opds-Fedora_Core.xml
+++ b/public_html/bn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
index 964a021..cc56b6b 100644
--- a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds.xml b/public_html/bn-IN/opds.xml
index 25e4ffb..a14a3df 100644
--- a/public_html/bn-IN/opds.xml
+++ b/public_html/bn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bn-IN/toc.html b/public_html/bn-IN/toc.html
index 7bc8dec..8d53bb6 100644
--- a/public_html/bn-IN/toc.html
+++ b/public_html/bn-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/bs-BA/Site_Statistics.html b/public_html/bs-BA/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/bs-BA/Site_Statistics.html
+++ b/public_html/bs-BA/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/bs-BA/opds-Fedora.xml b/public_html/bs-BA/opds-Fedora.xml
index 474cabc..dbbee7c 100644
--- a/public_html/bs-BA/opds-Fedora.xml
+++ b/public_html/bs-BA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>bs-BA</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
index 06703c1..e680764 100644
--- a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Core.xml b/public_html/bs-BA/opds-Fedora_Core.xml
index 947a081..71ad8e1 100644
--- a/public_html/bs-BA/opds-Fedora_Core.xml
+++ b/public_html/bs-BA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
index afef125..1951f55 100644
--- a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds.xml b/public_html/bs-BA/opds.xml
index ed82fa1..46ed8f8 100644
--- a/public_html/bs-BA/opds.xml
+++ b/public_html/bs-BA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bs-BA/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/bs-BA/toc.html b/public_html/bs-BA/toc.html
index 69b757f..836aead 100644
--- a/public_html/bs-BA/toc.html
+++ b/public_html/bs-BA/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ca-ES/Site_Statistics.html b/public_html/ca-ES/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/ca-ES/Site_Statistics.html
+++ b/public_html/ca-ES/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/ca-ES/opds-Fedora.xml b/public_html/ca-ES/opds-Fedora.xml
index 4dd7241..15f7db1 100644
--- a/public_html/ca-ES/opds-Fedora.xml
+++ b/public_html/ca-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>ca-ES</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-ca-ES.epub</id>
<!--author>
diff --git a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
index f74a730..327ce59 100644
--- a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Core.xml b/public_html/ca-ES/opds-Fedora_Core.xml
index 733131b..210891d 100644
--- a/public_html/ca-ES/opds-Fedora_Core.xml
+++ b/public_html/ca-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
index e447491..0fe0901 100644
--- a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds.xml b/public_html/ca-ES/opds.xml
index 02a7201..1168b09 100644
--- a/public_html/ca-ES/opds.xml
+++ b/public_html/ca-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ca-ES/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ca-ES/toc.html b/public_html/ca-ES/toc.html
index a2d8430..b78dc67 100644
--- a/public_html/ca-ES/toc.html
+++ b/public_html/ca-ES/toc.html
@@ -119,6 +119,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/cs-CZ/Site_Statistics.html b/public_html/cs-CZ/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/cs-CZ/Site_Statistics.html
+++ b/public_html/cs-CZ/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/cs-CZ/opds-Fedora.xml b/public_html/cs-CZ/opds-Fedora.xml
index 0e3572c..1b78722 100644
--- a/public_html/cs-CZ/opds-Fedora.xml
+++ b/public_html/cs-CZ/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>cs-CZ</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
index 44b4f95..4e65da3 100644
--- a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Core.xml b/public_html/cs-CZ/opds-Fedora_Core.xml
index 225b9d5..c5c8d42 100644
--- a/public_html/cs-CZ/opds-Fedora_Core.xml
+++ b/public_html/cs-CZ/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
index 069d4dc..9cec6af 100644
--- a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds.xml b/public_html/cs-CZ/opds.xml
index ee903b9..aa43a0d 100644
--- a/public_html/cs-CZ/opds.xml
+++ b/public_html/cs-CZ/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/cs-CZ/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/cs-CZ/toc.html b/public_html/cs-CZ/toc.html
index 3aab087..183da96 100644
--- a/public_html/cs-CZ/toc.html
+++ b/public_html/cs-CZ/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/da-DK/Site_Statistics.html b/public_html/da-DK/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/da-DK/Site_Statistics.html
+++ b/public_html/da-DK/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/da-DK/opds-Fedora.xml b/public_html/da-DK/opds-Fedora.xml
index b262352..a98d154 100644
--- a/public_html/da-DK/opds-Fedora.xml
+++ b/public_html/da-DK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>da-DK</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
index 4af4715..90ac78f 100644
--- a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Core.xml b/public_html/da-DK/opds-Fedora_Core.xml
index 1e21195..e0a67ea 100644
--- a/public_html/da-DK/opds-Fedora_Core.xml
+++ b/public_html/da-DK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
index 697a926..03b7857 100644
--- a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds.xml b/public_html/da-DK/opds.xml
index b93d0c0..7efba02 100644
--- a/public_html/da-DK/opds.xml
+++ b/public_html/da-DK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/da-DK/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/da-DK/toc.html b/public_html/da-DK/toc.html
index 9cebf64..0d240aa 100644
--- a/public_html/da-DK/toc.html
+++ b/public_html/da-DK/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/de-DE/Site_Statistics.html b/public_html/de-DE/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/de-DE/Site_Statistics.html
+++ b/public_html/de-DE/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/de-DE/opds-Fedora.xml b/public_html/de-DE/opds-Fedora.xml
index 03adf73..8e80269 100644
--- a/public_html/de-DE/opds-Fedora.xml
+++ b/public_html/de-DE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>de-DE</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-de-DE.epub</id>
<!--author>
diff --git a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
index cbe8d72..45fec89 100644
--- a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Core.xml b/public_html/de-DE/opds-Fedora_Core.xml
index 2be6b5b..af4181b 100644
--- a/public_html/de-DE/opds-Fedora_Core.xml
+++ b/public_html/de-DE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
index 2774b5f..ef9649a 100644
--- a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds.xml b/public_html/de-DE/opds.xml
index 162cf50..7174ec0 100644
--- a/public_html/de-DE/opds.xml
+++ b/public_html/de-DE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/de-DE/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/de-DE/toc.html b/public_html/de-DE/toc.html
index 4660c38..4ad6f24 100644
--- a/public_html/de-DE/toc.html
+++ b/public_html/de-DE/toc.html
@@ -111,6 +111,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/el-GR/Site_Statistics.html b/public_html/el-GR/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/el-GR/Site_Statistics.html
+++ b/public_html/el-GR/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/el-GR/opds-Fedora.xml b/public_html/el-GR/opds-Fedora.xml
index 8eade8d..1ef26ef 100644
--- a/public_html/el-GR/opds-Fedora.xml
+++ b/public_html/el-GR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>el-GR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
index f72a0b0..91dce79 100644
--- a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Core.xml b/public_html/el-GR/opds-Fedora_Core.xml
index fb6f136..29cfbf6 100644
--- a/public_html/el-GR/opds-Fedora_Core.xml
+++ b/public_html/el-GR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
index dd27ecd..0471c21 100644
--- a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds.xml b/public_html/el-GR/opds.xml
index 0f9c62f..03f593b 100644
--- a/public_html/el-GR/opds.xml
+++ b/public_html/el-GR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/el-GR/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/el-GR/toc.html b/public_html/el-GR/toc.html
index 525bd91..1cca543 100644
--- a/public_html/el-GR/toc.html
+++ b/public_html/el-GR/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub b/public_html/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub
new file mode 100644
index 0000000..a742caa
Binary files /dev/null and b/public_html/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..9d2ddca
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/common.css
@@ -0,0 +1,1474 @@
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ white-space: nowrap;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+}
+
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+}
+
+div.section {
+ margin-top:1em;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/default.css b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/lang.css b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/overrides.css b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,51 @@
+a:link {
+ color:#0066cc;
+}
+
+a:hover, a:active {
+ color:#003366;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+
+h1 {
+ color:#3c6eb4
+}
+
+.producttitle {
+ background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
+}
+
+.section h1.title {
+ color:#3c6eb4;
+}
+
+
+h2,h3,h4,h5,h6 {
+ color:#3c6eb4;
+}
+
+table {
+ border:1px solid #3c6eb4;
+}
+
+table th {
+ background-color:#3c6eb4;
+}
+
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#3c6eb4;
+}
+
+.titlepage .edition {
+ color: #3c6eb4;
+}
+
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/print.css b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/1.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..c21d7a3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/1.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/1.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#000000;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 17.853468,22.008438 -2.564941,0 0,-7.022461 c -5e-6,-0.143873 -5e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224122,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08854,0.08302 -0.17432,0.157723 -0.257324,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/10.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..15b81da
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/10.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/10.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/10.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/11.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..2fcc2dd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/11.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/11.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/11.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/12.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..edebe20
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/12.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/12.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/12.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/13.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..ec48cef
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/13.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/13.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/13.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/14.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..33d5637
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/14.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/14.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/14.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/15.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..f1a4eb2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/15.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/15.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/15.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2839"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2841"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/16.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..d38a155
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/16.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/16.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/16.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/17.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d83e898
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/17.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/17.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/17.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/18.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..9e39de4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/18.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/18.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/18.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/19.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..9eeedfb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/19.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/19.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/19.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/2.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..ff9cc57
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/2.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/2.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.89546,22.008438 -8.143066,0 0,-1.784668 2.855468,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979493,-1.0708 0.293289,-0.326492 0.545079,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.373529,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.17431,-0.666821 0.174316,-1.037598 -6e-6,-0.409496 -0.124517,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827313,0.522958 -1.270019,0.921386 l -1.394531,-1.651855 c 0.249022,-0.226877 0.509113,-0.442698 0.780273,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079102,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319824,-0.1494141 0.58105,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187012,0.6889648 0.326489,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.893727 0.265625,1.41
9433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/20.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b28b4aa
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/20.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/20.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/20.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/21.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..eda952c
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/21.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/21.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/21.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/22.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..90b14b0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/22.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/22.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/22.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/23.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..8b35a74
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/23.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/23.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/23.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/24.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..6041b02
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/24.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/24.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/25.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..ecb15e6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/25.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/25.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/26.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..4b2f560
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/26.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/26.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/27.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..ecf058e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/27.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/27.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/28.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..e64efb2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/28.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/28.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/29.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..dbbca1b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/29.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/29.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/3.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..4febe43
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/3.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/3.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.422316,12.587051 c -9e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.23243,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315437,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.392911,0.332031 -0.890957,0.592122 -1.494141,0.780273 -0.597661,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267255,-0.05534 -1.842773,-0.166016 -0.575523,-0.105143 -1.112306,-0.268392 -1.610352,-0.489746 l 0,-2.183105 c 0.249023,0.132815 0.511881,0.249025 0.788574,0.348632 0.276692,0.09961 0.553384,0.185387 0.830079,0.257325 0.27669,0.06641 0.547848,0.116212 0.813476,0.149414 0.271156,0.0332 0.525713,0.04981 0.763672,0.0498 0.475907,2e-6 0.871577,-0.04427 1.187012,-0.132812 0.315424,-
0.08854 0.567214,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320957,-0.351397 0.398437,-0.572754 0.083,-0.226885 0.124506,-0.473141 0.124512,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.265631,-0.376297 -0.498047,-0.514648 -0.226893,-0.143876 -0.525721,-0.254553 -0.896484,-0.332032 -0.370773,-0.07747 -0.827315,-0.116205 -1.369629,-0.116211 l -0.863281,0 0,-1.801269 0.846679,0 c 0.509111,7e-6 0.932451,-0.04426 1.27002,-0.132813 0.33756,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.43164,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.68897,-0.365224 -1.27002,-0.365234 -0.265629,10e-6 -0.514652,0.02768 -0.74707,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193688,0.07748 -0.373538,0.166026 -0.539551,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439941,0.282227 l -1.294922,-1.70
9961 c 0.232421,-0.171538 0.484211,-0.329253 0.755371,-0.473145 0.276691,-0.143868 0.575519,-0.26838 0.896484,-0.373535 0.320961,-0.1106647 0.666827,-0.1964393 1.037598,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492506,0.1272911 0.913079,0.3154421 1.261718,0.5644531 0.348626,0.243501 0.617017,0.545096 0.805176,0.904786 0.193677,0.354177 0.290519,0.760914 0.290528,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/30.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..f4ffb14
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/30.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/30.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/31.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..0b29e87
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/31.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/31.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/32.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..a4740a3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/32.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/32.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/33.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..f23ccea
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/33.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/33.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/34.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..7e2ab31
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/34.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/34.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/35.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..02118e3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/35.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/35.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/36.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..30f4fdf
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/36.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/36.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/37.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..6174706
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/37.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/37.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/38.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..161661d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/38.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/38.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/39.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..2d46b24
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/39.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/39.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/4.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..9b9dd88
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/4.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/4.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 20.078077,19.493301 -1.460937,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460937,0 0,1.992187 m -3.959472,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09962,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.12175,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.025391,3.071289 2.75586,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/40.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..fe2a68f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/40.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/40.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/5.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..f239fb6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/5.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/5.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 16.035597,14.255508 c 0.520177,8e-6 1.004388,0.08025 1.452637,0.240723 0.448235,0.160489 0.838371,0.395678 1.17041,0.705566 0.332023,0.309903 0.592114,0.697272 0.780273,1.16211 0.188143,0.459315 0.282218,0.987797 0.282227,1.585449 -9e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.204761,0.520184 -0.506356,0.962892 -0.904785,1.328125 -0.398445,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261724,0.290528 -2.025391,0.290528 -0.304365,0 -0.60596,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863281,-0.124512 -0.271161,-0.04981 -0.531252,-0.116211 -0.780274,-0.199219 -0.24349,-0.08301 -0.464844,-0.17985 -0.664062,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672363,0.31543 0.254556,0.09408 0.517414,0.177086 0.788574,0.249024 0.276691,0.06641 0.553383,0.121746 0.830078,0.166015 0.27669,0.03874 0.539548,0.05811 0.788575,0.05811 0.741532,2e-6 1.305984,-0.152179 1.693359,-0.456543 0.387364,-0.309893 0.5810
49,-0.799639 0.581055,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751465,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320966,0.03874 -0.481445,0.06641 -0.154951,0.02768 -0.304365,0.05811 -0.448242,0.09131 -0.143883,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456542,-6.1840821 6.408204,0 0,2.1748051 -4.183594,0 -0.199219,2.382324 c 0.17708,-0.03873 0.381832,-0.07747 0.614258,-0.116211 0.237951,-0.03873 0.542313,-0.0581 0.913086,-0.05811"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/6.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..18866e6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/6.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/6.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 11.702589,16.853653 c -10e-7,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.0664,-0.575514 0.179849,-1.126132 0.340332,-1.651856 0.166014,-0.531241 0.387368,-1.023753 0.664062,-1.477539 0.282225,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431638,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603186,-0.1936727 1.305984,-0.2905151 2.108399,-0.2905274 0.116204,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.138339,0.00555 0.276685,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251782,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210295,-0.04979 -0.434416,-0.08853 -0.672364,-0.116211 -0.232429,-0.03319 -0.467617,-0.04979 -0.705566,-0.0498 -0.747076,1e-5 -1.361334,0.09408 -1.842774,0.282226 -0.481449,0.182627 -0.863285,0.439951 -1.145507,0.771973 -0.28223,0.33204 -0.484216,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.215821,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243486,-0.384596 0.39843
7,-0.556153 0.160478,-0.177076 0.345862,-0.32649 0.556153,-0.448242 0.210282,-0.127271 0.44547,-0.22688 0.705566,-0.298828 0.26562,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419433,0.257324 0.420566,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.15494,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282226,1.768066 -0.182626,0.520184 -0.445484,0.962892 -0.788575,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643554,0.282227 -0.597661,0 -1.15658,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.973961,-0.542317 -1.361328,-0.979492 -0.381838,-0.437173 -0.683433,-0.987791 -0.904785,-1.651856 -0.215822,-0.669593 -0.323732,-1.460933 -0.323731,-2.374023 m 4.216797,3.270508 c 0.226883,2e-6 0.431635,-0.0415 0.614258,-0.124512 0.188145,-0.08854 0.348627,-0.218585 0.481445,-0.390137 0.13834,-0.17708 0.243483,-0.3
98434 0.31543,-0.664062 0.07747,-0.265622 0.116204,-0.581051 0.116211,-0.946289 -7e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243496,-0.343094 -0.617031,-0.514643 -1.120606,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.39014,0.229661 -0.53955,0.390137 -0.149418,0.160487 -0.265629,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.31543,0.755371 0.143876,0.221357 0.318193,0.401207 0.522949,0.539551 0.210282,0.138349 0.453772,0.207522 0.730469,0.20752"
+ id="path2846"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/7.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..52c3a18
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/7.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/7.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 12.789991,22.008438 4.316407,-9.960937 -5.578125,0 0,-2.1582035 8.367187,0 0,1.6103515 -4.424316,10.508789 -2.681153,0"
+ id="path2832"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/8.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..8a8cb21
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/8.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/8.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.761671,9.7149811 c 0.503576,1.23e-5 0.979487,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337558,0.243501 0.60595,0.547862 0.805176,0.913086 0.199211,0.365244 0.29882,0.794118 0.298828,1.286621 -8e-6,0.365243 -0.05535,0.697274 -0.166015,0.996094 -0.110686,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193693,0.237963 -0.423348,0.451017 -0.688965,0.639161 -0.265632,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.633619,0.362473 0.937988,0.572754 0.309888,0.210292 0.583814,0.448247 0.821777,0.713867 0.237948,0.260096 0.428866,0.55339 0.572754,0.879883 0.143872,0.326501 0.215812,0.691735 0.21582,1.095703 -8e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478686,0.758139 -0.838379,1.045898 -0.359707,0.287761 -0.791348,0.509115 -1.294921,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651856,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.9379
9,-0.362467 -1.286621,-0.639161 -0.348634,-0.276691 -0.614259,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265626,-0.857744 -0.265625,-1.361328 -10e-7,-0.415035 0.06087,-0.78857 0.182617,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498047,-0.896485 0.210285,-0.265619 0.456541,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271162,-0.171543 -0.525719,-0.356927 -0.763672,-0.556152 -0.237958,-0.204746 -0.445477,-0.428866 -0.622559,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -10e-7,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478677,-0.669585 0.821778,-0.913086 0.343096,-0.249012 0.738766,-0.434396 1.187011,-0.5561527 0.448239,-0.1217326 0.918616,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.107911,0.614258 0.07194,0.18262 0.17708,0.340334 0.315429,0.473145 0.143877,0.132814 0.32
096,0.237957 0.53125,0.315429 0.210283,0.07194 0.453772,0.107912 0.730469,0.10791 0.581049,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.43164,-1.087402 -6e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218593,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.320969,-0.307125 -0.514648,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 15.662062,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664063,0.398438 -0.199222,0.138351 -0.370772,0.293299 -0.514648,0.464844 -0.13835,0.16602 -0.24626,0.348637 -0.323731,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.701661,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514649,0.08301 -0.154952,0.05535 -0.290531,0.13559 -0.406738,0.240723 -0.110681,0.105153 -0.199223,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.31543
8 0.282226,0.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160478,0.09962 0.32926,0.199226 0.506348,0.298828 0.171545,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154943,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.12174,-0.138338 0.218582,-0.293286 0.290528,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.157721,-0.284984 -0.273926,-0.390137 -0.116217,-0.105133 -0.254563,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/9.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..0ae412f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/9.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/9.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.829054,15.052383 c -9e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340333,1.651856 -0.160489,0.525719 -0.381843,1.018232 -0.664062,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426113,0.332032 -0.940761,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.30046,0.282227 -2.108399,0.282227 -0.116214,0 -0.243492,-0.0028 -0.381836,-0.0083 -0.138348,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273927,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237954,0.02767 0.478676,0.04151 0.722168,0.0415 0.747067,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.481441,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.282221,-0.337562 0.481439,-0.738766 0.597657,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.107911,0 c -0.110683,0.199225 -0.243495,0.384609 -0.398437,0.556153 -0.
154954,0.171554 -0.337571,0.320968 -0.547852,0.448242 -0.210291,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.265629,0.07194 -0.56169,0.107914 -0.888183,0.10791 -0.52572,4e-6 -0.998864,-0.08577 -1.419434,-0.257324 -0.420575,-0.171545 -0.777508,-0.420568 -1.070801,-0.74707 -0.287761,-0.326492 -0.509115,-0.727696 -0.664062,-1.203614 -0.154949,-0.475904 -0.232423,-1.020988 -0.232422,-1.635253 -10e-7,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453774,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758135,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043127,-0.2905151 1.651855,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520176,0.210298 0.971184,0.534028 1.353027,0.971192 0.381829,0.437185 0.683423,0.990569 0.904786,1.660156 0.221345,0.669605 0.332022,1.458178 0.332031,2.365722 m -4.216797,-3.262207 c -0.226892,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188154,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132815,0.17155
9 -0.237959,0.392913 -0.315429,0.664062 -0.07194,0.265634 -0.107914,0.581063 -0.107911,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373536,1.394532 0.249019,0.343105 0.625321,0.514654 1.128906,0.514648 0.254552,6e-6 0.486974,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.53955,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124506,-0.401197 0.124512,-0.605958 -6e-6,-0.282218 -0.03598,-0.561677 -0.10791,-0.838378 -0.06641,-0.282218 -0.171556,-0.534008 -0.31543,-0.755372 -0.138352,-0.226878 -0.312668,-0.409495 -0.522949,-0.547851 -0.204758,-0.138336 -0.44548,-0.207509 -0.722168,-0.20752"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/documentation.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/dot.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/dot2.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/green.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/green.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/h1-bg.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/image_left.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/image_right.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..5b67443
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/important.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/important.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/important.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L 78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L 41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882 z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L 55.536215,56.538729 z"
+ id="path6824"
+ style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L 55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L 55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L 55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L 55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L 55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L 55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L 55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L 55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/logo.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/note.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/note.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/note.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L -2512.4524,4607.3813 L -2512.4524,56.33197 z"
+ transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+ style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ <g
+ transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928 370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C 154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353 494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+ style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+ style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729 326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C 209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L 509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C 495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+ style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C 253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861 313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345 440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+ style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+ style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+ style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/red.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/red.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/shade.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/shine.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-go-back.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-go-forward.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-go-up.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-home.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/title_logo.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/title_logo.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="220"
+ height="70"
+ id="svg6180">
+ <defs
+ id="defs6182" />
+ <g
+ transform="translate(-266.55899,-345.34488)"
+ id="layer1">
+ <path
+ d="m 316.7736,397.581 c 0,0 0,0 -20.53889,0 0.3327,4.45245 3.92157,7.77609 8.70715,7.77609 3.38983,0 6.31456,-1.39616 8.64094,-3.65507 0.46553,-0.46679 0.99726,-0.59962 1.59519,-0.59962 0.79781,0 1.59561,0.39932 2.12692,1.06388 0.3327,0.46553 0.53216,0.99726 0.53216,1.52857 0,0.73118 -0.3327,1.52857 -0.93106,2.12734 -2.7919,2.99052 -7.51086,4.98503 -12.16403,4.98503 -8.44149,0 -15.22074,-6.77967 -15.22074,-15.22158 0,-8.44149 6.58022,-15.22074 15.02171,-15.22074 8.37529,0 14.62323,6.51317 14.62323,15.08749 0,1.26418 -1.12924,2.12861 -2.39258,2.12861 z m -12.23065,-11.76512 c -4.45329,0 -7.51085,2.92473 -8.17499,7.17731 10.03626,0 16.35083,0 16.35083,0 -0.59836,-4.05355 -3.78874,-7.17731 -8.17584,-7.17731 z"
+ id="path11"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 375.46344,410.80807 c -8.44106,0 -15.22074,-6.77968 -15.22074,-15.22159 0,-8.44149 6.77968,-15.22074 15.22074,-15.22074 8.44234,0 15.22159,6.77925 15.22159,15.22074 -4.2e-4,8.44149 -6.77968,15.22159 -15.22159,15.22159 z m 0,-24.65992 c -5.31688,0 -8.77377,4.25427 -8.77377,9.43833 0,5.18364 3.45689,9.43833 8.77377,9.43833 5.31731,0 8.77504,-4.25469 8.77504,-9.43833 -4.2e-4,-5.18406 -3.45773,-9.43833 -8.77504,-9.43833 z"
+ id="path13"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 412.66183,380.36574 c -4.45963,0 -7.40966,1.319 -10.01391,4.62956 l -0.24036,-1.53995 0,0 c -0.20198,-1.60743 -1.57326,-2.84926 -3.23382,-2.84926 -1.80139,0 -3.26206,1.459 -3.26206,3.26081 0,0.003 0,0.005 0,0.008 l 0,0 0,0.003 0,0 0,23.40712 c 0,1.79464 1.46194,3.25743 3.257,3.25743 1.79465,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-12.56209 c 0,-5.71621 4.98502,-8.57432 10.23613,-8.57432 1.59519,0 2.85726,-1.32953 2.85726,-2.92515 0,-1.59561 -1.26207,-2.85726 -2.85768,-2.85726 z"
+ id="path15"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 447.02614,395.58648 c 0.0666,-8.17541 -5.78326,-15.22074 -15.222,-15.22074 -8.44192,0 -15.28779,6.77925 -15.28779,15.22074 0,8.44191 6.64684,15.22159 14.68985,15.22159 4.01434,0 7.62682,-2.06621 9.23846,-4.22518 l 0.79359,2.01434 0,0 c 0.42589,1.13177 1.5176,1.93717 2.7978,1.93717 1.65001,0 2.98756,-1.33671 2.99009,-2.98545 l 0,0 0,-7.80687 0,0 0,-4.1556 z m -15.222,9.43833 c -5.31773,0 -8.77419,-4.25469 -8.77419,-9.43833 0,-5.18406 3.45604,-9.43833 8.77419,-9.43833 5.3173,0 8.77419,4.25427 8.77419,9.43833 0,5.18364 -3.45689,9.43833 -8.77419,9.43833 z"
+ id="path17"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 355.01479,368.3337 c 0,-1.7938 -1.46194,-3.18997 -3.25659,-3.18997 -1.79422,0 -3.25743,1.39659 -3.25743,3.18997 l 0,17.1499 c -1.66097,-3.05756 -5.25026,-5.11786 -9.50495,-5.11786 -8.64052,0 -14.42336,6.51318 -14.42336,15.22074 0,8.70757 5.98229,15.22159 14.42336,15.22159 3.76555,0 7.03057,-1.55429 8.98587,-4.25554 l 0.72317,1.83428 c 0.44782,1.25912 1.64917,2.16024 3.06051,2.16024 1.78621,0 3.24984,-1.45435 3.24984,-3.24815 0,-0.005 0,-0.009 0,-0.0139 l 0,0 0,-38.95128 -4.2e-4,0 z m -15.22116,36.69111 c -5.31731,0 -8.70715,-4.25469 -8.70715,-9.43833 0,-5.18406 3.38984,-9.43833 8.70715,-9.43833 5.31773,0 8.70714,4.0544 8.70714,9.43833 0,5.38309 -3.38941,9.43833 -8.70714,9.43833 z"
+ id="path19"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 287.21553,365.34023 c -0.59414,-0.0877 -1.19966,-0.13198 -1.80097,-0.13198 -6.73118,0 -12.20746,5.4767 -12.20746,12.20788 l 0,3.8132 -3.98903,0 c -1.46237,0 -2.65908,1.19671 -2.65908,2.65781 0,1.46321 1.19671,2.93738 2.65908,2.93738 l 3.98819,0 0,20.46004 c 0,1.79464 1.46236,3.25743 3.25658,3.25743 1.79507,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-20.46004 4.40986,0 c 1.46194,0 2.65823,-1.47417 2.65823,-2.93738 0,-1.46152 -1.19629,-2.65823 -2.65823,-2.65823 l -4.40733,0 0,-3.8132 c 0,-3.13852 2.55323,-6.11469 5.69175,-6.11469 0.28294,0 0.56757,0.0211 0.84672,0.062 1.78031,0.26355 3.4358,-0.54269 3.70019,-2.32342 0.2627,-1.77904 -0.96606,-3.43538 -2.74594,-3.69935 z"
+ id="path21"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 482.01243,363.57426 c 0,-10.06788 -8.16108,-18.22938 -18.22897,-18.22938 -10.06282,0 -18.22179,8.15475 -18.22854,18.21631 l -4.2e-4,-4.2e-4 0,14.1071 4.2e-4,4.2e-4 c 0.005,2.28463 1.85832,4.13409 4.14463,4.13409 0.007,0 0.0127,-8.4e-4 0.0194,-8.4e-4 l 0.001,8.4e-4 14.07083,0 0,0 c 10.06409,-0.004 18.22138,-8.16276 18.22138,-18.22812 z"
+ id="path25"
+ style="fill:#294172" />
+ <path
+ d="m 469.13577,349.66577 c -4.72528,0 -8.55576,3.83049 -8.55576,8.55577 0,0.002 0,0.004 0,0.006 l 0,4.52836 -4.51444,0 c -8.5e-4,0 -8.5e-4,0 -0.001,0 -4.72528,0 -8.55576,3.81193 -8.55576,8.53678 0,4.72528 3.83048,8.55577 8.55576,8.55577 4.72486,0 8.55534,-3.83049 8.55534,-8.55577 0,-0.002 0,-0.004 0,-0.006 l 0,-4.54733 4.51444,0 c 8.5e-4,0 0.001,0 0.002,0 4.72486,0 8.55534,-3.79296 8.55534,-8.51781 0,-4.72528 -3.83048,-8.55577 -8.55534,-8.55577 z m -8.55576,21.63483 c -0.004,2.48998 -2.02446,4.50811 -4.51571,4.50811 -2.49378,0 -4.53426,-2.02193 -4.53426,-4.5157 0,-2.49421 2.04048,-4.55366 4.53426,-4.55366 0.002,0 0.004,4.2e-4 0.006,4.2e-4 l 3.86971,0 c 0.001,0 0.002,-4.2e-4 0.003,-4.2e-4 0.35209,0 0.63799,0.28505 0.63799,0.63715 0,4.2e-4 -4.2e-4,8.4e-4 -4.2e-4,0.001 l 0,3.92284 -4.2e-4,0 z m 8.55534,-8.5448 c -0.001,0 -0.003,0 -0.004,0 l -3.87223,0 c -8.4e-4,0 -0.002,0 -0.002,0 -0.35252,0 -0.63757,-0.28506 -0.63757,-0.63758 l 0,-4.2e-4 0,-3.90343 c 0.004,-2.49083 2.02
446,-4.50854 4.51571,-4.50854 2.49378,0 4.53468,2.02193 4.53468,4.51613 4.2e-4,2.49336 -2.04048,4.53384 -4.53426,4.53384 z"
+ id="path29"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 460.58001,362.7558 0,-4.52836 c 0,-0.002 0,-0.004 0,-0.006 0,-4.72528 3.83048,-8.55577 8.55576,-8.55577 0.71685,0 1.22623,0.0805 1.88952,0.25469 0.96774,0.25385 1.75796,1.04618 1.75838,1.96922 4.2e-4,1.11575 -0.80919,1.92621 -2.0194,1.92621 -0.57642,0 -0.78473,-0.11048 -1.62892,-0.11048 -2.49125,0 -4.51149,2.01771 -4.51571,4.50854 l 0,3.90385 0,4.2e-4 c 0,0.35252 0.28505,0.63758 0.63757,0.63758 4.3e-4,0 0.001,0 0.002,0 l 2.96521,0 c 1.10521,0 1.99747,0.88467 1.99832,1.99283 0,1.10816 -0.89353,1.99114 -1.99832,1.99114 l -3.60489,0 0,4.54733 c 0,0.002 0,0.004 0,0.006 0,4.72485 -3.83048,8.55534 -8.55534,8.55534 -0.71684,0 -1.22623,-0.0805 -1.88952,-0.25469 -0.96774,-0.25343 -1.75838,-1.04618 -1.7588,-1.9688 0,-1.11575 0.80919,-1.92663 2.01982,-1.92663 0.576,0 0.78473,0.11048 1.6285,0.11048 2.49125,0 4.51191,-2.01771 4.51613,-4.50811 0,0 0,-3.92368 0,-3.9241 0,-0.35168 -0.2859,-0.63673 -0.63799,-0.63673 -4.3e-4,0 -8.5e-4,0 -0.002,0 l -2.96521,-4.2e-4 c -1.10521,0 -1.
99831,-0.88214 -1.99831,-1.9903 -4.3e-4,-1.11533 0.90238,-1.99367 2.01939,-1.99367 l 3.58339,0 0,0 z"
+ id="path31"
+ style="fill:#ffffff" />
+ <path
+ d="m 477.41661,378.55292 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="text6223"
+ style="fill:#294172;enable-background:new" />
+ </g>
+ <path
+ d="m 181.98344,61.675273 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="path2391"
+ style="fill:#294172;enable-background:new" />
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/warning.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/warning.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+ style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1" />
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+ style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1" />
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987 -2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C -2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961 -2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L -2686.7886,1597.753"
+ id="path8038"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346 -2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C -2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346 -2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/watermark-draft.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/yellow.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ABRT-Main_Window.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ABRT-Main_Window.png
new file mode 100644
index 0000000..a3a4b0f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ABRT-Main_Window.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png
new file mode 100644
index 0000000..4d3ef28
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ABRT-plugins.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ABRT-plugins.png
new file mode 100644
index 0000000..88c1947
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ABRT-plugins.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-Authentication.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-Authentication.png
new file mode 100644
index 0000000..f6ba344
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-Authentication.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-Options.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-Options.png
new file mode 100644
index 0000000..4cdea6e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-Options.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-SSSD_Settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-SSSD_Settings.png
new file mode 100644
index 0000000..ed54c8c
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-SSSD_Settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-User_Information.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-User_Information.png
new file mode 100644
index 0000000..f15c4c0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Authentication_Configuration-authconfig-User_Information.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Change_Runtime_Boolean.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Change_Runtime_Boolean.png
new file mode 100644
index 0000000..307fb1d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Change_Runtime_Boolean.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/FirefoxWithKerberosSSO.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/FirefoxWithKerberosSSO.png
new file mode 100644
index 0000000..20fca1e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/FirefoxWithKerberosSSO.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-Software_Log_Viewer.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-Software_Log_Viewer.png
new file mode 100644
index 0000000..b65257d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-Software_Log_Viewer.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-Software_Update_Preferences.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-Software_Update_Preferences.png
new file mode 100644
index 0000000..200c773
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-Software_Update_Preferences.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-add_remove_software.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-add_remove_software.png
new file mode 100644
index 0000000..ceca3e0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-add_remove_software.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-additional_updates.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-additional_updates.png
new file mode 100644
index 0000000..a4998b9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-additional_updates.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-authenticate.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-authenticate.png
new file mode 100644
index 0000000..5276c79
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-authenticate.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-filters-only_available.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-filters-only_available.png
new file mode 100644
index 0000000..62848c3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-filters-only_available.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-filters-only_end_user.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-filters-only_end_user.png
new file mode 100644
index 0000000..eee440c
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-filters-only_end_user.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-htop.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-htop.png
new file mode 100644
index 0000000..c5a7357
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-htop.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-install.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-install.png
new file mode 100644
index 0000000..9a0d4c4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-install.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-installing_a_package_group.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-installing_a_package_group.png
new file mode 100644
index 0000000..e5035a9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-installing_a_package_group.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-removal_in_progress.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-removal_in_progress.png
new file mode 100644
index 0000000..c439981
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-removal_in_progress.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-remove.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-remove.png
new file mode 100644
index 0000000..0131330
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-remove.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-removing_a_package.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-removing_a_package.png
new file mode 100644
index 0000000..e6043a9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-removing_a_package.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-software_update.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-software_update.png
new file mode 100644
index 0000000..e181637
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-software_update.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-updates_available.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-updates_available.png
new file mode 100644
index 0000000..3a0128a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Graphical_Package_Management-updates_available.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Load_New_Policy.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Load_New_Policy.png
new file mode 100644
index 0000000..cd98e04
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Load_New_Policy.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png
new file mode 100644
index 0000000..e5c7782
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png
new file mode 100644
index 0000000..218ef23
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Connect_automatically.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Connect_automatically.png
new file mode 100644
index 0000000..7be39e5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Connect_automatically.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-IPv4_Settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-IPv4_Settings.png
new file mode 100644
index 0000000..f7d08b6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-IPv4_Settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-Wired.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-Wired.png
new file mode 100644
index 0000000..c2333ff
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-Wired.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png
new file mode 100644
index 0000000..60dee58
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png
new file mode 100644
index 0000000..d26d73a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Addresses.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Addresses.png
new file mode 100644
index 0000000..4c7cdce
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Addresses.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DHCP_Client_ID.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DHCP_Client_ID.png
new file mode 100644
index 0000000..377c12e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DHCP_Client_ID.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DNS_Servers.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DNS_Servers.png
new file mode 100644
index 0000000..b237513
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DNS_Servers.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Method.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Method.png
new file mode 100644
index 0000000..f8a34ec
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Method.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Routes.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Routes.png
new file mode 100644
index 0000000..b19e4dd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Routes.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Search_domains.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Search_domains.png
new file mode 100644
index 0000000..fd07c37
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Search_domains.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings.png
new file mode 100644
index 0000000..0189e20
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png
new file mode 100644
index 0000000..de27930
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-System_eth0-Routes.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-System_eth0-Routes.png
new file mode 100644
index 0000000..d7cbd30
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-System_eth0-Routes.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png
new file mode 100644
index 0000000..56baee0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png
new file mode 100644
index 0000000..be2b3f3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-applet_states.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-applet_states.png
new file mode 100644
index 0000000..9b7b776
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-applet_states.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png
new file mode 100644
index 0000000..7c979c8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png
new file mode 100644
index 0000000..cacaf1a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png
new file mode 100644
index 0000000..2f4c41b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/PS2port.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/PS2port.png
new file mode 100644
index 0000000..c1ef70b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/PS2port.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/SCLogin.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/SCLogin.png
new file mode 100644
index 0000000..5bdef58
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/SCLogin.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/SCLoginEnrollment.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/SCLoginEnrollment.png
new file mode 100644
index 0000000..2809b32
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/SCLoginEnrollment.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/SELinux_Decision_Process.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/SELinux_Decision_Process.png
new file mode 100644
index 0000000..acd0883
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/SELinux_Decision_Process.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Screenshot-1.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Screenshot-1.png
new file mode 100644
index 0000000..ab08c32
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Screenshot-1.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Screenshot-2.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Screenshot-2.png
new file mode 100644
index 0000000..fb95149
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Screenshot-2.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Users_Groups-Create_New_User.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Users_Groups-Create_New_User.png
new file mode 100644
index 0000000..8b8a6c1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Users_Groups-Create_New_User.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Users_Groups-User_Manager.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Users_Groups-User_Manager.png
new file mode 100644
index 0000000..c314821
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/Users_Groups-User_Manager.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-01.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-01.png
new file mode 100644
index 0000000..5d3952e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-01.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-02.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-02.png
new file mode 100644
index 0000000..5f0bb11
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-02.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-03.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-03.png
new file mode 100644
index 0000000..ff0eb87
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-03.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-04.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-04.png
new file mode 100644
index 0000000..1de182b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-04.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-05.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-05.png
new file mode 100644
index 0000000..4f2fa66
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-05.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-06.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-06.png
new file mode 100644
index 0000000..35bf2f3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-06.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-07.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-07.png
new file mode 100644
index 0000000..4da6ddf
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apache-mod_ssl-genkey-07.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apol-DIF.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apol-DIF.png
new file mode 100644
index 0000000..f8bcb41
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apol-DIF.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apol-TE-rule-search.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apol-TE-rule-search.png
new file mode 100644
index 0000000..1a063ed
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apol-TE-rule-search.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apol-plain.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apol-plain.png
new file mode 100644
index 0000000..a7415e8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/apol-plain.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/arrow.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/arrow.png
new file mode 100644
index 0000000..e4cc965
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/arrow.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/auth-panel.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/auth-panel.png
new file mode 100644
index 0000000..6335d2f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/auth-panel.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig-auth.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig-auth.png
new file mode 100644
index 0000000..c219198
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig-auth.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig-options.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig-options.png
new file mode 100644
index 0000000..5ed80b8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig-options.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig-user-info.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig-user-info.png
new file mode 100644
index 0000000..97b8689
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig-user-info.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig_LDAP_kerb.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig_LDAP_kerb.png
new file mode 100644
index 0000000..0da191d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig_LDAP_kerb.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig_advanced.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig_advanced.png
new file mode 100644
index 0000000..1fa30ce
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authconfig_advanced.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authentication_configuration.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authentication_configuration.png
new file mode 100644
index 0000000..ea48230
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authentication_configuration.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authicon.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authicon.png
new file mode 100644
index 0000000..e397b63
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/authicon.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/bugworkflow_new4.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/bugworkflow_new4.png
new file mode 100644
index 0000000..29151dd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/bugworkflow_new4.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/bugworkflow_old8.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/bugworkflow_old8.png
new file mode 100644
index 0000000..64025b2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/bugworkflow_old8.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-authentication.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-authentication.png
new file mode 100644
index 0000000..2e84f56
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-authentication.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-ntsysv.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-ntsysv.png
new file mode 100644
index 0000000..70bc146
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-ntsysv.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_configuration.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_configuration.png
new file mode 100644
index 0000000..ea3a46b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_configuration.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_disabled.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_disabled.png
new file mode 100644
index 0000000..3dceb52
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_disabled.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_enabled.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_enabled.png
new file mode 100644
index 0000000..dec0092
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_enabled.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_running.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_running.png
new file mode 100644
index 0000000..c2d1ca0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_running.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_selected.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_selected.png
new file mode 100644
index 0000000..13d5262
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_selected.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_stopped.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_stopped.png
new file mode 100644
index 0000000..bd9e1a8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_stopped.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_unknown.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_unknown.png
new file mode 100644
index 0000000..94dc930
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_unknown.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_wrong.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_wrong.png
new file mode 100644
index 0000000..f59ef68
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/controlling-access-to-services-service_wrong.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-authentication.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-authentication.png
new file mode 100644
index 0000000..97bd72d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-authentication.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-date_and_time.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-date_and_time.png
new file mode 100644
index 0000000..0c5c375
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-date_and_time.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-network_time_protocol.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-network_time_protocol.png
new file mode 100644
index 0000000..dac02af
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-network_time_protocol.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-time_zone.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-time_zone.png
new file mode 100644
index 0000000..33f305b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/date-and-time-time_zone.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/devicemngr.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/devicemngr.png
new file mode 100644
index 0000000..9709a00
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/devicemngr.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/display-dualhead.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/display-dualhead.png
new file mode 100644
index 0000000..8e5ddc6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/display-dualhead.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/display-hardware.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/display-hardware.png
new file mode 100644
index 0000000..1afbfb8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/display-hardware.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/display-settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/display-settings.png
new file mode 100644
index 0000000..dff2b43
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/display-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/flask-arch.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/flask-arch.png
new file mode 100644
index 0000000..3b560a4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/flask-arch.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/flow-diagram.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/flow-diagram.png
new file mode 100644
index 0000000..e693600
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/flow-diagram.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-print-manager-list.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-print-manager-list.png
new file mode 100644
index 0000000..b217335
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-print-manager-list.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-print-manager.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-print-manager.png
new file mode 100644
index 0000000..61c6aee
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-print-manager.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-print-queue.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-print-queue.png
new file mode 100644
index 0000000..0fb401b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-print-queue.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-system-monitor-filesystems.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-system-monitor-filesystems.png
new file mode 100644
index 0000000..78544f6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-system-monitor-filesystems.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-system-monitor-memory.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-system-monitor-memory.png
new file mode 100644
index 0000000..adddecb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-system-monitor-memory.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-system-monitor-processes.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-system-monitor-processes.png
new file mode 100644
index 0000000..a423370
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/gnome-system-monitor-processes.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/group-new.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/group-new.png
new file mode 100644
index 0000000..a9ad250
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/group-new.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/group-properties.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/group-properties.png
new file mode 100644
index 0000000..2fd40e4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/group-properties.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-directories-add.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-directories-add.png
new file mode 100644
index 0000000..6ae3fa1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-directories-add.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-directories.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-directories.png
new file mode 100644
index 0000000..3f9a08a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-directories.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-environment.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-environment.png
new file mode 100644
index 0000000..01e7b3f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-environment.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-general-options.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-general-options.png
new file mode 100644
index 0000000..a6be6ef
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-general-options.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-listen.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-listen.png
new file mode 100644
index 0000000..dc8d3fb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-listen.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-logging.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-logging.png
new file mode 100644
index 0000000..adc3abc
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-logging.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-main.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-main.png
new file mode 100644
index 0000000..a081a27
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-main.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-server.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-server.png
new file mode 100644
index 0000000..3cdb10f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-server.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-siteconfig.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-siteconfig.png
new file mode 100644
index 0000000..3b9d2f3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-siteconfig.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-tuning.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-tuning.png
new file mode 100644
index 0000000..4013cb9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-tuning.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-virtualhosts-ssl.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-virtualhosts-ssl.png
new file mode 100644
index 0000000..1e5a82b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-virtualhosts-ssl.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-virtualhosts.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-virtualhosts.png
new file mode 100644
index 0000000..9817274
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/httpd-virtualhosts.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/hwbrowser.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/hwbrowser.png
new file mode 100644
index 0000000..d3a44d8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/hwbrowser.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/icon-greencheck-pkgs.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/icon-greencheck-pkgs.png
new file mode 100644
index 0000000..961ba23
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/icon-greencheck-pkgs.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/icon-install-prep.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/icon-install-prep.png
new file mode 100644
index 0000000..877f768
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/icon-install-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/icon-removal-prep.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/icon-removal-prep.png
new file mode 100644
index 0000000..da5833e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/icon-removal-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/image_needed.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/image_needed.png
new file mode 100644
index 0000000..9c179f0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/image_needed.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/individual-pkgs.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/individual-pkgs.png
new file mode 100644
index 0000000..ce1b35d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/individual-pkgs.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/install-depend-prep.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/install-depend-prep.png
new file mode 100644
index 0000000..270046d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/install-depend-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/install-prep.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/install-prep.png
new file mode 100644
index 0000000..ffb480b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/install-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
new file mode 100644
index 0000000..190a06c
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
new file mode 100644
index 0000000..24638bf
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
new file mode 100644
index 0000000..031750e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png
new file mode 100644
index 0000000..a5cb44a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration.png
new file mode 100644
index 0000000..e2099b1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/kdump-kernel_dump_configuration.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-applet-addition.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-applet-addition.png
new file mode 100644
index 0000000..c3398d9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-applet-addition.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-applet-observation.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-applet-observation.png
new file mode 100644
index 0000000..fd74dd6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-applet-observation.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-applet-selection.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-applet-selection.png
new file mode 100644
index 0000000..1896a2e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-applet-selection.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-break-take.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-break-take.png
new file mode 100644
index 0000000..94a8ee2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-break-take.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-break.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-break.png
new file mode 100644
index 0000000..23c127f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-break.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-default.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-default.png
new file mode 100644
index 0000000..87143db
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-default.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-new.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-new.png
new file mode 100644
index 0000000..2976104
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-new.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-prioritize.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-prioritize.png
new file mode 100644
index 0000000..69d8c31
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-prioritize.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-separate.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-separate.png
new file mode 100644
index 0000000..7b2c9e1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-separate.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-test.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-test.png
new file mode 100644
index 0000000..3b2c6ef
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts-test.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts.png
new file mode 100644
index 0000000..82fc603
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/keyboard-configuration-layouts.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvg.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvg.png
new file mode 100644
index 0000000..c7a6719
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvg.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-auto-config.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-auto-config.png
new file mode 100644
index 0000000..bb8d7e4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-auto-config.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main1.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main1.png
new file mode 100644
index 0000000..b31935d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main1.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main10.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main10.png
new file mode 100644
index 0000000..d69338d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main10.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main12.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main12.png
new file mode 100644
index 0000000..e52b865
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main12.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main13.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main13.png
new file mode 100644
index 0000000..5dfb234
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main13.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main14.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main14.png
new file mode 100644
index 0000000..29679e9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main14.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main15.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main15.png
new file mode 100644
index 0000000..aaf3437
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main15.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main16.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main16.png
new file mode 100644
index 0000000..c621f91
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main16.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main17.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main17.png
new file mode 100644
index 0000000..3592633
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main17.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main18.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main18.png
new file mode 100644
index 0000000..b249b29
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main18.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main2.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main2.png
new file mode 100644
index 0000000..262b114
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main2.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main21.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main21.png
new file mode 100644
index 0000000..00bd4f9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main21.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main23.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main23.png
new file mode 100644
index 0000000..9b44669
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main23.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main26.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main26.png
new file mode 100644
index 0000000..bb6bff0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main26.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main27.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main27.png
new file mode 100644
index 0000000..6948d82
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main27.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main28.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main28.png
new file mode 100644
index 0000000..fc8707d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main28.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main3.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main3.png
new file mode 100644
index 0000000..9d219c4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main3.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main30.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main30.png
new file mode 100644
index 0000000..6a7c34b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main30.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main31.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main31.png
new file mode 100644
index 0000000..5d35af5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main31.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main32.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main32.png
new file mode 100644
index 0000000..84b6b88
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main32.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main33.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main33.png
new file mode 100644
index 0000000..cda6747
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main33.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main34.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main34.png
new file mode 100644
index 0000000..9e5fe58
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main34.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main36.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main36.png
new file mode 100644
index 0000000..9c71571
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main36.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main7.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main7.png
new file mode 100644
index 0000000..7c9f09a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-main7.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-boot.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-boot.png
new file mode 100644
index 0000000..6a0b6bc
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-boot.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-done.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-done.png
new file mode 100644
index 0000000..8735895
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-done.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-free.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-free.png
new file mode 100644
index 0000000..27ce579
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-free.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-lv.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-lv.png
new file mode 100644
index 0000000..2a39b2e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-lv.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-lvdone.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-lvdone.png
new file mode 100644
index 0000000..7a9f89b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-lvdone.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-postboot.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-postboot.png
new file mode 100644
index 0000000..30a65e5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-postboot.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-pv01.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-pv01.png
new file mode 100644
index 0000000..ea16714
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-pv01.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-pvdone.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-pvdone.png
new file mode 100644
index 0000000..872e47d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-pvdone.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-vg.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-vg.png
new file mode 100644
index 0000000..b6ec9af
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm-manual-vg.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm/lvg.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm/lvg.svg
new file mode 100644
index 0000000..f564769
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm/lvg.svg
@@ -0,0 +1,684 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/"
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://web.resource.org/cc/"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ id="svg2"
+ sodipodi:version="0.32"
+ inkscape:version="0.45+devel"
+ width="500"
+ height="262"
+ version="1.0"
+ sodipodi:docbase="/home/andy/Desktop"
+ sodipodi:docname="lvg.svg"
+ inkscape:export-filename="/home/andy/Build/RedHat/Deployment_Guide/en-US/images/lvmintro/lvg.png"
+ inkscape:export-xdpi="90"
+ inkscape:export-ydpi="90"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ sodipodi:modified="true">
+ <metadata
+ id="metadata7">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <defs
+ id="defs5">
+ <linearGradient
+ id="linearGradient3987">
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:0"
+ offset="0"
+ id="stop3989" />
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:1"
+ offset="1"
+ id="stop3991" />
+ </linearGradient>
+ <radialGradient
+ cx="265"
+ cy="789.56696"
+ r="265"
+ fx="265"
+ fy="789.56696"
+ id="radialGradient4023"
+ xlink:href="#linearGradient3987"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.886887,0,0,1.602074,-235.025,-437.5826)" />
+ <pattern
+ patternUnits="userSpaceOnUse"
+ width="32"
+ height="32"
+ id="white-spots"
+ patternTransform="matrix(0.375,0,0,0.375,379,400)">
+ <g
+ inkscape:label="#g3035"
+ id="white-spot"
+ transform="translate(-484.3997,-513.505)">
+ <path
+ sodipodi:nodetypes="czzzz"
+ d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z "
+ id="path3033"
+ style="opacity:0.3;fill:white" />
+ </g>
+ </pattern>
+ <pattern
+ xlink:href="#white-spots"
+ id="pattern4015"
+ patternTransform="matrix(0.375,0,0,0.375,379,437.7952)" />
+ <pattern
+ xlink:href="#pattern4015"
+ id="pattern4062"
+ patternTransform="matrix(0.3975,0,0,0.644084,0.7397418,648.83735)" />
+ <marker
+ inkscape:stockid="TriangleOutM"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="TriangleOutM"
+ style="overflow:visible">
+ <path
+ id="path3238"
+ d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z "
+ style="fill:#5c5c4f;fill-rule:evenodd;stroke-width:1pt;marker-start:none"
+ transform="scale(0.4,0.4)" />
+ </marker>
+ <linearGradient
+ x1="200.7363"
+ y1="100.4028"
+ x2="211.99519"
+ y2="89.143997"
+ id="XMLID_3298_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#bfbfbf;stop-opacity:1"
+ offset="0"
+ id="stop20103" />
+ <stop
+ style="stop-color:#f2f2f2;stop-opacity:1"
+ offset="1"
+ id="stop20105" />
+ <a:midPointStop
+ style="stop-color:#BFBFBF"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#BFBFBF"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#F2F2F2"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="200.7363"
+ y1="100.4028"
+ x2="211.99519"
+ y2="89.143997"
+ id="linearGradient36592"
+ xlink:href="#XMLID_3298_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="181.2925"
+ y1="110.8481"
+ x2="192.6369"
+ y2="99.5037"
+ id="XMLID_3297_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0"
+ id="stop20096" />
+ <stop
+ style="stop-color:#ccc;stop-opacity:1"
+ offset="1"
+ id="stop20098" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#CCCCCC"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="181.2925"
+ y1="110.8481"
+ x2="192.6369"
+ y2="99.5037"
+ id="linearGradient36595"
+ xlink:href="#XMLID_3297_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="211.77589"
+ y1="105.7749"
+ x2="212.6619"
+ y2="108.2092"
+ id="XMLID_3296_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#0f6124;stop-opacity:1"
+ offset="0"
+ id="stop20087" />
+ <stop
+ style="stop-color:#219630;stop-opacity:1"
+ offset="1"
+ id="stop20089" />
+ <a:midPointStop
+ style="stop-color:#0F6124"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#0F6124"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#219630"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="211.77589"
+ y1="105.7749"
+ x2="212.6619"
+ y2="108.2092"
+ id="linearGradient36677"
+ xlink:href="#XMLID_3296_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="208.9834"
+ y1="116.8296"
+ x2="200.0811"
+ y2="96.834602"
+ id="XMLID_3295_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#b2b2b2;stop-opacity:1"
+ offset="0"
+ id="stop20076" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0.5"
+ id="stop20078" />
+ <stop
+ style="stop-color:white;stop-opacity:1"
+ offset="1"
+ id="stop20080" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="208.9834"
+ y1="116.8296"
+ x2="200.0811"
+ y2="96.834602"
+ id="linearGradient36604"
+ xlink:href="#XMLID_3295_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="195.5264"
+ y1="97.911102"
+ x2="213.5213"
+ y2="115.9061"
+ id="XMLID_3294_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#ccc;stop-opacity:1"
+ offset="0"
+ id="stop20069" />
+ <stop
+ style="stop-color:white;stop-opacity:1"
+ offset="1"
+ id="stop20071" />
+ <a:midPointStop
+ style="stop-color:#CCCCCC"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#CCCCCC"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="195.5264"
+ y1="97.911102"
+ x2="213.5213"
+ y2="115.9061"
+ id="linearGradient36607"
+ xlink:href="#XMLID_3294_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="186.1938"
+ y1="109.1343"
+ x2="206.6881"
+ y2="88.639999"
+ id="XMLID_3293_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#b2b2b2;stop-opacity:1"
+ offset="0"
+ id="stop20056" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0.16850001"
+ id="stop20058" />
+ <stop
+ style="stop-color:white;stop-opacity:1"
+ offset="0.23029999"
+ id="stop20060" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0.2809"
+ id="stop20062" />
+ <stop
+ style="stop-color:#c2c2c2;stop-opacity:1"
+ offset="0.5"
+ id="stop20064" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.1685" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.2303" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.2809" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#C2C2C2"
+ offset="0.5" />
+ </linearGradient>
+ <linearGradient
+ x1="186.1938"
+ y1="109.1343"
+ x2="206.6881"
+ y2="88.639999"
+ id="linearGradient36610"
+ xlink:href="#XMLID_3293_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="184.8569"
+ y1="112.2676"
+ x2="211.94099"
+ y2="89.541397"
+ id="XMLID_3292_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#b2b2b2;stop-opacity:1"
+ offset="0"
+ id="stop20043" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0.16850001"
+ id="stop20045" />
+ <stop
+ style="stop-color:white;stop-opacity:1"
+ offset="0.23029999"
+ id="stop20047" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0.2809"
+ id="stop20049" />
+ <stop
+ style="stop-color:#ccc;stop-opacity:1"
+ offset="1"
+ id="stop20051" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.1685" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.2303" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.2809" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#CCCCCC"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="184.8569"
+ y1="112.2676"
+ x2="211.94099"
+ y2="89.541397"
+ id="linearGradient36613"
+ xlink:href="#XMLID_3292_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2887,-113.1416)" />
+ </defs>
+ <sodipodi:namedview
+ inkscape:window-height="680"
+ inkscape:window-width="1067"
+ inkscape:pageshadow="0"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ inkscape:zoom="1"
+ inkscape:cx="254.22455"
+ inkscape:cy="51.82077"
+ inkscape:window-x="1763"
+ inkscape:window-y="162"
+ inkscape:current-layer="svg2" />
+ <g
+ transform="matrix(0.9433962,0,0,0.5822222,0,-350.70864)"
+ id="background">
+ <rect
+ width="530"
+ height="450"
+ rx="21.200001"
+ ry="34.351147"
+ x="0"
+ y="602.36218"
+ style="fill:#e3dcc0"
+ id="rect1933" />
+ <rect
+ width="530"
+ height="450"
+ rx="21.200001"
+ ry="34.351147"
+ x="0"
+ y="602.36218"
+ style="fill:url(#pattern4062);fill-opacity:1"
+ id="rect3092" />
+ <rect
+ width="530"
+ height="450"
+ rx="21.200001"
+ ry="34.351147"
+ x="0"
+ y="602.36218"
+ style="fill:url(#radialGradient4023);fill-opacity:1"
+ id="rect3985" />
+ </g>
+ <g
+ transform="matrix(1.13733,0,0,1.13733,42.68492,14.4921)"
+ id="g36679">
+ <path
+ d="M 14.068171,35.701824 L -2.3269574,19.911437 C -2.487957,19.728132 -2.5818734,19.479362 -2.5818734,19.178218 L -2.5818734,10.379595 C -2.5818734,9.62019 -1.9512916,8.847691 -1.1597102,8.651294 L 26.652975,1.9344875 C 27.135974,1.8166488 27.55189,1.9475807 27.806806,2.2356309 L 44.175102,17.986738 C 44.362933,18.222415 44.45685,18.458093 44.45685,18.746143 L 44.45685,27.544767 C 44.45685,28.304172 43.826268,29.07667 43.034687,29.273068 L 15.222002,35.989874 C 14.739003,36.09462 14.323087,35.976781 14.068171,35.701824 z "
+ style="fill:url(#linearGradient36613);stroke:#000000;stroke-width:2.66666627;stroke-miterlimit:3.86369991;stroke-dasharray:none"
+ id="path20053" />
+ <path
+ d="M 14.068181,35.701818 L -2.3269553,19.911433 C -2.4879549,19.728128 -2.5818714,19.479358 -2.5818714,19.178215 L -2.5818714,10.379592 C -2.5818714,9.620187 -1.9512893,8.847689 -1.1597074,8.651291 L 26.65299,1.9344862 C 27.135989,1.8166475 27.551905,1.9475794 27.806821,2.2356295 L 44.215373,18.039107 L 14.068181,35.701818 z "
+ style="fill:url(#linearGradient36610);fill-rule:evenodd"
+ id="path20066" />
+ <path
+ d="M 15.208595,24.41549 L 43.021293,17.698684 C 43.799458,17.51538 44.443456,17.973641 44.443456,18.733046 L 44.443456,27.531669 C 44.443456,28.291073 43.812874,29.063572 43.021293,29.259969 L 15.208595,35.976775 C 14.43043,36.173173 13.786431,35.701818 13.786431,34.942413 L 13.786431,26.143791 C 13.786431,25.384386 14.417014,24.611888 15.208595,24.41549 z "
+ style="fill:url(#linearGradient36607);fill-rule:evenodd"
+ id="path20073" />
+ <path
+ d="M 42.216294,17.318982 C 43.571375,16.965466 44.443456,17.620125 44.443456,19.021096 L 44.443456,27.37455 C 44.443456,28.369633 43.665291,29.286156 42.71271,29.521833 L 16.080677,36.146986 C 15.356179,36.317198 13.853514,36.330291 13.853514,34.628177 L 13.853514,26.091418 C 13.853514,25.096336 14.631679,24.179812 15.584261,23.944135 L 42.216294,17.318982 z M 15.114678,34.981693 C 15.195178,34.981693 15.342762,34.981693 15.570844,34.92932 L 42.216294,28.304167 C 42.752959,28.173235 43.182292,27.610228 43.182292,27.165059 L 43.182292,18.811605 C 43.182292,18.615207 43.182292,18.536648 43.155458,18.471182 C 43.074959,18.471182 42.927376,18.484276 42.71271,18.536648 L 16.06726,25.174895 C 15.530595,25.305827 15.101262,25.868834 15.101262,26.314002 L 15.101262,34.850761 L 15.114678,34.981693 z "
+ style="fill:url(#linearGradient36604)"
+ id="path20082" />
+ <path
+ d="M 38.258384,26.104508 L 40.606297,25.567688 C 42.108961,25.227265 42.108961,27.42692 40.606297,27.767343 L 38.258384,28.304164 C 36.755721,28.65768 36.755721,26.444931 38.258384,26.104508 z "
+ style="fill:url(#linearGradient36677)"
+ id="path20091" />
+ <line
+ stroke-miterlimit="3.8637"
+ x1="38.177872"
+ y1="27.047226"
+ x2="40.431877"
+ y2="26.523495"
+ id="line20093"
+ style="fill:none;stroke:#7cc771;stroke-width:1.14049983;stroke-linecap:round;stroke-miterlimit:3.86369991" />
+ <path
+ d="M -1.5085401,19.361519 L 12.605766,32.533266 L 12.538684,28.160142 C 10.096854,29.286156 -1.5085401,16.598856 -1.5085401,16.598856 L -1.5085401,19.361519 z "
+ style="fill:url(#linearGradient36595);fill-rule:evenodd"
+ id="path20100" />
+ <path
+ d="M 26.89449,3.1390595 L 41.089296,16.402459 L 26.559074,20.251856 C 16.30741,10.968786 18.530549,3.9770231 23.62083,3.9770231 L 26.89449,3.1390595 z "
+ style="fill:url(#linearGradient36592);fill-rule:evenodd"
+ id="path20107" />
+ </g>
+ <use
+ id="use2083"
+ xlink:href="#g36679"
+ y="0"
+ x="0"
+ transform="translate(112,-5.8601806e-6)"
+ width="1"
+ height="1" />
+ <use
+ x="0"
+ y="0"
+ xlink:href="#g36679"
+ id="use2081"
+ transform="translate(236,-5.8601806e-6)"
+ width="500"
+ height="300" />
+ <path
+ sodipodi:nodetypes="cscs"
+ id="path7807"
+ d="M 334.65058,40.941748 L 381.51004,40.941748 C 396.59751,40.941748 404.00181,48.635068 404.00181,64.474428 C 404.00181,64.474428 404.00181,80.068835 404.00181,87.623995"
+ style="fill:none;fill-opacity:0.75;fill-rule:evenodd;stroke:#5c5c4f;stroke-width:1.99999976;stroke-linecap:butt;stroke-linejoin:miter;marker-mid:none;marker-end:url(#TriangleOutM);stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
+ <path
+ style="fill:none;fill-opacity:0.75;fill-rule:evenodd;stroke:#5c5c4f;stroke-width:1.99999976;stroke-linecap:butt;stroke-linejoin:miter;marker-mid:none;marker-end:url(#TriangleOutM);stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ d="M 70.023795,58.110466 C 70.023795,58.110466 70.023795,80.775945 70.023795,88.331105"
+ id="path2203"
+ sodipodi:nodetypes="cs" />
+ <use
+ id="use2209"
+ xlink:href="#path2203"
+ y="0"
+ x="0"
+ transform="translate(113.8442,4.1398194e-6)"
+ width="1"
+ height="1" />
+ <use
+ x="0"
+ y="0"
+ xlink:href="#path2203"
+ id="use2207"
+ transform="translate(230.8704,4.1398194e-6)"
+ width="500"
+ height="300" />
+ <use
+ x="0"
+ y="0"
+ xlink:href="#path2203"
+ id="use2213"
+ transform="translate(114.1978,98.64135)"
+ width="500"
+ height="300" />
+ <use
+ height="300"
+ width="500"
+ transform="matrix(0.965926,-0.258819,0.258819,0.965926,8.0694501,120.38211)"
+ id="use2211"
+ xlink:href="#path2203"
+ y="0"
+ x="0" />
+ <use
+ x="0"
+ y="0"
+ xlink:href="#path2203"
+ id="use2215"
+ transform="matrix(-0.965926,-0.258819,-0.258819,0.965926,358.87684,120.38211)"
+ width="500"
+ height="300" />
+ <use
+ height="300"
+ width="500"
+ transform="translate(367.723,-28.72283)"
+ id="use2225"
+ xlink:href="#rect2217"
+ y="0"
+ x="0" />
+ <g
+ id="g2365"
+ transform="translate(-4.50223,-28.72283)">
+ <rect
+ ry="10"
+ rx="10"
+ y="129.88016"
+ x="15.849242"
+ height="50.91169"
+ width="110.30865"
+ id="rect2217"
+ style="fill:#5c5c4f" />
+ <g
+ transform="translate(-11.80981,18.26833)"
+ id="g2070"
+ style="fill:#ffffff">
+ <text
+ id="text2032"
+ y="132.30888"
+ x="34"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ xml:space="preserve"><tspan
+ y="132.30888"
+ x="34"
+ id="tspan2034"
+ sodipodi:role="line">Physical Volume</tspan></text>
+ <text
+ id="text2052"
+ y="148.54446"
+ x="59.29908"
+ style="font-size:12px;fill:#e3dcc0;font-family:Interstate-Bold"
+ xml:space="preserve"><tspan
+ y="148.54446"
+ x="59.29908"
+ id="tspan2054"
+ sodipodi:role="line"
+ style="font-size:14px;fill:#e3dcc0">100 GB</tspan></text>
+ </g>
+ </g>
+ <use
+ id="use2375"
+ xlink:href="#g2365"
+ y="0"
+ x="0"
+ transform="translate(117.3797,4.1398194e-6)"
+ width="1"
+ height="1" />
+ <use
+ x="0"
+ y="0"
+ xlink:href="#g2365"
+ id="use2373"
+ transform="translate(236.1737,4.1398194e-6)"
+ width="500"
+ height="300" />
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#ffffff;font-family:Interstate-Bold"
+ x="439.05899"
+ y="121.56151"
+ id="text2377"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan2379"
+ x="439.05899"
+ y="121.56151">/boot</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#e3dcc0;font-family:Interstate-Bold"
+ x="438.24738"
+ y="137.79706"
+ id="text2381"
+ sodipodi:linespacing="125%"><tspan
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#e3dcc0;font-family:Interstate-Bold"
+ sodipodi:role="line"
+ id="tspan2383"
+ x="438.24738"
+ y="137.79706">100 MB (ext3)</tspan></text>
+ <g
+ id="g2401"
+ transform="translate(3.983051,-7.5096324)">
+ <rect
+ style="fill:#5c5c4f"
+ id="rect2227"
+ width="245.30865"
+ height="50.91169"
+ x="56.86396"
+ y="207.92432"
+ rx="10"
+ ry="10" />
+ <text
+ sodipodi:linespacing="125%"
+ id="text2389"
+ y="230.8945"
+ x="178.03696"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#ffffff;font-family:Interstate-Bold"
+ xml:space="preserve"><tspan
+ y="230.8945"
+ x="178.03696"
+ id="tspan2391"
+ sodipodi:role="line">Logical Volume Group</tspan></text>
+ <text
+ sodipodi:linespacing="125%"
+ id="text2393"
+ y="247.13007"
+ x="179.57793"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#e3dcc0;font-family:Interstate-Bold"
+ xml:space="preserve"><tspan
+ y="247.13007"
+ x="179.57793"
+ id="tspan2395"
+ sodipodi:role="line"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#e3dcc0;font-family:Interstate-Bold">(100 GB x3) - 100 MB</tspan></text>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm/lvols.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm/lvols.svg
new file mode 100644
index 0000000..a2c6a8f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvm/lvols.svg
@@ -0,0 +1,286 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="385"
+ height="189.99998"
+ id="svg2">
+ <defs
+ id="defs5">
+ <linearGradient
+ id="linearGradient3987">
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:0"
+ offset="0"
+ id="stop3989" />
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:1"
+ offset="1"
+ id="stop3991" />
+ </linearGradient>
+ <radialGradient
+ cx="265"
+ cy="789.56696"
+ r="265"
+ fx="265"
+ fy="789.56696"
+ id="radialGradient4023"
+ xlink:href="#linearGradient3987"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.886887,0,0,1.602074,-235.025,-437.5826)" />
+ <pattern
+ patternTransform="matrix(0.375,0,0,0.375,379,400)"
+ id="white-spots"
+ height="32"
+ width="32"
+ patternUnits="userSpaceOnUse">
+ <g
+ transform="translate(-484.3997,-513.505)"
+ id="white-spot"
+ inkscape:label="#g3035">
+ <path
+ style="opacity:0.3;fill:white"
+ id="path3033"
+ d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z "
+ sodipodi:nodetypes="czzzz" />
+ </g>
+ </pattern>
+ <pattern
+ patternTransform="matrix(0.375,0,0,0.375,379,437.7952)"
+ id="pattern4015"
+ xlink:href="#white-spots" />
+ <pattern
+ patternTransform="matrix(0.5162337,0,0,0.8881579,0.9607077,666.44901)"
+ id="pattern4062"
+ xlink:href="#pattern4015" />
+ <marker
+ refX="0"
+ refY="0"
+ orient="auto"
+ style="overflow:visible"
+ id="TriangleOutM">
+ <path
+ d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z "
+ transform="scale(0.4,0.4)"
+ style="fill:#5c5c4f;fill-rule:evenodd;stroke-width:1pt;marker-start:none"
+ id="path3238" />
+ </marker>
+ </defs>
+ <g
+ transform="matrix(0.7264151,0,0,0.4222222,0,-254.33069)"
+ id="background">
+ <rect
+ width="530"
+ height="450"
+ rx="27.532467"
+ ry="47.368423"
+ x="0"
+ y="602.36218"
+ style="fill:#e3dcc0"
+ id="rect1933" />
+ <rect
+ width="530"
+ height="450"
+ rx="27.532467"
+ ry="47.368423"
+ x="0"
+ y="602.36218"
+ style="fill:url(#pattern4062);fill-opacity:1"
+ id="rect3092" />
+ <rect
+ width="530"
+ height="450"
+ rx="27.532467"
+ ry="47.368423"
+ x="0"
+ y="602.36218"
+ style="fill:url(#radialGradient4023);fill-opacity:1"
+ id="rect3985" />
+ </g>
+ <path
+ d="M 105.47946,31.115562 L 95.96315,31.115562 C 80.875678,31.115562 73.471383,38.808874 73.471383,54.648239 L 73.471383,101.86887"
+ style="fill:none;fill-opacity:0.75;fill-rule:evenodd;stroke:#5c5c4f;stroke-width:1.99999976;stroke-linecap:butt;stroke-linejoin:miter;marker-mid:none;marker-end:url(#TriangleOutM);stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path7807" />
+ <use
+ transform="matrix(-1,0,0,1,388.2247,-4.1430667e-8)"
+ id="use2006"
+ x="0"
+ y="0"
+ width="406"
+ height="198"
+ xlink:href="#path7807" />
+ <path
+ d="M 194.0339,65.254841 L 194.0339,101.86887"
+ style="fill:none;fill-opacity:0.75;fill-rule:evenodd;stroke:#5c5c4f;stroke-width:1.99999976;stroke-linecap:butt;stroke-linejoin:miter;marker-mid:none;marker-end:url(#TriangleOutM);stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path2008" />
+ <g
+ transform="translate(-7.657627,-6.4864229)"
+ id="g2126">
+ <rect
+ width="115"
+ height="60"
+ rx="10"
+ ry="10"
+ x="19.948734"
+ y="115.77461"
+ style="fill:#5c5c4f"
+ id="rect2068" />
+ <g
+ transform="translate(-1.438859,0)"
+ style="fill:#ffffff"
+ id="g2070">
+ <text
+ x="34"
+ y="132.30888"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2032"
+ xml:space="preserve"><tspan
+ x="34"
+ y="132.30888"
+ id="tspan2034">Logical Volume</tspan></text>
+ <text
+ x="59.758186"
+ y="147.5739"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2044"
+ xml:space="preserve"><tspan
+ x="59.758186"
+ y="147.5739"
+ id="tspan2046">/home</tspan></text>
+ <text
+ x="59.29908"
+ y="164.54446"
+ style="font-size:12px;fill:#e3dcc0;font-family:Interstate-Bold"
+ id="text2052"
+ xml:space="preserve"><tspan
+ x="59.29908"
+ y="164.54446"
+ style="font-size:14px;fill:#e3dcc0"
+ id="tspan2054">200 GB</tspan></text>
+ </g>
+ </g>
+ <g
+ transform="translate(-7.657627,-6.4864229)"
+ id="g2117">
+ <use
+ transform="translate(124.2428,0)"
+ style="fill:#5c5c4f"
+ id="use2080"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#rect2068" />
+ <g
+ transform="translate(-5.196065,0)"
+ style="fill:#ffffff"
+ id="g2082">
+ <use
+ transform="translate(128,0)"
+ style="fill:#ffffff"
+ id="use2038"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#text2032" />
+ <text
+ x="204.0676"
+ y="148.44991"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2048"
+ xml:space="preserve"><tspan
+ x="204.0676"
+ y="148.44991"
+ id="tspan2050">/</tspan></text>
+ <text
+ x="192.11157"
+ y="164.54446"
+ style="font-size:12px;fill:#e3dcc0;font-family:Interstate-Bold"
+ id="text2060"
+ xml:space="preserve"><tspan
+ x="192.11157"
+ y="164.54446"
+ style="font-size:14px;fill:#e3dcc0"
+ id="tspan2062">20 GB</tspan></text>
+ </g>
+ </g>
+ <g
+ transform="translate(-7.657627,-6.4864229)"
+ id="g2109">
+ <use
+ transform="translate(248.1945,0)"
+ style="fill:#5c5c4f"
+ id="use2078"
+ x="0"
+ y="0"
+ width="406"
+ height="198"
+ xlink:href="#rect2068" />
+ <g
+ style="fill:#ffffff"
+ id="g2089">
+ <text
+ x="292.99136"
+ y="134.13889"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2040"
+ xml:space="preserve"><tspan
+ x="292.99136"
+ y="134.13889"
+ id="tspan2042">Free Space</tspan></text>
+ <text
+ x="304.35623"
+ y="164.54446"
+ style="font-size:12px;fill:#e3dcc0;font-family:Interstate-Bold"
+ id="text2056"
+ xml:space="preserve"><tspan
+ x="304.35623"
+ y="164.54446"
+ style="font-size:14px;fill:#e3dcc0"
+ id="tspan2058">80 GB</tspan></text>
+ </g>
+ </g>
+ <g
+ transform="translate(-7.657627,-6.4864229)"
+ id="g2101">
+ <rect
+ width="171.15254"
+ height="50.482662"
+ rx="10"
+ ry="10"
+ x="116.11526"
+ y="16.779661"
+ style="fill:#5c5c4f"
+ id="rect1885" />
+ <g
+ transform="translate(-1.047109,0)"
+ style="fill:#ffffff"
+ id="g2095">
+ <text
+ x="139.23997"
+ y="34"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2028"
+ xml:space="preserve"><tspan
+ x="139.23997"
+ y="34"
+ id="tspan2030">Logical Volume Group</tspan></text>
+ <text
+ x="140.57306"
+ y="57.064232"
+ style="font-size:12px;fill:#e3dcc0;font-family:Interstate-Bold"
+ id="text2064"
+ xml:space="preserve"><tspan
+ x="140.57306"
+ y="57.064232"
+ style="font-size:14px;fill:#e3dcc0"
+ id="tspan2066">(100 GB x3) -100MB</tspan></text>
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvols.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvols.png
new file mode 100644
index 0000000..dae912b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/lvols.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/mouseconfig.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/mouseconfig.png
new file mode 100644
index 0000000..52c513b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/mouseconfig.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/n-t-n-ipsec-diagram.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/n-t-n-ipsec-diagram.png
new file mode 100644
index 0000000..281afd6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/n-t-n-ipsec-diagram.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/n-to-n-ipsec-local.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/n-to-n-ipsec-local.png
new file mode 100644
index 0000000..ee306da
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/n-to-n-ipsec-local.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/n-to-n-ipsec-remote.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/n-to-n-ipsec-remote.png
new file mode 100644
index 0000000..48e5beb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/n-to-n-ipsec-remote.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-aliases.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-aliases.png
new file mode 100644
index 0000000..19bb5c0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-aliases.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-dns.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-dns.png
new file mode 100644
index 0000000..e91e5bd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-dns.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-ethernet-settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-ethernet-settings.png
new file mode 100644
index 0000000..0909194
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-ethernet-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-ethernet.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-ethernet.png
new file mode 100644
index 0000000..ec60e62
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-ethernet.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-home-profile.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-home-profile.png
new file mode 100644
index 0000000..39974eb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-home-profile.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-hosts.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-hosts.png
new file mode 100644
index 0000000..2605b7d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-hosts.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-isdn-settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-isdn-settings.png
new file mode 100644
index 0000000..3e1d01d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-isdn-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-isdn.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-isdn.png
new file mode 100644
index 0000000..afa4f42
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-isdn.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-modem-settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-modem-settings.png
new file mode 100644
index 0000000..195df2d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-modem-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-modem.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-modem.png
new file mode 100644
index 0000000..7e10037
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-modem.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-office-profile.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-office-profile.png
new file mode 100644
index 0000000..06f87ec
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-office-profile.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tokenring-settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tokenring-settings.png
new file mode 100644
index 0000000..e66bfc1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tokenring-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tokenring.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tokenring.png
new file mode 100644
index 0000000..36ea52a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tokenring.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tonline1.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tonline1.png
new file mode 100644
index 0000000..4fe97dd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tonline1.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tonlineAcctsetup.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tonlineAcctsetup.png
new file mode 100644
index 0000000..3735a96
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tonlineAcctsetup.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tonlineProvidertab.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tonlineProvidertab.png
new file mode 100644
index 0000000..bcdd369
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-tonlineProvidertab.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-wireless-settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-wireless-settings.png
new file mode 100644
index 0000000..7642a10
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-wireless-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-wireless.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-wireless.png
new file mode 100644
index 0000000..95b7955
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-wireless.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-xdsl-selectdevicetype.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-xdsl-selectdevicetype.png
new file mode 100644
index 0000000..c5d7e1d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-xdsl-selectdevicetype.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-xdsl-settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-xdsl-settings.png
new file mode 100644
index 0000000..fb58da0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-xdsl-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-xdsl.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-xdsl.png
new file mode 100644
index 0000000..1705dae
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat-xdsl.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat.png
new file mode 100644
index 0000000..8a00403
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/neat.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-add.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-add.png
new file mode 100644
index 0000000..2b70a3f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-add.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-general-options.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-general-options.png
new file mode 100644
index 0000000..21bab60
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-general-options.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-server-settings.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-server-settings.png
new file mode 100644
index 0000000..e2f63bd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-server-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-user-access.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-user-access.png
new file mode 100644
index 0000000..5192e64
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/nfs-user-access.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/oprof-start-config.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/oprof-start-config.png
new file mode 100644
index 0000000..32bd5e1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/oprof-start-config.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/oprof-start-setup.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/oprof-start-setup.png
new file mode 100644
index 0000000..06d8719
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/oprof-start-setup.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/originals/Graphical_Package_Management-software_update.xcf b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/originals/Graphical_Package_Management-software_update.xcf
new file mode 100644
index 0000000..0406f95
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/originals/Graphical_Package_Management-software_update.xcf differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/package-selections.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/package-selections.png
new file mode 100644
index 0000000..f9e1ea8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/package-selections.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/pam-icon.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/pam-icon.png
new file mode 100644
index 0000000..4db6046
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/pam-icon.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/print-manager-menu.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/print-manager-menu.png
new file mode 100644
index 0000000..e0625e3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/print-manager-menu.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-add-printer.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-add-printer.png
new file mode 100644
index 0000000..43cc6a2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-add-printer.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config1.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config1.png
new file mode 100644
index 0000000..0e95984
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config1.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config2.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config2.png
new file mode 100644
index 0000000..94a625d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config2.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config3.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config3.png
new file mode 100644
index 0000000..59ba05c
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config3.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config4.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config4.png
new file mode 100644
index 0000000..c4ebdf5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config4.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config5.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config5.png
new file mode 100644
index 0000000..e1b16bb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-config5.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-default-icon.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-default-icon.png
new file mode 100644
index 0000000..da8bfaf
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-default-icon.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-edit.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-edit.png
new file mode 100644
index 0000000..69b148d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-edit.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-ipp.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-ipp.png
new file mode 100644
index 0000000..19029d7
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-ipp.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-jetdirect.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-jetdirect.png
new file mode 100644
index 0000000..aa77195
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-jetdirect.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-local.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-local.png
new file mode 100644
index 0000000..0805ca5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-local.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-lpd.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-lpd.png
new file mode 100644
index 0000000..d9afe31
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-lpd.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-main.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-main.png
new file mode 100644
index 0000000..9bdfdb4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-main.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-ncp.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-ncp.png
new file mode 100644
index 0000000..6a475f0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-ncp.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-queue-name.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-queue-name.png
new file mode 100644
index 0000000..dc3d9a2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-queue-name.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-select-model.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-select-model.png
new file mode 100644
index 0000000..105bd16
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-select-model.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-sharing-general.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-sharing-general.png
new file mode 100644
index 0000000..495c934
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-sharing-general.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-sharing-hosts.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-sharing-hosts.png
new file mode 100644
index 0000000..a470ffa
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-sharing-hosts.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-sharing-queue.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-sharing-queue.png
new file mode 100644
index 0000000..fef0e03
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-sharing-queue.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-smb.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-smb.png
new file mode 100644
index 0000000..c03aec7
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-smb.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-test-page.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-test-page.png
new file mode 100644
index 0000000..41092e5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printconf-test-page.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printer-notification-icon.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printer-notification-icon.png
new file mode 100644
index 0000000..001bb42
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/printer-notification-icon.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-boot-error.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-boot-error.png
new file mode 100644
index 0000000..68df6f2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-boot-error.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-final.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-final.png
new file mode 100644
index 0000000..ffc3c63
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-final.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-free.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-free.png
new file mode 100644
index 0000000..3b98e20
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-free.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-lvm-final.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-lvm-final.png
new file mode 100644
index 0000000..859a2f3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-lvm-final.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-mntpt.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-mntpt.png
new file mode 100644
index 0000000..4a8a8fd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-mntpt.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-add.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-add.png
new file mode 100644
index 0000000..ed278ac
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-add.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-bootready.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-bootready.png
new file mode 100644
index 0000000..898162a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-bootready.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-opt.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-opt.png
new file mode 100644
index 0000000..8e99e92
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-opt.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-opt2.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-opt2.png
new file mode 100644
index 0000000..746b901
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/raid-manual-part-opt2.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-config-packages.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-config-packages.png
new file mode 100644
index 0000000..598ea42
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-config-packages.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-config-users.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-config-users.png
new file mode 100644
index 0000000..ad3d581
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-config-users.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-filter-enable.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-filter-enable.png
new file mode 100644
index 0000000..3c0c2f0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-filter-enable.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-filter-sample.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-filter-sample.png
new file mode 100644
index 0000000..7d349d6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-filter-sample.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-filters.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-filters.png
new file mode 100644
index 0000000..3c91d0d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-filters.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-logviewer-add.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-logviewer-add.png
new file mode 100644
index 0000000..07962eb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-logviewer-add.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-logviewer-monitoring.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-logviewer-monitoring.png
new file mode 100644
index 0000000..01e826b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-logviewer-monitoring.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-logviewer.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-logviewer.png
new file mode 100644
index 0000000..b24be71
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-logviewer.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-optional-packages.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-optional-packages.png
new file mode 100644
index 0000000..6f78f03
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/redhat-optional-packages.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/registering.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/registering.png
new file mode 100644
index 0000000..2d823b4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/registering.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/relevant-errata.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/relevant-errata.png
new file mode 100644
index 0000000..0c22605
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/relevant-errata.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/removal-prep.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/removal-prep.png
new file mode 100644
index 0000000..c187553
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/removal-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/remove-depend-prep.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/remove-depend-prep.png
new file mode 100644
index 0000000..24ddd0a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/remove-depend-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/rh-securitylevel.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/rh-securitylevel.png
new file mode 100644
index 0000000..8775cc8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/rh-securitylevel.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/rhl-common/networkconfig/n-t-n-ipsec-diagram.svg b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/rhl-common/networkconfig/n-t-n-ipsec-diagram.svg
new file mode 100644
index 0000000..c420f0c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/rhl-common/networkconfig/n-t-n-ipsec-diagram.svg
@@ -0,0 +1,658 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/"
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://web.resource.org/cc/"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="600"
+ height="185.99998"
+ id="svg2580"
+ sodipodi:version="0.32"
+ inkscape:version="0.44+devel"
+ sodipodi:docname="n-t-n-ipsec-diagram.svg"
+ sodipodi:docbase="/home/andy/Build/RedHat/Deployment_Guide/en-US/images/rhl-common/networkconfig"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ sodipodi:modified="TRUE"
+ inkscape:export-filename="/home/andy/Build/RedHat/Deployment_Guide/en-US/images/rhl-common/networkconfig/n-t-n-ipsec-diagram.png"
+ inkscape:export-xdpi="90"
+ inkscape:export-ydpi="90">
+ <metadata
+ id="metadata109">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="480"
+ inkscape:window-width="640"
+ inkscape:pageshadow="0"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base" />
+ <defs
+ id="defs3">
+ <radialGradient
+ cx="603.19"
+ cy="230.77"
+ r="1.67"
+ fx="603.19"
+ fy="230.77"
+ id="x5010_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.1,0,0,1.1,-54.33,-75.4)">
+ <stop
+ style="stop-color:#c9ffc9;stop-opacity:1"
+ offset="0"
+ id="stop29201" />
+ <stop
+ style="stop-color:#23a11f;stop-opacity:1"
+ offset="1"
+ id="stop29203" />
+ <a:midPointStop
+ style="stop-color:#C9FFC9"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#C9FFC9"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#23A11F"
+ offset="1" />
+ </radialGradient>
+ <linearGradient
+ x1="601.48999"
+ y1="170.16"
+ x2="613.84003"
+ y2="170.16"
+ id="x5002_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#d9d9d9;stop-opacity:1"
+ offset="0"
+ id="stop29134" />
+ <stop
+ style="stop-color:#ffffff;stop-opacity:1"
+ offset="0.2"
+ id="stop29136" />
+ <stop
+ style="stop-color:#999999;stop-opacity:1"
+ offset="1"
+ id="stop29138" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.20" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#999999"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="592.20001"
+ y1="156.45"
+ x2="609.98999"
+ y2="174.23"
+ id="x5004_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)">
+ <stop
+ style="stop-color:#d9d9d9;stop-opacity:1"
+ offset="0"
+ id="stop29157" />
+ <stop
+ style="stop-color:#ffffff;stop-opacity:1"
+ offset="1"
+ id="stop29159" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="592.31"
+ y1="162.60001"
+ x2="609.32001"
+ y2="145.59"
+ id="x5003_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#f2f2f2;stop-opacity:1"
+ offset="0"
+ id="stop29143" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="1"
+ id="stop29145" />
+ <a:midPointStop
+ style="stop-color:#F2F2F2"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#F2F2F2"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="592.20001"
+ y1="156.45"
+ x2="609.98999"
+ y2="174.24001"
+ id="x5000_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)">
+ <stop
+ style="stop-color:#d9d9d9;stop-opacity:1"
+ offset="0"
+ id="stop29124" />
+ <stop
+ style="stop-color:#ffffff;stop-opacity:1"
+ offset="1"
+ id="stop29126" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="1" />
+ </linearGradient>
+ <pattern
+ xlink:href="#pattern4396"
+ id="pattern4704"
+ patternTransform="matrix(0.4660769,0,0,0.4386606,446.32365,760.68863)" />
+ <pattern
+ xlink:href="#pattern4315"
+ id="pattern4396"
+ patternTransform="matrix(0.361895,0,0,0.361895,41.1944,774.2561)" />
+ <pattern
+ xlink:href="#pattern4038"
+ id="pattern4315"
+ patternTransform="matrix(0.361895,0,0,0.361895,253.6944,752.2561)" />
+ <pattern
+ xlink:href="#pattern4015"
+ id="pattern4062"
+ patternTransform="matrix(0.33125,0,0,0.9072579,0.6164534,667.82716)" />
+ <linearGradient
+ id="linearGradient4054">
+ <stop
+ style="stop-color:#a70000;stop-opacity:0"
+ offset="0"
+ id="stop4056" />
+ <stop
+ style="stop-color:#a70000;stop-opacity:1"
+ offset="1"
+ id="stop4058" />
+ </linearGradient>
+ <pattern
+ patternUnits="userSpaceOnUse"
+ width="32"
+ height="32"
+ id="black-spots"
+ patternTransform="matrix(0.455007,0,0,0.455007,20.99995,116)">
+ <g
+ inkscape:label="#g3039"
+ id="black-spot"
+ transform="translate(-448.3997,-513.505)">
+ <path
+ style="opacity:0.1;fill:black"
+ id="path2961"
+ d="M 473.39967,529.50504 C 473.39967,534.47304 469.36767,538.50504 464.39967,538.50504 C 459.43167,538.50504 455.39967,534.47304 455.39967,529.50504 C 455.39967,524.53704 459.43167,520.50504 464.39967,520.50504 C 469.36767,520.50504 473.39967,524.53704 473.39967,529.50504 z "
+ sodipodi:nodetypes="czzzz" />
+ </g>
+ </pattern>
+ <pattern
+ xlink:href="#black-spots"
+ id="pattern4038"
+ patternTransform="matrix(0.361895,0,0,0.361895,-33.80556,922.2561)" />
+ <pattern
+ xlink:href="#white-spots"
+ id="pattern4015"
+ patternTransform="matrix(0.375,0,0,0.375,379,437.7952)" />
+ <linearGradient
+ id="linearGradient3987">
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:0"
+ offset="0"
+ id="stop3989" />
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:1"
+ offset="1"
+ id="stop3991" />
+ </linearGradient>
+ <pattern
+ patternUnits="userSpaceOnUse"
+ width="32"
+ height="32"
+ id="white-spots"
+ patternTransform="matrix(0.375,0,0,0.375,379,400)">
+ <g
+ inkscape:label="#g3035"
+ id="white-spot"
+ transform="translate(-484.3997,-513.505)">
+ <path
+ sodipodi:nodetypes="czzzz"
+ d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z "
+ id="path3033"
+ style="opacity:0.3;fill:white" />
+ </g>
+ </pattern>
+ <radialGradient
+ cx="265"
+ cy="789.56696"
+ r="265"
+ fx="265"
+ fy="789.56696"
+ id="radialGradient4023"
+ xlink:href="#linearGradient3987"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.886887,0,0,1.602074,-235.025,-437.5826)" />
+ <radialGradient
+ cx="710"
+ cy="668.36218"
+ r="75"
+ fx="710"
+ fy="668.36218"
+ id="radialGradient4393"
+ xlink:href="#linearGradient4054"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.522104,0,0,1.217683,-946.194,60.5088)" />
+ <linearGradient
+ x1="592.20001"
+ y1="156.45"
+ x2="609.98999"
+ y2="174.24001"
+ id="linearGradient2554"
+ xlink:href="#x5000_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
+ <linearGradient
+ x1="592.31"
+ y1="162.60001"
+ x2="609.32001"
+ y2="145.59"
+ id="linearGradient2556"
+ xlink:href="#x5003_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
+ <linearGradient
+ x1="592.20001"
+ y1="156.45"
+ x2="609.98999"
+ y2="174.23"
+ id="linearGradient2558"
+ xlink:href="#x5004_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
+ <linearGradient
+ x1="601.48999"
+ y1="170.16"
+ x2="613.84003"
+ y2="170.16"
+ id="linearGradient2560"
+ xlink:href="#x5002_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
+ <linearGradient
+ x1="592.31"
+ y1="162.60001"
+ x2="609.32001"
+ y2="145.59"
+ id="linearGradient2562"
+ xlink:href="#x5003_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
+ <radialGradient
+ cx="603.19"
+ cy="230.77"
+ r="1.67"
+ fx="603.19"
+ fy="230.77"
+ id="radialGradient2564"
+ xlink:href="#x5010_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.23,0,0,1.23,-709.93,-245.02)" />
+ </defs>
+ <g
+ transform="translate(-8.5872532,-710.1876)"
+ id="layer1">
+ <g
+ transform="matrix(1.1320755,0,0,0.4133333,8.5872532,461.21125)"
+ id="background">
+ <rect
+ width="530"
+ height="450"
+ rx="17.666664"
+ ry="48.387093"
+ x="0"
+ y="602.36218"
+ style="fill:#e3dcc0"
+ id="rect1933" />
+ <rect
+ width="530"
+ height="450"
+ rx="17.666664"
+ ry="48.387093"
+ x="0"
+ y="602.36218"
+ style="fill:url(#pattern4062);fill-opacity:1"
+ id="rect3092" />
+ <rect
+ width="530"
+ height="450"
+ rx="17.666664"
+ ry="48.387093"
+ x="0"
+ y="602.36218"
+ style="fill:url(#radialGradient4023);fill-opacity:1"
+ id="rect3985" />
+ </g>
+ <g
+ transform="translate(248,0)"
+ id="g4070" />
+ <path
+ d="M 129.40054,237.86797 L 472.39401,237.86797"
+ transform="translate(0,602.3622)"
+ style="fill:none;stroke:#5c5c4f;stroke-width:2"
+ id="path3199" />
+ <text
+ x="-753.05115"
+ y="587.36591"
+ transform="matrix(0,-1,1,0,0,0)"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#c8c5ac;font-family:Interstate-Bold"
+ id="text3222"
+ xml:space="preserve"><tspan
+ x="-753.05115"
+ y="587.36591"
+ id="tspan3224">#4592</tspan></text>
+ <path
+ d="M 181.40054,840.23017 C 181.40054,778.65551 260.02962,738.50013 310.35665,840.23017 C 363.5259,739.1693 427.39402,778.43988 427.39402,840.23017"
+ style="fill:none;stroke:#5c5c4f;stroke-width:2"
+ id="path3248" />
+ <g
+ transform="translate(218.38333,751.3446)"
+ id="computer">
+ <path
+ d="M 10.98,7.35 L 10.98,31.17 L 24.76,45.05 C 24.76,45.05 28.25,45.27 31.9,44.16 C 35.55,43.05 36.95,41.49 36.95,41.49 L 36.95,17.46 L 23.59,4.07 L 10.98,7.35 z "
+ style="fill:url(#linearGradient2554)"
+ id="path4802" />
+ <path
+ d="M 36.18,16.79 L 23.61,3.9 L 10.61,7.23 L 24.81,21.11 C 24.81,21.11 28.44,21 31.76,20.11 C 35.07,19.22 37.03,17.66 37.03,17.66 L 36.18,16.79 z "
+ style="fill:url(#linearGradient2556)"
+ id="path4804" />
+ <path
+ d="M 10.98,7.35 L 10.98,31.17 L 24.76,45.05 C 24.76,45.05 28.25,45.27 31.9,44.16 C 35.55,43.05 36.95,41.49 36.95,41.49 L 36.95,17.46 L 23.59,4.07 L 10.98,7.35 z "
+ style="fill:none;stroke:#000000;stroke-width:1.92999995;stroke-linecap:round;stroke-linejoin:round"
+ id="path4806" />
+ <path
+ d="M 10.98,7.35 L 10.98,31.17 L 24.76,45.05 C 24.76,45.05 28.25,45.27 31.9,44.16 C 35.55,43.05 36.95,41.49 36.95,41.49 L 36.95,17.46 L 23.59,4.07 L 10.98,7.35 z "
+ style="fill:url(#linearGradient2558)"
+ id="path4808" />
+ <path
+ d="M 24.52,14.7 L 37,17.81 L 37,41.59 C 33.22,44.88 29.67,44.95 24.7,45 L 24.52,14.7 z "
+ style="fill:url(#linearGradient2560)"
+ id="path4810" />
+ <path
+ d="M 23.58,4.02 L 11.03,7.42 L 24.81,21.11 C 24.81,21.11 28.44,21 31.76,20.11 C 35.07,19.22 37.03,17.66 37.03,17.66 L 23.58,4.02 z "
+ style="fill:url(#linearGradient2562)"
+ id="path4812" />
+ <path
+ d="M 11.27,7.58 L 24.82,21.12 C 24.82,21.12 28.03,21.33 31.68,20.35 C 35.18,19.41 36.83,17.71 36.83,17.71"
+ style="fill:none;stroke:#ffffff;stroke-width:0.47999999;stroke-linecap:round"
+ id="path4814" />
+ <path
+ d="M 24.74,21.3 L 24.74,44.76"
+ style="fill:none;stroke:#ffffff;stroke-width:0.47999999;stroke-linecap:round"
+ id="path4816" />
+ <path
+ d="M 27.44,23.79 C 30.4,23.66 33.22,22.96 35.54,21.38 C 35.75,21.91 35.7,23.06 35.54,23.36 C 35.45,23.45 34.62,23.99 33.18,24.54 C 31.77,25.07 29.77,25.62 27.47,25.68 C 27.19,25.22 27.27,24.04 27.44,23.79 z "
+ style="fill:#808080"
+ id="path4818" />
+ <path
+ d="M 35.53,23.38 L 27.44,25.56 C 27.45,25.6 27.45,25.66 27.47,25.69 C 29.78,25.63 31.78,25.07 33.19,24.53 C 34.63,23.98 35.44,23.46 35.53,23.38 z "
+ style="fill:#b2b2b2"
+ id="path4820" />
+ <path
+ d="M 27.44,27.28 C 30.4,27.16 33.22,26.46 35.54,24.88 C 35.75,25.4 35.7,26.56 35.54,26.86 C 35.45,26.95 34.62,27.49 33.18,28.03 C 31.77,28.57 29.77,29.12 27.47,29.18 C 27.19,28.72 27.27,27.54 27.44,27.28 z "
+ style="fill:#808080"
+ id="path4822" />
+ <path
+ d="M 35.53,26.87 L 27.44,29.06 C 27.45,29.1 27.45,29.16 27.47,29.19 C 29.78,29.13 31.78,28.57 33.19,28.03 C 34.63,27.48 35.44,26.96 35.53,26.87 z "
+ style="fill:#b2b2b2"
+ id="path4824" />
+ <path
+ d="M 27.21,42.71 L 27.21,31.52 C 27.21,31.52 29,31.51 31.85,30.69 C 34.68,29.87 35.58,29.02 35.58,29.02 L 35.58,40.05 C 35.58,40.05 34.21,41.19 31.54,41.98 C 28.88,42.76 27.21,42.71 27.21,42.71 z "
+ style="fill:none;stroke:#b2b2b2;stroke-width:0.47999999;stroke-linecap:round;stroke-linejoin:round"
+ id="path4826" />
+ <path
+ d="M 31.68,37.72 C 32.29,37.54 32.79,37.95 32.79,38.62 C 32.79,39.29 32.29,39.97 31.68,40.15 C 31.07,40.33 30.58,39.93 30.58,39.27 C 30.58,38.58 31.07,37.9 31.68,37.72 z "
+ style="fill:url(#radialGradient2564);stroke:#328e36;stroke-width:0.44"
+ id="path4828" />
+ </g>
+ <use
+ transform="translate(131.19729,-4)"
+ id="use3219"
+ x="0"
+ y="0"
+ width="530"
+ height="450"
+ xlink:href="#computer" />
+ <use
+ transform="translate(-59.201614,63)"
+ id="use3189"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#computer" />
+ <use
+ transform="translate(190.39892,56)"
+ id="use3187"
+ x="0"
+ y="0"
+ width="530"
+ height="450"
+ xlink:href="#computer" />
+ <path
+ d="M 139,831.8622 C 143.432,831.8622 147,835.4302 147,839.8622 C 147,844.2942 143.432,847.8622 139,847.8622 C 134.568,847.8622 131,844.2942 131,839.8622 C 131,835.4302 134.568,831.8622 139,831.8622 z "
+ style="fill:#5c5c4f"
+ id="rect3250" />
+ <use
+ transform="translate(340,0)"
+ id="use3255"
+ x="0"
+ y="0"
+ width="530"
+ height="450"
+ xlink:href="#rect3250" />
+ <use
+ transform="translate(456.57438,0)"
+ id="use3236"
+ x="0"
+ y="0"
+ width="530"
+ height="450"
+ xlink:href="#g3226" />
+ <g
+ id="g3226">
+ <g
+ transform="matrix(0.7764706,0,0,0.825,-24.775496,114.51338)"
+ id="redbox">
+ <rect
+ width="150"
+ height="120"
+ rx="12.878788"
+ ry="12.121212"
+ x="59.5"
+ y="814.36218"
+ style="fill:#a70000"
+ id="rect2056" />
+ <rect
+ width="150"
+ height="120"
+ rx="12.878788"
+ ry="12.121212"
+ x="59.5"
+ y="814.36218"
+ style="fill:url(#pattern4704);fill-opacity:1"
+ id="rect4036" />
+ <rect
+ width="150"
+ height="120"
+ rx="12.878788"
+ ry="12.121212"
+ x="59.5"
+ y="814.36218"
+ style="fill:url(#radialGradient4393);fill-opacity:1"
+ id="rect4052" />
+ </g>
+ <g
+ transform="translate(14,-3.5)"
+ id="g3201">
+ <use
+ transform="translate(28,11)"
+ id="use3197"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#use3191" />
+ <use
+ transform="matrix(0.8136403,0,0,0.8136403,-134.27293,193.59903)"
+ id="use3191"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#computer" />
+ <use
+ transform="translate(-26,13)"
+ id="use3195"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#use3191" />
+ </g>
+ </g>
+ <text
+ x="79.673676"
+ y="869.12421"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;font-family:Interstate-Bold"
+ id="text3206"
+ xml:space="preserve"><tspan
+ x="79.673676"
+ y="869.12421"
+ id="tspan3208"><tspan
+ style="fill:#e3dcc0"
+ id="tspan3214">192.168</tspan><tspan
+ style="fill:#ffffff;font-family:Interstate-Black"
+ id="tspan3210">.1.0</tspan><tspan
+ style="fill:#e3dcc0"
+ id="tspan3216">/24</tspan></tspan></text>
+ <text
+ x="536.24792"
+ y="869.12421"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;font-family:Interstate-Bold"
+ id="text3238"
+ xml:space="preserve"
+ sodipodi:linespacing="125%"><tspan
+ x="536.24792"
+ y="869.12421"
+ id="tspan3240"><tspan
+ style="fill:#e3dcc0"
+ id="tspan3242">192.168</tspan><tspan
+ style="fill:#ffffff;font-family:Interstate-Black"
+ id="tspan3244">.2.0</tspan><tspan
+ style="fill:#e3dcc0"
+ id="tspan3246">/24</tspan></tspan></text>
+ </g>
+ <g
+ transform="translate(72.359706,94.597376)"
+ id="g5942">
+ <path
+ d="M 227.11741,-2.304662 C 218.61044,-2.304662 211.08086,1.861868 206.4667,8.285438 C 195.39058,8.321638 186.41172,17.32208 186.41169,28.40664 C 172.14009,28.40664 172.14966,48.52785 185.94835,48.52785 C 189.32794,48.52785 192.29548,46.79837 194.05642,44.19252 C 200.67358,49.26756 208.83789,49.60772 216.16326,46.04579 C 223.4569,49.52596 232.72939,49.18683 238.60105,45.78104 C 244.88316,49.59798 253.32269,49.74361 259.1119,45.00919 C 260.85648,47.99903 264.57749,48.52785 268.28642,48.52785 C 273.83988,48.52785 278.34705,44.02069 278.34703,38.46723 C 277.87274,30.86628 270.94669,26.89599 264.14967,29.26709 C 263.09801,22.48659 258.00258,17.05277 251.37537,15.56615 C 248.16502,5.206798 238.52748,-2.304662 227.11741,-2.304662 z "
+ style="fill:#5c5c4f"
+ id="path3769" />
+ <text
+ x="225.04935"
+ y="31.033188"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2388"
+ xml:space="preserve"><tspan
+ x="225.04935"
+ y="31.033188"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#ffffff;font-family:Interstate-Bold"
+ id="tspan2390">Internet</tspan></text>
+ </g>
+ <text
+ x="232.42056"
+ y="33.855572"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#000000;font-family:Interstate-Bold"
+ id="text2431"
+ xml:space="preserve"><tspan
+ x="232.42056"
+ y="33.855572"
+ style="fill:#000000"
+ id="tspan2433">ipsec0</tspan></text>
+ <text
+ x="363.21115"
+ y="33.855572"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#000000;font-family:Interstate-Bold"
+ id="text2443"
+ xml:space="preserve"><tspan
+ x="363.21115"
+ y="33.855572"
+ style="fill:#000000"
+ id="tspan2445">ipsec1</tspan></text>
+ <text
+ x="178.05638"
+ y="160.83585"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#000000;font-family:Interstate-Bold"
+ id="text2447"
+ xml:space="preserve"><tspan
+ x="178.05638"
+ y="160.83585"
+ style="fill:#000000"
+ id="tspan2449">gateway0</tspan></text>
+ <text
+ x="427.51163"
+ y="160.83585"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#000000;font-family:Interstate-Bold"
+ id="text2451"
+ xml:space="preserve"><tspan
+ x="427.51163"
+ y="160.83585"
+ style="fill:#000000"
+ id="tspan2453">gateway1</tspan></text>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-basic.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-basic.png
new file mode 100644
index 0000000..8efc8f9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-basic.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-create-share.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-create-share.png
new file mode 100644
index 0000000..7dee83e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-create-share.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-security.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-security.png
new file mode 100644
index 0000000..a219bc7
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-security.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-users.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-users.png
new file mode 100644
index 0000000..e9a1747
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba-users.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba.png
new file mode 100644
index 0000000..df9e9a3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/s-c-samba.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/samba-nautilus-machines.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/samba-nautilus-machines.png
new file mode 100644
index 0000000..cdf3062
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/samba-nautilus-machines.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/samba-nautilus.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/samba-nautilus.png
new file mode 100644
index 0000000..f97da4f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/samba-nautilus.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-Edit-filter.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-Edit-filter.png
new file mode 100644
index 0000000..f1260e3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-Edit-filter.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-Query-policy.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-Query-policy.png
new file mode 100644
index 0000000..fed4f51
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-Query-policy.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-Select-target-type-filtering.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-Select-target-type-filtering.png
new file mode 100644
index 0000000..58f2737
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-Select-target-type-filtering.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-View-filtering.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-View-filtering.png
new file mode 100644
index 0000000..492c483
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-View-filtering.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-plain.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-plain.png
new file mode 100644
index 0000000..4b21882
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/seaudit-plain.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/sec-ipsec-host2host.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/sec-ipsec-host2host.png
new file mode 100644
index 0000000..2661e1f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/sec-ipsec-host2host.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/security-intro-to-mls.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/security-intro-to-mls.png
new file mode 100644
index 0000000..2e0fa95
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/security-intro-to-mls.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/security-mls-data-flow.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/security-mls-data-flow.png
new file mode 100644
index 0000000..a2ecd24
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/security-mls-data-flow.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/serialport.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/serialport.png
new file mode 100644
index 0000000..a283eae
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/serialport.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/serv-config.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/serv-config.png
new file mode 100644
index 0000000..f0ca0b3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/serv-config.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-passphrase-prompt.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-passphrase-prompt.png
new file mode 100644
index 0000000..420a5b1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-passphrase-prompt.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-startup-applications-add.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-startup-applications-add.png
new file mode 100644
index 0000000..0e8ccde
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-startup-applications-add.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-startup-applications-check.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-startup-applications-check.png
new file mode 100644
index 0000000..bd8e824
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-startup-applications-check.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-startup-applications.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-startup-applications.png
new file mode 100644
index 0000000..27dedc7
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/ssh-startup-applications.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/switchmail-gui.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/switchmail-gui.png
new file mode 100644
index 0000000..09688a1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/switchmail-gui.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/system-config-nfs.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/system-config-nfs.png
new file mode 100644
index 0000000..b5f1979
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/system-config-nfs.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/tcp_wrap_diagram.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/tcp_wrap_diagram.png
new file mode 100644
index 0000000..38ee5ea
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/tcp_wrap_diagram.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/usbport.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/usbport.png
new file mode 100644
index 0000000..d2e5525
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/usbport.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user-new.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user-new.png
new file mode 100644
index 0000000..29bef28
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user-new.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user-properties.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user-properties.png
new file mode 100644
index 0000000..97179d9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user-properties.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user_pass_groups.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user_pass_groups.png
new file mode 100644
index 0000000..2d50e83
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user_pass_groups.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user_pass_info.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user_pass_info.png
new file mode 100644
index 0000000..5eaedfe
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/user_pass_info.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/your-rhn.png b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/your-rhn.png
new file mode 100644
index 0000000..31a03ed
Binary files /dev/null and b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/images/your-rhn.png differ
diff --git a/public_html/en-US/Fedora/14/html-single/Deployment_Guide/index.html b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/index.html
new file mode 100644
index 0000000..f9b15dd
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html-single/Deployment_Guide/index.html
@@ -0,0 +1,13155 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Deployment Guide</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><meta name="description" content="The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14." /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="en-US" class="book" title="Deployment Guide" id="id796275" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><span class="productname">Fedora</span> <span class="productnumber">14</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id796275" class="title">Deployment
Guide</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Deployment, configuration and administration of Fedora 14</h2></div><p class="edition">Edition 1.0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
+
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><div class="author"><h3 class="author"><span class="firstname">Douglas</span> <span class="surname">Silas</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:dhensley at redhat.com">dhensley at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Martin</span> <span class="surname">Prpič</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mprpic at redhat.com">mprpic at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Florian</span> <span class="surname">Nadge</span>
</h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:fnadge at redhat.com">fnadge at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Jaromír</span> <span class="surname">Hradílek</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:jhradile at redhat.com">jhradile at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="surname">Ha</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">O'Brien</span></h3><div class="affiliation"><sp
an class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Michael</span> <span class="surname">Hideo</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Don</span> <span class="surname">Domingo</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id543997" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2010 Red Hat, Inc. and others.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines">https://fedoraproject.org/wiki/Legal:Trademark_guidelines</a>.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract" title="Abstract"><h6>Abstract</h6><div class="para">
+ The <em class="citetitle">Deployment Guide</em> documents relevant information regarding the deployment, configuration and administration of Fedora 14.
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="#id1768868">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="#id553014">1. Document Conventions</a></span></dt><dt><span class="section"><a href="#sect-RedHat-We_Need_Feedback">2. We Need Feedback!</a></span></dt><dt><span class="section"><a href="#Acknowledgements">3. Acknowledgements</a></span></dt></dl></dd><dt><span class="preface"><a href="#ch-intro">Introduction</a></span></dt><dt><span class="part"><a href="#pt-pkg-management">I. Package Management</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-yum">1. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_and_Updating_Packages">1.1. Checking For and Updating Packages</a></span></dt><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">1.2. Packages and Package Groups</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositor
ies">1.3. Configuring Yum and Yum Repositories</a></span></dt><dt><span class="section"><a href="#sec-Yum_Plugins">1.4. Yum Plugins</a></span></dt><dt><span class="section"><a href="#sec-Additional_Resources">1.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-PackageKit">2. PackageKit</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Updating_Packages_with_Software_Update">2.1. Updating Packages with Software Update</a></span></dt><dt><span class="section"><a href="#sec-Using_Add_Remove_Software">2.2. Using Add/Remove Software</a></span></dt><dt><span class="section"><a href="#sec-PackageKit_Architecture">2.3. PackageKit Architecture</a></span></dt><dt><span class="section"><a href="#ch-Graphical_Package_Management-sec-Additional_Resources">2.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-RPM">3. RPM</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rpm-design">3.1. RPM D
esign Goals</a></span></dt><dt><span class="section"><a href="#s1-rpm-using">3.2. Using RPM</a></span></dt><dt><span class="section"><a href="#s1-check-rpm-sig">3.3. Checking a Package's Signature</a></span></dt><dt><span class="section"><a href="#s1-rpm-impressing">3.4. Practical and Common Examples of RPM Usage</a></span></dt><dt><span class="section"><a href="#s1-rpm-additional-resources">3.5. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#pt-network-related-config">II. Network-Related Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Network_Interfaces">4. Network Interfaces</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-networkscripts-files">4.1. Network Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-interfaces">4.2. Interface Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-control">4.3. Interface Control S
cripts</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-static-routes">4.4. Configuring Static Routes</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-functions">4.5. Network Function Files</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-resources">4.6. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Network_Configuration">5. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-The_NetworkManager_Daemon">5.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="#sec-Interacting_with_NetworkManager">5.2. Interacting with NetworkManager</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">5.3. Configuring Connection Settings</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Dynamic_Host_Configuration_Protocol_DHCP">6. Dynamic Host Configuration Protocol (DHCP)</a></span></dt><dd
><dl><dt><span class="section"><a href="#s1-dhcp-why">6.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-server">6.2. Configuring a DHCP Server</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-client">6.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="#sect-Configuring_a_Multihomed_DHCP_Server">6.4. Configuring a Multihomed DHCP Server</a></span></dt><dt><span class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">6.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="#s1-dhcp-additional-resources">6.6. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Controlling_Access_to_Services">7. Controlling Access to Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-services-runlevels">7.1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="#s1-services-configuring">7.2. Configuring the Se
rvices</a></span></dt><dt><span class="section"><a href="#s1-services-running">7.3. Running the Services</a></span></dt><dt><span class="section"><a href="#s1-services-additional-resources">7.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Authentication_Configuration">8. Authentication Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool">8.1. The Authentication Configuration Tool</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Introduction">8.2. The System Security Services Daemon (SSSD)</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-OpenSSH">9. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ssh-protocol">9.1. The SSH Protocol</a></span></dt><dt><span class="section"><a href="#s1-ssh-configuration">9.2. An OpenSSH Configuration</a></span></dt><dt><span class="section"><a href="#s1-ssh-clients">9.3. OpenSSH Cl
ients</a></span></dt><dt><span class="section"><a href="#s1-ssh-beyondshell">9.4. More Than a Secure Shell</a></span></dt><dt><span class="section"><a href="#s1-openssh-additional-resources">9.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-The_BIND_DNS_Server">10. The BIND DNS Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-bind-introduction">10.1. Introduction to DNS</a></span></dt><dt><span class="section"><a href="#s1-bind-namedconf">10.2. Configuring the <code class="command">named</code> Service</a></span></dt><dt><span class="section"><a href="#s1-bind-zone">10.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="#s1-bind-rndc">10.4. Using the <code class="command">rndc</code> Utility</a></span></dt><dt><span class="section"><a href="#s1-bind-dig">10.5. Using the <code class="command">dig</code> Utility</a></span></dt><dt><span class="section"><a href="#s1-bind-features">10.6. Advanced Fea
tures of BIND</a></span></dt><dt><span class="section"><a href="#s1-bind-mistakes">10.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="#s1-bind-additional-resources">10.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-The_Apache_HTTP_Server">11. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-apache-version2">11.1. The Apache HTTP Server 2.2</a></span></dt><dt><span class="section"><a href="#s1-apache-running">11.2. Running the <code class="systemitem">httpd</code> Service</a></span></dt><dt><span class="section"><a href="#s1-apache-editing">11.3. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-apache-dso">11.4. Working with Modules</a></span></dt><dt><span class="section"><a href="#s1-apache-virtualhosts">11.5. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="#s1-apache-mod_ssl">11.6. Setting Up an SSL Serve
r</a></span></dt><dt><span class="section"><a href="#s1-apache-resources">11.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-email">12. Email</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-email-protocols">12.1. Email Protocols</a></span></dt><dt><span class="section"><a href="#s1-email-types">12.2. Email Program Classifications</a></span></dt><dt><span class="section"><a href="#s1-email-mta">12.3. Mail Transport Agents</a></span></dt><dt><span class="section"><a href="#s1-email-mda">12.4. Mail Delivery Agents</a></span></dt><dt><span class="section"><a href="#s1-email-mua">12.5. Mail User Agents</a></span></dt><dt><span class="section"><a href="#s1-email-additional-resources">12.6. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#pt-sysconfig">III. System Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="#chap-Date_and_Time_Configuration">13. Date and Time Co
nfiguration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool">13.1. Date/Time Properties Tool</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration">13.2. Command Line Configuration</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Keyboard_Configuration">14. Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-keyboard-layout">14.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="#s1-keyboard-indicator">14.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="#s1-keyboard-break">14.3. Setting Up a Typing Break</a></span></dt></dl></dd><dt><span class="chapter"><a href="#Users_and_Groups">15. Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-users-configui">15.1. User and Group Configuration</a></span></dt><
dt><span class="section"><a href="#s1-users-tools">15.2. User and Group Management Tools</a></span></dt><dt><span class="section"><a href="#s1-users-groups-standard-users">15.3. Standard Users</a></span></dt><dt><span class="section"><a href="#s1-users-groups-standard-groups">15.4. Standard Groups</a></span></dt><dt><span class="section"><a href="#s1-users-groups-private-groups">15.5. User Private Groups</a></span></dt><dt><span class="section"><a href="#s1-users-groups-shadow-utilities">15.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="#s1-users-groups-additional-resources">15.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Automated_Tasks">16. Automated Tasks</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-autotasks-cron-anacron">16.1. Cron and Anacron</a></span></dt><dt><span class="section"><a href="#s1-autotasks-at-batch">16.2. At and Batch</a></span></dt><dt><span class="section"><a href="#s1-
autotasks-additional-resources">16.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Log_Files">17. Log Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-configuring-rsyslog">17.1. Configuring <code class="command">rsyslog</code> </a></span></dt><dt><span class="section"><a href="#s1-rsyslog-performance">17.2. <code class="command">rsyslog</code> Performance</a></span></dt><dt><span class="section"><a href="#s1-logfiles-locating">17.3. Locating Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-viewing">17.4. Viewing Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-adding">17.5. Adding a Log File</a></span></dt><dt><span class="section"><a href="#s1-logfiles-examining">17.6. Monitoring Log Files</a></span></dt><dt><span class="section"><a href="#s1-log-files-additional-resources">17.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-The_s
ysconfig_Directory">18. The sysconfig Directory</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-sysconfig-files">18.1. Files in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="#s1-sysconfig-etcsysconf-dir">18.2. Directories in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="#s1-sysconfig-additional-resources">18.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-proc">19. The <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-proc-virtual">19.1. A Virtual File System</a></span></dt><dt><span class="section"><a href="#s1-proc-topfiles">19.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dt><span class="section"><a href="#s1-proc-directories">19.3. Directories within <code class="filename">/proc/</code> <
/a></span></dt><dt><span class="section"><a href="#s1-proc-sysctl">19.4. Using the <code class="command">sysctl</code> Command</a></span></dt><dt><span class="section"><a href="#s1-proc-additional-resources">19.5. References</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#pt-system-monitoring">IV. System Monitoring</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Gathering_System_Information">20. Gathering System Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-sysinfo-system-processes">20.1. System Processes</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-memory-usage">20.2. Memory Usage</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-filesystems">20.3. File Systems</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-hardware">20.4. Hardware</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-additional-resources">20.5. Additional Resources</a></span></dt></dl></dd><dt>
<span class="chapter"><a href="#ch-abrt">21. ABRT</a></span></dt><dd><dl><dt><span class="section"><a href="#id525678">21.1. Overview</a></span></dt><dt><span class="section"><a href="#id741804">21.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="#abrt-plugins">21.3. <span class="application"><strong>ABRT</strong></span> Plugins</a></span></dt><dt><span class="section"><a href="#generating-backtrace">21.4. Generating Backtraces</a></span></dt><dt><span class="section"><a href="#id944926">21.5. Using the Command Line Interface</a></span></dt><dt><span class="section"><a href="#configuring">21.6. Configuring ABRT</a></span></dt><dt><span class="section"><a href="#configuring-centralized-crash-collection">21.7. Configuring Centralized Crash Collection</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#pt-kernel-configuration">V. Kernel, Module and Driver Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch
-Working_with_Kernel_Modules">22. Working with Kernel Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="#sec-Loading_a_Module">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="#sec-Unloading_a_Module">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="#sec-Setting_Module_Parameters">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="#sec-Persistent_Module_Loading">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#sec-Specific_Kernel_Module_Capabilities">22.7. Specific Kernel Module Capabilities</a></span></dt><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">22.8
. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Manually_Upgrading_the_Kernel">23. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kernel-packages">23.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">23.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">23.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">23.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image">23.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">23.6. Verifying the Boot Loader</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-kdump">24. The <code class="systemitem">kdump</code> Crash Recovery Service</a></span></dt><dd><dl><dt>
<span class="section"><a href="#s1-kdump-configuration">24.1. Configuring the <code class="systemitem">kdump</code> Service</a></span></dt><dt><span class="section"><a href="#s1-kdump-crash">24.2. Analyzing the Core Dump</a></span></dt><dt><span class="section"><a href="#s1-kdump-resources">24.3. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#app-Revision_History">A. Revision History</a></span></dt><dt><span class="index"><a href="#id703416">Index</a></span></dt></dl></div><div xml:lang="en-US" class="preface" title="Preface" id="id1768868" lang="en-US"><div class="titlepage"><div><div><h1 id="id1768868" class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" title="1. Document Conventions" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id553014">1. Document Conventions</h2></div></div></div><div class="para">
+ This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
+ </div><div class="para">
+ In PDF and paper editions, this manual uses typefaces drawn from the <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
+ </div><div class="section" title="1.1. Typographic Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id801820">1.1. Typographic Conventions</h3></div></div></div><div class="para">
+ Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
+ </div><div class="para">
+ <code class="literal">Mono-spaced Bold</code>
+ </div><div class="para">
+ Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ To see the contents of the file <code class="filename">my_next_bestselling_novel</code> in your current working directory, enter the <code class="command">cat my_next_bestselling_novel</code> command at the shell prompt and press <span class="keycap"><strong>Enter</strong></span> to execute the command.
+ </div></blockquote></div><div class="para">
+ The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
+ </div><div class="para">
+ Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to execute the command.
+ </div><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> to switch to the first virtual terminal. Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F1</strong></span> to return to your X-Windows session.
+ </div></blockquote></div><div class="para">
+ The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously).
+ </div><div class="para">
+ If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in <code class="literal">mono-spaced bold</code>. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ File-related classes include <code class="classname">filesystem</code> for file systems, <code class="classname">file</code> for files, and <code class="classname">dir</code> for directories. Each class has its own associated set of permissions.
+ </div></blockquote></div><div class="para">
+ <span class="application"><strong>Proportional Bold</strong></span>
+ </div><div class="para">
+ This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Choose <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Mouse</strong></span> from the main menu bar to launch <span class="application"><strong>Mouse Preferences</strong></span>. In the <span class="guilabel"><strong>Buttons</strong></span> tab, click the <span class="guilabel"><strong>Left-handed mouse</strong></span> check box and click <span class="guibutton"><strong>Close</strong></span> to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
+ </div><div class="para">
+ To insert a special character into a <span class="application"><strong>gedit</strong></span> file, choose <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>Accessories</strong></span> → <span class="guimenuitem"><strong>Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search</strong></span> → <span class="guimenuitem"><strong>Find…</strong></span> from the <span class="application"><strong>Character Map</strong></span> menu bar, type the name of the character in the <span class="guilabel"><strong>Search</strong></span> field and click <span class="guibutton"><strong>Next</strong></span>. The character you sought will be highlighted in the <span class="guilabel"><strong>Character Table</strong></span>. Double-click this highlighted character to place it in the <span class="guilabel"><strong>Text to copy</strong></span> field and then click the <span class="guibutton"><stron
g>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit</strong></span> → <span class="guimenuitem"><strong>Paste</strong></span> from the <span class="application"><strong>gedit</strong></span> menu bar.
+ </div></blockquote></div><div class="para">
+ The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
+ </div><div class="para">
+ <code class="command"><em class="replaceable"><code>Mono-spaced Bold Italic</code></em></code> or <span class="application"><strong><em class="replaceable"><code>Proportional Bold Italic</code></em></strong></span>
+ </div><div class="para">
+ Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ To connect to a remote machine using ssh, type <code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>domain.name</code></em></code> at a shell prompt. If the remote machine is <code class="filename">example.com</code> and your username on that machine is john, type <code class="command">ssh john at example.com</code>.
+ </div><div class="para">
+ The <code class="command">mount -o remount <em class="replaceable"><code>file-system</code></em></code> command remounts the named file system. For example, to remount the <code class="filename">/home</code> file system, the command is <code class="command">mount -o remount /home</code>.
+ </div><div class="para">
+ To see the version of a currently installed package, use the <code class="command">rpm -q <em class="replaceable"><code>package</code></em></code> command. It will return a result as follows: <code class="command"><em class="replaceable"><code>package-version-release</code></em></code>.
+ </div></blockquote></div><div class="para">
+ Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
+ </div><div class="para">
+ Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Publican is a <em class="firstterm">DocBook</em> publishing system.
+ </div></blockquote></div></div><div class="section" title="1.2. Pull-quote Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id583752">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ Terminal output and source code listings are set off visually from the surrounding text.
+ </div><div class="para">
+ Output sent to a terminal is set in <code class="computeroutput">mono-spaced roman</code> and presented thus:
+ </div><pre class="screen">books Desktop documentation drafts mss photos stuff svn
+books_tests Desktop1 downloads images notes scripts svgs</pre><div class="para">
+ Source-code listings are also set in <code class="computeroutput">mono-spaced roman</code> but add syntax highlighting as follows:
+ </div><pre class="programlisting">package org.<span class="perl_Function">jboss</span>.<span class="perl_Function">book</span>.<span class="perl_Function">jca</span>.<span class="perl_Function">ex1</span>;
+
+<span class="perl_Keyword">import</span> javax.naming.InitialContext;
+
+<span class="perl_Keyword">public</span> <span class="perl_Keyword">class</span> ExClient
+{
+ <span class="perl_Keyword">public</span> <span class="perl_DataType">static</span> <span class="perl_DataType">void</span> <span class="perl_Function">main</span>(String args[])
+ <span class="perl_Keyword">throws</span> Exception
+ {
+ InitialContext iniCtx = <span class="perl_Keyword">new</span> InitialContext();
+ Object ref = iniCtx.<span class="perl_Function">lookup</span>(<span class="perl_String">"EchoBean"</span>);
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.<span class="perl_Function">create</span>();
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Created Echo"</span>);
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
+ }
+}</pre></div><div class="section" title="1.3. Notes and Warnings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id441869">1.3. Notes and Warnings</h3></div></div></div><div class="para">
+ Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
+ </div></div></div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
+ </div></div></div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </div></div></div></div></div><div xml:lang="en-US" class="section" title="2. We Need Feedback!" id="sect-RedHat-We_Need_Feedback" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-RedHat-We_Need_Feedback">2. We Need Feedback!</h2></div></div></div><a id="id500918" class="indexterm"></a><div class="para">
+ If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: <a href="http://bugzilla.redhat.com/">http://bugzilla.redhat.com/</a> against the product <span class="application"><strong>Fedora Documentation.</strong></span>
+ </div><div class="para">
+ When submitting a bug report, be sure to mention the manual's identifier: <em class="citetitle">deployment-guide</em> and version number: <code class="literal">14</code>.
+ </div><div class="para">
+ If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
+ </div><div class="section" title="2.1. Technical Review Requests"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id481182">2.1. Technical Review Requests</h3></div></div></div><div class="para">
+ All review requests are classified into one of the following five categories:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">New Content</span></dt><dd><div class="para">
+ content documented for the first time — an entirely new feature, procedure, or concept. For example: "Section now describes the new procedure for creating bootable USB devices."
+ </div></dd><dt class="varlistentry"><span class="term">Correction</span></dt><dd><div class="para">
+ a factual error previously present in the text has been corrected. For example: "Section previously stated (incorrectly) that IPv4 and IPv6 were both supported; section now states that IPv6 has never been supported."
+ </div></dd><dt class="varlistentry"><span class="term">Clarification</span></dt><dd><div class="para">
+ material that was already factually correct but is now better explained. Clarifications are usually in response to reader feedback that the previous content was confusing or misleading in some way. For example: "Paths described in Example 1.2.3 now better reflect the directory structure of an actual installed system."
+ </div></dd><dt class="varlistentry"><span class="term">Obsoletion</span></dt><dd><div class="para">
+ a description of a feature or a procedure has been dropped. Material might be obsolete because of a feature that is no longer supported, a known issue that has been corrected, or hardware that is now obsolete. For example, "Section no longer describes how to update kernel modules using a floppy disk."
+ </div></dd><dt class="varlistentry"><span class="term">Verification</span></dt><dd><div class="para">
+ a request to check a fact, procedure, or whether material should be obsoleted. For example, "Section describes how to connect to a generic iSCSI storage device. Please verify this on your hardware" or "Section still describes how to update kernel modules using a LS-120 SuperDisk; please verify that we still need to tell readers about this obsolete hardware."
+ </div></dd></dl></div></div></div><div class="section" title="3. Acknowledgements" id="Acknowledgements"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Acknowledgements">3. Acknowledgements</h2></div></div></div><div class="para">
+ Certain portions of this text first appeared in the <em class="citetitle">Deployment Guide</em>, copyright © 2007 Red Hat, Inc., available at <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/index.html">http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/index.html</a>.
+ </div><div class="para">
+ The authors of this book would like to thank the following people for their valuable contributions: Adam Tkáč, Andrew Fitzsimon, Andrius Benokraitis, Brian Cleary Edward Bailey, Garrett LeSage, Jeffrey Fearn, Joe Orton, Joshua Wulf, KarstenWade, Lucy Ringland, Marcela Mašláňová, Mark Johnson, Michael Behm, Michael Behm, Miroslav Lichvár, Radek Vokál, Rahul Kavalapara, Rahul Sundaram, Sandra Moore, and Zbyšek Mráz, among many others.
+ </div></div></div><div xml:lang="en-US" class="preface" title="Introduction" id="ch-intro" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Introduction</h1></div></div></div><a id="id747409" class="indexterm"></a><div class="para">
+ Welcome to the <em class="citetitle">Fedora 14 Deployment Guide</em>.
+ </div><div class="para">
+ The <em class="citetitle">Deployment Guide</em> contains information on how to customize your Fedora 14 system to fit your needs. If you are looking for a comprehensive, task-oriented guide for configuring and customizing your system, this is the manual for you.
+ </div><div class="para">
+ This manual discusses many intermediate topics such as the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Installing and managing packages using the graphical <span class="application"><strong>PackageKit</strong></span> and command line <span class="application"><strong>Yum</strong></span> package managers
+ </div></li><li class="listitem"><div class="para">
+ Setting up a network—from establishing an Ethernet connection using <span class="application"><strong>NetworkManager</strong></span> to configuring channel bonding interfaces to increase server bandwidth
+ </div></li><li class="listitem"><div class="para">
+ Configuring <code class="systemitem">DHCP</code>, <span class="application"><strong>BIND</strong></span>, <span class="application"><strong>Apache</strong></span>, <span class="application"><strong>Postfix</strong></span>, <span class="application"><strong>Sendmail</strong></span> and other enterprise-class servers and software
+ </div></li><li class="listitem"><div class="para">
+ Gathering information about your system, including obtaining user-space crash data with the <span class="application"><strong>Automatic Bug Reporting Tool</strong></span>, and kernel-space crash data with <code class="systemitem">kdump</code>
+ </div></li><li class="listitem"><div class="para">
+ Easily working with kernel modules and upgrading the kernel
+ </div></li></ul></div><div class="para">
+ This manual is divided into the following main categories:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a class="xref" href="#pt-pkg-management" title="Part I. Package Management">Part I, “Package Management”</a>
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#pt-network-related-config" title="Part II. Network-Related Configuration">Part II, “Network-Related Configuration”</a>
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#pt-sysconfig" title="Part III. System Configuration">Part III, “System Configuration”</a>
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#pt-system-monitoring" title="Part IV. System Monitoring">Part IV, “System Monitoring”</a>
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#pt-kernel-configuration" title="Part V. Kernel, Module and Driver Configuration">Part V, “Kernel, Module and Driver Configuration”</a>
+ </div></li></ul></div><div class="para">
+ This guide assumes you have a basic understanding of your Fedora system. If you need help installing Fedora, refer to the <em class="citetitle">Fedora 14 Installation Guide</em>.
+ </div></div><div class="part" title="Part I. Package Management" id="pt-pkg-management"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part I. Package Management</h1></div></div></div><div class="partintro" title="Package Management" id="id844113"><div></div><div class="para">
+ All software on a Fedora system is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages on Fedora using the <span class="application"><strong>Yum</strong></span> and <span class="application"><strong>RPM</strong></span> package managers and the <span class="application"><strong>PackageKit</strong></span> suite of graphical package management tools.
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#ch-yum">1. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_and_Updating_Packages">1.1. Checking For and Updating Packages</a></span></dt><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">1.2. Packages and Package Groups</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">1.3. Configuring Yum and Yum Repositories</a></span></dt><dt><span class="section"><a href="#sec-Yum_Plugins">1.4. Yum Plugins</a></span></dt><dt><span class="section"><a href="#sec-Additional_Resources">1.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-PackageKit">2. PackageKit</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Updating_Packages_with_Software_Update">2.1. Updating Packages with Software Update</a></span></dt><dt><span class="section"><a href="#sec-Using_
Add_Remove_Software">2.2. Using Add/Remove Software</a></span></dt><dt><span class="section"><a href="#sec-PackageKit_Architecture">2.3. PackageKit Architecture</a></span></dt><dt><span class="section"><a href="#ch-Graphical_Package_Management-sec-Additional_Resources">2.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-RPM">3. RPM</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rpm-design">3.1. RPM Design Goals</a></span></dt><dt><span class="section"><a href="#s1-rpm-using">3.2. Using RPM</a></span></dt><dt><span class="section"><a href="#s1-check-rpm-sig">3.3. Checking a Package's Signature</a></span></dt><dt><span class="section"><a href="#s1-rpm-impressing">3.4. Practical and Common Examples of RPM Usage</a></span></dt><dt><span class="section"><a href="#s1-rpm-additional-resources">3.5. Additional Resources</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" title="Chapter 1. Yum" id="ch-
yum" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Yum</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sec-Checking_For_and_Updating_Packages">1.1. Checking For and Updating Packages</a></span></dt><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">1.2. Packages and Package Groups</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">1.3. Configuring Yum and Yum Repositories</a></span></dt><dt><span class="section"><a href="#sec-Yum_Plugins">1.4. Yum Plugins</a></span></dt><dt><span class="section"><a href="#sec-Additional_Resources">1.5. Additional Resources</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>Yum</strong></span> is the The Fedora Project package manager that is able to query for information about packages, fetch packages from repositories, install and uninstall packages using automatic dependency resolution, and update an entire system to the latest available packages. <span class="application"><strong>Yum</strong></span> performs automatic dependency resolution on packages you are updating, installing or removing, and thus is able to automatically determine, fetch and install all available dependent packages. <span class="application"><strong>Yum</strong></span> can be configured with new, additional repositories, or <em class="firstterm">package sources</em>, and also provides many plugins which enhance and extend its capabilities. <span class="application"><strong>Yum</strong></span> is able to perform many of the same tasks that <span class="application"><strong>RPM</strong></span> can; additionally, many of the command lin
e options are similar. <span class="application"><strong>Yum</strong></span> enables easy and simple package management on a single machine or on groups of them.
+ </div><div class="important" title="Secure Package Management with GPG-Signed Packages" id="important-Secure_Package_Management_with_GPG-Signed_Packages"><div class="admonition_header"><h2>Secure Package Management with GPG-Signed Packages</h2></div><div class="admonition"><div class="para">
+ <span class="application"><strong>Yum</strong></span> provides secure package management by enabling GPG (Gnu Privacy Guard; also known as GnuPG) signature verification on GPG-signed packages to be turned on for all package repositories (i.e. package sources), or for individual repositories. When signature verification is enabled, <span class="application"><strong>Yum</strong></span> will refuse to install any packages not GPG-signed with the correct key for that repository. This means that you can trust that the <span class="application"><strong>RPM</strong></span> packages you download and install on your system are from a trusted source, such as The Fedora Project, and were not modified during transfer. Refer to <a class="xref" href="#sec-Configuring_Yum_and_Yum_Repositories" title="1.3. Configuring Yum and Yum Repositories">Section 1.3, “Configuring Yum and Yum Repositories”</a> for details on enabling signature-checking with <span class="application"><strong>Yu
m</strong></span>, or <a class="xref" href="#s1-check-rpm-sig" title="3.3. Checking a Package's Signature">Section 3.3, “Checking a Package's Signature”</a> for information on working with and verifying GPG-signed <span class="application"><strong>RPM</strong></span> packages in general.
+ </div></div></div><div class="para">
+ <span class="application"><strong>Yum</strong></span> also enables you to easily set up your own repositories of <span class="application"><strong>RPM</strong></span> packages for download and installation on other machines.
+ </div><div class="para">
+ Learning <span class="application"><strong>Yum</strong></span> is a worthwhile investment because it is often the fastest way to perform system administration tasks, and it provides capabilities beyond those provided by the <span class="application"><strong>PackageKit</strong></span> graphical package management tools. Refer to <a class="xref" href="#ch-PackageKit" title="Chapter 2. PackageKit">Chapter 2, <i>PackageKit</i></a> for details on using <span class="application"><strong>PackageKit</strong></span>.
+ </div><div class="section" title="1.1. Checking For and Updating Packages" id="sec-Checking_For_and_Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Checking_For_and_Updating_Packages">1.1. Checking For and Updating Packages</h2></div></div></div><div class="section" title="1.1.1. Checking For Updates" id="sec-Checking_For_Updates"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Checking_For_Updates">1.1.1. Checking For Updates</h3></div></div></div><a id="id795039" class="indexterm"></a><div class="para">
+ You can use the <code class="command">yum check-update</code> command to see which installed packages on your system have updates available.
+ </div><div class="note" title="Note: Yum and Superuser Privileges" id="note-Note_Yum_and_Superuser_Privileges"><div class="admonition_header"><h2>Note: <span class="application"><strong>Yum</strong></span> and Superuser Privileges</h2></div><div class="admonition"><div class="para">
+ You must have superuser privileges in order to use <code class="command">yum</code> to install, update or remove packages on your system. All examples in this chapter assume that you have already obtained superuser privileges by using either the <code class="command">su</code> or <code class="command">sudo</code> command.
+ </div></div></div><pre class="screen">
+~]# <code class="command">yum check-update</code>
+Loaded plugins: presto, refresh-packagekit, security
+PackageKit.x86_64 0.5.3-0.1.20090915git.fc12 fedora
+PackageKit-glib.x86_64 0.5.3-0.1.20090915git.fc12 fedora
+PackageKit-yum.x86_64 0.5.3-0.1.20090915git.fc12 fedora
+PackageKit-yum-plugin.x86_64 0.5.3-0.1.20090915git.fc12 fedora
+glibc.x86_64 2.10.90-22 fedora
+glibc-common.x86_64 2.10.90-22 fedora
+kernel.x86_64 2.6.31-14.fc12 fedora
+kernel-firmware.noarch 2.6.31-14.fc12 fedora
+rpm.x86_64 4.7.1-5.fc12 fedora
+rpm-libs.x86_64 4.7.1-5.fc12 fedora
+rpm-python.x86_64 4.7.1-5.fc12 fedora
+yum.noarch 3.2.24-4.fc12 fedora
+</pre><div class="para">
+ These packages are listed as having updates available. The first package in the list is <span class="application"><strong>PackageKit</strong></span>, the graphical package manager. The first line of the above output tells us:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">PackageKit</code> — the name of the package
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">x86_64</code> — the CPU architecture the package was built for
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">0.5.3-0.1.20090915git.fc12</code> — the version of the updated package to be installed
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">fedora</code> — the repository in which the updated package is located
+ </div></li></ul></div><div class="para">
+ The output also shows us that we can update the kernel (the kernel package), <span class="application"><strong>Yum</strong></span> and <span class="application"><strong>RPM</strong></span> themselves (the <code class="filename">yum</code> and <code class="filename">rpm</code> packages), as well as their dependencies (such as the <code class="computeroutput">kernel-firmware</code>, <code class="computeroutput">rpm-libs</code> and <code class="computeroutput">rpm-python</code> packages), all using <code class="command">yum</code>.
+ </div></div><div class="section" title="1.1.2. Updating Packages" id="sec-Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Updating_Packages">1.1.2. Updating Packages</h3></div></div></div><a id="id518162" class="indexterm"></a><div class="para">
+ You can choose to update a single package, multiple packages, or all packages at once. If any dependencies of the package (or packages) you update have updates available themselves, then they are updated too. To update a single package
+ <a id="id518180" class="indexterm"></a>
+ , enter <code class="command">yum update <package_name></code>:
+ </div><pre class="screen">
+~]# <code class="command">yum update glibc</code>
+Loaded plugins: presto, refresh-packagekit, security
+Setting up Install Process
+Resolving Dependencies
+--> Running transaction check
+--> Processing Dependency: glibc = 2.10.90-21 for package: glibc-common-2.10.90-21.x86_64
+---> Package glibc.x86_64 0:2.10.90-22 set to be updated
+--> Running transaction check
+---> Package glibc-common.x86_64 0:2.10.90-22 set to be updated
+--> Finished Dependency Resolution
+Dependencies Resolved
+======================================================================
+ Package Arch Version Repository Size
+======================================================================
+Updating:
+ glibc x86_64 2.10.90-22 fedora 2.7 M
+Updating for dependencies:
+ glibc-common x86_64 2.10.90-22 fedora 6.0 M
+Transaction Summary
+======================================================================
+Install 0 Package(s)
+Upgrade 2 Package(s)
+Total download size: 8.7 M
+Is this ok [y/N]:
+</pre><div class="para">
+ This output contains several items of interest:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="computeroutput">Loaded plugins: presto, refresh-packagekit, security</code> — <code class="command">yum</code> always informs you which <span class="application"><strong>Yum</strong></span> plugins are installed and enabled. Here, <code class="command">yum</code> is using the <span class="application"><strong>presto</strong></span>, <span class="application"><strong>refresh-packagekit</strong></span> and <span class="application"><strong>security</strong></span> plugins. Refer to <a class="xref" href="#sec-Yum_Plugins" title="1.4. Yum Plugins">Section 1.4, “Yum Plugins”</a> for general information on <span class="application"><strong>Yum</strong></span> plugins, or to <a class="xref" href="#sec-Plugin_Descriptions" title="1.4.3. Plugin Descriptions">Section 1.4.3, “Plugin Descriptions”</a> for descriptions of specific plugins.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">kernel.x86_64</code> — you can download and install new kernels safely with <code class="command">yum</code>.
+ </div><div class="important" title="Important: Updating and Installing Kernels with Yum" id="important-Important-Updating_and_Installing_Kernels_with_Yum"><div class="admonition_header"><h2>Important: Updating and Installing Kernels with Yum</h2></div><div class="admonition"><div class="para">
+ <code class="command">yum</code> always <span class="strong strong"><strong>install</strong></span>s a new kernel in the same sense that <span class="application"><strong>RPM</strong></span> <span class="emphasis"><em>installs</em></span> a new kernel when you use the command <code class="command">rpm -i kernel</code>. Therefore, you do not need to worry about the distinction between <span class="emphasis"><em>installing</em></span> and <span class="emphasis"><em>upgrading</em></span> a kernel package when you use <code class="command">yum</code>: it will do the right thing, regardless of whether you are using the <code class="command">yum update</code> or <code class="command">yum install</code> command.
+ </div><div class="para">
+ When using <span class="application"><strong>RPM</strong></span>, on the other hand, it is important to use the <code class="command">rpm -i kernel</code> command (which installs a new kernel) instead of <code class="command">rpm -u kernel</code> (which <span class="emphasis"><em>replaces</em></span> the current kernel). Refer to <a class="xref" href="#sec-Installing_and_Upgrading" title="3.2.2. Installing and Upgrading">Section 3.2.2, “Installing and Upgrading”</a> for more information on installing/updating kernels with <span class="application"><strong>RPM</strong></span>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="command">yum</code> presents the update information and then prompts you as to whether you want it to perform the update; <code class="command">yum</code> runs interactively by default. If you already know which transactions <code class="command">yum</code> plans to perform, you can use the <code class="option">-y</code> option to automatically answer <code class="command">yes</code> to any questions <code class="command">yum</code> may ask (in which case it runs non-interactively). However, you should always examine which changes <code class="command">yum</code> plans to make to the system so that you can easily troubleshoot any problems that might arise.
+ </div><div class="para">
+ If a transaction does go awry, you can view <span class="application"><strong>Yum</strong></span>'s log of transactions by entering <code class="command">cat /var/log/yum.log</code> at the shell prompt. The most recent transactions are listed at the end of the log file.
+ </div></li></ol></div><h4>Updating All Packages and Their Dependencies</h4><a id="id779452" class="indexterm"></a><div class="para">
+ To update all packages and their dependencies, simply enter <code class="command">yum update</code> (without any arguments):
+ </div><div class="example" title="Example 1.1. Updating all packages at once" id="ex-Updating_all_packages_at_once"><h6>Example 1.1. Updating all packages at once</h6><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum update</code>
+</pre></div></div><br class="example-break" /></div><div class="section" title="1.1.3. Updating Security-Related Packages" id="sec-Updating_Security-Related_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Updating_Security-Related_Packages">1.1.3. Updating Security-Related Packages</h3></div></div></div><a id="id528808" class="indexterm"></a><a id="id528819" class="indexterm"></a><div class="para">
+ Discovering which packages have security updates available and then updating those packages quickly and easily is important. <span class="application"><strong>Yum</strong></span> provides the
+ <a id="id1229134" class="indexterm"></a>
+ plugin for this purpose. The <span class="application"><strong>security</strong></span> plugin extends the <code class="command">yum</code> command with a set of highly-useful security-centric commands, subcommands and options. Refer to <a class="xref" href="#bh-security_yum-plugin-security" title="1.4.3. security (yum-plugin-security)">Section 1.4.3, “security (yum-plugin-security)”</a> for specific information.
+ </div></div><div class="section" title="1.1.4. Preserving Configuration File Changes" id="sec-Preserving_Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Preserving_Configuration_File_Changes">1.1.4. Preserving Configuration File Changes</h3></div></div></div><a id="id772253" class="indexterm"></a><div class="para">
+ You will inevitably make changes to the configuration files installed by packages as you use your Fedora system. <span class="application"><strong>RPM</strong></span>, which <span class="application"><strong>Yum</strong></span> uses to perform changes to the system, provides a mechanism for ensuring their integrity. Refer to <a class="xref" href="#sec-Installing_and_Upgrading" title="3.2.2. Installing and Upgrading">Section 3.2.2, “Installing and Upgrading”</a> for details on how to manage changes to configuration files across package upgrades.
+ </div></div></div><div class="section" title="1.2. Packages and Package Groups" id="sec-Packages_and_Package_Groups"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Packages_and_Package_Groups">1.2. Packages and Package Groups</h2></div></div></div><a id="id421507" class="indexterm"></a><a id="id421519" class="indexterm"></a><div class="section" title="1.2.1. Searching, Listing and Displaying Package Information" id="sec-Searching_Listing_and_Displaying_Package_Information"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Searching_Listing_and_Displaying_Package_Information">1.2.1. Searching, Listing and Displaying Package Information</h3></div></div></div><a id="id774060" class="indexterm"></a><a id="id774072" class="indexterm"></a><a id="id774083" class="indexterm"></a><a id="id774095" class="indexterm"></a><a id="id524848" class="indexterm"></a><a id="id524859" class="ind
exterm"></a><div class="para">
+ You can search all <span class="application"><strong>RPM</strong></span> package names, descriptions and summaries by using the <code class="command">yum search <em class="replaceable"><code><term></code></em> [<span class="optional"><em class="replaceable"><code>more_terms</code></em></span>] </code> command. <code class="command">yum</code> displays the list of matches for each term:
+ </div><pre class="screen">
+~]# <code class="command">yum search meld kompare</code>
+Loaded plugins: presto, refresh-packagekit, security
+=============================== Matched: kompare ===============================
+kdesdk.x86_64 : The KDE Software Development Kit (SDK)
+komparator.x86_64 : Kompare and merge two folders
+================================ Matched: meld =================================
+meld.noarch : Visual diff and merge tool
+python-meld3.x86_64 : An HTML/XML templating system for Python
+</pre><div class="para">
+ <a id="id686736" class="indexterm"></a>
+ <a id="id845549" class="indexterm"></a>
+ <code class="command">yum search</code> is useful for searching for packages you do not know the name of, but for which you know a related term.
+ </div><h4>Listing Packages</h4><div class="para">
+ <a id="id724371" class="indexterm"></a>
+ <a id="id724387" class="indexterm"></a>
+ <code class="command">yum list</code> and related commands provide information about packages, package groups, and repositories.
+ </div><div class="note" title="Tip: Filtering Results with Glob Expressions" id="note-Tip-Filtering_Results_with_Glob_Expressions"><div class="admonition_header"><h2>Tip: Filtering Results with Glob Expressions</h2></div><div class="admonition"><a id="id535037" class="indexterm"></a><a id="id535053" class="indexterm"></a><div class="para">
+ All of <span class="application"><strong>Yum</strong></span>'s various list commands allow you to filter the results by appending one or more <span class="emphasis"><em>glob expressions</em></span> as arguments. Glob expressions are normal strings of characters which contain one or more of the wildcard characters <code class="command">*</code> (which expands to match any character multiple times) and <code class="command">?</code> (which expands to match any one character). Be careful to escape both of these glob characters when passing them as arguments to a <code class="command">yum</code> command. If you do not, the bash shell will interpret the glob expressions as <span class="emphasis"><em>pathname expansions</em></span>, and potentially pass all files in the current directory that match the globs to <code class="command">yum</code>, which is not what you want. Instead, you want to pass the glob expressions themselves to <code class="command">yum</code>, which you
can do by either:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ escaping the wildcard characters
+ </div></li><li class="listitem"><div class="para">
+ double-quoting or single-quoting the entire glob expression.
+ </div></li></ul></div><div class="para">
+ The following examples show both methods:
+ </div><div class="example" title="Example 1.2. Filtering results using a single glob expression with two escaped wildcard characters" id="ex-Filtering_results_using_a_single_glob_expression_with_two_escaped_wildcards"><h6>Example 1.2. Filtering results using a single glob expression with two escaped wildcard characters</h6><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum list available gimp\*plugin\*</code>
+Loaded plugins: presto, refresh-packagekit, security
+Available Packages
+gimp-fourier-plugin.x86_64 0.3.2-3.fc11 fedora
+gimp-lqr-plugin.x86_64 0.6.1-2.fc11 updates
+</pre></div></div><br class="example-break" /><div class="example" title="Example 1.3. Filtering results using a double-quoted glob expression" id="ex-Filtering_results_using_a_double-quoted_glob_expression"><h6>Example 1.3. Filtering results using a double-quoted glob expression</h6><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum list installed "krb?-*"</code>
+Loaded plugins: presto, refresh-packagekit, security
+Installed Packages
+krb5-auth-dialog.x86_64 0.12-2.fc12 @fedora
+krb5-libs.x86_64 1.7-8.fc12 @fedora
+krb5-workstation.x86_64 1.7-8.fc12 @fedora
+</pre></div></div><br class="example-break" /></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yum list <em class="replaceable"><code><glob_expr></code></em> [<span class="optional"><em class="replaceable"><code>more_glob_exprs</code></em></span>] </code> — List information on installed and available packages matching all glob expressions.
+ </div><div class="example" title="Example 1.4. Listing all ABRT addons and plugins using glob expressions" id="ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions"><h6>Example 1.4. Listing all ABRT addons and plugins using glob expressions</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum list abrt-addon\* abrt-plugin\*</code>
+Loaded plugins: presto, refresh-packagekit, security
+Installed Packages
+abrt-addon-ccpp.x86_64 0.0.9-2.fc12 @fedora
+abrt-addon-kerneloops.x86_64 0.0.9-2.fc12 @fedora
+abrt-addon-python.x86_64 0.0.9-2.fc12 @fedora
+abrt-plugin-bugzilla.x86_64 0.0.9-2.fc12 @fedora
+abrt-plugin-kerneloopsreporter.x86_64 0.0.9-2.fc12 @fedora
+abrt-plugin-sqlite3.x86_64 0.0.9-2.fc12 @fedora
+Available Packages
+abrt-plugin-filetransfer.x86_64 0.0.9-2.fc12 fedora
+abrt-plugin-logger.x86_64 0.0.9-2.fc12 fedora
+abrt-plugin-mailx.x86_64 0.0.9-2.fc12 fedora
+abrt-plugin-runapp.x86_64 0.0.9-2.fc12 fedora
+abrt-plugin-sosreport.x86_64 0.0.9-2.fc12 fedora
+abrt-plugin-ticketuploader.x86_64 0.0.9-2.fc12 fedora</pre></div></div><br class="example-break" /></li></ul></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yum list all</code> —
+ <a id="id1806545" class="indexterm"></a>
+ <a id="id824905" class="indexterm"></a>
+ List all installed <span class="emphasis"><em>and</em></span> available packages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum list installed</code> —
+ <a id="id824936" class="indexterm"></a>
+ <a id="id1320595" class="indexterm"></a>
+ List all packages installed on your system. The rightmost column in the output lists the repository from which the package was retrieved.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum list available</code> —
+ <a id="id773437" class="indexterm"></a>
+ <a id="id773453" class="indexterm"></a>
+ List all available packages in all enabled repositories.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum grouplist</code> —
+ <a id="id415383" class="indexterm"></a>
+ <a id="id415398" class="indexterm"></a>
+ List all package groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum repolist</code> —
+ <a id="id829819" class="indexterm"></a>
+ <a id="id829835" class="indexterm"></a>
+ List the repository ID, name, and number of packages it provides for each <span class="emphasis"><em>enabled</em></span> repository.
+ </div></li></ul></div><h4>Displaying Package Info</h4><div class="para">
+ <code class="command">yum info <em class="replaceable"><code><package_name></code></em> [<span class="optional"><em class="replaceable"><code>more_names</code></em></span>] </code> <a id="id769574" class="indexterm"></a>
+ <a id="id769590" class="indexterm"></a>
+ displays information about one or more packages (glob expressions are valid here as well):
+ </div><pre class="screen">
+~]# <code class="command">yum info abrt</code>
+Loaded plugins: presto, refresh-packagekit, security
+Installed Packages
+Name : abrt
+Arch : x86_64
+Version : 0.0.9
+Release : 2.fc12
+Size : 525 k
+Repo : installed
+From repo : fedora
+Summary : Automatic bug detection and reporting tool
+URL : https://fedorahosted.org/abrt/
+License : GPLv2+
+Description: abrt is a tool to help users to detect defects in applications and
+ : to create bug reports that include all information required by the
+ : maintainer to hopefully resolve it. It uses a plugin system to extend
+ : its functionality.
+</pre><div class="para">
+ <a id="id458655" class="indexterm"></a>
+ <a id="id458671" class="indexterm"></a>
+ <code class="command">yum info <em class="replaceable"><code><package_name></code></em> </code> is similar to the <code class="command">rpm -q --info <em class="replaceable"><code><package_name></code></em> </code> command, but provides as additional information the ID of the <span class="application"><strong>Yum</strong></span> repository the RPM package is found in (look for the <span class="emphasis"><em>From repo:</em></span> line in the output).
+ </div><div class="para">
+ <code class="command">yumdb info <em class="replaceable"><code><package_name></code></em> [<span class="optional"><em class="replaceable"><code>more_names</code></em></span>] </code> can be used to query the <span class="application"><strong>Yum</strong></span> database for alternative and useful information about a package, including the checksum of the package (and algorithm used to produce it, such as SHA-256), the command given on the command line that was invoked to install the package (if any), and the reason that the package is installed on the system (where <code class="computeroutput">user</code> indicates it was installed by the user, and <code class="computeroutput">dep</code> means it was brought in as a dependency):
+ </div><pre class="screen">~]# <code class="command">yumdb info yum</code>
+yum-3.2.27-3.fc12.noarch
+ checksum_data = 8d7773ec28c954c69c053ea4bf61dec9fdea11a59c50a2c31d1aa2e24bc611d9
+ checksum_type = sha256
+ command_line = update
+ from_repo = updates
+ from_repo_revision = 1272392716
+ from_repo_timestamp = 1272414297
+ reason = user
+ releasever = 12</pre><div class="para">
+ See <code class="command">man yumdb</code> for more information on the <code class="command">yumdb</code> command.
+ </div><div class="para">
+ Finally, the <code class="command">yum history</code> command, which is new in Fedora 14, can be used to show a timeline of <span class="application"><strong>Yum</strong></span> transactions, the dates and times on when they occurred, the number of packages affected, whether transactions succeeded or were aborted, and if the RPM database was changed between transactions. Refer to the <code class="computeroutput">history</code> section of <code class="command">man yum</code> for details.
+ </div></div><div class="section" title="1.2.2. Installing" id="sec-Installing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Installing">1.2.2. Installing</h3></div></div></div><a id="id473683" class="indexterm"></a><a id="id473695" class="indexterm"></a><div class="para">
+ You can install a package and all of its non-installed dependencies by entering:
+ </div><pre class="screen">~]# <code class="command">yum install <em class="replaceable"><code><package_name></code></em> </code>
+</pre><div class="para">
+ You can install multiple packages simultaneously by appending their names as arguments: <code class="command">yum install <em class="replaceable"><code><package_name></code></em> [<span class="optional"><em class="replaceable"><code>more_names</code></em></span>] </code>.
+ </div><div class="para">
+ If you are installing packages on a <em class="firstterm">multilib</em> system, such as an AMD64 or Intel64 machine, you can specify the architecture of the package (as long as it's available in an enabled repository) by appending <em class="replaceable"><code>.arch</code></em> to the package name:
+ </div><pre class="screen">
+~]# <code class="command">yum install sqlite2.i586</code>
+</pre><div class="para">
+ You can use glob expressions to quickly install multiple similarly-named packages:
+ </div><pre class="screen">
+~]# <code class="command">yum install audacious-plugins-\*</code>
+</pre><div class="para">
+ In addition to package names and glob expressions, you can also provide file names to <code class="command">yum install</code>. If you know the name of the binary you want to install, but not its package name, you can give <code class="command">yum install</code> the path name:
+ </div><pre class="screen">~]# <code class="command">yum install /usr/sbin/named</code>
+</pre><div class="para">
+ <code class="command">yum</code> then searches through its package lists, finds the package which provides /usr/sbin/named, if any, and prompts you as to whether you want to install it.
+ </div><div class="para">
+ What if you know you want to install the package that contains the <code class="filename">named</code> binary, but don't know in which bin or sbin directory that file lives? In that situation, you can give <code class="command">yum provides</code> a glob expression:
+ </div><div class="example" title="Example 1.5. Finding which package owns a file and installing it" id="ex-Finding_which_package_owns_a_file_and_installing_it"><h6>Example 1.5. Finding which package owns a file and installing it</h6><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum provides "*bin/named"</code>
+Loaded plugins: presto, refresh-packagekit, security
+32:bind-9.6.1-0.3.b1.fc11.x86_64 : The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server
+Repo : fedora
+Matched from:
+Filename : /usr/sbin/named
+~]# <code class="command">yum install bind</code>
+</pre></div></div><br class="example-break" /><div class="note" title="Note" id="note-Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <code class="command">yum provides</code> is the same as <code class="command">yum whatprovides</code>.
+ </div></div></div><div class="note" title="Tip: yum provides/whatprovides and Glob Expressions" id="note-Tip-yum_provides_whatprovides_and_Glob_Expressions"><div class="admonition_header"><h2>Tip: yum provides/whatprovides and Glob Expressions</h2></div><div class="admonition"><div class="para">
+ <code class="command">yum provides "*/<file_name>"</code> is a common and useful trick to quickly find the package(s) that contain <file_name>.
+ </div></div></div><h4>Installing a Package Group</h4><a id="id2226870" class="indexterm"></a><a id="id2226881" class="indexterm"></a><div class="para">
+ A package group is similar to a package: it is not useful by itself, but installing one pulls a group of dependent packages that serve a common purpose. A package group has a name and a groupid. The <code class="command">yum grouplist -v</code> command lists the names of all package groups, and, next to each of them, their <em class="firstterm">groupid</em> in parentheses. The groupid is always the term in the last pair of parentheses, such as <code class="literal">kde-desktop</code> and <code class="literal">kde-software-development</code> in this example:
+ </div><div class="important" title="Not all packages used in examples may be available on RHN"><div class="admonition_header"><h2>Not all packages used in examples may be available on RHN</h2></div><div class="admonition"><div class="para">
+ Some of the software packages—or package groups—queried for and installed with <span class="application"><strong>Yum</strong></span> in this chapter may not be available from Red Hat Network. Their use in examples is purely to demonstrate <span class="application"><strong>Yum</strong></span>'s command usage.
+ </div><div class="para">
+ Note that obtaining and installing software packages from unverified or untrusted software sources other than Red Hat Network constitutes a potential security risk, and could lead to security, stability, compatibility maintainability issues.
+ </div></div></div><pre class="screen">
+~]# <code class="command">yum -v grouplist kde\*</code>
+KDE (K Desktop Environment) (kde-desktop)
+KDE Software Development (kde-software-development)
+</pre><div class="para">
+ You can install a package group by passing its full group name (without the groupid part) to <code class="command">groupinstall</code>:
+ </div><pre class="screen">
+~]# <code class="command">yum groupinstall "KDE (K Desktop Environment)"</code>
+</pre><div class="para">
+ You can also install by groupid:
+ </div><pre class="screen">
+~]# <code class="command">yum groupinstall kde-desktop</code>
+</pre><div class="para">
+ You can even pass the groupid (or quoted name) to the <code class="command">install</code> command if you prepend it with an <span class="keysym">@</span>-symbol (which tells <code class="command">yum</code> that you want to perform a <code class="command">groupinstall</code>):
+ </div><pre class="screen">
+~]# <code class="command">yum install @kde-desktop</code>
+</pre></div><div class="section" title="1.2.3. Removing" id="sec-Removing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Removing">1.2.3. Removing</h3></div></div></div><a id="id849797" class="indexterm"></a><a id="id849809" class="indexterm"></a><div class="para">
+ <code class="command">yum remove <package_name></code> <a id="id2229300" class="indexterm"></a>
+ <a id="id2229316" class="indexterm"></a>
+ uninstalls (removes in <span class="application"><strong>RPM</strong></span> and <span class="application"><strong>Yum</strong></span> terminology) the package, as well as any packages that depend on it. As when you install multiple packages, you can remove several at once by adding more package names to the command:
+ </div><pre class="screen">
+ <code class="command">yum remove foo bar baz</code>
+</pre><div class="para">
+ Similar to <code class="command">install</code>, <code class="command">remove</code> can take these arguments:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ package names
+ </div></li><li class="listitem"><div class="para">
+ glob expressions
+ </div></li><li class="listitem"><div class="para">
+ file lists
+ </div></li><li class="listitem"><div class="para">
+ package provides
+ </div></li></ul></div>
+
+ </div><div class="warning" title="Warning: Removing a Package when Other Packages Depend On It" id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It"><div class="admonition_header"><h2>Warning: Removing a Package when Other Packages Depend On It</h2></div><div class="admonition"><div class="para">
+ <span class="application"><strong>Yum</strong></span> is not able to remove a package without also removing packages which depend on it. This type of operation can only be performed by <span class="application"><strong>RPM</strong></span>, is not advised, and can potentially leave your system in a non-functioning state or cause applications to misbehave and/or crash. For further information, refer to <a class="xref" href="#s2-rpm-uninstalling" title="3.2.4. Uninstalling">Section 3.2.4, “Uninstalling”</a> in the <span class="application"><strong>RPM</strong></span> chapter.
+ </div></div></div><h4>Removing a Package Group</h4><div class="para">
+ You can remove a package group using syntax congruent with the <code class="command">install</code> syntax.
+ </div><div class="example" title="Example 1.6. Alternative but equivalent ways of removing a package group" id="ex-Alternative_but_equivalent_ways_of_removing_a_package_group"><h6>Example 1.6. Alternative but equivalent ways of removing a package group</h6><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum groupremove "KDE (K Desktop Environment)"</code>
+~]# <code class="command">yum groupremove kde-desktop</code>
+~]# <code class="command">yum remove @kde-desktop</code>
+</pre></div></div><br class="example-break" /><div class="important" title="Smart package group removal" id="important-Smart_package_group_removal"><div class="admonition_header"><h2>Smart package group removal</h2></div><div class="admonition"><a id="id499522" class="indexterm"></a><a id="id508600" class="indexterm"></a><div class="para">
+ When you tell <span class="application"><strong>yum</strong></span> to remove a package group, it will remove every package in that group, even if those packages are members of other package groups or dependencies of other installed packages. However, you can instruct <code class="command">yum</code> to remove only those packages which are not required by any other packages or groups by adding the <code class="option">groupremove_leaf_only=1</code> directive to the <code class="literal">[main]</code> section of the <code class="filename">/etc/yum.conf</code> configuration file. For more information on this directive, refer to <a class="xref" href="#sec-Setting_main_Options" title="1.3.1. Setting [main] Options">Section 1.3.1, “Setting [main] Options”</a>.
+ </div></div></div></div></div><div class="section" title="1.3. Configuring Yum and Yum Repositories" id="sec-Configuring_Yum_and_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Configuring_Yum_and_Yum_Repositories">1.3. Configuring Yum and Yum Repositories</h2></div></div></div><a id="id548177" class="indexterm"></a><a id="id548188" class="indexterm"></a><div class="para">
+ This section shows you how to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ set global <span class="application"><strong>Yum</strong></span> options by editing the <code class="literal">[main]</code> section of the <code class="filename">/etc/yum.conf</code> configuration file;
+ </div></li><li class="listitem"><div class="para">
+ set options for individual repositories by editing the [<em class="replaceable"><code>repository</code></em>] sections in <code class="filename">/etc/yum.conf</code> and <em class="replaceable"><code>.repo</code></em> files in the <code class="filename">/etc/yum.repos.d/</code> directory;
+ </div></li><li class="listitem"><div class="para">
+ use <span class="application"><strong>Yum</strong></span> variables in <code class="filename">/etc/yum.conf</code> and files in <code class="filename">/etc/yum.repos.d/</code>so that dynamic version and architecture values are handled correctly; and,
+ </div></li><li class="listitem"><div class="para">
+ set up your own custom <span class="application"><strong>Yum</strong></span> repository.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">/etc/yum.conf</code> configuration file contains one mandatory <code class="literal">[main]</code> section under which you can set <span class="application"><strong>Yum</strong></span> options. The values that you define in the <code class="literal">[main]</code> section of <code class="filename">yum.conf</code> have global effect, and may override values set any individual [<em class="replaceable"><code>repository</code></em>] sections. You can also add [<em class="replaceable"><code>repository</code></em>] sections to <code class="filename">/etc/yum.conf</code>; however, best practice is to define individual repositories in new or existing <code class="filename">.repo</code> files in the <code class="filename">/etc/yum.repos.d/</code>directory. Refer to <a class="xref" href="#sec-Setting_repository_Options" title="1.3.2. Setting [repository] Options">Section 1.3.2, “Setting [repository] Options”</a> if you need to add or edit repository-
specific information.
+ </div><div class="section" title="1.3.1. Setting [main] Options" id="sec-Setting_main_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Setting_main_Options">1.3.1. Setting [main] Options</h3></div></div></div><a id="id1118499" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/yum.conf</code> configuration file contains exactly one <code class="literal">[main]</code> section. You can add many additional options under the <code class="literal">[main]</code> section heading in <code class="filename">/etc/yum.conf</code>. Some of the key-value pairs in the <code class="literal">[main]</code> section affect how <code class="command">yum</code> operates; others affect how <span class="application"><strong>Yum</strong></span> treats repositories. The best source of information for all <span class="application"><strong>Yum</strong></span> options is in the <code class="literal">[main] OPTIONS</code> and <code class="literal">[repository] OPTIONS</code> sections of <code class="command">man yum.conf</code>.
+ </div><div class="para">
+ Here is a sample <code class="filename">/etc/yum.conf</code> configuration file:
+ </div><pre class="screen">
+[main]
+cachedir=/var/cache/yum/$basearch/$releasever
+keepcache=0
+debuglevel=2
+logfile=/var/log/yum.log
+exactarch=1
+obsoletes=1
+gpgcheck=1
+plugins=1
+installonly_limit=3
+<em class="lineannotation"><span class="lineannotation">[comments abridged]</span></em>
+# PUT YOUR REPOS HERE OR IN separate files named file.repo
+# in /etc/yum.repos.d
+</pre><div class="para">
+ Here is a list of the most commonly-used options in the <code class="literal">[main]</code> section, and descriptions for each:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">assumeyes=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — <code class="command">yum</code> should prompt for confirmation of critical actions it performs. This is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — Do not prompt for confirmation of critical <code class="command">yum</code> actions. If <code class="literal">assumeyes=1</code> is set, <code class="command">yum</code> behaves in the same way that the command line option <code class="option">-y</code> does.
+ </div></dd><dt class="varlistentry"><span class="term">cachedir=<code class="filename">/var/cache/yum/$basearch/$releasever</code> </span></dt><dd><div class="para">
+ This option specifies the directory where <span class="application"><strong>Yum</strong></span> should store its cache and database files. By default, <span class="application"><strong>Yum</strong></span>'s cache directory is <code class="filename">/var/cache/yum/$basearch/$releasever</code>. See <a class="xref" href="#sec-Using_Yum_Variables" title="1.3.3. Using Yum Variables">Section 1.3.3, “Using Yum Variables”</a> for descriptions of the <code class="envar">$basearch</code> and <code class="envar">$releasever</code> <span class="application"><strong>Yum</strong></span> variables.
+ </div></dd><dt class="varlistentry"><span class="term">debuglevel=<em class="replaceable"><code>value</code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is an integer between <code class="constant">1</code> and <code class="constant">10</code>. Setting a higher <code class="literal">debuglevel</code> value causes <code class="command">yum</code> to display more detailed debugging output. <code class="literal">debuglevel=0</code> disables debugging output, while <code class="literal">debuglevel=2</code> is the default.
+ </div></dd><dt class="varlistentry"><span class="term">exactarch=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Do not take into account the exact architecture when updating packages.
+ </div><div class="para">
+ <code class="constant">1</code> — Consider the exact architecture when updating packages. With this setting, <code class="command">yum</code> will not install an i686 package to update an i386 package already installed on the system. This is the default.
+ </div></dd><dt class="varlistentry"><span class="term">exclude=<em class="replaceable"><code><package_name></code></em> [<span class="optional"><em class="replaceable"><code>more_package_names</code></em> </span>] </span></dt><dd><div class="para">
+ This option allows you to exclude packages by keyword during installation/updates. Listing multiple packages for exclusion can be accomplished by quoting a space-delimited list of packages. Shell globs using wildcards (for example, <code class="literal">*</code> and <code class="literal">?</code>) are allowed.
+ </div></dd><dt class="varlistentry"><span class="term">gpgcheck=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable GPG signature-checking on packages in all repositories, including local package installation.
+ </div><div class="para">
+ <code class="constant">1</code> — Enable GPG signature-checking on all packages in all repositories, including local package installation. <code class="literal">gpgcheck=1</code> is the default, and thus all packages' signatures are checked.
+ </div><div class="para">
+ If this option is set in the <code class="literal">[main]</code> section of the <code class="filename">/etc/yum.conf</code> file, it sets the GPG-checking rule for all repositories. However, you can also set <code class="literal">gpgcheck=</code> <em class="replaceable"><code><value></code></em> for individual repositories instead; i.e., you can enable GPG-checking on one repository while disabling it on another. Setting <code class="literal">gpgcheck=<em class="replaceable"><code><value></code></em> </code> for an individual repository in its correpsonding <code class="filename">.repo</code> file overrides the default if it is present in <code class="filename">/etc/yum.conf</code>. Refer to <a class="xref" href="#s1-check-rpm-sig" title="3.3. Checking a Package's Signature">Section 3.3, “Checking a Package's Signature”</a> for further information on GPG signature-checking.
+ </div></dd><dt class="varlistentry"><span class="term">groupremove_leaf_only=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — <code class="command">yum</code> should <span class="emphasis"><em>not</em></span> check the dependencies of each package when removing a package group. With this setting, <code class="command">yum</code> removes all packages in a package group, regardless of whether those packages are required by other packages or groups. <code class="literal">groupremove_leaf_only=0</code> is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — <code class="command">yum</code> should check the dependencies of each package when removing a package group, and remove only those packages which are not not required by any other package or group.
+ </div><div class="para">
+ For more information on removing packages, refer to <a class="xref" href="#important-Smart_package_group_removal" title="Smart package group removal">Smart package group removal</a>.
+ </div></dd><dt class="varlistentry"><span class="term">installonlypkgs=<em class="replaceable"><code><space></code></em> <em class="replaceable"><code><separated></code></em> <em class="replaceable"><code><list></code></em> <em class="replaceable"><code><of></code></em> <em class="replaceable"><code><packages></code></em> </span></dt><dd><div class="para">
+ Here you can provide a space-separated list of packages which <code class="command">yum</code> can <span class="emphasis"><em>install</em></span>, but will never <span class="emphasis"><em>update</em></span>. Refer to <code class="command">man yum.conf</code> for the list of packages which are install-only by default. If you add the <code class="literal">installonlypkgs</code> directive to <code class="filename">/etc/yum.conf</code>, you should ensure that you list <span class="emphasis"><em>all</em></span> of the packages that should be install-only, including any of those listed under the <code class="literal">installonlypkgs</code> section of <code class="command">man yum.conf</code>. In particular, kernel packages should always be listed in <code class="literal">installonlypkgs</code> (as they are by default), and <code class="literal">installonly_limit</code> should always be set to a value greater than <code class="constant">2</code> so that a backup kernel is a
lways available in case the default one fails to boot. Refer to <a class="xref" href="#varentry-installonly_limit_value">installonly_limit=<em class="replaceable"><code><value></code></em> </a> for details on the <code class="literal">installonly_limit</code> directive.
+ </div></dd><dt class="varlistentry" id="varentry-installonly_limit_value"><span class="term">installonly_limit=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is an integer representing the maximum number of versions that can be installed simultaneously for any single package listed in the <code class="literal">installonlypkgs</code> directive. The defaults for the <code class="literal">installonlypkgs</code> directive include several different kernel packages, so be aware that changing the value of <code class="literal">installonly_limit</code> will also affect the maximum number of installed versions of any single kernel package. The default value listed in <code class="filename">/etc/yum.conf</code> is <code class="literal">installonly_limit=3</code>, and it is not recommended to decrease this value, particularly below <code class="constant">2</code>.
+ </div></dd><dt class="varlistentry"><span class="term">keepcache=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where value is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Do not retain the cache of headers and packages after a successful installation. This is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — Retain the cache after a successful installation.
+ </div></dd><dt class="varlistentry"><span class="term">logfile=<code class="filename">/var/log/yum.log</code> </span></dt><dd><div class="para">
+ This option specifies where <code class="command">yum</code> should send its logging output. By default, <code class="command">yum</code> logs to <code class="filename">/var/log/yum.log</code>.
+ </div></dd><dt class="varlistentry"><span class="term">multilib_policy=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <strong class="userinput"><code>best</code></strong> — install the best-choice architecture for this system. For example, setting <code class="literal">multilib_policy=best</code> on an AMD64 system causes <code class="command">yum</code> to install 64-bit versions of all packages.
+ </div><div class="para">
+ <strong class="userinput"><code>all</code></strong> — always install every possible architecture for every package. For example, with <code class="literal">multilib_policy</code> set to <code class="literal">all</code> on an AMD64 system, <code class="command">yum</code> would install both the i586 and AMD64 versions of a package, if both were available.
+ </div></dd><dt class="varlistentry"><span class="term">obsoletes=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable <code class="command">yum</code>'s obsoletes processing logic when performing updates.
+ </div><div class="para">
+ <code class="constant">1</code> — Enable <code class="command">yum</code>'s obsoletes processing logic when performing updates. When one package declares in its spec file that it <em class="firstterm">obsoletes</em> another package, the latter package will be replaced by the former package when the former package is installed. Obsoletes are declared, for example, when a package is renamed. <code class="literal">obsoletes=1</code> the default.
+ </div></dd><dt class="varlistentry"><span class="term">plugins=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable all <span class="application"><strong>Yum</strong></span> plugins globally.
+ </div><div class="important" title="Disabling plugins is not advised" id="important-Disabling_plugins_is_not_advised-main_options"><div class="admonition_header"><h2>Disabling plugins is not advised</h2></div><div class="admonition"><div class="para">
+ Disabling all plugins is not advised because certain plugins provide important <code class="command">Yum</code> services. In particular, <span class="application"><strong>rhnplugin</strong></span> enables connecting to <code class="systemitem">Red Hat Network</code>, and the security plugin allows system administrators to easily update the system with (sometimes critical) security updates. Disabling plugins globally is provided as a convenience option, and is generally only recommended when diagnosing a potential problem with <code class="command">Yum</code>.
+ </div></div></div><div class="para">
+ <code class="constant">1</code> — Enable all <span class="application"><strong>Yum</strong></span> plugins globally. With <code class="literal">plugins=1</code>, you can still disable a specific <span class="application"><strong>Yum</strong></span> plugin by setting <code class="literal">enabled=0</code> in that plugin's configuration file. Refer to <a class="xref" href="#sec-Yum_Plugins" title="1.4. Yum Plugins">Section 1.4, “Yum Plugins”</a> for more information about various <span class="application"><strong>Yum</strong></span> plugins, or to <a class="xref" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins" title="1.4.1. Enabling, Configuring and Disabling Yum Plugins">Section 1.4.1, “Enabling, Configuring and Disabling Yum Plugins”</a> for further information on controlling plugins.
+ </div></dd><dt class="varlistentry"><span class="term">reposdir=<em class="replaceable"><code></absolute/path/to/directory/containing/repo/files></code></em> </span></dt><dd><div class="para">
+ This option allows you to specify a directory where <code class="filename">.repo</code> files are located. All <code class="filename">.repo</code> files contain repository information (similar to the [<em class="replaceable"><code>repository</code></em>] section(s) of <code class="filename">/etc/yum.conf</code>). <code class="command">yum</code> collects all repository information from <code class="filename">.repo</code> files and the [<em class="replaceable"><code>repository</code></em>] section of the <code class="filename">/etc/yum.conf</code> file to create a master list of repositories to use for transactions. Refer to <a class="xref" href="#sec-Setting_repository_Options" title="1.3.2. Setting [repository] Options">Section 1.3.2, “Setting [repository] Options”</a> for more information about options you can use for both the [<em class="replaceable"><code>repository</code></em>] section and <code class="filename">.repo</code> files. If <code class="literal">
reposdir</code> is not set, <code class="command">yum</code> uses the default directory <code class="filename">/etc/yum.repos.d/</code>.
+ </div></dd><dt class="varlistentry"><span class="term">retries=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is an integer <code class="constant">0</code> or greater. This value sets the number of times <code class="command">yum</code> should attempt to retrieve a file before returning an error. Setting this to <code class="constant">0</code> makes <code class="command">yum</code> retry forever. The default value is <code class="constant">10</code>.
+ </div></dd></dl></div></div><div class="section" title="1.3.2. Setting [repository] Options" id="sec-Setting_repository_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Setting_repository_Options">1.3.2. Setting [repository] Options</h3></div></div></div><a id="id2226334" class="indexterm"></a><div class="para">
+ You can define individual <span class="application"><strong>Yum</strong></span> repositories by adding [<em class="replaceable"><code>repository</code></em>] sections (where <em class="replaceable"><code>repository</code></em> is a unique repository ID, such as [<em class="replaceable"><code>my_personal_repo</code></em>]) to <code class="filename">/etc/yum.conf</code> or to <code class="filename">.repo</code> files in the <code class="filename">/etc/yum.repos.d/</code>directory. All <code class="filename">.repo</code> files in <code class="filename">/etc/yum.repos.d/</code>are read by <code class="command">yum</code>; best practice is to define your repositories here instead of in <code class="filename">/etc/yum.conf</code>. You can create new, custom <code class="filename">.repo</code> files in this directory, add [<em class="replaceable"><code>repository</code></em>] sections to those files, and the next time you run a <code class="command">yum</code> command, it will
take all newly-added repositories into account.
+ </div><div class="para">
+ Here is a (bare-minimum) example of the form a <code class="filename">.repo</code> file should take:
+ </div><pre class="screen">
+[repository_ID]
+name=A Repository Name
+baseurl=http://path/to/repo or ftp://path/to/repo or file://path/to/local/repo
+</pre><div class="para">
+ Every [<em class="replaceable"><code>repository</code></em>] section must contain the following minimum parts:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> [<em class="replaceable"><code>repository_ID</code></em>] </span></dt><dd><div class="para">
+ The repository ID is a unique, one-word (no spaces; underscores are allowed) string of characters (enclosed by brackets) that serves as a repository identifier.
+ </div></dd><dt class="varlistentry"><span class="term">name=<em class="replaceable"><code><My Repository Name></code></em> </span></dt><dd><div class="para">
+ This is a human-readable string describing the repository.
+ </div></dd><dt class="varlistentry"><span class="term">baseurl=http://path/to/repo, ftp://path/to/repo, file://path/to/local/repo</span></dt><dd><div class="para">
+ This is a URL to the directory where the repodata directory of a repository is located. Usually this URL is an HTTP link, such as:
+ </div><pre class="screen">baseurl=http://path/to/repo/releases/$releasever/server/$basearch/os/</pre><div class="para">
+ <span class="application"><strong>Yum</strong></span> always expands the <code class="envar">$releasever</code>, <code class="envar">$arch</code> and <code class="envar">$basearch</code> variables in URLs. See the following section for explanations of all <span class="application"><strong>Yum</strong></span> variables: <a class="xref" href="#sec-Using_Yum_Variables" title="1.3.3. Using Yum Variables">Section 1.3.3, “Using Yum Variables”</a>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If the repository is available over FTP, use: ftp://path/to/repo
+ </div></li><li class="listitem"><div class="para">
+ If the repository is local to the machine, use file://path/to/local/repo
+ </div></li><li class="listitem"><div class="para">
+ If a specific online repository requires basic HTTP authentication, you can specify your username and password in the <code class="literal">http://path/to/repo</code> by prepending it as <code class="command">username:password at link</code>. For example, if a repository on http://www.example.com/repo/ requires a username of "user" and a password of "password", then the <code class="literal">baseurl</code> link could be specified as:
+ </div><pre class="screen">baseurl=http://<strong class="userinput"><code>user</code></strong>:<strong class="userinput"><code>password</code></strong>@www.example.com/repo/</pre></li></ul></div></dd></dl></div><div class="para">
+ The following is another useful [<em class="replaceable"><code>repository</code></em>] directive:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">enabled=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — do not include this repository as a package source when performing updates and installs. This is an easy way of quickly turning repositories on and off, which is useful when you desire a single package from a repository that you do not want to enable for updates or installs.
+ </div><div class="para">
+ <code class="constant">1</code> — include this repository as a package source.
+ </div><div class="para">
+ Turning repositories on and off can also be performed quickly by passing either the <code class="option">--enablerepo=<<em class="replaceable"><code>repo_name</code></em>></code> or <code class="option">--disablerepo=<<em class="replaceable"><code>repo_name</code></em>></code> option to <code class="command">yum</code>, or easily through <span class="application"><strong>PackageKit</strong></span>'s <span class="guilabel"><strong>Add/Remove Software</strong></span> window.
+ </div></dd></dl></div><div class="para">
+ Many more [<em class="replaceable"><code>repository</code></em>] options exist. Refer to the <code class="literal">[repository] OPTIONS</code> section of <code class="command">man yum.conf</code> for the exhaustive list and descriptions for each.
+ </div></div><div class="section" title="1.3.3. Using Yum Variables" id="sec-Using_Yum_Variables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Using_Yum_Variables">1.3.3. Using Yum Variables</h3></div></div></div><a id="id476013" class="indexterm"></a><div class="para">
+ You can use and reference the following variables in <code class="command">yum</code> commands and in all <span class="application"><strong>Yum</strong></span> configuration files (<code class="filename">/etc/yum.conf</code> and all <code class="filename">.repo</code> files in <code class="filename">/etc/yum.repos.d/</code>.
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="envar">$releasever</code> </span></dt><dd><div class="para">
+ You can use this variable to reference the release version of Fedora. <span class="application"><strong>Yum</strong></span> obtains the value of <code class="filename">$releasever</code> from the <code class="literal">distroverpkg=<value></code> line in the <code class="filename">/etc/yum.conf</code> configuration file. If there is no such line in <code class="filename">/etc/yum.conf</code>, then <code class="command">yum</code> infers the correct value by deriving the version number from the <code class="filename">redhat-release</code> package.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="envar">$arch</code> </span></dt><dd><div class="para">
+ You can use this variable to refer to the system's CPU architecture as returned when calling Python's <code class="methodname">os.uname()</code> function. Valid values for <code class="envar">$arch</code> include: <code class="literal">i586</code>, <code class="literal">i686</code> and <code class="literal">x86_64</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="envar">$basearch</code> </span></dt><dd><div class="para">
+ You can use <code class="envar">$basearch</code> to reference the base architecture of the system. For example, i686 and i586 machines both have a base architecture of <code class="literal">i386</code>, and AMD64 and Intel64 machines have a base architecture of <code class="literal">x86_64</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="envar">$YUM0-9</code> </span></dt><dd><div class="para">
+ These ten variables are each replaced with the value of any shell environment variables with the same name. If one of these variables is referenced (in <code class="filename">/etc/yum.conf</code> for example) and a shell environment variable with the same name does not exist, then the configuration file variable is not replaced.
+ </div></dd></dl></div></div><div class="section" title="1.3.4. Creating a Yum Repository" id="sec-Creating_a_Yum_Repository"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Creating_a_Yum_Repository">1.3.4. Creating a Yum Repository</h3></div></div></div><a id="id716850" class="indexterm"></a><div class="para">
+ To set up a <span class="application"><strong>Yum</strong></span> repository, follow these steps:
+ </div><div class="procedure" title="Procedure 1.1. Setting Up a Yum repository" id="procedure-Setting_Up_a_Yum_repository"><h6>Procedure 1.1. Setting Up a <span class="application"><strong>Yum</strong></span> repository</h6><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Install the <code class="filename">createrepo</code> package:
+ </div><pre class="screen">~]# <code class="command">yum install createrepo</code>
+</pre></li><li class="step" title="Step 2"><div class="para">
+ Copy all of the packages into one directory, such as <code class="filename">/mnt/local_repo/</code>.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Run the <code class="command">createrepo --database</code> command on that directory:
+ </div><pre class="screen">~]# <code class="command">createrepo --database /mnt/local_repo</code>
+</pre><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Because RPM packages for Fedora 14 are compressed using the XZ lossless data compression format, and may also be signed using alternative (and stronger) hash algorithms such as SHA-256, it is not possible to run <code class="command">createrepo</code> on Fedora 5 to create the package metadata for Fedora 14 packages. The <code class="command">createrepo</code> command relies on <code class="command">rpm</code> to open and inspect the packages, and <code class="command">rpm</code> on Fedora 5 is not able to open the improved Fedora 14 RPM package format.
+ </div></div></div></li></ol></div><div class="para">
+ This will create the necessary metadata for your <span class="application"><strong>Yum</strong></span> repository, as well as the <span class="application"><strong>sqlite</strong></span> database for speeding up <code class="command">yum</code> operations.
+ </div></div></div><div class="section" title="1.4. Yum Plugins" id="sec-Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Yum_Plugins">1.4. Yum Plugins</h2></div></div></div><a id="id834456" class="indexterm"></a><div class="para">
+ <span class="application"><strong>Yum</strong></span> provides plugins that extend and enhance its operations. Certain plugins are installed by default. <span class="application"><strong>Yum</strong></span> always informs you which plugins, if any, are loaded and active whenever you call any <code class="command">yum</code> command:
+ </div><pre class="screen">
+~]# <code class="command">yum info yum</code>
+Loaded plugins: presto, refresh-packagekit, security
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em>
+</pre><div class="para">
+ Note that the plugin names which follow <code class="command">Loaded plugins</code> are the names you can provide to the <code class="option">--disableplugins=<em class="replaceable"><code><plugin_name></code></em> </code> option.
+ </div><div class="section" title="1.4.1. Enabling, Configuring and Disabling Yum Plugins" id="sec-Enabling_Configuring_and_Disabling_Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Enabling_Configuring_and_Disabling_Yum_Plugins">1.4.1. Enabling, Configuring and Disabling Yum Plugins</h3></div></div></div><a id="id831489" class="indexterm"></a><a id="id831501" class="indexterm"></a><a id="id831513" class="indexterm"></a><div class="para">
+ To enable <span class="application"><strong>Yum</strong></span> plugins, ensure that a line beginning with <code class="command">plugins=</code> is present in the <code class="literal">[main]</code> section of <code class="filename">/etc/yum.conf</code>, and that its value is set to <code class="constant">1</code>:
+ </div><pre class="screen">
+plugins=1
+</pre><div class="para">
+ You can disable all plugins by changing this line to <code class="command">plugins=0</code>.
+ </div><div class="important" title="Disabling plugins is not advised" id="important-Disabling_plugins_is_not_advised-plugins"><div class="admonition_header"><h2>Disabling plugins is not advised</h2></div><div class="admonition"><div class="para">
+ Disabling all plugins is not advised because certain plugins provide important <code class="command">Yum</code> services. In particular, <span class="application"><strong>rhnplugin</strong></span> enables connecting to <code class="systemitem">Red Hat Network</code>, and the security plugin allows system administrators to easily update the system with (sometimes critical) security updates. Disabling plugins globally is provided as a convenience option, and is generally only recommended when diagnosing a potential problem with <code class="command">Yum</code>.
+ </div></div></div><div class="para">
+ Every installed plugin has its own configuration file in the <code class="filename">/etc/yum/pluginconf.d/</code> directory. You can set plugin-specific options in these files. For example, here is the <span class="application"><strong>security</strong></span> plugin's <code class="filename">security.conf</code> configuration file:
+ </div><div class="example" title="Example 1.7. A minimal Yum plugin configuration file" id="ex-A_minimal_Yum_plugin_configuration_file"><h6>Example 1.7. A minimal <span class="application">Yum</span> plugin configuration file</h6><div class="example-contents"><pre class="screen">
+[main]
+enabled=1
+</pre></div></div><br class="example-break" /><div class="para">
+ Plugin configuration files always contain a <code class="literal">[main]</code> section (similar to <span class="application"><strong>Yum</strong></span>'s <code class="filename">/etc/yum.conf</code> file) in which there is (or you can place if it is missing) an <code class="literal">enabled=</code> option that controls whether the plugin is enabled when you run <code class="command">yum</code> commands.
+ </div><div class="para">
+ If you disable all plugins by setting <code class="command">enabled=0</code> in <code class="filename">/etc/yum.conf</code>, then all plugins are disabled regardless of whether they are enabled in their individual configuration files.
+ </div><div class="para">
+ If you merely want to disable all <span class="application"><strong>Yum</strong></span> plugins for a single <code class="command">yum</code> command, use the <code class="option">--noplugins</code> option.
+ </div><div class="para">
+ If you simply want to disable one or more <span class="application"><strong>Yum</strong></span> plugins for a single <code class="command">yum</code> command, then you can add the <code class="option">--disableplugin=<plugin_name></code> option to the command:
+ </div><div class="example" title="Example 1.8. Disabling the presto plugin while running yum update" id="ex-Disabling_the_presto_plugin_while_running_yum_update"><h6>Example 1.8. Disabling the presto plugin while running yum update</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum update --disableplugin=presto</code>
+</pre></div></div><br class="example-break" /><div class="para">
+ The plugin names you provide to the <code class="option">--disableplugin=</code> option are the same names listed after the <code class="command">Loaded plugins:</code> line in the output of any <code class="command">yum</code> command. You can disable multiple plugins by separating their names with commas. In addition, you can match multiple similarly-named plugin names or simply shorten long ones by using glob expressions: <code class="option">--disableplugin=presto,refresh-pack*</code>.
+ </div></div><div class="section" title="1.4.2. Installing More Yum Plugins" id="sec-Installing_More_Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Installing_More_Yum_Plugins">1.4.2. Installing More Yum Plugins</h3></div></div></div><div class="para">
+ <span class="application"><strong>Yum</strong></span> plugins usually adhere to the <code class="filename">yum-plugin-<em class="replaceable"><code><plugin_name></code></em> </code> package-naming convention, but not always: the package which provides the <span class="application"><strong>presto</strong></span> plugin is named <code class="filename">yum-presto</code>, for example. You can install a <span class="application"><strong>Yum</strong></span> plugin in the same way you install other packages:
+ </div><pre class="screen">
+~]# <code class="command">yum install yum-plugin-security</code>
+</pre></div><div class="section" title="1.4.3. Plugin Descriptions" id="sec-Plugin_Descriptions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Plugin_Descriptions">1.4.3. Plugin Descriptions</h3></div></div></div><div class="para">
+ Here are descriptions of a few useful <span class="application"><strong>Yum</strong></span> plugins:
+ </div><h4>presto (yum-presto)</h4><a id="id630785" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>presto</strong></span> plugin adds support to <span class="application"><strong>Yum</strong></span> for downloading <em class="firstterm">delta RPM</em> packages, during updates, from repositories which have <span class="application"><strong>presto</strong></span> metadata enabled. Delta RPMs contain only the differences between the version of the package installed on the client requesting the RPM package and the updated version in the repository. Downloading a delta RPM is much quicker than downloading the entire updated package, and can speed up updates considerably. Once the delta RPMs are downloaded, they must be rebuilt (the difference applied to the currently-installed package to create the full updated package) on the installing machine, which takes CPU time. Using delta RPMs is therefore a tradeoff between time-to-download, which depends on the network connection, and time-to-rebuild, which is CPU-bound. Using the <span class
="application"><strong>presto</strong></span> plugin is recommended for fast machines and systems with slower network connections, while slower machines on very fast connections <span class="emphasis"><em>may</em></span> benefit more from downloading normal RPM packages, i.e. by disabling <span class="application"><strong>presto</strong></span>. The <span class="application"><strong>presto</strong></span> plugin is enabled by default.
+ </div><h4>protect-packages (yum-plugin-protect-packages)</h4><a id="id576335" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>protect-packages</strong></span> plugin prevents the <code class="filename">yum</code> package and all packages it depends on from being purposefully or accidentally removed. This simple scheme prevents many of the most important packages necessary for your system to run from being removed. In addition, you can list more packages, one per line, in the <code class="filename">/etc/sysconfig/protected-packages</code> file<sup>[<a id="footnote-Alternative_Locations_for_protect-packages_Lists" href="#ftn.footnote-Alternative_Locations_for_protect-packages_Lists" class="footnote">1</a>]</sup> (which you should create if it does not exist), and <span class="application"><strong>protect-packages</strong></span> will extend protection-from-removal to those packages as well. To temporarily override package protection, use the <code class="option">--override-protection</code> option with an applicable <code class="command">yum</code> command.
+ </div><h4>rhnplugin (yum-rhn-plugin)</h4><a id="id670129" class="indexterm"></a><a id="id759867" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>rhnplugin</strong></span> for <span class="application"><strong>Yum</strong></span> provides support for connecting to <code class="systemitem">Red Hat Network</code> (RHN). Systems registered with <code class="systemitem">RHN</code> are able to update and install packages from <code class="systemitem">Red Hat Network</code>.
+ </div><div class="para">
+ Refer to <code class="command">man rhnplugin</code> for more information.
+ </div><h4>refresh-packagekit (PackageKit-yum-plugin)</h4><a id="id830192" class="indexterm"></a><div class="para">
+ This plugin updates metadata for <span class="application"><strong>PackageKit</strong></span> whenever <span class="application"><strong>yum</strong></span> is run. The <span class="application"><strong>refresh-packagekit</strong></span> plugin is installed by default.
+ </div><h4>security (yum-plugin-security)</h4><a id="id503126" class="indexterm"></a><div class="para">
+ Discovering information about and applying security updates easily and often is important to all system administrators. For this reason <span class="application"><strong>Yum</strong></span> provides the <span class="application"><strong>security</strong></span> plugin, which extends <code class="command">yum</code> with a set of highly-useful security-related commands, subcommands and options.
+ </div><div class="para">
+ You can check for all security-related updates as follows:
+ </div><pre class="screen">
+~]# <code class="command">yum check-update --security</code>
+Loaded plugins: presto, refresh-packagekit, security
+Limiting package lists to security relevant ones
+Needed 3 of 7 packages, for security
+elinks.x86_64 0.12-0.13.pre3.fc11 fedora
+kernel.x86_64 2.6.30.8-64.fc11 fedora
+kernel-headers.x86_64 2.6.30.8-64.fc11 fedora</pre><div class="para">
+ You can then use either <code class="command">yum update --security</code> or <code class="command">yum update-minimal --security</code> to update those packages which are affected by security advisories. Both of these commands update all packages on the system for which a security advisiory has been issued. <code class="command">yum update-minimal --security</code> updates them to the latest packages which were released as part of a security advisory, while <code class="command">yum update --security</code> will update all packages affected by a security advisory <span class="emphasis"><em>to the latest version of that package available</em></span>.
+ </div><div class="para">
+ In other words, if:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ the <span class="package">kernel-2.6.30.8-16</span> package is installed on your system;
+ </div></li><li class="listitem"><div class="para">
+ the <span class="package">kernel-2.6.30.8-32</span> package was released as a security update;
+ </div></li><li class="listitem"><div class="para">
+ then <span class="package">kernel-2.6.30.8-64</span> was released as a bug fix update,
+ </div></li></ul></div><div class="para">
+ ...then <code class="command">yum update-minimal --security</code> will update you to <span class="package">kernel-2.6.30.8-32</span>, and <code class="command">yum update --security</code> will update you to <span class="package">kernel-2.6.30.8-64</span>. Conservative system administrators may want to use <code class="command">update-minimal</code> to reduce the risk incurred by updating packages as much as possible.
+ </div><div class="para">
+ Refer to <code class="command">man yum-security</code> for usage details and further explanation of the enhancements the <span class="application"><strong>security</strong></span> plugin adds to <code class="command">yum</code>.
+ </div></div></div><div class="section" title="1.5. Additional Resources" id="sec-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Additional_Resources">1.5. Additional Resources</h2></div></div></div><a id="id807350" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> The <span class="application"><strong>Yum</strong></span> home page and wiki — <a href="http://yum.baseurl.org/wiki/Guides">http://yum.baseurl.org/wiki/Guides</a> </span></dt><dd><div class="para">
+ The <code class="literal">Yum Guides</code> section of the wiki contains more <span class="application"><strong>Yum</strong></span> documentation.
+ </div></dd><dt class="varlistentry"><span class="term"> Managing Software with <span class="application"><strong>Yum</strong></span> — <a href="http://docs.fedoraproject.org/en-US/Fedora_Core/5/html-single/Software_Management_Guide/">http://docs.fedoraproject.org/en-US/Fedora_Core/5/html-single/Software_Management_Guide/</a> </span></dt><dd><div class="para">
+ A useful resource that provides additional information about using the <span class="application"><strong>Yum</strong></span> package manager.
+ </div></dd></dl></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote" id="footnote-Alternative_Locations_for_protect-packages_Lists"><p><sup>[<a id="ftn.footnote-Alternative_Locations_for_protect-packages_Lists" href="#footnote-Alternative_Locations_for_protect-packages_Lists" class="para">1</a>] </sup>
+ You can also place files with the extension <code class="filename">.list</code> in the <code class="filename">/etc/sysconfig/protected-packages.d/</code> directory (which you should create if it does not exist), and list packages—one per line—in these files. <span class="application"><strong>protect-packages</strong></span> will protect these too.
+ </p></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 2. PackageKit" id="ch-PackageKit" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. PackageKit</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sec-Updating_Packages_with_Software_Update">2.1. Updating Packages with Software Update</a></span></dt><dt><span class="section"><a href="#sec-Using_Add_Remove_Software">2.2. Using Add/Remove Software</a></span></dt><dt><span class="section"><a href="#sec-PackageKit_Architecture">2.3. PackageKit Architecture</a></span></dt><dt><span class="section"><a href="#ch-Graphical_Package_Management-sec-Additional_Resources">2.4. Additional Resources</a></span></dt></dl></div><a id="id833871" class="indexterm"></a><div class="para">
+ Red Hat provides <span class="application"><strong>PackageKit</strong></span> for viewing, managing, updating, installing and uninstalling packages
+ <a id="id848985" class="indexterm"></a>
+ <a id="id499202" class="indexterm"></a>
+ <a id="id813327" class="indexterm"></a>
+ <a id="id533309" class="indexterm"></a>
+ <a id="id581123" class="indexterm"></a>
+ <a id="id1636290" class="indexterm"></a>
+ <a id="id729368" class="indexterm"></a>
+ <a id="id1338746" class="indexterm"></a>
+ <a id="id426191" class="indexterm"></a>
+ <a id="id435508" class="indexterm"></a>
+ compatible with your system. <span class="application"><strong>PackageKit</strong></span> consists of several graphical interfaces that can be opened from the GNOME panel menu, or from the Notification Area when <span class="application"><strong>PackageKit</strong></span> alerts you that updates are available. For more information on <span class="application"><strong>PackageKit's</strong></span> architecture and available front ends, refer to <a class="xref" href="#sec-PackageKit_Architecture" title="2.3. PackageKit Architecture">Section 2.3, “PackageKit Architecture”</a>.
+ </div><div class="section" title="2.1. Updating Packages with Software Update" id="sec-Updating_Packages_with_Software_Update"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Updating_Packages_with_Software_Update">2.1. Updating Packages with Software Update</h2></div></div></div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> displays a starburst icon in the Notification Area whenever updates are available to be installed on your system.
+ </div><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-updates_available.png" align="middle" /></div><div class="para">
+ Clicking on the notification icon opens the <span class="guilabel"><strong>Software Update</strong></span> <a id="id704220" class="indexterm"></a>
+ <a id="id768966" class="indexterm"></a>
+ window. Alternatively, you can open <span class="guilabel"><strong>Software Updates</strong></span> by clicking <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Software Update</strong></span> from the GNOME panel, or running the <code class="command">gpk-update-viewer</code> command at the shell prompt. In the <span class="guilabel"><strong>Software Updates</strong></span> window, all available updates are listed along with the names of the packages being updated (minus the <code class="filename">.rpm</code> suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
+ </div><div class="figure" title="Figure 2.1. Installing updates with Software Update" id="fig-Graphical_Package_Management-software_update"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-software_update.png" align="middle" width="444" alt="Installing updates with Software Update" /><div class="longdesc"><div class="para">
+ installing 12 updates with packagekit's software update window
+ </div></div></div></div><h6>Figure 2.1. Installing updates with Software Update</h6></div><br class="figure-break" /><div class="para">
+ The updates presented in the <span class="guilabel"><strong>Software Updates</strong></span> window only represent the currently-installed packages on your system for which updates are available;
+ <a id="id679553" class="indexterm"></a>
+ <a id="id824833" class="indexterm"></a>
+ dependencies of those packages, whether they are existing packages on your system or new ones, are not shown until you click <span class="guibutton"><strong>Install Updates</strong></span>.
+ </div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> <a id="id824858" class="indexterm"></a>
+ <a id="id572902" class="indexterm"></a>
+ <a id="id572914" class="indexterm"></a>
+ utilizes the fine-grained user authentication
+ <a id="id572921" class="indexterm"></a>
+ capabilities provided by the <span class="application"><strong>PolicyKit</strong></span> toolkit whenever you request it to make changes to the system. Whenever you instruct <span class="application"><strong>PackageKit</strong></span> to update, install or remove packages, you will be prompted to enter the superuser password before changes are made to the system.
+ </div><div class="figure" title="Figure 2.2. PackageKit uses PolicyKit to authenticate" id="fig-Graphical_Package_Management-authenticate"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-authenticate.png" align="middle" alt="PackageKit uses PolicyKit to authenticate" /><div class="longdesc"><div class="para">
+ packagekit defers to policykit to provide authentication in order to make changes to the system
+ </div></div></div></div><h6>Figure 2.2. PackageKit uses PolicyKit to authenticate</h6></div><br class="figure-break" /><div class="para">
+ If you instruct <span class="application"><strong>PackageKit</strong></span> to update the <code class="filename">kernel</code> package, then it will prompt you after installation, asking you whether you want to reboot the system and thereby boot into the newly-installed kernel.
+ </div><h3>Setting the Update-Checking Interval</h3><a id="id847534" class="indexterm"></a><div class="para">
+ Right-clicking on <span class="application"><strong>PackageKit</strong></span>'s Notification Area icon and clicking <span class="guimenuitem"><strong>Preferences</strong></span> opens the <span class="guilabel"><strong>Software Update Preferences</strong></span> window, where you can define the interval at which <span class="application"><strong>PackageKit</strong></span> checks for package updates, as well as whether or not to automatically install all updates or only security updates, and how often to check for major upgrades. Leaving the <span class="guilabel"><strong>Check for updates when using mobile broadband</strong></span> box unchecked is handy for avoiding extraneous bandwidth usage when using a wireless connection on which you are charged for the amount of data you download.
+ </div><div class="figure" title="Figure 2.3. Setting PackageKit's update-checking interval" id="fig-Graphical_Package_Management-Software_Update_Preferences"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-Software_Update_Preferences.png" align="middle" alt="Setting PackageKit's update-checking interval" /><div class="longdesc"><div class="para">
+ Setting the update-checking interval for packagekit by right-clicking on the notification area applet
+ </div></div></div></div><h6>Figure 2.3. Setting PackageKit's update-checking interval</h6></div><br class="figure-break" /></div><div class="section" title="2.2. Using Add/Remove Software" id="sec-Using_Add_Remove_Software"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Using_Add_Remove_Software">2.2. Using Add/Remove Software</h2></div></div></div><a id="id583452" class="indexterm"></a><a id="id583464" class="indexterm"></a><div class="para">
+ <span class="application"><strong>PackageKit</strong></span>'s <span class="application"><strong>Software Update</strong></span> GUI window is a separate application from its <span class="guilabel"><strong>Add/Remove Software</strong></span> application, although the two have intuitively similar interfaces. To find and install a new package, on the GNOME panel click on <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Add/Remove Software</strong></span>, or run the <code class="command">gpk-application</code> command at the shell prompt.
+ </div><div class="figure" title="Figure 2.4. PackageKit's Add/Remove Software window" id="fig-Graphical_Package_Management-add_remove_software"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-add_remove_software.png" align="middle" width="444" alt="PackageKit's Add/Remove Software window" /><div class="longdesc"><div class="para">
+ viewing packagekit's add/remove softvware window
+ </div></div></div></div><h6>Figure 2.4. PackageKit's Add/Remove Software window</h6></div><br class="figure-break" /><div class="section" title="2.2.1. Refreshing Software Sources (Yum Repositories)" id="sec-Refreshing_Software_Sources_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Refreshing_Software_Sources_Yum_Repositories">2.2.1. Refreshing Software Sources (Yum Repositories)</h3></div></div></div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> refers to <span class="application"><strong>Yum</strong></span> repositories as
+ <a id="id777809" class="indexterm"></a>
+ <a id="id777820" class="indexterm"></a>
+ software sources. It obtains all packages from enabled software sources. You can view the list of all <span class="emphasis"><em>configured</em></span> and unfiltered (see below) <span class="application"><strong>Yum</strong></span> repositories by opening <span class="guilabel"><strong>Add/Remove Software</strong></span> and clicking <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Software sources</strong></span>. The <span class="guilabel"><strong>Software Sources</strong></span> dialog shows the repository name, as written on the <code class="computeroutput">name=<em class="replaceable"><code><My Repository Name></code></em> </code> field of all [<em class="replaceable"><code>repository</code></em>] sections in the <code class="filename">/etc/yum.conf</code> configuration file, and in all <code class="filename"><em class="replaceable"><code>repository</code></em>.repo</code> files in the <code class="filename">/etc/yum.
repos.d/</code> directory.
+ </div><div class="para">
+ Entries which are checked in the <span class="guilabel"><strong>Enabled</strong></span> column indicate that the corresponding repository will be used to locate packages to satisfy all update and installation requests (including dependency resolution). The <span class="guilabel"><strong>Enabled</strong></span> column corresponds to the <code class="computeroutput">enabled=<em class="replaceable"><code><1 or 0></code></em> </code> field in [<em class="replaceable"><code>repository</code></em>] sections. Checking an unchecked box enables the Yum repository, and unchecking it disables it. Performing either function causes <span class="application"><strong>PolicyKit</strong></span> to prompt for superuser authentication to enable or disable the repository. <span class="application"><strong>PackageKit</strong></span> actually inserts the <code class="literal">enabled=<em class="replaceable"><code><1 or 0></code></em> </code> line into the correct [<em class="repla
ceable"><code>repository</code></em>] section if it does not exist, or changes the value if it does. This means that enabling or disabling a repository through the <span class="guilabel"><strong>Software Sources</strong></span> window causes that change to persist after closing the window or rebooting the system. The ability to quickly enable and disable repositories based on our needs is a highly-convenient feature of <span class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Note that it is not possible to add or remove <span class="application"><strong>Yum</strong></span> repositories through <span class="application"><strong>PackageKit</strong></span>.
+ </div><div class="note" title="Showing Source RPM, Test and Debuginfo Repositories" id="note-Showing_Source_RPM_and_Test_Repositories"><div class="admonition_header"><h2>Showing Source RPM, Test and Debuginfo Repositories</h2></div><div class="admonition"><div class="para">
+ Checking the box at the bottom of the <span class="guilabel"><strong>Software Sources</strong></span> window causes <span class="application"><strong>PackageKit</strong></span> to display source RPM, testing and debuginfo repositories as well. This box is unchecked by defaut.
+ </div></div></div><div class="para">
+ After enabling and/or disabling the correct <span class="application"><strong>Yum</strong></span> repositories, ensure that you have the latest list of available packages. Click on <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Refresh package lists</strong></span> and <span class="application"><strong>PackageKit</strong></span> will obtain the latest lists of packages from all enabled software sources, i.e. <span class="application"><strong>Yum</strong></span> repositories.
+ </div></div><div class="section" title="2.2.2. Finding Packages with Filters" id="sec-Finding_Packages_with_Filters"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Finding_Packages_with_Filters">2.2.2. Finding Packages with Filters</h3></div></div></div><a id="id432545" class="indexterm"></a><div class="para">
+ Once the software sources have been updated, it is often beneficial to apply some filters so that <span class="application"><strong>PackageKit</strong></span> retrieves the results of our <span class="guilabel"><strong>Find</strong></span> queries faster. This is especially helpful when performing many package searches. Four of the filters in the <span class="guimenu"><strong>Filters</strong></span> drop-down menu are used to split results by matching or not matching a single criterion. By default when <span class="application"><strong>PackageKit</strong></span> starts, these filters are all unapplied (<span class="guibutton"><strong>No filter</strong></span>), but once you do filter by one of them, that filter remains set until you either change it or close <span class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Because you are usually searching for available packages that are <span class="emphasis"><em>not</em></span> installed on the system, click <span class="guimenu"><strong>Filters</strong></span> → <span class="guimenuitem"><strong>Installed</strong></span> and select the <span class="guimenuitem"><strong>Only available</strong></span> radio button.
+ <a id="id1690381" class="indexterm"></a>
+ <a id="id1690396" class="indexterm"></a>
+ <a id="id543797" class="indexterm"></a>
+ <a id="id543813" class="indexterm"></a>
+ <a id="id543828" class="indexterm"></a>
+
+ </div><div class="figure" title="Figure 2.5. Filtering out already-installed packages" id="Graphical_Package_Management-filters-only_available"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-filters-only_available.png" align="middle" width="444" alt="Filtering out already-installed packages" /><div class="longdesc"><div class="para">
+ filtering out packages which are already installed
+ </div></div></div></div><h6>Figure 2.5. Filtering out already-installed packages</h6></div><br class="figure-break" /><div class="para">
+ <a id="id769298" class="indexterm"></a>
+ <a id="id769314" class="indexterm"></a>
+ <a id="id739048" class="indexterm"></a>
+ Also, unless we require development files such as C header files, we can filter for <span class="guimenu"><strong>Only end user files</strong></span> and, in doing so, filter out all of the <code class="filename"><em class="replaceable"><code><package_name></code></em>-devel</code> packages we are not interested in.
+ </div><div class="figure" title="Figure 2.6. Filtering out development packages from the list of Find results" id="fig-Graphical_Package_Management-filters-only_end_user"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-filters-only_end_user.png" align="middle" width="444" alt="Filtering out development packages from the list of Find results" /><div class="longdesc"><div class="para">
+ filtering out development packages from our results
+ </div></div></div></div><h6>Figure 2.6. Filtering out development packages from the list of Find results</h6></div><br class="figure-break" /><div class="para">
+ The two remaining filters with submenus are:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <span class="guisubmenu"><strong>Graphical</strong></span> <a id="id529026" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Narrows the search to either applications which provide a GUI interface or those that do not (<span class="guibutton"><strong>Only text</strong></span>). This filter is useful when browsing for GUI applications that perform a specific function.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guisubmenu"><strong>Free</strong></span> <a id="id762644" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Search for packages which are considered to be free software Refer to the <a href="https://fedoraproject.org/wiki/Licensing#SoftwareLicenses">Fedora Licensing List</a> for details on approved licenses.
+ </div></dd></dl></div><div class="para">
+ The remaining checkbox filters are always either checked or unchecked. They are:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <span class="guimenuitem"><strong>Hide subpackages</strong></span> </span></dt><dd><div class="para">
+ Checking the <span class="guimenuitem"><strong>Hide subpackages</strong></span> <a id="id708952" class="indexterm"></a>
+ checkbox filters out generally-uninteresting packages that are typically only dependencies of other packages that we want. For example, checking <span class="guimenuitem"><strong>Hide subpackages</strong></span> and searching for <code class="filename"><em class="replaceable"><code><package></code></em> </code> would cause the following related packages to be filtered out of the <span class="guibutton"><strong>Find</strong></span> results (if it exists):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code><package></code></em>-devel</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code><package></code></em>-libs</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code><package></code></em>-libs-devel</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code><package></code></em>-debuginfo</code>
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <span class="guimenuitem"><strong>Only newest items</strong></span> </span></dt><dd><div class="para">
+ Checking <span class="guimenuitem"><strong>Only newest items</strong></span> <a id="id1325446" class="indexterm"></a>
+ filters out all older versions of the same package from the list of results, which is generally what we want.
+ </div><div class="important" title="Important: Using the Only newest items filter" id="important-Using_the_Only_newest_items_filter"><div class="admonition_header"><h2>Important: Using the Only newest items filter</h2></div><div class="admonition"><div class="para">
+ Checking <span class="guimenuitem"><strong>Only newest items</strong></span> filters out all but the most recent version of any package from the results list. This filter is often combined with the <span class="guimenuitem"><strong>Only available</strong></span> filter to search for the latest available versions of new (not installed) packages.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Only native packages</span></dt><dd><div class="para">
+ Checking the <span class="guimenuitem"><strong>Only native packages</strong></span> <a id="id803307" class="indexterm"></a>
+ box on a multilib system causes <span class="application"><strong>PackageKit</strong></span> to omit listing results for packages compiled for the architecture that runs in <span class="emphasis"><em>compatibility mode</em></span>. For example, enabling this filter on a 64-bit system with an AMD64 CPU would cause all packages built for the 32-bit x86 CPU architecture not to be shown in the list of results, even though those packages are able to run on an AMD64 machine. Packages which are architecture-agnostic (i.e. <em class="firstterm">noarch</em> packages such as <code class="filename">crontabs-1.10-32.1.el6.noarch.rpm</code>) are never filtered out by checking <span class="guimenuitem"><strong>Only native packages</strong></span>. This filter has no affect on non-multilib systems, such as x86 machines.
+ </div></dd></dl></div></div><div class="section" title="2.2.3. Installing and Removing Packages (and Dependencies)" id="sec-Installing_and_Removing_Packages_and_Dependencies"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Installing_and_Removing_Packages_and_Dependencies">2.2.3. Installing and Removing Packages (and Dependencies)</h3></div></div></div><a id="id1715294" class="indexterm"></a><a id="id1715306" class="indexterm"></a><div class="para">
+ With the two filters selected, <span class="guibutton"><strong>Only available</strong></span> and <span class="guibutton"><strong>Only end user files</strong></span>, search for the <span class="application"><strong>htop</strong></span> interactive process viewer and highlight the package. You now have access to some very useful information about it, including: a clickable link to the project homepage; the <span class="application"><strong>Yum</strong></span> package group it is found in, if any; the license of the package; a pointer to the GNOME menu location from where the application can be opened, if applicable (<span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Htop</strong></span> in our case); and the size of the package, which is relevant when we download and install it.
+ </div><div class="figure" title="Figure 2.7. Viewing and installing a package with PackageKit's Add/Remove Software window" id="fig-Graphical_Package_Management-install"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-install.png" align="middle" width="444" alt="Viewing and installing a package with PackageKit's Add/Remove Software window" /><div class="longdesc"><div class="para">
+ Viewing and installing a package with PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>Figure 2.7. Viewing and installing a package with PackageKit's Add/Remove Software window</h6></div><br class="figure-break" /><div class="para">
+ When the checkbox next to a package or group is checked, then that item is already installed on the system. Checking an unchecked box causes it to be <span class="emphasis"><em>marked</em></span> for installation, which only occurs when the <span class="guibutton"><strong>Apply</strong></span> button is clicked. In this way, you can search for and select multiple packages or package groups before performing the actual installation transactions. Additionally, you can remove installed packages by unchecking the checked box, and the removal will occur along with any pending installations when <span class="guibutton"><strong>Apply</strong></span> is pressed. Dependency resolution
+ <a id="id532276" class="indexterm"></a>
+ , which may add additional packages to be installed or removed, is performed after pressing <span class="guibutton"><strong>Apply</strong></span>. <span class="application"><strong>PackageKit</strong></span> will then display a window listing those additional packages to install or remove, and ask for confirmation to proceed.
+ </div><div class="para">
+ Check <span class="application"><strong>htop</strong></span> and click the <span class="guibutton"><strong>Apply</strong></span> button. You will then be prompted for the superuser password; enter it, and <span class="application"><strong>PackageKit</strong></span> will install <span class="application"><strong>htop</strong></span>. One nice feature of <span class="application"><strong>PackageKit</strong></span> is that, following installation, it sometimes presents you with a list of your newly-installed applications and offer you the choice of running them immediately. Alternatively, you will remember that finding a package and selecting it in the <span class="guilabel"><strong>Add/Remove Software</strong></span> window shows you the <span class="guilabel"><strong>Location</strong></span> of where in the GNOME menus its application shortcut is located, which is helpful when you want to run it.
+ </div><div class="para">
+ Once it is installed, you can run <code class="command">htop</code>, an colorful and enhanced version of the <code class="command">top</code> process viewer, by opening a shell prompt and entering:
+ </div><pre class="screen">~]$ <code class="command">htop</code>
+</pre><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-htop.png" align="middle" width="444" /><div class="caption"><div class="para">
+ Viewing processes with <span class="application"><strong>htop</strong></span>!
+ </div></div></div><div class="para">
+ <span class="application"><strong>htop</strong></span> is nifty, but we decide that <code class="command">top</code> is good enough for us and we want to uninstall it. Remembering that we need to change the <span class="guibutton"><strong>Only available</strong></span> filter we recently used to install it to <span class="guibutton"><strong>Only installed</strong></span> in <span class="guimenu"><strong>Filters</strong></span> → <span class="guimenuitem"><strong>Installed</strong></span>, we search for <span class="application"><strong>htop</strong></span> again and uncheck it. The program did not install any dependencies of its own; if it had, those would be automatically removed as well, as long as they were not also dependencies of any other packages still installed on our system.
+ </div><div class="warning" title="Warning: Removing a Package when Other Packages Depend On It" id="warning-PackageKit-Removing_a_Package_Without_Removing_Packages_Depending_on_It"><div class="admonition_header"><h2>Warning: Removing a Package when Other Packages Depend On It</h2></div><div class="admonition"><div class="para">
+ Although <span class="application"><strong>PackageKit</strong></span> automatically resolves dependencies during package installation and removal, it is unable to remove a package without also removing packages which depend on it. This type of operation can only be performed by <span class="application"><strong>RPM</strong></span>, is not advised, and can potentially leave your system in a non-functioning state or cause applications to misbehave and/or crash.
+ </div></div></div><div class="figure" title="Figure 2.8. Removing a package with PackageKit's Add/Remove Software window" id="fig-Graphical_Package_Management-removing_a_package"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-removing_a_package.png" align="middle" width="444" alt="Removing a package with PackageKit's Add/Remove Software window" /><div class="longdesc"><div class="para">
+ removing the htop package with packagekit's add/remove software window
+ </div></div></div></div><h6>Figure 2.8. Removing a package with PackageKit's Add/Remove Software window</h6></div><br class="figure-break" /></div><div class="section" title="2.2.4. Installing and Removing Package Groups" id="sec-Installing_and_Removing_Package_Groups"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Installing_and_Removing_Package_Groups">2.2.4. Installing and Removing Package Groups</h3></div></div></div><a id="id751080" class="indexterm"></a><a id="id751092" class="indexterm"></a><a id="id751104" class="indexterm"></a><a id="id461464" class="indexterm"></a><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> also has the ability to install <span class="application"><strong>Yum</strong></span> package groups, which it calls <span class="guilabel"><strong>Package collections</strong></span>. Clicking on <span class="guilabel"><strong>Package collections</strong></span> in the top-left list of categories in the <span class="guilabel"><strong>Software Updates</strong></span> window allows us to scroll through and find the package group we want to install. In this case, we want to install Czech language support (the <span class="guilabel"><strong>Czech Support</strong></span> group). Checking the box and clicking <span class="guibutton"><strong>apply</strong></span> informs us how many <span class="emphasis"><em>additional</em></span> packages must be installed in order to fulfill the dependencies of the package group.
+ </div><div class="figure" title="Figure 2.9. Installing the Czech Support package group" id="fig-Graphical_Package_Management-installing_a_package_group"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-installing_a_package_group.png" align="middle" width="444" alt="Installing the Czech Support package group" /><div class="longdesc"><div class="para">
+ using PackageKit to install czech language support with PackageKit's add/remove software window
+ </div></div></div></div><h6>Figure 2.9. Installing the Czech Support package group</h6></div><br class="figure-break" /><div class="para">
+ Similarly, installed package groups can be uninstalled by selecting <span class="guilabel"><strong>Package collections</strong></span>, unchecking the appropriate checkbox, and applying.
+ </div></div><div class="section" title="2.2.5. Viewing the Transaction Log" id="sec-Viewing_the_Transaction_Log"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Viewing_the_Transaction_Log">2.2.5. Viewing the Transaction Log</h3></div></div></div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> maintains a log of the transactions
+ <a id="id476156" class="indexterm"></a>
+ <a id="id476168" class="indexterm"></a>
+ that it performs. To view the log, from the <span class="guilabel"><strong>Add/Remove Software</strong></span> window, click <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Software log</strong></span>, or run the <code class="command">gpk-log</code> command at the shell prompt.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Software Log Viewer</strong></span> shows the <span class="guilabel"><strong>Action</strong></span>, such as <em class="replaceable"><code>Updated System</code></em> or <em class="replaceable"><code>Installed Packages</code></em>, the <span class="guilabel"><strong>Date</strong></span> on which that action was performed, the <span class="guilabel"><strong>Username</strong></span> of the user who performed the action, and the front end <span class="guilabel"><strong>Application</strong></span> the user used (such as <em class="replaceable"><code>Update Icon</code></em>, or <em class="replaceable"><code>kpackagekit</code></em>). The <span class="guilabel"><strong>Details</strong></span> column provides the types of the transactions, such as <em class="replaceable"><code>Updated</code></em>, <em class="replaceable"><code>Installed</code></em> or <em class="replaceable"><code>Removed</code></em>, as well as the list of packages the transact
ions were performed on.
+ </div><div class="figure" title="Figure 2.10. Viewing the log of package management transactions with the Software Log Viewer" id="fig-Graphical_Package_Management-Software_Log_Viewer"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-Software_Log_Viewer.png" align="middle" width="444" alt="Viewing the log of package management transactions with the Software Log Viewer" /><div class="longdesc"><div class="para">
+ viewing the log of package management transactions with packagekit's loftware log viewer window
+ </div></div></div></div><h6>Figure 2.10. Viewing the log of package management transactions with the Software Log Viewer</h6></div><br class="figure-break" /><div class="para">
+ Typing the name of a package in the top text entry field filters the list of transactions to those which affected that package.
+ </div></div></div><div class="section" title="2.3. PackageKit Architecture" id="sec-PackageKit_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-PackageKit_Architecture">2.3. PackageKit Architecture</h2></div></div></div><a id="id476543" class="indexterm"></a><div class="para">
+ Red Hat provides the <span class="application"><strong>PackageKit</strong></span> suite of applications for viewing, updating, installing and uninstalling packages and package groups compatible with your system. Architecturally, <span class="application"><strong>PackageKit</strong></span> consists of several graphical front ends that communicate with the <code class="command">packagekitd</code> daemon back end, which communicates with a package manager-specific back end that utilizes <span class="application"><strong>Yum</strong></span> to perform the actual transactions, such as installing and removing packages, etc.
+ </div><div class="para">
+ <a class="xref" href="#table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands" title="Table 2.1. PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands">Table 2.1, “PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands”</a> shows the name of the GUI window, how to start the window from the GNOME desktop or from the <span class="guilabel"><strong>Add/Remove Software</strong></span> window, and the name of the command line application that opens that window.
+ </div><div class="table" title="Table 2.1. PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands" id="table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands"><h6>Table 2.1. PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands</h6><div class="table-contents"><table summary="PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands" border="1"><colgroup><col align="left" width="25%" /><col align="left" width="25%" /><col align="left" width="25%" /><col align="left" width="25%" /></colgroup><thead><tr><th align="left">
+ Window Title
+ </th><th align="left">
+ Function
+ </th><th align="left">
+ How to Open
+ </th><th align="left">
+ Shell Command
+ </th></tr></thead><tbody><tr><td align="left">
+ Add/Remove Software
+ </td><td align="left">
+ Install, remove or view package info
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Add/Remove Software</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-application
+ </td></tr><tr><td align="left">
+ Software Update
+ </td><td align="left">
+ Perform package updates
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Software Update</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-update-viewer
+ </td></tr><tr><td align="left">
+ Software Sources
+ </td><td align="left">
+ Enable and disable <span class="application"><strong>Yum</strong></span> repositories
+ </td><td align="left">
+ <div class="para">
+ From <span class="guilabel"><strong>Add/Remove Software</strong></span>: <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Software sources</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-repo
+ </td></tr><tr><td align="left">
+ Software Log Viewer
+ </td><td align="left">
+ View the transaction log
+ </td><td align="left">
+ <div class="para">
+ From <span class="guilabel"><strong>Add/Remove Software</strong></span>: <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Software log</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-log
+ </td></tr><tr><td align="left">
+ Software Update Preferences
+ </td><td align="left">
+ Set <span class="application"><strong>PackageKit</strong></span> preferences
+ </td><td align="left">
+ </td><td align="left">
+ gpk-prefs
+ </td></tr><tr><td align="left">
+ (Notification Area Alert)
+ </td><td align="left">
+ Alerts you when updates are available
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Startup Applications</strong></span>, <span class="guilabel"><strong>Startup Programs</strong></span> tab
+ </div>
+
+ </td><td align="left">
+ gpk-update-icon
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">packagekitd</code> daemon runs outside the user session and communicates with the various graphical front ends. The <code class="command">packagekitd</code> daemon<sup>[<a id="footnote-Daemons" href="#ftn.footnote-Daemons" class="footnote">2</a>]</sup> communicates via the <span class="application"><strong>DBus</strong></span> system message bus with another back end, which utilizes <span class="application"><strong>Yum</strong></span>'s Python API to perform queries and make changes to the sytem. On Linux systems other than Red Hat and Fedora, <code class="command">packagekitd</code> can communicate with other back ends that are able to utilize the native package manager for that system. This modular architecture provides the abstraction necessary for the graphical interfaces to work with many different package managers to perform essentially the same types of package management tasks. Learning how to use the <span class="application"><strong>Pa
ckageKit</strong></span> front ends means that you can use the same familiar graphical interface across many different Linux distributions, even when they utilize a native package manager other than <span class="application"><strong>Yum</strong></span>.
+ </div><div class="para">
+ In addition, <span class="application"><strong>PackageKit</strong></span>'s separation of concerns provides reliability in that a crash of one of the GUI windows—or even the user's X Window session—will not affect any package management tasks being supervised by the <code class="command">packagekitd</code> daemon, which runs outside of the user session.
+ </div><div class="para">
+ All of the front end graphical applications discussed in this chapter are provided by the <code class="filename">gnome-packagekit</code> package instead of by <span class="application"><strong>PackageKit</strong></span> and its dependencies. Users working in a KDE environment may prefer to install the <code class="filename">kpackagekit</code> package, which provides a KDE interface for <span class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Finally, <span class="application"><strong>PackageKit</strong></span> also comes with a console-based frontend called <code class="command">pkcon</code>.
+ </div></div><div class="section" title="2.4. Additional Resources" id="ch-Graphical_Package_Management-sec-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="ch-Graphical_Package_Management-sec-Additional_Resources">2.4. Additional Resources</h2></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <span class="application"><strong>PackageKit</strong></span> home page — <a href="http://www.packagekit.org/index.html">http://www.packagekit.org/index.html</a> </span></dt><dd><div class="para">
+ Information about and mailing lists for <span class="application"><strong>PackageKit</strong></span>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="application"><strong>PackageKit</strong></span> FAQ — <a href="http://www.packagekit.org/pk-faq.html">http://www.packagekit.org/pk-faq.html</a> </span></dt><dd><div class="para">
+ An informative list of Frequently Asked Questions for the <span class="application"><strong>PackageKit</strong></span> software suite.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="application"><strong>PackageKit</strong></span> Feature Matrix — <a href="http://www.packagekit.org/pk-matrix.html">http://www.packagekit.org/pk-matrix.html</a> </span></dt><dd><div class="para">
+ Cross-reference <span class="application"><strong>PackageKit</strong></span>-provided features with the long list of package manager back ends.
+ </div></dd></dl></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote" id="footnote-Daemons"><p><sup>[<a id="ftn.footnote-Daemons" href="#footnote-Daemons" class="para">2</a>] </sup>
+ System daemons are typically long-running processes that provide services to the user or to other programs, and which are started, often at boot time, by special initialization scripts (often shortened to <span class="emphasis"><em>init scripts</em></span>). Daemons respond to the <code class="command">service</code> command and can be turned on or off permanently by using the <code class="command">chkconfig on</code> or <code class="command">chkconfig off</code>commands. They can typically be recognized by a <span class="quote">“<span class="quote"><span class="emphasis"><em>d</em></span> </span>”</span> appended to their name, such as the <code class="command">packagekitd</code> daemon. Refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for information about system services.
+ </p></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 3. RPM" id="ch-RPM" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. RPM</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-rpm-design">3.1. RPM Design Goals</a></span></dt><dt><span class="section"><a href="#s1-rpm-using">3.2. Using RPM</a></span></dt><dt><span class="section"><a href="#s1-check-rpm-sig">3.3. Checking a Package's Signature</a></span></dt><dt><span class="section"><a href="#s1-rpm-impressing">3.4. Practical and Common Examples of RPM Usage</a></span></dt><dt><span class="section"><a href="#s1-rpm-additional-resources">3.5. Additional Resources</a></span></dt></dl></div><a id="id484233" class="indexterm"></a><a id="id484227" class="indexterm"></a><div class="para">
+ The <em class="firstterm">RPM Package Manager</em> (RPM) is an open packaging system
+ <a id="id484214" class="indexterm"></a>
+ , which runs on Fedora as well as other Linux and UNIX systems. Red Hat, Inc. and the Fedora Project encourage other vendors to use RPM for their own products. RPM is distributed under the terms of the <em class="firstterm">GPL</em> (<em class="firstterm">GNU General Public License</em>).
+ </div><div class="para">
+ The RPM Package Manager only works with packages built to work with the <span class="emphasis"><em>RPM format</em></span>. RPM is itself provided as a pre-installed <span class="package">rpm</span> package. For the end user, RPM makes system updates easy. Installing, uninstalling and upgrading RPM packages can be accomplished with short commands. RPM maintains a database of installed packages and their files, so you can invoke powerful queries and verifications on your system.
+ </div><div class="para">
+ The RPM package format has been improved for Fedora 14. RPM packages are now compressed using the XZ lossless data compression format, which has the benefit of greater compression and less CPU usage during decompression, and support multiple strong hash algorithms, such as SHA-256, for package signing and verification.
+ </div><div class="warning" title="Use Yum Instead of RPM Whenever Possible" id="warning-Use_Yum_Instead_of_RPM_Whenever_Possible"><div class="admonition_header"><h2>Use Yum Instead of RPM Whenever Possible</h2></div><div class="admonition"><div class="para">
+ For most package management tasks, the <span class="application"><strong>Yum</strong></span> package manager offers equal and often greater capabilities and utility than RPM
+ <a id="id553922" class="indexterm"></a>
+ . <span class="application"><strong>Yum</strong></span> also performs and tracks complicated system dependency resolution, and will complain and force system integrity checks if you use RPM as well to install and remove packages. For these reasons, it is highly recommended that you use <span class="application"><strong>Yum</strong></span> instead of RPM whenever possible to perform package management tasks. Refer to <a class="xref" href="#ch-yum" title="Chapter 1. Yum">Chapter 1, <i>Yum</i></a>.
+ </div><div class="para">
+ If you prefer a graphical interface, you can use the <span class="application"><strong>PackageKit</strong></span> GUI application, which uses <span class="application"><strong>Yum</strong></span> as its back end, to manage your system's packages. Refer to <a class="xref" href="#ch-PackageKit" title="Chapter 2. PackageKit">Chapter 2, <i>PackageKit</i></a> for details.
+ </div></div></div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When installing a package, ensure it is compatible with your operating system and processor architecture. This can usually be determined by checking the package name. Many of the following examples show RPM packages compiled for the AMD64/Intel 64 computer architectures; thus, the RPM file name ends in <code class="filename">x86_64.rpm</code>.
+ </div></div></div><div class="para">
+ During upgrades, RPM handles configuration files carefully, so that you never lose your customizations—something that you cannot accomplish with regular <code class="filename">.tar.gz</code> files.
+ </div><div class="para">
+ For the developer, RPM allows you to take software source code and package it into source and binary packages for end users.
+ <a id="id833792" class="indexterm"></a>
+ This process is quite simple and is driven from a single file and optional patches that you create. This clear delineation between <em class="firstterm">pristine</em> sources and your patches along with build instructions eases the maintenance of the package as new versions of the software are released.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Because RPM makes changes to your system, you must be logged in as root to install, remove, or upgrade an RPM package.
+ </div></div></div><div class="section" title="3.1. RPM Design Goals" id="s1-rpm-design"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-rpm-design">3.1. RPM Design Goals</h2></div></div></div><a id="id503566" class="indexterm"></a><div class="para">
+ To understand how to use RPM, it can be helpful to understand the design goals of RPM:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Upgradability
+ <a id="id503540" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ With RPM, you can upgrade individual components of your system without completely reinstalling. When you get a new release of an operating system based on RPM, such as Fedora, you do not need to reinstall a fresh copy of the operating system your machine (as you might need to with operating systems based on other packaging systems). RPM allows intelligent, fully-automated, in-place upgrades of your system. In addition, configuration files in packages are preserved across upgrades, so you do not lose your customizations. There are no special upgrade files needed to upgrade a package because the same RPM file is used to both install and upgrade the package on your system.
+ </div></dd><dt class="varlistentry"><span class="term">Powerful Querying
+ <a id="id1520432" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ RPM is designed to provide powerful querying options. You can perform searches on your entire database for packages or even just certain files. You can also easily find out what package a file belongs to and from where the package came. The files an RPM package contains are in a compressed archive, with a custom binary header containing useful information about the package and its contents, allowing you to query individual packages quickly and easily.
+ </div></dd><dt class="varlistentry"><span class="term"> System Verification
+ <a id="id758562" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Another powerful RPM feature is the ability to verify packages. If you are worried that you deleted an important file for some package, you can verify the package. You are then notified of anomalies, if any—at which point you can reinstall the package, if necessary. Any configuration files that you modified are preserved during reinstallation.
+ </div></dd><dt class="varlistentry"><span class="term">Pristine Sources
+ <a id="id860661" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ A crucial design goal was to allow the use of <span class="emphasis"><em>pristine </em></span> software sources, as distributed by the original authors of the software. With RPM, you have the pristine sources along with any patches that were used, plus complete build instructions. This is an important advantage for several reasons. For instance, if a new version of a program is released, you do not necessarily have to start from scratch to get it to compile. You can look at the patch to see what you <span class="emphasis"><em>might</em></span> need to do. All the compiled-in defaults, and all of the changes that were made to get the software to build properly, are easily visible using this technique.
+ </div><div class="para">
+ The goal of keeping sources pristine may seem important only for developers, but it results in higher quality software for end users, too.
+ </div></dd></dl></div></div><div class="section" title="3.2. Using RPM" id="s1-rpm-using"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-rpm-using">3.2. Using RPM</h2></div></div></div><div class="para">
+ RPM has five basic modes of operation
+ <a id="id466879" class="indexterm"></a>
+ (not counting package building): installing, uninstalling, upgrading, querying, and verifying. This section contains an overview of each mode. For complete details and options, try <code class="command">rpm --help</code> or <code class="command">man rpm</code>. You can also refer to <a class="xref" href="#s1-rpm-additional-resources" title="3.5. Additional Resources">Section 3.5, “Additional Resources”</a> for more information on RPM.
+ </div><div class="section" title="3.2.1. Finding RPM Packages" id="s2-rpm-finding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-finding">3.2.1. Finding RPM Packages</h3></div></div></div><a id="id522515" class="indexterm"></a><a id="id602879" class="indexterm"></a><div class="para">
+ Before using any RPM packages, you must know where to find them. An Internet search returns many RPM repositories, but if you are looking for Red Hat RPM packages, they can be found at the following locations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The Fedora installation media
+ <a id="id689113" class="indexterm"></a>
+ <a id="id832018" class="indexterm"></a>
+ contain many installable RPMs.
+ </div></li><li class="listitem"><div class="para">
+ The initial RPM repositories provided with the YUM package manager
+ <a id="id533382" class="indexterm"></a>
+ <a id="id663681" class="indexterm"></a>
+ . Refer to <a class="xref" href="#ch-yum" title="Chapter 1. Yum">Chapter 1, <i>Yum</i></a> for details on how to use the official Fedora package repositories.
+ </div></li><li class="listitem"><div class="para">
+ The active Fedora mirrors contains many installable RPMs: <a href="http://mirrors.fedoraproject.org/publiclist/">http://mirrors.fedoraproject.org/publiclist/</a>.
+ </div></li><li class="listitem"><div class="para">
+ Unofficial, third-party repositories not ahffiliated Red Hat also provide RPM packages.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When considering third-party repositories for use with your Fedora system, pay close attention to the repository's web site with regard to package compatibility before adding the repository as a package source. Alternate package repositories may offer different, incompatible versions of the same software, including packages already included in the Fedora repositories.
+ </div></div></div></li></ul></div></div><div class="section" title="3.2.2. Installing and Upgrading" id="sec-Installing_and_Upgrading"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Installing_and_Upgrading">3.2.2. Installing and Upgrading</h3></div></div></div><a id="id781699" class="indexterm"></a><a id="id500735" class="indexterm"></a><a id="id494321" class="indexterm"></a><a id="id733917" class="indexterm"></a><div class="para">
+ RPM packages typically have file names
+ <a id="id700688" class="indexterm"></a>
+ like <code class="filename">tree-1.5.3-2.fc14.x86_64.rpm</code>. The file name includes the package name (<code class="filename">tree</code>), version (<code class="filename">1.5.3</code>), release (<code class="filename">2</code>), operating system major version (<code class="filename">fc14</code>) and CPU architecture (<code class="filename">x86_64</code>).
+ </div><div class="para">
+ You can use <code class="command">rpm</code>'s <code class="option">-U</code> option to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ upgrade an existing but older package on the system to a newer version, or
+ </div></li><li class="listitem"><div class="para">
+ install the package even if an older version is not already installed.
+ </div></li></ul></div><div class="para">
+ That is, <code class="command">rpm -U <em class="replaceable"><code><rpm_file></code></em> </code> is able to perform the function of either <span class="emphasis"><em>upgrading</em></span> or <span class="emphasis"><em>installing</em></span> as is appropriate for the package.
+ </div><div class="para">
+ Assuming the <code class="filename">tree-1.5.3-2.fc14.x86_64.rpm</code> package is in the current directory, log in as root and type the following command at a shell prompt to either upgrade or install the <span class="package">tree</span> package as determined by <code class="command">rpm</code>:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh tree-1.5.3-2.fc14.x86_64.rpm</code>
+</pre><div class="note" title="Use -Uvh for nicely-formatted RPM installs" id="note-Use_-Uvh_for_nicely-formatted_RPM_installs"><div class="admonition_header"><h2>Use -Uvh for nicely-formatted RPM installs</h2></div><div class="admonition"><div class="para">
+ The <code class="option">-v</code> and <code class="option">-h</code> options (which are combined with <code class="option">-U</code>) cause <span class="application"><strong>rpm</strong></span> to print more verbose output and display a progress meter using hash signs.
+ </div></div></div><div class="para">
+ If the upgrade/installation is successful, the following output is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ 1:tree ########################################### [100%]</pre><div class="warning" title="Always use the -i (install) option to install new kernel packages!" id="warning-Always_use_the_-i_install_option_to_install_new_kernel_packages"><div class="admonition_header"><h2>Always use the -i (install) option to install new kernel packages!</h2></div><div class="admonition"><div class="para">
+ <code class="command">rpm</code> provides two different options for installing packages: the aforementioned <code class="option">-U</code> option (which historically stands for <span class="emphasis"><em>upgrade</em></span>), and the <code class="option">-i</code> option, historically standing for <span class="emphasis"><em>install</em></span>. Because the <code class="option">-U</code> option subsumes both install and upgrade functions, we recommend to use <code class="command">rpm -Uvh</code> with all packages <span class="emphasis"><em>except <span class="package">kernel</span> packages</em></span>.
+ </div><div class="para">
+ You should always use the <code class="option">-i</code> option to simply <span class="emphasis"><em>install</em></span> a new kernel package instead of upgrading it. This is because using the <code class="option">-U</code> option to upgrade a kernel package removes the previous (older) kernel package, which could render the system unable to boot if there is a problem with the new kernel. Therefore, use the <code class="command">rpm -i <em class="replaceable"><code><kernel_package></code></em> </code> command to install a new kernel <span class="emphasis"><em>without replacing any older <span class="package">kernel</span> packages</em></span>. For more information on installing <span class="package">kernel</span> packages, refer to <a class="xref" href="#ch-Manually_Upgrading_the_Kernel" title="Chapter 23. Manually Upgrading the Kernel">Chapter 23, <i>Manually Upgrading the Kernel</i></a>.
+ </div></div></div><div class="para">
+ The signature of a package is checked automatically when installing or upgrading a package. The signature confirms that the package was signed by an authorized party. For example, if the verification of the signature fails, an error message such as the following is displayed:
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc14.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD, key ID
+d22e77f2</pre><div class="para">
+ If it is a new, header-only, signature, an error message such as the following is displayed:
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc14.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD,
+key ID d22e77f2</pre><div class="para">
+ If you do not have the appropriate key installed to verify the signature, the message contains the word <code class="computeroutput">NOKEY</code>:
+ </div><pre class="screen">warning: tree-1.5.2.2-4.fc14.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 57bbccba</pre><div class="para">
+ Refer to <a class="xref" href="#s1-check-rpm-sig" title="3.3. Checking a Package's Signature">Section 3.3, “Checking a Package's Signature”</a> for more information on checking a package's signature.
+ </div><div class="section" title="3.2.2.1. Package Already Installed" id="s3-rpm-errors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-rpm-errors">3.2.2.1. Package Already Installed</h4></div></div></div><div class="para">
+ If a package of the same name and version is already installed
+ <a id="id505575" class="indexterm"></a>
+ <a id="id505587" class="indexterm"></a>
+ , the following output is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ package tree-1.5.3-2.fc14.x86_64 is already installed</pre><div class="para">
+ However, if you want to install the package anyway, you can use the <code class="command">--replacepkgs</code> option, which tells RPM to ignore the error:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --replacepkgs tree-1.5.3-2.fc14.x86_64.rpm</code>
+</pre><div class="para">
+ This option is helpful if files installed from the RPM were deleted or if you want the original configuration files from the RPM to be installed.
+ </div></div><div class="section" title="3.2.2.2. Conflicting Files" id="s3-rpm-conflicting-files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-rpm-conflicting-files">3.2.2.2. Conflicting Files</h4></div></div></div><a id="id689136" class="indexterm"></a><div class="para">
+ If you attempt to install a package that contains a file which has already been installed by another package
+ <a id="id819803" class="indexterm"></a>
+ <a id="id481250" class="indexterm"></a>
+ , the following is displayed:
+ </div><pre class="screen">Preparing... ##################################################
+ file /usr/bin/foobar from install of foo-1.0-1.fc14.x86_64 conflicts
+with file from package bar-3.1.1.fc14.x86_64</pre><div class="para">
+ To make RPM ignore this error, use the <code class="command">--replacefiles</code> option:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --replacefiles foo-1.0-1.fc14.x86_64.rpm</code>
+</pre></div><div class="section" title="3.2.2.3. Unresolved Dependency" id="s3-rpm-unresolved-dependency"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-rpm-unresolved-dependency">3.2.2.3. Unresolved Dependency</h4></div></div></div><a id="id702230" class="indexterm"></a><a id="id522826" class="indexterm"></a><div class="para">
+ RPM packages may sometimes depend on other packages
+ <a id="id538302" class="indexterm"></a>
+ <a id="id786486" class="indexterm"></a>
+ , which means that they require other packages to be installed to run properly. If you try to install a package which has an unresolved dependency, output similar to the following is displayed:
+ </div><pre class="screen">error: Failed dependencies:
+ bar.so.3()(64bit) is needed by foo-1.0-1.fc14.x86_64</pre><div class="para">
+ If you are installing a package from the Fedora installation media, such as from a CD-ROM or DVD, the dependencies may be available. Find the suggested package(s) on the Fedora installation media or on one of the active Fedora mirrors and add it to the command:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh foo-1.0-1.fc14.x86_64.rpm bar-3.1.1.fc14.x86_64.rpm</code>
+</pre><div class="para">
+ If installation of both packages is successful, output similar to the following is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ 1:foo ########################################### [ 50%]
+ 2:bar ########################################### [100%]</pre><div class="para">
+ You can try the <code class="option">--whatprovides</code> option to determine which package contains the required file.
+ </div><pre class="screen">
+<code class="command">rpm -q --whatprovides "bar.so.3"</code>
+</pre><div class="para">
+ If the package that contains <code class="filename">bar.so.3</code> is in the RPM database, the name of the package is displayed:
+ </div><pre class="screen">bar-3.1.1.fc14.i586.rpm</pre><div class="warning" title="Warning: Forcing Package Installation" id="warning-install-Warning-Forcing_Package_Installation"><div class="admonition_header"><h2>Warning: Forcing Package Installation</h2></div><div class="admonition"><div class="para">
+ Although we can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to install a package that gives us a <code class="computeroutput">Failed dependencies</code> error (using the <code class="option">--nodeps</code> option), this is <span class="emphasis"><em>not</em></span> recommended, and will usually result in the installed package failing to run. Installing or removing packages with <code class="command">rpm --nodeps</code> can cause applications to misbehave and/or crash, and can cause serious package management problems or, possibly, system failure. For these reasons, it is best to heed such warnings; the package manager—whether <span class="application"><strong>RPM</strong></span>, <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span>—shows us these warnings and suggests possible fixes because accounting for dependencies is critical. The <span class="application"><stron
g>Yum</strong></span> package manager can perform dependency resolution and fetch dependencies from online repositories, making it safer, easier and smarter than forcing <code class="command">rpm</code> to carry out actions without regard to resolving dependencies.
+ </div></div></div></div></div><div class="section" title="3.2.3. Configuration File Changes" id="sec-Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuration_File_Changes">3.2.3. Configuration File Changes</h3></div></div></div><a id="id864155" class="indexterm"></a><a id="id864167" class="indexterm"></a><div class="para">
+ Because RPM performs intelligent upgrading of packages with configuration files
+ <a id="id573516" class="indexterm"></a>
+ , you may see one or the other of the following messages:
+ </div><pre class="screen">saving /etc/foo.conf as /etc/foo.conf.rpmsave</pre><div class="para">
+ This message means that changes you made to the configuration file may not be <span class="emphasis"><em>forward-compatible</em></span> with the new configuration file in the package, so RPM saved your original file and installed a new one. You should investigate the differences between the two configuration files and resolve them as soon as possible, to ensure that your system continues to function properly.
+ </div><div class="para">
+ Alternatively, RPM may save the package's <span class="emphasis"><em>new</em></span> configuration file as, for example, <code class="filename">foo.conf.rpmnew</code>, and leave the configuration file you modified untouched. You should still resolve any conflicts between your modified configuration file and the new one, usually by merging changes from the old one to the new one with a <code class="command">diff</code> program.
+ </div><div class="para">
+ If you attempt to upgrade to a package with an <span class="emphasis"><em>older</em></span> version number (that is, if a higher version of the package is already installed), the output is similar to the following:
+ </div><pre class="screen">package foo-2.0-1.fc14.x86_64.rpm (which is newer than foo-1.0-1) is already installed</pre><div class="para">
+ To force RPM to upgrade anyway, use the <code class="command">--oldpackage</code> option:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --oldpackage foo-1.0-1.fc14.x86_64.rpm</code>
+</pre></div><div class="section" title="3.2.4. Uninstalling" id="s2-rpm-uninstalling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-uninstalling">3.2.4. Uninstalling</h3></div></div></div><a id="id569242" class="indexterm"></a><a id="id569254" class="indexterm"></a><a id="id672531" class="indexterm"></a><a id="id467339" class="indexterm"></a><div class="para">
+ Uninstalling a package is just as simple as installing one. Type the following command at a shell prompt:
+ </div><pre class="screen">rpm -e foo</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Notice that we used the package <span class="emphasis"><em>name</em></span> <code class="filename">foo</code>, not the name of the original package <span class="emphasis"><em>file</em></span>, <code class="filename">foo-1.0-1.fc14.x86_64</code>. If you attempt to uninstall a package using the <code class="command">rpm -e</code> command and the original full file name, you will receive a package name error.
+ </div></div></div><div class="para">
+ You can encounter dependency errors when uninstalling a package if another installed package depends on the one you are trying to remove. For example:
+ </div><pre class="screen">
+<code class="command">rpm -e ghostscript</code>
+error: Failed dependencies:
+ libgs.so.8()(64bit) is needed by (installed) libspectre-0.2.2-3.fc14.x86_64
+ libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc14.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc14.x86_64
+ ghostscript is needed by (installed) printer-filters-1.1-4.fc14.noarch</pre><div class="para">
+ Similar to how we searched for a shared object library (i.e. a <code class="filename"><em class="replaceable"><code><library_name></code></em>.so.<em class="replaceable"><code><number></code></em> </code> file) in <a class="xref" href="#s3-rpm-unresolved-dependency" title="3.2.2.3. Unresolved Dependency">Section 3.2.2.3, “Unresolved Dependency”</a>, we can search for a 64-bit shared object library using this exact syntax (and making sure to quote the file name):
+ </div><pre class="screen">~]# <code class="command">rpm -q --whatprovides "libgs.so.8()(64bit)"</code>
+ghostscript-8.70-1.fc14.x86_64</pre><div class="warning" title="Warning: Forcing Package Installation" id="warning-uninstall-Warning-Forcing_Package_Installation"><div class="admonition_header"><h2>Warning: Forcing Package Installation</h2></div><div class="admonition"><div class="para">
+ Although we can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to remove a package that gives us a <code class="computeroutput">Failed dependencies</code> error (using the <code class="option">--nodeps</code> option), this is <span class="emphasis"><em>not</em></span> recommended, and may cause harm to other installed applications. Installing or removing packages with <code class="command">rpm --nodeps</code> can cause applications to misbehave and/or crash, and can cause serious package management problems or, possibly, system failure. For these reasons, it is best to heed such warnings; the package manager—whether <span class="application"><strong>RPM</strong></span>, <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span>—shows us these warnings and suggests possible fixes because accounting for dependencies is critical. The <span class="application"><strong>Yum</strong><
/span> package manager can perform dependency resolution and fetch dependencies from online repositories, making it safer, easier and smarter than forcing <code class="command">rpm</code> to carry out actions without regard to resolving dependencies.
+ </div></div></div></div><div class="section" title="3.2.5. Freshening" id="s2-rpm-freshening"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-freshening">3.2.5. Freshening</h3></div></div></div><a id="id1557559" class="indexterm"></a><a id="id777974" class="indexterm"></a><div class="para">
+ Freshening is similar to upgrading, except that only existent packages are upgraded. Type the following command at a shell prompt:
+ </div><pre class="screen">
+<code class="command">rpm -Fvh foo-2.0-1.fc14.x86_64.rpm</code>
+</pre><div class="para">
+ RPM's freshen option checks the versions of the packages specified on the command line against the versions of packages that have already been installed on your system. When a newer version of an already-installed package is processed by RPM's freshen option, it is upgraded to the newer version. However, RPM's freshen option does not install a package if no previously-installed package of the same name exists. This differs from RPM's upgrade option, as an upgrade <span class="emphasis"><em>does</em></span> install packages whether or not an older version of the package was already installed.
+ </div><div class="para">
+ Freshening works for single packages or package groups. If you have just downloaded a large number of different packages, and you only want to upgrade those packages that are already installed on your system, freshening does the job. Thus, you do not have to delete any unwanted packages from the group that you downloaded before using RPM.
+ </div><div class="para">
+ In this case, issue the following with the <code class="filename">*.rpm</code> glob:
+ </div><pre class="screen">
+<code class="command">rpm -Fvh *.rpm</code>
+</pre><div class="para">
+ RPM then automatically upgrades only those packages that are already installed.
+ </div></div><div class="section" title="3.2.6. Querying" id="s2-rpm-querying"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-querying">3.2.6. Querying</h3></div></div></div><a id="id683833" class="indexterm"></a><a id="id786472" class="indexterm"></a><div class="para">
+ The RPM database stores information about all RPM packages installed in your system. It is stored in the directory <code class="filename">/var/lib/rpm/</code>, and is used to query what packages are installed, what versions each package is, and to calculate any changes to any files in the package since installation, among other use cases.
+ </div><div class="para">
+ To query this database, use the <code class="command">-q</code> option. The <code class="command">rpm -q <em class="replaceable"><code>package name</code></em> </code> command displays the package name, version, and release number of the installed package <em class="replaceable"><code><package_name></code></em>. For example, using <code class="command">rpm -q tree</code> to query installed package <code class="filename">tree</code> might generate the following output:
+ </div><pre class="screen">tree-1.5.2.2-4.fc14.x86_64</pre><div class="para">
+ You can also use the following <span class="emphasis"><em>Package Selection Options</em></span> (which is a subheading in the RPM man page: see <code class="command">man rpm</code> for details) to further refine or qualify your query:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-a</code> — queries all currently installed packages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-f <code class="filename"><em class="replaceable"><code><file_name></code></em> </code> </code> — queries the RPM database for which package owns <code class="filename"><em class="replaceable"><code><file_name></code></em> </code>. Specify the absolute path of the file (for example, <code class="command">rpm -qf <code class="filename">/bin/ls</code> </code> instead of <code class="command">rpm -qf ls</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-p <code class="filename"><em class="replaceable"><code><package_file></code></em> </code> </code> — queries the uninstalled package <code class="filename"><em class="replaceable"><code><package_file></code></em> </code>.
+ </div></li></ul></div><div class="para">
+ There are a number of ways to specify what information to display about queried packages. The following options are used to select the type of information for which you are searching. These are called the <span class="emphasis"><em>Package Query Options</em></span>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-i</code> displays package information including name, description, release, size, build date, install date, vendor, and other miscellaneous information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-l</code> displays the list of files that the package contains.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-s</code> displays the state of all the files in the package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-d</code> displays a list of files marked as documentation (man pages, info pages, READMEs, etc.) in the package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-c</code> displays a list of files marked as configuration files. These are the files you edit after installation to adapt and customize the package to your system (for example, <code class="filename">sendmail.cf</code>, <code class="filename">passwd</code>, <code class="filename">inittab</code>, etc.).
+ </div></li></ul></div><div class="para">
+ For options that display lists of files, add <code class="command">-v</code> to the command to display the lists in a familiar <code class="command">ls -l</code> format.
+ </div></div><div class="section" title="3.2.7. Verifying" id="s2-rpm-verifying"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-verifying">3.2.7. Verifying</h3></div></div></div><a id="id786423" class="indexterm"></a><a id="id786435" class="indexterm"></a><div class="para">
+ Verifying a package compares information about files installed from a package with the same information from the original package. Among other things, verifying compares the file size, MD5 sum, permissions, type, owner, and group of each file.
+ </div><div class="para">
+ The command <code class="command">rpm -V</code> verifies a package. You can use any of the <span class="emphasis"><em>Verify Options</em></span> listed for querying to specify the packages you wish to verify. A simple use of verifying is <code class="command">rpm -V tree</code>, which verifies that all the files in the <code class="command">tree</code> package are as they were when they were originally installed. For example:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To verify a package containing a particular file:
+ </div><pre class="screen">
+<code class="command">rpm -Vf /usr/bin/tree</code>
+</pre><div class="para">
+ In this example, <code class="filename">/usr/bin/tree</code> is the absolute path to the file used to query a package.
+ </div></li><li class="listitem"><div class="para">
+ To verify ALL installed packages throughout the system (which will take some time):
+ </div><pre class="screen">
+<code class="command">rpm -Va</code>
+</pre></li><li class="listitem"><div class="para">
+ To verify an installed package against an RPM package file:
+ </div><pre class="screen">
+<code class="command">rpm -Vp tree-1.5.2.2-4.fc14.x86_64.rpm</code>
+</pre><div class="para">
+ This command can be useful if you suspect that your RPM database is corrupt.
+ </div></li></ul></div><div class="para">
+ If everything verified properly, there is no output. If there are any discrepancies, they are displayed. The format of the output is a string of eight characters (a "<code class="computeroutput">c</code>" denotes a configuration file) and then the file name. Each of the eight characters denotes the result of a comparison of one attribute of the file to the value of that attribute recorded in the RPM database. A single period (<code class="computeroutput">.</code>) means the test passed. The following characters denote specific discrepancies:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">5</code> — MD5 checksum
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">S</code> — file size
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">L</code> — symbolic link
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">T</code> — file modification time
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">D</code> — device
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">U</code> — user
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">G</code> — group
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">M</code> — mode (includes permissions and file type)
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">?</code> — unreadable file (file permission errors, for example)
+ </div></li></ul></div><div class="para">
+ If you see any output, use your best judgment to determine if you should remove the package, reinstall it, or fix the problem in another way.
+ </div></div></div><div xml:lang="en-US" class="section" title="3.3. Checking a Package's Signature" id="s1-check-rpm-sig" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-check-rpm-sig">3.3. Checking a Package's Signature</h2></div></div></div><a id="id1771634" class="indexterm"></a><div class="para">
+ If you wish to verify that a package has not been corrupted or tampered with, you can examine just the md5sum by entering this command at the shell prompt: (where <em class="replaceable"><code><rpm_file></code></em> is the file name of the RPM package):
+ </div><pre class="screen">
+<code class="command">rpm -K --nosignature <em class="replaceable"><code><rpm_file></code></em> </code>
+</pre><div class="para">
+ The output <code class="computeroutput"><em class="replaceable"><code><rpm_file></code></em>: rsa sha1 (md5) pgp md5 OK</code> (specifically the <span class="emphasis"><em>OK</em></span> part of it) indicates that the file was not corrupted during download. To see a more verbose message, replace <code class="option">-K</code> with <code class="option">-Kvv</code> in the command.
+ </div><div class="para">
+ On the other hand, how trustworthy is the developer who created the package? If the package is <em class="firstterm">signed</em> with the developer's GnuPG <em class="firstterm">key</em>, you know that the developer really is who they say they are.
+ </div><a id="id689159" class="indexterm"></a><a id="id689172" class="indexterm"></a><a id="id838217" class="indexterm"></a><div class="para">
+ An RPM package can be signed using <em class="firstterm">Gnu Privacy Guard</em> (or GnuPG), to help you make certain your downloaded package is trustworthy.
+ </div><div class="para">
+ GnuPG is a tool for secure communication; it is a complete and free replacement for the encryption technology of PGP, an electronic privacy program. With GnuPG, you can authenticate the validity of documents and encrypt/decrypt data to and from other recipients. GnuPG is capable of decrypting and verifying PGP 5.<em class="replaceable"><code>x</code></em> files as well.
+ </div><div class="para">
+ During installation, GnuPG is installed by defaut, which enables you to immediately start using it to verify any packages that you download from the Fedora Project. Before doing so, you first need to import the correct Fedora key.
+ </div><div class="section" title="3.3.1. Importing Keys" id="s2-keys-importing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-keys-importing">3.3.1. Importing Keys</h3></div></div></div><div class="para">
+ Fedora GnuPG keys are located in the <code class="filename">/etc/pki/rpm-gpg/</code> directory. To verify a Fedora Project package, first import the correct key based on your processor architecture:
+ </div><pre class="screen">
+<code class="command">rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-<em class="replaceable"><code>x86_64</code></em></code>
+</pre><div class="para">
+ To display a list of all keys installed for RPM verification, execute the command:
+ </div><pre class="screen">
+<code class="command">rpm -qa gpg-pubkey*</code>
+</pre><div class="para">
+ For the Fedora Project key, the output states:
+ </div><pre class="screen">gpg-pubkey-57bbccba-4a6f97af</pre><div class="para">
+ To display details about a specific key, use <code class="command">rpm -qi</code> followed by the output from the previous command:
+ </div><pre class="screen">
+<code class="command">rpm -qi gpg-pubkey-57bbccba-4a6f97af</code>
+</pre></div><div class="section" title="3.3.2. Verifying Signature of Packages" id="s2-keys-checking"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-keys-checking">3.3.2. Verifying Signature of Packages</h3></div></div></div><div class="para">
+ To check the GnuPG signature of an RPM file after importing the builder's GnuPG key, use the following command (replace <em class="replaceable"><code><rpm_file></code></em> with the filename of the RPM package):
+ </div><pre class="screen">
+<code class="command">rpm -K <em class="replaceable"><code><rpm_file></code></em> </code>
+</pre><div class="para">
+ If all goes well, the following message is displayed: <code class="computeroutput">rsa sha1 (md5) pgp md5 OK</code>. This means that the signature of the package has been verified, that it is not corrupt, and is therefore safe to install and use.
+ </div><div class="para">
+ For more information, including a list of currently-used Fedora Project keys and their fingerprints, refer to <a href="http://fedoraproject.org/en/keys">http://fedoraproject.org/en/keys</a>.
+ </div></div></div><div class="section" title="3.4. Practical and Common Examples of RPM Usage" id="s1-rpm-impressing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-rpm-impressing">3.4. Practical and Common Examples of RPM Usage</h2></div></div></div><a id="id662801" class="indexterm"></a><a id="id630864" class="indexterm"></a><div class="para">
+ RPM is a useful tool for both managing your system and diagnosing and fixing problems. The best way to make sense of all its options is to look at some examples.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Perhaps you have deleted some files by accident, but you are not sure what you deleted. To verify your entire system and see what might be missing, you could try the following command:
+ </div><a id="id889643" class="indexterm"></a><a id="id889655" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -Va</code>
+</pre><div class="para">
+ If some files are missing or appear to have been corrupted, you should probably either re-install the package or uninstall and then re-install the package.
+ </div></li><li class="listitem"><div class="para">
+ At some point, you might see a file that you do not recognize. To find out which package owns it, enter:
+ </div><a id="id621885" class="indexterm"></a><a id="id538754" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qf /usr/bin/ghostscript</code>
+</pre><div class="para">
+ The output would look like the following:
+ </div><pre class="screen">ghostscript-8.70-1.fc14.x86_64</pre></li><li class="listitem"><div class="para">
+ We can combine the above two examples in the following scenario. Say you are having problems with <code class="filename">/usr/bin/paste</code>. You would like to verify the package that owns that program, but you do not know which package owns <code class="command">paste</code>. Enter the following command,
+ </div><pre class="screen">
+<code class="command">rpm -Vf /usr/bin/paste</code>
+</pre><div class="para">
+ and the appropriate package is verified.
+ </div></li><li class="listitem"><div class="para">
+ Do you want to find out more information about a particular program? You can try the following command to locate the documentation which came with the package that owns that program:
+ </div><a id="id825860" class="indexterm"></a><a id="id825872" class="indexterm"></a><a id="id700696" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qdf /usr/bin/free</code>
+</pre><div class="para">
+ The output would be similar to the following:
+ </div><pre class="screen">/usr/share/doc/procps-3.2.8/BUGS
+/usr/share/doc/procps-3.2.8/FAQ
+/usr/share/doc/procps-3.2.8/NEWS
+/usr/share/doc/procps-3.2.8/TODO
+/usr/share/man/man1/free.1.gz
+/usr/share/man/man1/pgrep.1.gz
+/usr/share/man/man1/pkill.1.gz
+/usr/share/man/man1/pmap.1.gz
+/usr/share/man/man1/ps.1.gz
+/usr/share/man/man1/pwdx.1.gz
+/usr/share/man/man1/skill.1.gz
+/usr/share/man/man1/slabtop.1.gz
+/usr/share/man/man1/snice.1.gz
+/usr/share/man/man1/tload.1.gz
+/usr/share/man/man1/top.1.gz
+/usr/share/man/man1/uptime.1.gz
+/usr/share/man/man1/w.1.gz
+/usr/share/man/man1/watch.1.gz
+/usr/share/man/man5/sysctl.conf.5.gz
+/usr/share/man/man8/sysctl.8.gz
+/usr/share/man/man8/vmstat.8.gz</pre></li><li class="listitem"><div class="para">
+ You may find a new RPM, but you do not know what it does. To find information about it, use the following command:
+ </div><a id="id815804" class="indexterm"></a><a id="id815816" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qip crontabs-1.10-31.fc14.noarch.rpm</code>
+</pre><div class="para">
+ The output would be similar to the following:
+ </div><pre class="screen">Name : crontabs Relocations: (not relocatable)
+Size : 2486 License: Public Domain and GPLv2
+Signature : RSA/SHA1, Tue 11 Aug 2009 01:11:19 PM CEST, Key ID 9d1cc34857bbccba
+Packager : Fedora Project
+Summary : Root crontab files used to schedule the execution of programs
+Description :
+The crontabs package contains root crontab files and directories.
+You will need to install cron daemon to run the jobs from the crontabs.
+The cron daemon such as cronie or fcron checks the crontab files to
+see when particular commands are scheduled to be executed. If commands
+are scheduled, it executes them.
+Crontabs handles a basic system function, so it should be installed on
+your system.</pre></li><li class="listitem"><div class="para">
+ Perhaps you now want to see what files the <code class="filename">crontabs</code> RPM package installs. You would enter the following:
+ </div><a id="id773899" class="indexterm"></a><a id="id773911" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qlp crontabs-1.10-31.fc14.noarch.rpm</code>
+</pre><div class="para">
+ The output is similar to the following:
+ </div><pre class="screen">/etc/cron.daily
+/etc/cron.hourly
+/etc/cron.monthly
+/etc/cron.weekly
+/etc/crontab
+/usr/bin/run-parts
+/usr/share/man/man4/crontabs.4.gz</pre></li></ul></div><div class="para">
+ These are just a few examples. As you use RPM, you may find more uses for it.
+ </div></div><div class="section" title="3.5. Additional Resources" id="s1-rpm-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-rpm-additional-resources">3.5. Additional Resources</h2></div></div></div><a id="id533497" class="indexterm"></a><div class="para">
+ RPM is an extremely complex utility with many options and methods for querying, installing, upgrading, and removing packages. Refer to the following resources to learn more about RPM.
+ </div><div class="section" title="3.5.1. Installed Documentation" id="s2-rpm-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-installed-docs">3.5.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">rpm --help</code> — This command displays a quick reference of RPM parameters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man rpm</code> — The RPM man page gives more detail about RPM parameters than the <code class="command">rpm --help</code> command.
+ </div></li></ul></div></div><div class="section" title="3.5.2. Useful Websites" id="s2-rpm-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-useful-websites">3.5.2. Useful Websites</h3></div></div></div><div class="itemizedlist"><a id="id481227" class="indexterm"></a><ul><li class="listitem"><div class="para">
+ The RPM website — <a href="http://www.rpm.org/">http://www.rpm.org/</a>
+ </div></li><li class="listitem"><div class="para">
+ The RPM mailing list can be subscribed to, and its archives read from, here — <a href="http://www.redhat.com/mailman/listinfo/rpm-list/">https://lists.rpm.org/mailman/listinfo/rpm-list</a>
+ </div></li></ul></div></div><div class="section" title="3.5.3. Related Books" id="s2-rpm-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-related-books">3.5.3. Related Books</h3></div></div></div><a id="id729839" class="indexterm"></a><a id="id800378" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <em class="citetitle">Maximum RPM</em> — <a href="http://www.redhat.com/docs/books/max-rpm/">http://www.redhat.com/docs/books/max-rpm/</a> </span></dt><dd><div class="para">
+ The <em class="citetitle">Maximum RPM</em> book, which you can read online or download in HTML or PDF, covers everything from general RPM usage to building your own RPMs to programming with rpmlib.
+ </div></dd><dt class="varlistentry"><span class="term"> <em class="citetitle">Red Hat RPM Guide</em> — <a href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html">http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html</a> </span></dt><dd><div class="para">
+ The <em class="citetitle">Red Hat RPM Guide</em> by Eric Foster-Johnson is an excellent resource on all details of the RPM package format and the RPM package management utility.
+ </div></dd></dl></div></div></div></div></div><div class="part" title="Part II. Network-Related Configuration" id="pt-network-related-config"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part II. Network-Related Configuration</h1></div></div></div><div class="partintro" title="Network-Related Configuration" id="id796371"><div></div><div class="para">
+ After explaining how to configure the network, this part discusses topics related to networking such as how to allow remote logins, share files and directories over the network, and set up a Web server.
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#ch-Network_Interfaces">4. Network Interfaces</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-networkscripts-files">4.1. Network Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-interfaces">4.2. Interface Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-control">4.3. Interface Control Scripts</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-static-routes">4.4. Configuring Static Routes</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-functions">4.5. Network Function Files</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-resources">4.6. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Network_Configuration">5. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-T
he_NetworkManager_Daemon">5.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="#sec-Interacting_with_NetworkManager">5.2. Interacting with NetworkManager</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">5.3. Configuring Connection Settings</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Dynamic_Host_Configuration_Protocol_DHCP">6. Dynamic Host Configuration Protocol (DHCP)</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-dhcp-why">6.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-server">6.2. Configuring a DHCP Server</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-client">6.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="#sect-Configuring_a_Multihomed_DHCP_Server">6.4. Configuring a Multihomed DHCP Server</a></span></dt><dt><span class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">6.5. DH
CP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="#s1-dhcp-additional-resources">6.6. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Controlling_Access_to_Services">7. Controlling Access to Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-services-runlevels">7.1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="#s1-services-configuring">7.2. Configuring the Services</a></span></dt><dt><span class="section"><a href="#s1-services-running">7.3. Running the Services</a></span></dt><dt><span class="section"><a href="#s1-services-additional-resources">7.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Authentication_Configuration">8. Authentication Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool">8.1. The Authentication Configuration Tool</a></span></dt><dt><span
class="section"><a href="#chap-SSSD_User_Guide-Introduction">8.2. The System Security Services Daemon (SSSD)</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-OpenSSH">9. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ssh-protocol">9.1. The SSH Protocol</a></span></dt><dt><span class="section"><a href="#s1-ssh-configuration">9.2. An OpenSSH Configuration</a></span></dt><dt><span class="section"><a href="#s1-ssh-clients">9.3. OpenSSH Clients</a></span></dt><dt><span class="section"><a href="#s1-ssh-beyondshell">9.4. More Than a Secure Shell</a></span></dt><dt><span class="section"><a href="#s1-openssh-additional-resources">9.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-The_BIND_DNS_Server">10. The BIND DNS Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-bind-introduction">10.1. Introduction to DNS</a></span></dt><dt><span class="section"><a href="#s1-bind-namedconf">10.2. Con
figuring the <code class="command">named</code> Service</a></span></dt><dt><span class="section"><a href="#s1-bind-zone">10.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="#s1-bind-rndc">10.4. Using the <code class="command">rndc</code> Utility</a></span></dt><dt><span class="section"><a href="#s1-bind-dig">10.5. Using the <code class="command">dig</code> Utility</a></span></dt><dt><span class="section"><a href="#s1-bind-features">10.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="#s1-bind-mistakes">10.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="#s1-bind-additional-resources">10.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-The_Apache_HTTP_Server">11. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-apache-version2">11.1. The Apache HTTP Server 2.2</a></span></dt><dt><span class="section"><a href="#s1-apache-ru
nning">11.2. Running the <code class="systemitem">httpd</code> Service</a></span></dt><dt><span class="section"><a href="#s1-apache-editing">11.3. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-apache-dso">11.4. Working with Modules</a></span></dt><dt><span class="section"><a href="#s1-apache-virtualhosts">11.5. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="#s1-apache-mod_ssl">11.6. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="#s1-apache-resources">11.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-email">12. Email</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-email-protocols">12.1. Email Protocols</a></span></dt><dt><span class="section"><a href="#s1-email-types">12.2. Email Program Classifications</a></span></dt><dt><span class="section"><a href="#s1-email-mta">12.3. Mail Transport Agents</a></span></dt><dt><span class="s
ection"><a href="#s1-email-mda">12.4. Mail Delivery Agents</a></span></dt><dt><span class="section"><a href="#s1-email-mua">12.5. Mail User Agents</a></span></dt><dt><span class="section"><a href="#s1-email-additional-resources">12.6. Additional Resources</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" title="Chapter 4. Network Interfaces" id="ch-Network_Interfaces" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Network Interfaces</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-networkscripts-files">4.1. Network Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-interfaces">4.2. Interface Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-control">4.3. Interface Control Scripts</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-static-routes">4.4. Configuring Static Routes</a></span></d
t><dt><span class="section"><a href="#s1-networkscripts-functions">4.5. Network Function Files</a></span></dt><dt><span class="section"><a href="#s1-networkscripts-resources">4.6. Additional Resources</a></span></dt></dl></div><a id="id419279" class="indexterm"></a><a id="id441410" class="indexterm"></a><div class="para">
+ Under Fedora, all network communications occur between configured software <em class="firstterm">interfaces</em> and <em class="firstterm">physical networking devices</em> connected to the system.
+ </div><div class="para">
+ The configuration files for network interfaces are located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. The scripts used to activate and deactivate these network interfaces are also located here. Although the number and type of interface files can differ from system to system, there are three categories of files that exist in this directory:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <em class="firstterm">Interface configuration files</em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Interface control scripts</em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Network function files</em>
+ </div></li></ol></div><div class="para">
+ The files in each of these categories work together to enable various network devices.
+ </div><div class="para">
+ This chapter explores the relationship between these files and how they are used.
+ </div><div class="section" title="4.1. Network Configuration Files" id="s1-networkscripts-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-files">4.1. Network Configuration Files</h2></div></div></div><a id="id735299" class="indexterm"></a><div class="para">
+ Before delving into the interface configuration files, let us first itemize the primary configuration files used in network configuration. Understanding the role these files play in setting up the network stack can be helpful when customizing a Fedora system.
+ </div><div class="para">
+ The primary network configuration files are as follows:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">/etc/hosts</code> </span></dt><dd><div class="para">
+ The main purpose of this file is to resolve hostnames that cannot be resolved any other way. It can also be used to resolve hostnames on small networks with no DNS server. Regardless of the type of network the computer is on, this file should contain a line specifying the IP address of the loopback device (<code class="command">127.0.0.1</code>) as <code class="command">localhost.localdomain</code>. For more information, refer to the <code class="filename">hosts</code> man page.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/resolv.conf</code> </span></dt><dd><div class="para">
+ This file specifies the IP addresses of DNS servers and the search domain. Unless configured to do otherwise, the network initialization scripts populate this file. For more information about this file, refer to the <code class="filename">resolv.conf</code> man page.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/network</code> </span></dt><dd><div class="para">
+ This file specifies routing and host information for all network interfaces. For more information about this file and the directives it accepts, refer to <a class="xref" href="#s2-sysconfig-network" title="18.1.13. /etc/sysconfig/network">Section 18.1.13, “ <code class="filename">/etc/sysconfig/network</code> ”</a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code><interface-name></code></em> </code> </span></dt><dd><div class="para">
+ For each network interface, there is a corresponding interface configuration script. Each of these files provide information specific to a particular network interface. Refer to <a class="xref" href="#s1-networkscripts-interfaces" title="4.2. Interface Configuration Files">Section 4.2, “Interface Configuration Files”</a> for more information on this type of file and the directives it accepts.
+ </div></dd></dl></div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The <code class="filename">/etc/sysconfig/networking/</code> directory is used by the <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>) and its contents should <span class="bold bold"><strong>not</strong></span> be edited manually. Using only one method for network configuration is strongly encouraged, due to the risk of configuration deletion.
+ </div><div class="para">
+ For more information about configuring network interfaces using the <span class="application"><strong>Network Administration Tool</strong></span>, refer to <a class="xref" href="#ch-Network_Configuration" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a>
+ </div></div></div></div><div class="section" title="4.2. Interface Configuration Files" id="s1-networkscripts-interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-interfaces">4.2. Interface Configuration Files</h2></div></div></div><a id="id581813" class="indexterm"></a><a id="id581826" class="indexterm"></a><div class="para">
+ Interface configuration files control the software interfaces for individual network devices. As the system boots, it uses these files to determine what interfaces to bring up and how to configure them. These files are usually named <code class="filename">ifcfg-<em class="replaceable"><code><name></code></em> </code>, where <em class="replaceable"><code><name></code></em> refers to the name of the device that the configuration file controls.
+ </div><div class="section" title="4.2.1. Ethernet Interfaces" id="s2-networkscripts-interfaces-eth0"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-interfaces-eth0">4.2.1. Ethernet Interfaces</h3></div></div></div><a id="id716980" class="indexterm"></a><a id="id1376360" class="indexterm"></a><div class="para">
+ One of the most common interface files is <code class="filename">ifcfg-eth0</code>, which controls the first Ethernet <em class="firstterm">network interface card</em> or <em class="firstterm">NIC</em> in the system. In a system with multiple NICs, there are multiple <code class="filename">ifcfg-eth<em class="replaceable"><code><X></code></em> </code> files (where <em class="replaceable"><code><X></code></em> is a unique number corresponding to a specific interface). Because each device has its own configuration file, an administrator can control how each interface functions individually.
+ </div><div class="para">
+ The following is a sample <code class="filename">ifcfg-eth0</code> file for a system using a fixed IP address:
+ </div><pre class="screen">DEVICE=eth0
+BOOTPROTO=none
+ONBOOT=yes
+NETMASK=255.255.255.0
+IPADDR=10.0.1.27
+USERCTL=no</pre><div class="para">
+ The values required in an interface configuration file can change based on other values. For example, the <code class="filename">ifcfg-eth0</code> file for an interface using DHCP looks different because IP information is provided by the DHCP server:
+ </div><pre class="screen">DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes</pre><div class="para">
+ The <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>) is an easy way to make changes to the various network interface configuration files (refer to <a class="xref" href="#ch-Network_Configuration" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a> for detailed instructions on using this tool).
+ </div><div class="para">
+ However, it is also possible to manually edit the configuration files for a given network interface.
+ </div><div class="para">
+ Below is a listing of the configurable parameters in an Ethernet interface configuration file:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="command">BONDING_OPTS=<em class="replaceable"><code><parameters></code></em> </code> </span></dt><dd><div class="para">
+ sets the configuration parameters for the bonding device, and is used in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond<em class="replaceable"><code><N></code></em> </code> (see <a class="xref" href="#s2-networkscripts-interfaces-chan" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a>). These parameters are identical to those used for bonding devices in <code class="filename">/sys/class/net/<em class="replaceable"><code><bonding device></code></em>/bonding</code>, and the module parameters for the bonding driver as described in <span class="emphasis"><em><code class="filename">bonding</code> Module Directives</em></span>.
+ </div><div class="para">
+ This configuration method is used so that multiple bonding devices can have different configurations. It is highly recommened to place all of your bonding options after the <code class="command">BONDING_OPTS</code> directive in <code class="filename">ifcfg-<em class="replaceable"><code><name></code></em></code>. Do <span class="emphasis"><em>not</em></span> specify options for the bonding device in <code class="filename">/etc/modprobe.d/<em class="replaceable"><code><bonding></code></em>.conf</code>, or in the deprecated <code class="filename">/etc/modprobe.conf</code> file.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">BOOTPROTO=<em class="replaceable"><code><protocol></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><protocol></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">none</code> — No boot-time protocol should be used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">bootp</code> — The BOOTP protocol should be used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">dhcp</code> — The DHCP protocol should be used.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">BROADCAST=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is the broadcast address. This directive is deprecated, as the value is calculated automatically with <code class="command">ifcalc</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">DEVICE=<em class="replaceable"><code><name></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><name></code></em> </code> is the name of the physical device (except for dynamically-allocated PPP devices where it is the <span class="emphasis"><em>logical name</em></span>).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">DHCP_HOSTNAME</code> </span></dt><dd><div class="para">
+ Use this option only if the DHCP server requires the client to specify a hostname before receiving an IP address.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">DNS<em class="replaceable"><code>{1,2}</code></em>=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is a name server address to be placed in <code class="filename">/etc/resolv.conf</code> if the <code class="command">PEERDNS</code> directive is set to <code class="command">yes</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">ETHTOOL_OPTS=<em class="replaceable"><code><options></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><options></code></em> </code> are any device-specific options supported by <code class="command">ethtool</code>. For example, if you wanted to force 100Mb, full duplex:
+ </div><pre class="screen">
+<code class="command">ETHTOOL_OPTS="autoneg off speed 100 duplex full"</code>
+</pre><div class="para">
+ Instead of a custom initscript, use <code class="command">ETHTOOL_OPTS</code> to set the interface speed and duplex settings. Custom initscripts run outside of the network init script lead to unpredictable results during a post-boot network service restart.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Changing speed or duplex settings almost always requires disabling autonegotiation with the <code class="command">autoneg off</code> option. This needs to be stated first, as the option entries are order-dependent.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="command">GATEWAY=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code><address></code></em> is the IP address of the network router or gateway device (if any).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">HWADDR=<em class="replaceable"><code><MAC-address></code></em> </code> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code><MAC-address></code></em> is the hardware address of the Ethernet device in the form <em class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em>. This directive must be used in machines containing more than one NIC to ensure that the interfaces are assigned the correct device names regardless of the configured load order for each NIC's module. This directive should <span class="bold bold"><strong>not</strong></span> be used in conjunction with <code class="command">MACADDR</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">IPADDR=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is the IP address.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">MACADDR=<em class="replaceable"><code><MAC-address></code></em> </code> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code><MAC-address></code></em> is the hardware address of the Ethernet device in the form <em class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em>. This directive is used to assign a MAC address to an interface, overriding the one assigned to the physical NIC. This directive should <span class="bold bold"><strong>not</strong></span> be used in conjunction with <code class="command">HWADDR</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">MASTER=<em class="replaceable"><code><bond-interface></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><bond-interface></code></em> </code> is the channel bonding interface to which the Ethernet interface is linked.
+ </div><div class="para">
+ This directive is used in conjunction with the <code class="command">SLAVE</code> directive.
+ </div><div class="para">
+ Refer to <a class="xref" href="#s2-networkscripts-interfaces-chan" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a> for more information about channel bonding interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">NETMASK=<em class="replaceable"><code><mask></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><mask></code></em> </code> is the netmask value.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">NETWORK=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is the network address. This directive is deprecated, as the value is calculated automatically with <code class="command">ifcalc</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">ONBOOT=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — This device should be activated at boot-time.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — This device should not be activated at boot-time.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">PEERDNS=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Modify <code class="filename">/etc/resolv.conf</code> if the DNS directive is set. If using DHCP, then <code class="command">yes</code> is the default.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Do not modify <code class="filename">/etc/resolv.conf</code>.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">SLAVE=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — This device is controlled by the channel bonding interface specified in the <code class="command">MASTER</code> directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — This device is <span class="emphasis"><em>not</em></span> controlled by the channel bonding interface specified in the <code class="command">MASTER</code> directive.
+ </div></li></ul></div><div class="para">
+ This directive is used in conjunction with the <code class="command">MASTER</code> directive.
+ </div><div class="para">
+ Refer to <a class="xref" href="#s2-networkscripts-interfaces-chan" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a> for more about channel bonding interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">SRCADDR=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is the specified source IP address for outgoing packets.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">USERCTL=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Non-root users are allowed to control this device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Non-root users are not allowed to control this device.
+ </div></li></ul></div></dd></dl></div></div><div class="section" title="4.2.2. Channel Bonding Interfaces" id="s2-networkscripts-interfaces-chan"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-interfaces-chan">4.2.2. Channel Bonding Interfaces</h3></div></div></div><a id="id1558608" class="indexterm"></a><a id="id579465" class="indexterm"></a><div class="para">
+ Fedora allows administrators to bind multiple network interfaces together into a single channel using the <code class="filename">bonding</code> kernel module and a special network interface called a <em class="firstterm">channel bonding interface</em>. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
+ </div><div class="para">
+ To create a channel bonding interface, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory called <code class="filename">ifcfg-bond<em class="replaceable"><code><N></code></em> </code>, replacing <em class="replaceable"><code><N></code></em> with the number for the interface, such as <code class="filename">0</code>.
+ </div><div class="para">
+ The contents of the file can be identical to whatever type of interface is getting bonded, such as an Ethernet interface. The only difference is that the <code class="command">DEVICE=</code> directive must be <code class="command">bond<em class="replaceable"><code><N></code></em> </code>, replacing <em class="replaceable"><code><N></code></em> with the number for the interface.
+ </div><div class="para">
+ The following is a sample channel bonding configuration file:
+ </div><div class="example" title="Example 4.1. Sample ifcfg-bond0 interface configuration file" id="ex-Sample_ifcfg-bond0_interface_configuration_file"><h6>Example 4.1. Sample ifcfg-bond0 interface configuration file</h6><div class="example-contents"><pre class="screen">DEVICE=bond0
+IPADDR=192.168.1.1
+NETMASK=255.255.255.0
+ONBOOT=yes
+BOOTPROTO=none
+USERCTL=no
+BONDING_OPTS="<em class="replaceable"><code><bonding parameters separated by spaces></code></em>"</pre></div></div><br class="example-break" /><div class="para">
+ After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the <code class="command">MASTER=</code> and <code class="command">SLAVE=</code> directives to their configuration files. The configuration files for each of the channel-bonded interfaces can be nearly identical.
+ </div><div class="para">
+ For example, if two Ethernet interfaces are being channel bonded, both <code class="filename">eth0</code> and <code class="filename">eth1</code> may look like the following example:
+ </div><pre class="screen">
+DEVICE=eth<em class="replaceable"><code><N></code></em>
+BOOTPROTO=none
+ONBOOT=yes
+MASTER=bond0
+SLAVE=yes
+USERCTL=no
+</pre><div class="para">
+ In this example, replace <em class="replaceable"><code><N></code></em> with the numerical value for the interface.
+ </div><div class="para">
+ For a channel bonding interface to be valid, the kernel module must be loaded. To ensure that the module is loaded when the channel bonding interface is brought up, create a new file as root named <code class="filename"><em class="replaceable"><code><bonding></code></em>.conf</code> in the <code class="filename">/etc/modprobe.d/</code> directory. Note that you can name this file anything you like as long as it ends with a <code class="filename">.conf</code> extension. Insert the following line in this new file:
+ </div><pre class="screen">alias bond<em class="replaceable"><code><N></code></em> bonding</pre><div class="para">
+ Replace <em class="replaceable"><code><N></code></em> with the interface number, such as <code class="command">0</code>. For each configured channel bonding interface, there must be a corresponding entry in your new <code class="filename">/etc/modprobe.d/<em class="replaceable"><code><bonding></code></em>.conf</code> file.
+ </div><div class="important" title="Important: put all bonding module parameters in ifcfg-bondN files"><div class="admonition_header"><h2>Important: put all bonding module parameters in ifcfg-bondN files</h2></div><div class="admonition"><div class="para">
+ Parameters for the bonding kernel module must be specified as a space-separated list in the <em class="parameter"><code>BONDING_OPTS="<em class="replaceable"><code><bonding parameters></code></em>"</code></em> directive in the ifcfg-bond<em class="replaceable"><code><N></code></em> interface file. Do <span class="emphasis"><em>not</em></span> specify options for the bonding device in <code class="filename">/etc/modprobe.d/<em class="replaceable"><code><bonding></code></em>.conf</code>, or in the deprecated <code class="filename">/etc/modprobe.conf</code> file. For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, refer to <a class="xref" href="#sec-Using_Channel_Bonding" title="22.7.2. Using Channel Bonding">Section 22.7.2, “Using Channel Bonding”</a>.
+ </div></div></div></div><div class="section" title="4.2.3. Alias and Clone Files" id="s2-networkscripts-interfaces-alias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-interfaces-alias">4.2.3. Alias and Clone Files</h3></div></div></div><a id="id583271" class="indexterm"></a><a id="id583288" class="indexterm"></a><div class="para">
+ Two lesser-used types of interface configuration files are <em class="firstterm">alias</em> and <em class="firstterm">clone</em> files.
+ </div><div class="para">
+ Alias interface configuration files, which are used to bind multiple addresses to a single interface, use the <code class="filename">ifcfg-<em class="replaceable"><code><if-name></code></em>:<em class="replaceable"><code><alias-value></code></em> </code> naming scheme.
+ </div><div class="para">
+ For example, an <code class="filename">ifcfg-eth0:0</code> file could be configured to specify <code class="computeroutput">DEVICE=eth0:0</code> and a static IP address of 10.0.0.2, serving as an alias of an Ethernet interface already configured to receive its IP information via DHCP in <code class="filename">ifcfg-eth0</code>. Under this configuration, <code class="filename">eth0</code> is bound to a dynamic IP address, but the same physical network card can receive requests via the fixed, 10.0.0.2 IP address.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Alias interfaces do not support DHCP.
+ </div></div></div><div class="para">
+ A clone interface configuration file should use the following naming convention: <code class="filename">ifcfg-<em class="replaceable"><code><if-name></code></em>-<em class="replaceable"><code><clone-name></code></em> </code>. While an alias file allows multiple addresses for an existing interface, a clone file is used to specify additional options for an interface. For example, a standard DHCP Ethernet interface called <code class="filename">eth0</code>, may look similar to this:
+ </div><pre class="screen">DEVICE=eth0
+ONBOOT=yes
+BOOTPROTO=dhcp</pre><div class="para">
+ Since the default value for the <code class="command">USERCTL</code> directive is <code class="command">no</code> if it is not specified, users cannot bring this interface up and down. To give users the ability to control the interface, create a clone by copying <code class="filename">ifcfg-eth0</code> to <code class="filename">ifcfg-eth0-user</code> and add the following line to <code class="filename">ifcfg-eth0-user</code>:
+ </div><pre class="screen">USERCTL=yes</pre><div class="para">
+ This way a user can bring up the <code class="filename">eth0</code> interface using the <code class="command">/sbin/ifup eth0-user</code> command because the configuration options from <code class="filename">ifcfg-eth0</code> and <code class="filename">ifcfg-eth0-user</code> are combined. While this is a very basic example, this method can be used with a variety of options and interfaces.
+ </div><div class="para">
+ The easiest way to create alias and clone interface configuration files is to use the graphical <span class="application"><strong>Network Administration Tool</strong></span>. For more information on using this tool, refer to <a class="xref" href="#ch-Network_Configuration" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a>.
+ </div></div><div class="section" title="4.2.4. Dialup Interfaces" id="s2-networkscripts-interfaces-ppp0"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-interfaces-ppp0">4.2.4. Dialup Interfaces</h3></div></div></div><a id="id707578" class="indexterm"></a><div class="para">
+ If you are connecting to the Internet via a dialup connection, a configuration file is necessary for the interface.
+ </div><div class="para">
+ PPP interface files are named using the following format:
+ <div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="filename">ifcfg-ppp<em class="replaceable"><code><X></code></em> </code> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code><X></code></em> is a unique number corresponding to a specific interface.
+ </div></dd></dl></div>
+
+ </div><div class="para">
+ The PPP interface configuration file is created automatically when <code class="command">wvdial</code>, the <span class="application"><strong>Network Administration Tool</strong></span> or <span class="application"><strong>Kppp</strong></span> is used to create a dialup account. It is also possible to create and edit this file manually.
+ </div><div class="para">
+ The following is a typical <code class="filename">ifcfg-ppp0</code> file:
+ </div><pre class="screen">DEVICE=ppp0
+NAME=test
+WVDIALSECT=test
+MODEMPORT=/dev/modem
+LINESPEED=115200
+PAPNAME=test
+USERCTL=true
+ONBOOT=no
+PERSIST=no
+DEFROUTE=yes
+PEERDNS=yes
+DEMAND=no
+IDLETIMEOUT=600</pre><div class="para">
+ <em class="firstterm">Serial Line Internet Protocol (SLIP)</em> is another dialup interface, although it is used less frequently. SLIP files have interface configuration file names such as <code class="filename">ifcfg-sl0</code>.
+ </div><div class="para">
+ Other options that may be used in these files include:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="command">DEFROUTE=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Set this interface as the default route.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Do not set this interface as the default route.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">DEMAND=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — This interface allows <code class="command">pppd</code> to initiate a connection when someone attempts to use it.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — A connection must be manually established for this interface.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">IDLETIMEOUT=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the number of seconds of idle activity before the interface disconnects itself.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">INITSTRING=<em class="replaceable"><code><string></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><string></code></em> </code> is the initialization string passed to the modem device. This option is primarily used in conjunction with SLIP interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">LINESPEED=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the baud rate of the device. Possible standard values include <code class="command">57600</code>, <code class="command">38400</code>, <code class="command">19200</code>, and <code class="command">9600</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">MODEMPORT=<em class="replaceable"><code><device></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><device></code></em> </code> is the name of the serial device that is used to establish the connection for the interface.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">MTU=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the <em class="firstterm">Maximum Transfer Unit (MTU)</em> setting for the interface. The MTU refers to the largest number of bytes of data a frame can carry, not counting its header information. In some dialup situations, setting this to a value of <code class="command">576</code> results in fewer packets dropped and a slight improvement to the throughput for a connection.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">NAME=<em class="replaceable"><code><name></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><name></code></em> </code> is the reference to the title given to a collection of dialup connection configurations.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">PAPNAME=<em class="replaceable"><code><name></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><name></code></em> </code> is the username given during the <em class="firstterm">Password Authentication Protocol (PAP)</em> exchange that occurs to allow connections to a remote system.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">PERSIST=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — This interface should be kept active at all times, even if deactivated after a modem hang up.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — This interface should not be kept active at all times.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">REMIP=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is the IP address of the remote system. This is usually left unspecified.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">WVDIALSECT=<em class="replaceable"><code><name></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><name></code></em> </code> associates this interface with a dialer configuration in <code class="filename">/etc/wvdial.conf</code>. This file contains the phone number to be dialed and other important information for the interface.
+ </div></dd></dl></div></div><div class="section" title="4.2.5. Other Interfaces" id="s2-networkscripts-interfaces-other"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-interfaces-other">4.2.5. Other Interfaces</h3></div></div></div><div class="para">
+ Other common interface configuration files include the following:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">ifcfg-lo</code> </span></dt><dd><div class="para">
+ A local <em class="firstterm">loopback interface</em> is often used in testing, as well as being used in a variety of applications that require an IP address pointing back to the same system. Any data sent to the loopback device is immediately returned to the host's network layer.
+ </div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The loopback interface script, <code class="filename">/etc/sysconfig/network-scripts/ifcfg-lo</code>, should never be edited manually. Doing so can prevent the system from operating correctly.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifcfg-irlan0</code> </span></dt><dd><div class="para">
+ An <em class="firstterm">infrared interface</em> allows information between devices, such as a laptop and a printer, to flow over an infrared link. This works in a similar way to an Ethernet device except that it commonly occurs over a peer-to-peer connection.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifcfg-plip0</code> </span></dt><dd><div class="para">
+ A <em class="firstterm">Parallel Line Interface Protocol (PLIP)</em> connection works much the same way as an Ethernet device, except that it utilizes a parallel port.
+ </div></dd></dl></div></div></div><div class="section" title="4.3. Interface Control Scripts" id="s1-networkscripts-control"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-control">4.3. Interface Control Scripts</h2></div></div></div><a id="id599804" class="indexterm"></a><a id="id483639" class="indexterm"></a><a id="id483661" class="indexterm"></a><a id="id549456" class="indexterm"></a><a id="id549469" class="indexterm"></a><div class="para">
+ The interface control scripts activate and deactivate system interfaces. There are two primary interface control scripts that call on control scripts located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory: <code class="command">/sbin/ifdown</code> and <code class="command">/sbin/ifup</code>.
+ </div><div class="para">
+ The <code class="filename">ifup</code> and <code class="filename">ifdown</code> interface scripts are symbolic links to scripts in the <code class="filename">/sbin/</code> directory. When either of these scripts are called, they require the value of the interface to be specified, such as:
+ </div><pre class="screen">
+<code class="command">ifup eth0</code>
+</pre><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ The <code class="filename">ifup</code> and <code class="filename">ifdown</code> interface scripts are the only scripts that the user should use to bring up and take down network interfaces.
+ </div><div class="para">
+ The following scripts are described for reference purposes only.
+ </div></div></div><div class="para">
+ Two files used to perform a variety of network initialization tasks during the process of bringing up a network interface are <code class="filename">/etc/rc.d/init.d/functions</code> and <code class="filename">/etc/sysconfig/network-scripts/network-functions</code>. Refer to <a class="xref" href="#s1-networkscripts-functions" title="4.5. Network Function Files">Section 4.5, “Network Function Files”</a> for more information.
+ </div><div class="para">
+ After verifying that an interface has been specified and that the user executing the request is allowed to control the interface, the correct script brings the interface up or down. The following are common interface control scripts found within the <code class="filename">/etc/sysconfig/network-scripts/</code> directory:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">ifup-aliases</code> </span></dt><dd><div class="para">
+ Configures IP aliases from interface configuration files when more than one IP address is associated with an interface.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-ippp</code> and <code class="filename">ifdown-ippp</code> </span></dt><dd><div class="para">
+ Brings ISDN interfaces up and down.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-ipv6</code> and <code class="filename">ifdown-ipv6</code> </span></dt><dd><div class="para">
+ Brings IPv6 interfaces up and down.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-plip</code> </span></dt><dd><div class="para">
+ Brings up a PLIP interface.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-plusb</code> </span></dt><dd><div class="para">
+ Brings up a USB interface for network connections.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-post</code> and <code class="filename">ifdown-post</code> </span></dt><dd><div class="para">
+ Contains commands to be executed after an interface is brought up or down.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-ppp</code> and <code class="filename">ifdown-ppp</code> </span></dt><dd><div class="para">
+ Brings a PPP interface up or down.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-routes</code> </span></dt><dd><div class="para">
+ Adds static routes for a device as its interface is brought up.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifdown-sit</code> and <code class="filename">ifup-sit</code> </span></dt><dd><div class="para">
+ Contains function calls related to bringing up and down an IPv6 tunnel within an IPv4 connection.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-wireless</code> </span></dt><dd><div class="para">
+ Brings up a wireless interface.
+ </div></dd></dl></div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Removing or modifying any scripts in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory can cause interface connections to act irregularly or fail. Only advanced users should modify scripts related to a network interface.
+ </div></div></div><div class="para">
+ The easiest way to manipulate all network scripts simultaneously is to use the <code class="command">/sbin/service</code> command on the network service (<code class="filename">/etc/rc.d/init.d/network</code>), as illustrated the following command:
+ </div><pre class="screen">
+<code class="command">/sbin/service network <em class="replaceable"><code><action></code></em> </code>
+</pre><div class="para">
+ Here, <em class="replaceable"><code><action></code></em> can be either <code class="command">start</code>, <code class="command">stop</code>, or <code class="command">restart</code>.
+ </div><div class="para">
+ To view a list of configured devices and currently active network interfaces, use the following command:
+ </div><pre class="screen">
+<code class="command">/sbin/service network status</code>
+</pre></div><div class="section" title="4.4. Configuring Static Routes" id="s1-networkscripts-static-routes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-static-routes">4.4. Configuring Static Routes</h2></div></div></div><div class="para">
+ Routing will be configured on routing devices, therefore it should not be necessary to configure static routes on Fedora servers or clients. However, if static routes are required they can be configured for each interface. This can be useful if you have multiple interfaces in different subnets. Use the <code class="command">route</code> command to display the IP routing table.
+ </div><div class="para">
+ Static route configuration is stored in a <code class="filename">/etc/sysconfig/network-scripts/route-<em class="replaceable"><code>interface</code></em> </code> file. For example, static routes for the eth0 interface would be stored in the <code class="filename">/etc/sysconfig/network-scripts/route-eth0</code> file. The <code class="filename">route-<em class="replaceable"><code>interface</code></em> </code> file has two formats: IP command arguments and network/netmask directives.
+ </div><div class="formalpara"><h5 class="formalpara" id="id971199">IP Command Arguments Format</h5>
+ Define a default gateway on the first line. This is only required if the default gateway is not set via DHCP:
+ </div><pre class="screen">
+default <em class="replaceable"><code>X.X.X.X</code></em> dev <em class="replaceable"><code>interface</code></em>
+</pre><div class="para">
+ <em class="replaceable"><code>X.X.X.X</code></em> is the IP address of the default gateway. The <em class="replaceable"><code>interface</code></em> is the interface that is connected to, or can reach, the default gateway.
+ </div><div class="para">
+ Define a static route. Each line is parsed as an individual route:
+ </div><pre class="screen">
+<em class="replaceable"><code>X.X.X.X/X</code></em> via <em class="replaceable"><code>X.X.X.X</code></em> dev <em class="replaceable"><code>interface</code></em>
+</pre><div class="para">
+ <em class="replaceable"><code>X.X.X.X/X</code></em> is the network number and netmask for the static route. <em class="replaceable"><code>X.X.X.X</code></em> and <em class="replaceable"><code>interface</code></em> are the IP address and interface for the default gateway respectively. The <em class="replaceable"><code>X.X.X.X</code></em> address does not have to be the default gateway IP address. In most cases, <em class="replaceable"><code>X.X.X.X</code></em> will be an IP address in a different subnet, and <em class="replaceable"><code>interface</code></em> will be the interface that is connected to, or can reach, that subnet. Add as many static routes as required.
+ </div><div class="para">
+ The following is a sample <code class="filename">route-eth0</code> file using the IP command arguments format. The default gateway is 192.168.0.1, interface eth0. The two static routes are for the 10.10.10.0/24 and 172.16.1.0/24 networks:
+ </div><pre class="screen">
+default 192.168.0.1 dev eth0
+10.10.10.0/24 via 192.168.0.1 dev eth0
+172.16.1.0/24 via 192.168.0.1 dev eth0
+</pre><div class="para">
+ Static routes should only be configured for other subnets. The above example is not necessary, since packets going to the 10.10.10.0/24 and 172.16.1.0/24 networks will use the default gateway anyway. Below is an example of setting static routes to a different subnet, on a machine in a 192.168.0.0/24 subnet. The example machine has an eth0 interface in the 192.168.0.0/24 subnet, and an eth1 interface (10.10.10.1) in the 10.10.10.0/24 subnet:
+ </div><pre class="screen">
+10.10.10.0/24 via 10.10.10.1 dev eth1
+</pre><div class="warning" title="Duplicate Default Gateways"><div class="admonition_header"><h2>Duplicate Default Gateways</h2></div><div class="admonition"><div class="para">
+ If the default gateway is already assigned from DHCP, the IP command arguments format can cause one of two errors during start-up, or when bringing up an interface from the down state using the <code class="command">ifup</code> command: "RTNETLINK answers: File exists" or 'Error: either "to" is a duplicate, or "<em class="replaceable"><code>X.X.X.X</code></em>" is a garbage.', where <em class="replaceable"><code>X.X.X.X</code></em> is the gateway, or a different IP address. These errors can also occur if you have another route to another network using the default gateway. Both of these errors are safe to ignore.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="id793359">Network/Netmask Directives Format</h5>
+ You can also use the network/netmask directives format for <code class="filename">route-<em class="replaceable"><code>interface</code></em> </code> files. The following is a template for the network/netmask format, with instructions following afterwards:
+ </div><pre class="screen">
+ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em>
+NETMASK0=<em class="replaceable"><code>X.X.X.X</code></em>
+GATEWAY0=<em class="replaceable"><code>X.X.X.X</code></em>
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em> </code> is the network number for the static route.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">NETMASK0=<em class="replaceable"><code>X.X.X.X</code></em> </code> is the netmask for the network number defined with <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em> </code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">GATEWAY0=<em class="replaceable"><code>X.X.X.X</code></em> </code> is the default gateway, or an IP address that can be used to reach <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em> </code>
+ </div></li></ul></div><div class="para">
+ The following is a sample <code class="filename">route-eth0</code> file using the network/netmask directives format. The default gateway is 192.168.0.1, interface eth0. The two static routes are for the 10.10.10.0/24 and 172.16.1.0/24 networks. However, as mentioned before, this example is not necessary as the 10.10.10.0/24 and 172.16.1.0/24 networks would use the default gateway anyway:
+ </div><pre class="screen">
+ADDRESS0=10.10.10.0
+NETMASK0=255.255.255.0
+GATEWAY0=192.168.0.1
+ADDRESS1=172.16.1.0
+NETMASK1=255.255.255.0
+GATEWAY1=192.168.0.1
+</pre><div class="para">
+ Subsequent static routes must be numbered sequentially, and must not skip any values. For example, <code class="computeroutput">ADDRESS0</code>, <code class="computeroutput">ADDRESS1</code>, <code class="computeroutput">ADDRESS2</code>, and so on.
+ </div><div class="para">
+ Below is an example of setting static routes to a different subnet, on a machine in the 192.168.0.0/24 subnet. The example machine has an eth0 interface in the 192.168.0.0/24 subnet, and an eth1 interface (10.10.10.1) in the 10.10.10.0/24 subnet:
+ </div><pre class="screen">
+ADDRESS0=10.10.10.0
+NETMASK0=255.255.255.0
+GATEWAY0=10.10.10.1
+</pre><div class="para">
+ DHCP should assign these settings automatically, therefore it should not be necessary to configure static routes on Fedora servers or clients.
+ </div></div><div class="section" title="4.5. Network Function Files" id="s1-networkscripts-functions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-functions">4.5. Network Function Files</h2></div></div></div><a id="id2225749" class="indexterm"></a><div class="para">
+ Fedora makes use of several files that contain important common functions used to bring interfaces up and down. Rather than forcing each interface control file to contain these functions, they are grouped together in a few files that are called upon when necessary.
+ </div><div class="para">
+ The <code class="filename">/etc/sysconfig/network-scripts/network-functions</code> file contains the most commonly used IPv4 functions, which are useful to many interface control scripts. These functions include contacting running programs that have requested information about changes in the status of an interface, setting hostnames, finding a gateway device, verifying whether or not a particular device is down, and adding a default route.
+ </div><div class="para">
+ As the functions required for IPv6 interfaces are different from IPv4 interfaces, a <code class="filename">/etc/sysconfig/network-scripts/network-functions-ipv6</code> file exists specifically to hold this information. The functions in this file configure and delete static IPv6 routes, create and remove tunnels, add and remove IPv6 addresses to an interface, and test for the existence of an IPv6 address on an interface.
+ </div></div><div class="section" title="4.6. Additional Resources" id="s1-networkscripts-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-resources">4.6. Additional Resources</h2></div></div></div><a id="id2225765" class="indexterm"></a><div class="para">
+ The following are resources which explain more about network interfaces.
+ </div><div class="section" title="4.6.1. Installed Documentation" id="s2-networkscripts-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-docs-inst">4.6.1. Installed Documentation</h3></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code><version></code></em>/sysconfig.txt</code> </span></dt><dd><div class="para">
+ A guide to available options for network configuration files, including IPv6 options not covered in this chapter.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/usr/share/doc/iproute-<em class="replaceable"><code><version></code></em>/ip-cref.ps</code> </span></dt><dd><div class="para">
+ This file contains a wealth of information about the <code class="command">ip</code> command, which can be used to manipulate routing tables, among other things. Use the <span class="application"><strong>ggv</strong></span> or <span class="application"><strong>kghostview</strong></span> application to view this file.
+ </div></dd></dl></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 5. Network Configuration" id="ch-Network_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Network Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sec-The_NetworkManager_Daemon">5.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="#sec-Interacting_with_NetworkManager">5.2. Interacting with NetworkManager</a></span></dt><dt><span class="section"><a href="#sec-Configuring_Connection_Settings">5.3. Configuring Connection Settings</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> is a dynamic network control and configuration system that attempts to keep network devices and connections up and active when they are available. <span class="application"><strong>NetworkManager</strong></span> consists of a core daemon, a GNOME Notification Area applet that provides network status information, and graphical configuration tools that can create, edit and remove connections and interfaces. <span class="application"><strong>NetworkManager</strong></span> can be used to configure the following types of connections: Ethernet, wireless, mobile broadband (such as cellular 3G), and <code class="systemitem">DSL</code> and <code class="systemitem">PPPoE</code> (Point-to-Point over Ethernet). In addition, <span class="application"><strong>NetworkManager</strong></span> allows for the configuration of network aliases, static routes, DNS information and VPN connections, as well as many connection-specifi
c parameters. Finally, <span class="application"><strong>NetworkManager</strong></span> provides a rich API via D-Bus which allows applications to query and control network configuration and state.
+ </div><div class="para">
+ Previous versions of Fedora shipped with the <span class="application"><strong>Network Administration Tool</strong></span>, which was commonly known as <code class="command">system-config-network</code> after its command line invocation. In Fedora 14, <span class="application"><strong>NetworkManager</strong></span> replaces the former <span class="application"><strong>Network Administration Tool</strong></span> while providing enhanced functionality, such as user-specific and mobile broadband configuration. It is also possible to configure the network in Fedora 14 by editing interface configuration files; refer to <a class="xref" href="#ch-Network_Interfaces" title="Chapter 4. Network Interfaces">Chapter 4, <i>Network Interfaces</i></a> for more information.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> may be installed by default on Fedora. To ensure that it is, first run the following command as the root user:
+ </div><pre class="screen">~]# <code class="command">yum install NetworkManager</code>
+</pre><div class="section" title="5.1. The NetworkManager Daemon" id="sec-The_NetworkManager_Daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-The_NetworkManager_Daemon">5.1. The NetworkManager Daemon</h2></div></div></div><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> daemon runs with root privileges and is usually configured to start up at boot time. You can determine whether the <span class="application"><strong>NetworkManager</strong></span> daemon is running by entering this command as root:
+ </div><pre class="screen">~]# <code class="command">service NetworkManager status</code>
+NetworkManager (pid 1527) is running...
+</pre><div class="para">
+ The <code class="command">service</code> command will report <code class="computeroutput">NetworkManager is stopped</code> if the <span class="application"><strong>NetworkManager</strong></span> service is not running. To start it for the current session:
+ </div><pre class="screen">~]# <code class="command">service NetworkManager start</code>
+</pre><div class="para">
+ Run the <code class="command">chkconfig</code> command to ensure that <span class="application"><strong>NetworkManager</strong></span> starts up every time the system boots:
+ </div><pre class="screen">~]# <code class="command">chkconfig NetworkManager on</code>
+</pre><div class="para">
+ For more information on starting, stopping and managing services and runlevels, refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div></div><div class="section" title="5.2. Interacting with NetworkManager" id="sec-Interacting_with_NetworkManager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Interacting_with_NetworkManager">5.2. Interacting with NetworkManager</h2></div></div></div><div class="para">
+ Users do not interact with the <span class="application"><strong>NetworkManager</strong></span> system service directly. Instead, you can perform network configuration tasks via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet. The applet has multiple states that serve as visual indicators for the type of connection you are currently using. Hover the pointer over the applet icon for tooltip information on the current connection state.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-All_applet_states.png" align="middle" /><div class="caption"><div class="para">
+ NetworkManager applet states
+ </div></div></div><div class="para">
+ If you do not see the <span class="application"><strong>NetworkManager</strong></span> applet in the GNOME panel, and assuming that the <span class="application"><strong>NetworkManager</strong></span> package is installed on your system, you can start the applet by running the following command as a normal user (not root):
+ </div><pre class="screen">~]$ <code class="command">nm-applet &</code>
+</pre><div class="para">
+ After running this command, the applet appears in your Notification Area. You can ensure that the applet runs each time you log in by clicking <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Startup Applications</strong></span> to open the <span class="guilabel"><strong>Startup Applications Preferences</strong></span> window. Then, select the <span class="guilabel"><strong>Startup Programs</strong></span> tab and check the box next to <span class="application"><strong>NetworkManager</strong></span>.
+ </div><div class="section" title="5.2.1. Connecting to a Network" id="sec-Connecting_to_a_Network"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Connecting_to_a_Network">5.2.1. Connecting to a Network</h3></div></div></div><div class="para">
+ When you left-click on the applet icon, you are presented with:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ a list of categorized networks you are currently connected to (such as <span class="guilabel"><strong>Wired</strong></span> and <span class="guilabel"><strong>Wireless</strong></span>);
+ </div></li><li class="listitem"><div class="para">
+ a list of all <span class="guilabel"><strong>Available Networks</strong></span> <span class="application"><strong>NetworkManager</strong></span> has detected;
+ </div></li><li class="listitem"><div class="para">
+ options for connecting to any configured Virtual Private Networks (VPNs); and,
+ </div></li><li class="listitem"><div class="para">
+ options for connecting to hidden or new wireless networks.
+ </div></li></ul></div><div class="para">
+ When many networks are available (as when there are many wireless access points in the area), the <span class="guilabel"><strong>More networks</strong></span> expandable menu entry appears. If you are connected to a network, its name is presented in bold typeface under its network type, such as <span class="guilabel"><strong>Wired</strong></span> or <span class="guilabel"><strong>Wireless</strong></span>.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-left-click_menu.png" align="middle" /><div class="caption"><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> applet's left-click menu, showing all available and connected-to networks
+ </div></div></div></div><div class="section" title="5.2.2. Configuring New and Editing Existing Connections" id="sec-Configuring_New_and_Editing_Existing_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_New_and_Editing_Existing_Connections">5.2.2. Configuring New and Editing Existing Connections</h3></div></div></div><div class="para">
+ Next, right-click on the <span class="application"><strong>NetworkManager</strong></span> applet to open its context menu, which is the main point of entry for interacting with <span class="application"><strong>NetworkManager</strong></span> to configure connections.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-right-click_menu.png" align="middle" /><div class="caption"><div class="para">
+ The NetworkManager applet's context menu
+ </div></div></div><div class="para">
+ Ensure that the <span class="guilabel"><strong>Enable Networking</strong></span> box is checked. if the system has detected a wireless card, then you will also see an <span class="guilabel"><strong>Enable Wireless</strong></span> menu option. Check the <span class="guilabel"><strong>Enable Wireless</strong></span> checkbox as well. <span class="application"><strong>NetworkManager</strong></span> notifies you of network connection status changes if you check the <span class="guilabel"><strong>Enable Notifications</strong></span> box. Clicking the <span class="guilabel"><strong>Connection Information</strong></span> entry presents an informative <span class="guilabel"><strong>Connection Information</strong></span> window that lists the connection type and interface, your IP address and routing details, and so on. Useful network information is thus always two clicks away.
+ </div><div class="para">
+ Finally, clicking on <span class="guilabel"><strong>Edit Connections</strong></span> opens the <span class="guilabel"><strong>Network Connections</strong></span> window, from where you can perform most of your network configuration tasks. Note that this window can also be opened by running, as a normal user:
+ </div><pre class="screen">~]$ <code class="command">nm-connection-editor &</code>
+</pre><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Network_Connections.png" align="middle" width="444" /><div class="caption"><div class="para">
+ Configure networks using the Network Connections window
+ </div></div></div></div><div class="section" title="5.2.3. Connecting to a Network Automatically" id="sec-Connecting_to_a_Network_Automatically"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Connecting_to_a_Network_Automatically">5.2.3. Connecting to a Network Automatically</h3></div></div></div><div class="para">
+ For any connection type you add or configure, you can choose whether you want <span class="application"><strong>NetworkManager</strong></span> to try to connect to that network automatically when it is available.
+ </div><div class="procedure" title="Procedure 5.1. Configuring NetworkManager to Connect to a Network Automatically When Detected" id="procedure-Configuring_NetworkManager_to_Connect_to_a_Network_Automatically_When_Detected"><h6>Procedure 5.1. Configuring NetworkManager to Connect to a Network Automatically When Detected</h6><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Right-click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area and click <span class="guilabel"><strong>Edit Connections</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> window appears.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Select the tab for the type of network connection you want to configure.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Select the specific connection that you want to configure and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ Check <span class="guilabel"><strong>Connect automatically</strong></span> to cause <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the connection whenever <span class="application"><strong>NetworkManager</strong></span> detects that it is available. Uncheck the checkbox if you do not want <span class="application"><strong>NetworkManager</strong></span> to connect automatically. If the box is unchecked, you will have to select that connection manually in the <span class="application"><strong>NetworkManager</strong></span> applet's left-click menu to cause it to connect.
+ </div></li></ol></div></div><div class="section" title="5.2.4. User and System Connections" id="sec-User_and_System_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-User_and_System_Connections">5.2.4. User and System Connections</h3></div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> connections are always either <span class="emphasis"><em>user connections</em></span> or <span class="emphasis"><em>system connections</em></span>. Depending on the system-specific policy that the administrator has configured, users may need root privileges to create and modify system connections. <span class="application"><strong>NetworkManager</strong></span>'s default policy enables users to create and modify user connections, but requires them to have root privileges to add, modify or delete system connections.
+ </div><div class="para">
+ User connections are so-called because they are specific to the user who creates them. In contrast to system connections, whose configurations are stored under the <code class="filename">/etc/sysconfig/network-scripts/</code> directory (mainly in <code class="filename">ifcfg-<em class="replaceable"><code><network_type></code></em> </code> interface configuration files), user connection settings are stored in the GConf configuration database and the GNOME keyring, and are only available during login sessions for the user who created them. Thus, logging out of the desktop session causes user-specific connections to become unavailable.
+ </div><div class="note" title="Tip: Increase security by making VPN connections user-specific" id="note-Tip-Increase_security_by_making_VPN_connections_user-specific"><div class="admonition_header"><h2>Tip: Increase security by making VPN connections user-specific</h2></div><div class="admonition"><div class="para">
+ Because <span class="application"><strong>NetworkManager</strong></span> uses the GConf and GNOME keyring applications to store user connection settings, and because these settings are specific to your desktop session, it is highly recommended to configure your personal VPN connections as user connections. If you do so, other non-root users on the system cannot view or access these connections in any way.
+ </div></div></div><div class="para">
+ System connections, on the other hand, become available at boot time and can be used by other users on the system without first logging in to a desktop session.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> can quickly and conveniently convert user to system connections and vice versa. Converting a user connection to a system connection causes <span class="application"><strong>NetworkManager</strong></span> to create the relevant interface configuration files under the <code class="filename">/etc/sysconfig/network-scripts/</code> directory, and to delete the GConf settings from the user's session. Conversely, converting a system to a user-specific connection causes <span class="application"><strong>NetworkManager</strong></span> to remove the system-wide configuration files and create the corresponding GConf/GNOME keyring settings.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Available_to_all_users.png" align="middle" /><div class="caption"><div class="para">
+ The <span class="guilabel"><strong>Available to all users</strong></span> checkbox controls whether connections are user-specific or system-wide
+ </div></div></div><div class="procedure" title="Procedure 5.2. Changing a Connection to be User-Specific instead of System-Wide, or Vice-Versa" id="procedure-Changing_a_Connection_to_be_User-Specific_instead_of_System-Wide_or_Vice-Versa"><h6>Procedure 5.2. Changing a Connection to be User-Specific instead of System-Wide, or Vice-Versa</h6><div class="note" title="Depending on the system's policy, root privileges may be required" id="note-Depending_on_the_systems_policy_root_privileges_may_be_required"><div class="admonition_header"><h2>Depending on the system's policy, root privileges may be required</h2></div><div class="admonition"><div class="para">
+ As discussed, you may need root privileges on the system in order to change whether a connection is user-specific or system-wide.
+ </div></div></div><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Right-click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area and click <span class="guilabel"><strong>Edit Connections</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> window appears.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Select the tab for the type of network connection you want to configure.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Select the specific connection that you want to configure and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ Check the <span class="guilabel"><strong>Available to all users</strong></span> checkbox to ask <span class="application"><strong>NetworkManager</strong></span> to make the connection a system-wide connection. Depending on system policy, you may then be prompted for the root password by the <span class="application"><strong>PolicyKit</strong></span> application. If so, enter the root password to finalize the change.
+ </div><div class="para">
+ Conversely, uncheck the <span class="guilabel"><strong>Available to all users</strong></span> checkbox to make the connection user-specific.
+ </div></li></ol></div></div></div><div class="section" title="5.3. Configuring Connection Settings" id="sec-Configuring_Connection_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Configuring_Connection_Settings">5.3. Configuring Connection Settings</h2></div></div></div><div class="section" title="5.3.1. Configuring IPv4 Settings" id="sec-Configuring_IPv4_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_IPv4_Settings">5.3.1. Configuring IPv4 Settings</h3></div></div></div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-IPv4_Settings.png" align="middle" /><div class="caption"><div class="para">
+ Editing the IPv4 Settings Tab
+ </div></div></div><div class="para">
+ The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab allows you to configure the method by which you connect to the Internet and enter IP address, route, and DNS information as required. The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab is available when you create and modify one of the following connection types: wired, wireless, mobile broadband, VPN or DSL.
+ </div><div class="para">
+ If you are using DHCP to obtain a dynamic IP address from a DHCP server, you can simply set <span class="guilabel"><strong>Method</strong></span> to <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span>.
+ </div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)" id="ch-Dynamic_Host_Configuration_Protocol_DHCP" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Dynamic Host Configuration Protocol (DHCP)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-dhcp-why">6.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-server">6.2. Configuring a DHCP Server</a></span></dt><dt><span class="section"><a href="#s1-dhcp-configuring-client">6.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="#sect-Configuring_a_Multihomed_DHCP_Server">6.4. Configuring a Multihomed DHCP Server</a></span></dt><dt><span class="section"><a href="#s1-dhcp_for_ipv6_dhcpv6">6.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="#s1-dhcp-additional-resources">6.6. Additional Resources</a></span></d
t></dl></div><a id="id738823" class="indexterm"></a><a id="id688732" class="indexterm"></a><div class="para">
+ Dynamic Host Configuration Protocol (<acronym class="acronym">DHCP</acronym>) is a network protocol that automatically assigns TCP/IP information to client machines. Each DHCP client connects to the centrally located DHCP server, which returns that client's network configuration (including the IP address, gateway, and DNS servers).
+ </div><div class="section" title="6.1. Why Use DHCP?" id="s1-dhcp-why"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-dhcp-why">6.1. Why Use DHCP?</h2></div></div></div><a id="id830939" class="indexterm"></a><div class="para">
+ DHCP is useful for automatic configuration of client network interfaces. When configuring the client system, the administrator chooses DHCP instead of specifying an IP address, netmask, gateway, or DNS servers. The client retrieves this information from the DHCP server. DHCP is also useful if an administrator wants to change the IP addresses of a large number of systems. Instead of reconfiguring all the systems, he can just edit one DHCP configuration file on the server for the new set of IP addresses. If the DNS servers for an organization changes, the changes are made on the DHCP server, not on the DHCP clients. When the administrator restarts the network or reboots the clients, the changes will go into effect.
+ </div><div class="para">
+ If an organization has a functional DHCP server properly connected to a network, laptops and other mobile computer users can move these devices from office to office.
+ </div></div><div class="section" title="6.2. Configuring a DHCP Server" id="s1-dhcp-configuring-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-dhcp-configuring-server">6.2. Configuring a DHCP Server</h2></div></div></div><a id="id569272" class="indexterm"></a><div class="para">
+ The <code class="filename">dhcp</code> package contains an ISC DHCP server. First, install the package as the superuser:
+ </div><pre class="screen">~]# <code class="command">yum install dhcp</code>
+</pre><div class="para">
+ Installing the <code class="filename">dhcp</code> package creates a file, <code class="filename">/etc/dhcp/dhcpd.conf</code>, which is merely an empty configuration file:
+ </div><pre class="screen">~]# <code class="command">cat /etc/dhcp/dhcpd.conf</code>
+#
+# DHCP Server Configuration file.
+# see /usr/share/doc/dhcp*/dhcpd.conf.sample</pre><div class="para">
+ The sample configuration file can be found at <code class="filename">/usr/share/doc/dhcp-<<em class="replaceable"><code>version</code></em>>/dhcpd.conf.sample</code>. You should use this file to help you configure <code class="filename">/etc/dhcp/dhcpd.conf</code>, which is explained in detail below.
+ </div><div class="para">
+ DHCP also uses the file <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> to store the client lease database. Refer to <a class="xref" href="#lease-database" title="6.2.2. Lease Database">Section 6.2.2, “Lease Database”</a> for more information.
+ </div><div class="section" title="6.2.1. Configuration File" id="config-file"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="config-file">6.2.1. Configuration File</h3></div></div></div><a id="id774790" class="indexterm"></a><a id="id774804" class="indexterm"></a><div class="para">
+ The first step in configuring a DHCP server is to create the configuration file that stores the network information for the clients. Use this file to declare options and global options for client systems.
+ </div><div class="para">
+ The configuration file can contain extra tabs or blank lines for easier formatting. Keywords are case-insensitive and lines beginning with a hash sign (#) are considered comments.
+ </div><div class="para">
+ There are two types of statements in the configuration file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Parameters — State how to perform a task, whether to perform a task, or what network configuration options to send to the client.
+ </div></li><li class="listitem"><div class="para">
+ Declarations — Describe the topology of the network, describe the clients, provide addresses for the clients, or apply a group of parameters to a group of declarations.
+ </div></li></ul></div><a id="id835127" class="indexterm"></a><div class="para">
+ The parameters that start with the keyword option are reffered to as <em class="firstterm">options</em>. These options control DHCP options; whereas, parameters configure values that are not optional or control how the DHCP server behaves.
+ </div><a id="id668507" class="indexterm"></a><div class="para">
+ Parameters (including options) declared before a section enclosed in curly brackets ({ }) are considered global parameters. Global parameters apply to all the sections below it.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If the configuration file is changed, the changes do not take effect until the DHCP daemon is restarted with the command <code class="command">service dhcpd restart</code>.
+ </div></div></div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ Instead of changing a DHCP configuration file and restarting the service each time, using the <code class="command">omshell</code> command provides an interactive way to connect to, query, and change the configuration of a DHCP server. By using <code class="command">omshell</code>, all changes can be made while the server is running. For more information on <code class="command">omshell</code>, refer to the <code class="command">omshell</code> man page.
+ </div></div></div><div class="para">
+ In <a class="xref" href="#subnet" title="Example 6.1. Subnet Declaration">Example 6.1, “Subnet Declaration”</a>, the <code class="filename">routers</code>, <code class="filename">subnet-mask</code>, <code class="filename">domain-search</code>, <code class="filename">domain-name-servers</code>, and <code class="filename">time-offset</code> options are used for any <code class="filename">host</code> statements declared below it.
+ </div><a id="id806998" class="indexterm"></a><div class="para">
+ Additionally, a <code class="filename">subnet</code> can be declared, a <code class="filename">subnet</code> declaration must be included for every subnet in the network. If it is not, the DHCP server fails to start.
+ </div><div class="para">
+ In this example, there are global options for every DHCP client in the subnet and a <code class="filename">range</code> declared. Clients are assigned an IP address within the <code class="filename">range</code>.
+ </div><div class="example" title="Example 6.1. Subnet Declaration" id="subnet"><h6>Example 6.1. Subnet Declaration</h6><div class="example-contents"><pre class="screen">
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ range 192.168.1.10 192.168.1.100;
+}
+</pre></div></div><br class="example-break" /><div class="para">
+ To configure a DHCP server that leases a dynamic IP address to a system within a subnet, modify <a class="xref" href="#dynamic-ip" title="Example 6.2. Range Parameter">Example 6.2, “Range Parameter”</a> with your values. It declares a default lease time, maximum lease time, and network configuration values for the clients. This example assigns IP addresses in the <code class="filename">range</code> 192.168.1.10 and 192.168.1.100 to client systems.
+ </div><div class="example" title="Example 6.2. Range Parameter" id="dynamic-ip"><h6>Example 6.2. Range Parameter</h6><div class="example-contents"><pre class="screen">
+default-lease-time 600;
+max-lease-time 7200;
+option subnet-mask 255.255.255.0;
+option broadcast-address 192.168.1.255;
+option routers 192.168.1.254;
+option domain-name-servers 192.168.1.1, 192.168.1.2;
+option domain-search "example.com";
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ range 192.168.1.10 192.168.1.100;
+}
+</pre></div></div><br class="example-break" /><div class="para">
+ To assign an IP address to a client based on the MAC address of the network interface card, use the <code class="filename">hardware ethernet</code> parameter within a <code class="filename">host</code> declaration. As demonstrated in <a class="xref" href="#static-ip" title="Example 6.3. Static IP Address using DHCP">Example 6.3, “Static IP Address using DHCP”</a>, the <code class="filename">host apex</code> declaration specifies that the network interface card with the MAC address 00:A0:78:8E:9E:AA always receives the IP address 192.168.1.4.
+ </div><div class="para">
+ Note that the optional parameter <code class="filename">host-name</code> can also be used to assign a host name to the client.
+ </div><div class="example" title="Example 6.3. Static IP Address using DHCP" id="static-ip"><h6>Example 6.3. Static IP Address using DHCP</h6><div class="example-contents"><pre class="screen">
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+</pre></div></div><br class="example-break" /><a id="id727394" class="indexterm"></a><div class="para">
+ All subnets that share the same physical network should be declared within a <code class="filename">shared-network</code> declaration as shown in <a class="xref" href="#shared-network" title="Example 6.4. Shared-network Declaration">Example 6.4, “Shared-network Declaration”</a>. Parameters within the <code class="filename">shared-network</code>, but outside the enclosed <code class="filename">subnet</code> declarations, are considered to be global parameters. The name of the <code class="filename">shared-network</code> must be a descriptive title for the network, such as using the title 'test-lab' to describe all the subnets in a test lab environment.
+ </div><div class="example" title="Example 6.4. Shared-network Declaration" id="shared-network"><h6>Example 6.4. Shared-network Declaration</h6><div class="example-contents"><pre class="screen">
+shared-network name {
+ option domain-search "test.redhat.com";
+ option domain-name-servers ns1.redhat.com, ns2.redhat.com;
+ option routers 192.168.0.254;
+ more parameters for EXAMPLE shared-network
+ subnet 192.168.1.0 netmask 255.255.252.0 {
+ parameters for subnet
+ range 192.168.1.1 192.168.1.254;
+ }
+ subnet 192.168.2.0 netmask 255.255.252.0 {
+ parameters for subnet
+ range 192.168.2.1 192.168.2.254;
+ }
+}
+</pre></div></div><br class="example-break" /><a id="id719533" class="indexterm"></a><div class="para">
+ As demonstrated in <a class="xref" href="#group" title="Example 6.5. Group Declaration">Example 6.5, “Group Declaration”</a>, the <code class="filename">group</code> declaration is used to apply global parameters to a group of declarations. For example, shared networks, subnets, and hosts can be grouped.
+ </div><div class="example" title="Example 6.5. Group Declaration" id="group"><h6>Example 6.5. Group Declaration</h6><div class="example-contents"><pre class="screen">
+group {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+ }
+ host raleigh {
+ option host-name "raleigh.example.com";
+ hardware ethernet 00:A1:DD:74:C3:F2;
+ fixed-address 192.168.1.6;
+ }
+}
+</pre></div></div><br class="example-break" /><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ The sample configuration file provided can be used as a starting point and custom configuration options can be added to it. To copy it to the proper location, use the following command:
+ </div><pre class="screen">
+<code class="command">cp /usr/share/doc/dhcp-<em class="replaceable"><code><version-number></code></em>/dhcpd.conf.sample /etc/dhcp/dhcpd.conf</code>
+</pre><div class="para">
+ ... where <em class="replaceable"><code><version-number></code></em> is the DHCP version number.
+ </div></div></div><div class="para">
+ For a complete list of option statements and what they do, refer to the <code class="filename">dhcp-options</code> man page.
+ </div></div><div class="section" title="6.2.2. Lease Database" id="lease-database"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="lease-database">6.2.2. Lease Database</h3></div></div></div><div class="para">
+ On the DHCP server, the file <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> stores the DHCP client lease database. Do not change this file. DHCP lease information for each recently assigned IP address is automatically stored in the lease database. The information includes the length of the lease, to whom the IP address has been assigned, the start and end dates for the lease, and the MAC address of the network interface card that was used to retrieve the lease.
+ </div><div class="para">
+ All times in the lease database are in Coordinated Universal Time (UTC), not local time.
+ </div><div class="para">
+ The lease database is recreated from time to time so that it is not too large. First, all known leases are saved in a temporary lease database. The <code class="filename">dhcpd.leases</code> file is renamed <code class="filename">dhcpd.leases~</code> and the temporary lease database is written to <code class="filename">dhcpd.leases</code>.
+ </div><div class="para">
+ The DHCP daemon could be killed or the system could crash after the lease database has been renamed to the backup file but before the new file has been written. If this happens, the <code class="filename">dhcpd.leases</code> file does not exist, but it is required to start the service. Do not create a new lease file. If you do, all old leases are lost which causes many problems. The correct solution is to rename the <code class="filename">dhcpd.leases~</code> backup file to <code class="filename">dhcpd.leases</code> and then start the daemon.
+ </div></div><div class="section" title="6.2.3. Starting and Stopping the Server"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id634664">6.2.3. Starting and Stopping the Server</h3></div></div></div><a id="id634670" class="indexterm"></a><a id="id634684" class="indexterm"></a><a id="id566053" class="indexterm"></a><a id="id566070" class="indexterm"></a><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When the DHCP server is started for the first time, it fails unless the <code class="filename">dhcpd.leases</code> file exists. Use the command <code class="command">touch /var/lib/dhcpd/dhcpd.leases</code> to create the file if it does not exist.
+ </div><div class="para">
+ If the same server is also running BIND as a DNS server, this step is not necessary, as starting the <code class="command">named</code> service automatically checks for a <code class="filename">dhcpd.leases</code> file.
+ </div></div></div><div class="para">
+ To start the DHCP service, use the command <code class="command">/sbin/service dhcpd start</code>. To stop the DHCP server, use the command <code class="command">/sbin/service dhcpd stop</code>.
+ </div><div class="para">
+ By default, the DHCP service does not start at boot time. To configure the daemon to start automatically at boot time, refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div><a id="id1710359" class="indexterm"></a><a id="id1710372" class="indexterm"></a><div class="para">
+ If more than one network interface is attached to the system, but the DHCP server should only be started on one of the interfaces, configure the DHCP server to start only on that device. In <code class="filename">/etc/sysconfig/dhcpd</code>, add the name of the interface to the list of <code class="command">DHCPDARGS</code>:
+ </div><pre class="screen">
+# Command line options here
+DHCPDARGS=eth0
+</pre><div class="para">
+ This is useful for a firewall machine with two network cards. One network card can be configured as a DHCP client to retrieve an IP address to the Internet. The other network card can be used as a DHCP server for the internal network behind the firewall. Specifying only the network card connected to the internal network makes the system more secure because users can not connect to the daemon via the Internet.
+ </div><div class="para">
+ Other command line options that can be specified in <code class="filename">/etc/sysconfig/dhcpd</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-p <em class="replaceable"><code><portnum></code></em> </code> — Specifies the UDP port number on which <code class="command">dhcpd</code> should listen. The default is port 67. The DHCP server transmits responses to the DHCP clients at a port number one greater than the UDP port specified. For example, if the default port 67 is used, the server listens on port 67 for requests and responses to the client on port 68. If a port is specified here and the DHCP relay agent is used, the same port on which the DHCP relay agent should listen must be specified. Refer to <a class="xref" href="#dhcp-relay-agent" title="6.2.4. DHCP Relay Agent">Section 6.2.4, “DHCP Relay Agent”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-f</code> — Runs the daemon as a foreground process. This is mostly used for debugging.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-d</code> — Logs the DHCP server daemon to the standard error descriptor. This is mostly used for debugging. If this is not specified, the log is written to <code class="filename">/var/log/messages</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-cf <em class="replaceable"><code><filename></code></em> </code> — Specifies the location of the configuration file. The default location is <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-lf <em class="replaceable"><code><filename></code></em> </code> — Specifies the location of the lease database file. If a lease database file already exists, it is very important that the same file be used every time the DHCP server is started. It is strongly recommended that this option only be used for debugging purposes on non-production machines. The default location is <code class="filename">/var/lib/dhcpd/dhcpd.leases</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-q</code> — Do not print the entire copyright message when starting the daemon.
+ </div></li></ul></div></div><div class="section" title="6.2.4. DHCP Relay Agent" id="dhcp-relay-agent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="dhcp-relay-agent">6.2.4. DHCP Relay Agent</h3></div></div></div><a id="id751060" class="indexterm"></a><a id="id751074" class="indexterm"></a><a id="id834165" class="indexterm"></a><div class="para">
+ The DHCP Relay Agent (<code class="command">dhcrelay</code>) allows for the relay of DHCP and BOOTP requests from a subnet with no DHCP server on it to one or more DHCP servers on other subnets.
+ </div><div class="para">
+ When a DHCP client requests information, the DHCP Relay Agent forwards the request to the list of DHCP servers specified when the DHCP Relay Agent is started. When a DHCP server returns a reply, the reply is broadcast or unicast on the network that sent the original request.
+ </div><div class="para">
+ The DHCP Relay Agent listens for DHCP requests on all interfaces unless the interfaces are specified in <code class="filename">/etc/sysconfig/dhcrelay</code> with the <code class="computeroutput">INTERFACES</code> directive.
+ </div><div class="para">
+ To start the DHCP Relay Agent, use the command <code class="command">service dhcrelay start</code>.
+ </div></div></div><div class="section" title="6.3. Configuring a DHCP Client" id="s1-dhcp-configuring-client"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-dhcp-configuring-client">6.3. Configuring a DHCP Client</h2></div></div></div><a id="id971315" class="indexterm"></a><a id="id729179" class="indexterm"></a><div class="para">
+ To configure a DHCP client manually, modify the <code class="filename">/etc/sysconfig/network</code> file to enable networking and the configuration file for each network device in the <code class="filename">/etc/sysconfig/network-scripts</code> directory. In this directory, each device should have a configuration file named <code class="filename">ifcfg-eth0</code>, where <code class="filename">eth0</code> is the network device name.
+ </div><div class="para">
+ The <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code> file should contain the following lines:
+ </div><pre class="screen">
+DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes
+</pre><div class="para">
+ A configuration file is needed for each device to be configured to use DHCP.
+ </div><div class="para">
+ Other options for the network script includes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">DHCP_HOSTNAME</code> — Only use this option if the DHCP server requires the client to specify a hostname before receiving an IP address. (The DHCP server daemon in Fedora does not support this feature.)
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">PEERDNS=<em class="replaceable"><code><answer></code></em> </code>, where <code class="literal"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Modify <code class="filename">/etc/resolv.conf</code> with information from the server. If using DHCP, then <code class="command">yes</code> is the default.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Do not modify <code class="filename">/etc/resolv.conf</code>.
+ </div></li></ul></div></li></ul></div><div class="para">
+ If you prefer using a graphical interface, refer to <a class="xref" href="#ch-Network_Configuration" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a> for instructions on using the <span class="application"><strong>Network Administration Tool</strong></span> to configure a network interface to use DHCP.
+ </div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ For advanced configurations of client DHCP options such as protocol timing, lease requirements and requests, dynamic DNS support, aliases, as well as a wide variety of values to override, prepend, or append to client-side configurations, refer to the <code class="command">dhclient</code> and <code class="command">dhclient.conf</code> man pages.
+ </div></div></div></div><div class="section" title="6.4. Configuring a Multihomed DHCP Server" id="sect-Configuring_a_Multihomed_DHCP_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Configuring_a_Multihomed_DHCP_Server">6.4. Configuring a Multihomed DHCP Server</h2></div></div></div><a id="id696889" class="indexterm"></a><div class="para">
+ A multihomed DHCP server serves multiple networks, that is, multiple subnets. The examples in these sections detail how to configure a DHCP server to serve multiple networks, select which network interfaces to listen on, and how to define network settings for systems that move networks.
+ </div><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/sysconfig/dhcpd</code> and <code class="filename">/etc/dhcp/dhcpd.conf</code> files.
+ </div><div class="para">
+ The DHCP daemon listens on all network interfaces unless otherwise specified. Use the <code class="filename">/etc/sysconfig/dhcpd</code> file to specify which network interfaces the DHCP daemon listens on. The following <code class="filename">/etc/sysconfig/dhcpd</code> example specifies that the DHCP daemon listens on the <code class="filename">eth0</code> and <code class="filename">eth1</code> interfaces:
+ </div><pre class="screen">
+DHCPDARGS="eth0 eth1";
+</pre><div class="para">
+ If a system has three network interfaces cards -- <code class="filename">eth0</code>, <code class="filename">eth1</code>, and <code class="filename">eth2</code> -- and it is only desired that the DHCP daemon listens on <code class="filename">eth0</code>, then only specify <code class="computeroutput">eth0</code> in <code class="filename">/etc/sysconfig/dhcpd</code>:
+ </div><pre class="screen">
+DHCPDARGS="eth0";
+</pre><div class="para">
+ The following is a basic <code class="filename">/etc/dhcp/dhcpd.conf</code> file, for a server that has two network interfaces, <code class="filename">eth0</code> in a 10.0.0.0/24 network, and <code class="filename">eth1</code> in a 172.16.0.0/24 network. Multiple <code class="computeroutput">subnet</code> declarations allow different settings to be defined for multiple networks:
+ </div><pre class="screen">
+default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}
+</pre><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="computeroutput">subnet <em class="replaceable"><code>10.0.0.0</code></em> netmask <em class="replaceable"><code>255.255.255.0</code></em>;</code> </span></dt><dd><div class="para">
+ A <code class="computeroutput">subnet</code> declaration is required for every network your DHCP server is serving. Multiple subnets require multiple <code class="computeroutput">subnet</code> declarations. If the DHCP server does not have a network interface in a range of a <code class="computeroutput">subnet</code> declaration, the DHCP server does not serve that network.
+ </div><div class="para">
+ If there is only one <code class="computeroutput">subnet</code> declaration, and no network interfaces are in the range of that subnet, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="screen">
+dhcpd: No subnet declaration for eth0 (0.0.0.0).
+dhcpd: ** Ignoring requests on eth0. If this is not what
+dhcpd: you want, please write a subnet declaration
+dhcpd: in your dhcpd.conf file for the network segment
+dhcpd: to which interface eth1 is attached. **
+dhcpd:
+dhcpd:
+dhcpd: Not configured to listen on any interfaces!
+</pre></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">option subnet-mask <em class="replaceable"><code>255.255.255.0</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">option subnet-mask</code> option defines a subnet mask, and overrides the <code class="computeroutput">netmask</code> value in the <code class="computeroutput">subnet</code> declaration. In simple cases, the subnet and netmask values are the same.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">option routers <em class="replaceable"><code>10.0.0.1</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">option routers</code> option defines the default gateway for the subnet. This is required for systems to reach internal networks on a different subnet, as well as external networks.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">range <em class="replaceable"><code>10.0.0.5</code></em> <em class="replaceable"><code>10.0.0.15</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">range</code> option specifies the pool of available IP addresses. Systems are assigned an address from the range of specified IP addresses.
+ </div></dd></dl></div><div class="para">
+ For further information, refer to the <code class="computeroutput">dhcpd.conf(5)</code> man page.
+ </div><div class="warning" title="Alias Interfaces"><div class="admonition_header"><h2>Alias Interfaces</h2></div><div class="admonition"><div class="para">
+ Alias interfaces are not supported by DHCP. If an alias interface is the only interface, in the only subnet specified in <code class="filename">/etc/dhcp/dhcpd.conf</code>, the DHCP daemon fails to start.
+ </div></div></div><div class="section" title="6.4.1. Host Configuration" id="sect-dns_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-dns_Host_Configuration">6.4.1. Host Configuration</h3></div></div></div><a id="id453484" class="indexterm"></a><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/sysconfig/dhcpd</code> and <code class="filename">/etc/dhcp/dhcpd.conf</code> files.
+ </div><div class="formalpara"><h5 class="formalpara" id="id453509">Configuring a single system for multiple networks</h5>
+ The following <code class="filename">/etc/dhcp/dhcpd.conf</code> example creates two subnets, and configures an IP address for the same system, depending on which network it connects to:
+ </div><pre class="screen">
+default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}
+host example0 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 10.0.0.20;
+}
+host example1 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 172.16.0.20;
+}
+</pre><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="computeroutput">host <em class="replaceable"><code>example0</code></em> </code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">host</code> declaration defines specific parameters for a single system, such as an IP address. To configure specific parameters for multiple hosts, use multiple <code class="computeroutput">host</code> declarations.
+ </div><div class="para">
+ Most DHCP clients ignore the name in <code class="computeroutput">host</code> declarations, and as such, this name can anything, as long as it is unique to other <code class="computeroutput">host</code> declarations. To configure the same system for multiple networks, use a different name for each <code class="computeroutput">host</code> declaration, otherwise the DHCP daemon fails to start. Systems are identified by the <code class="computeroutput">hardware ethernet</code> option, not the name in the <code class="computeroutput">host</code> declaration.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">hardware ethernet <em class="replaceable"><code>00:1A:6B:6A:2E:0B</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">hardware ethernet</code> option identifies the system. To find this address, run the <code class="command">ip link</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">fixed-address <em class="replaceable"><code>10.0.0.20</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">fixed-address</code> option assigns a valid IP address to the system specified by the <code class="computeroutput">hardware ethernet</code> option. This address must be outside the IP address pool specified with the <code class="computeroutput">range</code> option.
+ </div></dd></dl></div><div class="para">
+ If <code class="computeroutput">option</code> statements do not end with a semicolon, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="screen">
+/etc/dhcp/dhcpd.conf line 20: semicolon expected.
+dhcpd: }
+dhcpd: ^
+dhcpd: /etc/dhcp/dhcpd.conf line 38: unexpected end of file
+dhcpd:
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting
+</pre><div class="formalpara"><h5 class="formalpara" id="id469361">Configuring systems with multiple network interfaces</h5>
+ The following <code class="computeroutput">host</code> declarations configure a single system, that has multiple network interfaces, so that each interface receives the same IP address. This configuration will not work if both network interfaces are connected to the same network at the same time:
+ </div><pre class="screen">
+host interface0 {
+ hardware ethernet 00:1a:6b:6a:2e:0b;
+ fixed-address 10.0.0.18;
+}
+host interface1 {
+ hardware ethernet 00:1A:6B:6A:27:3A;
+ fixed-address 10.0.0.18;
+}
+</pre><div class="para">
+ For this example, <code class="computeroutput">interface0</code> is the first network interface, and <code class="computeroutput">interface1</code> is the second interface. The different <code class="computeroutput">hardware ethernet</code> options identify each interface.
+ </div><div class="para">
+ If such a system connects to another network, add more <code class="computeroutput">host</code> declarations, remembering to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ assign a valid <code class="computeroutput">fixed-address</code> for the network the host is connecting to.
+ </div></li><li class="listitem"><div class="para">
+ make the name in the <code class="computeroutput">host</code> declaration unique.
+ </div></li></ul></div><div class="para">
+ When a name given in a <code class="computeroutput">host</code> declaration is not unique, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="screen">
+dhcpd: /etc/dhcp/dhcpd.conf line 31: host interface0: already exists
+dhcpd: }
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting
+</pre><div class="para">
+ This error was caused by having multiple <code class="computeroutput">host interface0</code> declarations defined in <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></div></div><div class="section" title="6.5. DHCP for IPv6 (DHCPv6)" id="s1-dhcp_for_ipv6_dhcpv6"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-dhcp_for_ipv6_dhcpv6">6.5. DHCP for IPv6 (DHCPv6)</h2></div></div></div><a id="id832402" class="indexterm"></a><a id="id732210" class="indexterm"></a><div class="para">
+ The ISC DHCP includes support for IPv6 (DHCPv6) since the 4.x release with a DHCPv6 server, client and relay agent functionality. The server, client and relay agents support both IPv4 and IPv6. However, the client and the server can only manage one protocol at a time — for dual support they must be started separately for IPv4 and IPv6.
+ </div><div class="para">
+ The DHCPv6 server configuration file can be found at <code class="filename">/etc/dhcp/dhcpd6.conf</code>.
+ </div><div class="para">
+ The sample server configuration file can be found at <code class="filename">/usr/share/doc/dhcp-<version>/dhcpd6.conf.sample</code>.
+ </div><div class="para">
+ To start the DHCPv6 service, use the command <code class="command">/sbin/service dhcpd6 start</code>.
+ </div><div class="para">
+ A simple DHCPv6 server configuration file can look like this:
+ </div><pre class="screen">
+subnet6 2001:db8:0:1::/64 {
+ range6 2001:db8:0:1::129 2001:db8:0:1::254;
+ option dhcp6.name-servers fec0:0:0:1::1;
+ option dhcp6.domain-search "domain.example";
+}
+</pre></div><div class="section" title="6.6. Additional Resources" id="s1-dhcp-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-dhcp-additional-resources">6.6. Additional Resources</h2></div></div></div><a id="id695736" class="indexterm"></a><div class="para">
+ For additional information, refer to <em class="citetitle">The DHCP Handbook; Ralph Droms and Ted Lemon; 2003</em> or the following resources.
+ </div><div class="section" title="6.6.1. Installed Documentation" id="s2-dhcp-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-dhcp-installed-docs">6.6.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">dhcpd</code> man page — Describes how the DHCP daemon works.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.conf</code> man page — Explains how to configure the DHCP configuration file; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.leases</code> man page — Describes a persistent database of leases.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcp-options</code> man page — Explains the syntax for declaring DHCP options in <code class="filename">dhcpd.conf</code>; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcrelay</code> man page — Explains the DHCP Relay Agent and its configuration options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/dhcp-<<em class="replaceable"><code>version</code></em>>/</code> — Contains sample files, README files, and release notes for current versions of the DHCP service.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 7. Controlling Access to Services" id="ch-Controlling_Access_to_Services" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. Controlling Access to Services</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-services-runlevels">7.1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="#s1-services-configuring">7.2. Configuring the Services</a></span></dt><dt><span class="section"><a href="#s1-services-running">7.3. Running the Services</a></span></dt><dt><span class="section"><a href="#s1-services-additional-resources">7.4. Additional Resources</a></span></dt></dl></div><a id="id589935" class="indexterm"></a><div class="para">
+ Maintaining security on your system is extremely important, and one approach for this task is to manage access to system services carefully. Your system may need to provide open access to particular services (for example, <code class="command">httpd</code> if you are running a web server). However, if you do not need to provide a service, you should turn it off to minimize your exposure to possible bug exploits.
+ </div><div class="para">
+ This chapter explains the concept of runlevels, and describes how to set the default one. It also covers the setup of the services to be run in each of them using three different utilities: the <span class="application"><strong>Service Configuration</strong></span> graphical application, the <span class="application"><strong>ntsysv</strong></span> text user interface, and the <span class="application"><strong>chkconfig</strong></span> command line tool. Finally, it describes how to start, stop, and restart the services on a command line using the <span class="application"><strong>service</strong></span> command.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When you allow access for new services, always remember that both the firewall and <span class="application"><strong>SELinux</strong></span> need to be configured as well. One of the most common mistakes committed when configuring a new service is neglecting to implement the necessary firewall configuration and SELinux policies to allow access for it. Refer to the Fedora <em class="citetitle">Security Guide</em> (see <a class="xref" href="#s1-services-additional-resources" title="7.4. Additional Resources">Section 7.4, “Additional Resources”</a>) for more information.
+ </div></div></div><div class="section" title="7.1. Configuring the Default Runlevel" id="s1-services-runlevels"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-services-runlevels">7.1. Configuring the Default Runlevel</h2></div></div></div><div class="para">
+ A <em class="firstterm">runlevel</em> is a state, or <em class="firstterm">mode</em>, defined by services that are meant to be run when this runlevel is selected. Seven numbered runlevels exist (indexed from <span class="emphasis"><em>0</em></span>):
+ </div><div class="table" title="Table 7.1. Runlevels in Fedora" id="table-services-runlevels"><h6>Table 7.1. Runlevels in Fedora</h6><div class="table-contents"><table summary="Runlevels in Fedora" border="1"><colgroup><col width="14%" /><col width="86%" /></colgroup><thead><tr><th>
+ Runlevel
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">0</code>
+ </td><td>
+ Used to halt the system. This runlevel is reserved and cannot be changed.
+ </td></tr><tr><td>
+ <code class="option">1</code>
+ </td><td>
+ Used to run in a single-user mode. This runlevel is reserved and cannot be changed.
+ </td></tr><tr><td>
+ <code class="option">2</code>
+ </td><td>
+ Not used by default. You are free to define it yourself.
+ </td></tr><tr><td>
+ <code class="option">3</code>
+ </td><td>
+ Used to run in a full multi-user mode with a command line user interface.
+ </td></tr><tr><td>
+ <code class="option">4</code>
+ </td><td>
+ Not used by default. You are free to define it yourself.
+ </td></tr><tr><td>
+ <code class="option">5</code>
+ </td><td>
+ Used to run in a full multi-user mode with a graphical user interface.
+ </td></tr><tr><td>
+ <code class="option">6</code>
+ </td><td>
+ Used to reboot the system. This runlevel is reserved and cannot be changed.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ To check in which runlevel you are operating, type the following:
+ </div><a id="id590525" class="indexterm"></a><a id="id670293" class="indexterm"></a><pre class="screen">~]$ <code class="command">runlevel</code>
+N 5</pre><div class="para">
+ The <code class="command">runlevel</code> command displays previous and current runlevel. In this case it is number <span class="emphasis"><em>5</em></span>, which means the system is running in a full multi-user mode with a graphical user interface.
+ </div><div class="para">
+ The default runlevel can be changed by modifying the <code class="filename">/etc/inittab</code> file, which contains a line near the end of the file similar to the following:
+ </div><pre class="screen">id:5:initdefault:</pre><div class="para">
+ In order to edit this file, you must have superuser privileges. To obtain them, log in as root by typing the following command:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="para">
+ Now open the file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>:
+ </div><pre class="screen">~]# <code class="command">nano /etc/inittab</code></pre><div class="para">
+ Then change the number in this line to the desired value and exit the editor. Note that the change does not take effect until you reboot the system.
+ </div></div><div class="section" title="7.2. Configuring the Services" id="s1-services-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-services-configuring">7.2. Configuring the Services</h2></div></div></div><div class="section" title="7.2.1. Using the Service Configuration Utility" id="s2-services-serviceconf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-serviceconf">7.2.1. Using the <span class="application"><strong>Service Configuration</strong></span> Utility</h3></div></div></div><div class="para">
+ The <span class="application"><strong>Service Configuration</strong></span> utility is a graphical application developed by Red Hat to configure which services are started at boot time, as well as to start, stop, and restart them from the menu.
+ </div><a id="id645613" class="indexterm"></a><a id="id729909" class="indexterm"></a><div class="para">
+ To start the utility, select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Services</strong></span> from the panel, or type the command <code class="command">system-config-services</code> at a shell prompt (e.g., <span class="emphasis"><em>xterm</em></span> or <span class="emphasis"><em>GNOME Terminal</em></span>).
+ </div><div class="figure" title="Figure 7.1. The Service Configuration Utility" id="fig-services-serviceconf"><div class="figure-contents"><div class="mediaobject"><img src="images/controlling-access-to-services-service_configuration.png" alt="The Service Configuration Utility" /><div class="longdesc"><div class="para">
+ The Service Configuration Utility
+ </div></div></div></div><h6>Figure 7.1. The <span class="application">Service Configuration</span> Utility </h6></div><br class="figure-break" /><div class="para">
+ The utility displays the list of all available services (i.e., both the services from the <code class="filename">/etc/rc.d/init.d/</code> directory, and the services controlled by <span class="application"><strong>xinetd</strong></span>) along with their description and the current status. See <a class="xref" href="#tab-services-serviceconf-states" title="Table 7.2. Possible Service States">Table 7.2, “Possible Service States”</a> for a complete list of used icons and an explanation of their meaning.
+ </div><div class="table" title="Table 7.2. Possible Service States" id="tab-services-serviceconf-states"><h6>Table 7.2. Possible Service States</h6><div class="table-contents"><table summary="Possible Service States" border="1"><colgroup><col width="14%" /><col width="86%" /></colgroup><thead><tr><th>
+ Icon
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_enabled.png" /><div class="longdesc"><div class="para">
+ Green bullet
+ </div></div></span>
+
+ </td><td>
+ The service is enabled.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_disabled.png" /><div class="longdesc"><div class="para">
+ Red bullet
+ </div></div></span>
+
+ </td><td>
+ The service is disabled.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_selected.png" /><div class="longdesc"><div class="para">
+ Control panel
+ </div></div></span>
+
+ </td><td>
+ The service is enabled for selected runlevels only.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_running.png" /><div class="longdesc"><div class="para">
+ Plugged plug
+ </div></div></span>
+
+ </td><td>
+ The service is running.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_stopped.png" /><div class="longdesc"><div class="para">
+ Unplugged plug
+ </div></div></span>
+
+ </td><td>
+ The service is stopped.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_wrong.png" /><div class="longdesc"><div class="para">
+ Exclamation mark
+ </div></div></span>
+
+ </td><td>
+ There is something wrong with the service.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_unknown.png" /><div class="longdesc"><div class="para">
+ Question mark
+ </div></div></span>
+
+ </td><td>
+ The status of the service is unknown.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Unless you are already authenticated, you will be prompted to enter the superuser password the first time you make a change:
+ </div><div class="figure" title="Figure 7.2. Authentication Query" id="fig-services-serviceconf-authentication"><div class="figure-contents"><div class="mediaobject"><img src="images/controlling-access-to-services-authentication.png" alt="Authentication Query" /><div class="longdesc"><div class="para">
+ Authentication Query
+ </div></div></div></div><h6>Figure 7.2. Authentication Query</h6></div><br class="figure-break" /><div class="section" title="7.2.1.1. Enabling the Service" id="s3-services-serviceconf-enabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-enabling">7.2.1.1. Enabling the Service</h4></div></div></div><div class="para">
+ To enable a service, select it from the list and either click the <span class="guilabel"><strong>Enable</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guimenuitem"><strong>Enable</strong></span> from the main menu.
+ </div></div><div class="section" title="7.2.1.2. Disabling the Service" id="s3-services-serviceconf-disabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-disabling">7.2.1.2. Disabling the Service</h4></div></div></div><div class="para">
+ To disable the service, select it from the list and either click the <span class="guilabel"><strong>Disable</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guimenuitem"><strong>Disable</strong></span> from the main menu.
+ </div></div><div class="section" title="7.2.1.3. Running the Service" id="s3-services-serviceconf-running"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-running">7.2.1.3. Running the Service</h4></div></div></div><div class="para">
+ To run the service, select it from the list and either click the <span class="guilabel"><strong>Start</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guimenuitem"><strong>Start</strong></span> from the main menu. Note that this option is not available for services controlled by <span class="application"><strong>xinetd</strong></span>, as they are started by it on demand.
+ </div></div><div class="section" title="7.2.1.4. Stopping the Service" id="s3-services-serviceconf-stopping"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-stopping">7.2.1.4. Stopping the Service</h4></div></div></div><div class="para">
+ To stop the service, select it from the list and either click the <span class="guilabel"><strong>Stop</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guimenuitem"><strong>Stop</strong></span> from the main menu. Note that this option is not available for services controlled by <span class="application"><strong>xinetd</strong></span>, as they are stopped by it when their job is finished.
+ </div></div><div class="section" title="7.2.1.5. Restarting the Running Service" id="s3-services-serviceconf-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-restarting">7.2.1.5. Restarting the Running Service</h4></div></div></div><div class="para">
+ To restart the running service, select it from the list and either click the <span class="guilabel"><strong>Restart</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guimenuitem"><strong>Restart</strong></span> from the main menu. Note that this option is not available for services controlled by <span class="application"><strong>xinetd</strong></span>, as they are started and stopped by it automatically.
+ </div></div><div class="section" title="7.2.1.6. Selecting the Runlevels" id="s3-services-serviceconf-selecting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-selecting">7.2.1.6. Selecting the Runlevels</h4></div></div></div><div class="para">
+ To enable the service for certain runlevels only, select it from the list and either click the <span class="guilabel"><strong>Customize</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guisubmenu"><strong>Customize</strong></span> from the main menu. Then select the checkbox beside each runlevel in which you want the service to run. Note that this option is not available for services controlled by <span class="application"><strong>xinetd</strong></span>.
+ </div></div></div><div class="section" title="7.2.2. Using the ntsysv Utility" id="s2-services-ntsysv"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-ntsysv">7.2.2. Using the <span class="application"><strong>ntsysv</strong></span> Utility</h3></div></div></div><a id="id726846" class="indexterm"></a><a id="id470161" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>ntsysv</strong></span> utility is a command line application with a simple text user interface to configure which services are to be started in selected runlevels. Note that in order to use the utility, you must obtain superuser privileges first:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="para">
+ To start the utility, type the following command:
+ </div><pre class="screen">~]# <code class="command">ntsysv</code></pre><div class="figure" title="Figure 7.3. The ntsysv utility" id="fig-ntsysv"><div class="figure-contents"><div class="mediaobject"><img src="images/controlling-access-to-services-ntsysv.png" alt="The ntsysv utility" /><div class="longdesc"><div class="para">
+ The <span class="application"><strong>ntsysv</strong></span> utility
+ </div></div></div></div><h6>Figure 7.3. The <span class="application">ntsysv</span> utility</h6></div><br class="figure-break" /><div class="para">
+ The utility displays the list of available services (i.e., the services from the <code class="filename">/etc/rc.d/init.d/</code> directory) along with their current status and a description obtainable by pressing <span class="keycap"><strong>F1</strong></span>. See <a class="xref" href="#tab-services-ntsysv-states" title="Table 7.3. Possible Service States">Table 7.3, “Possible Service States”</a> for a list of used symbols and an explanation of their meaning.
+ </div><div class="table" title="Table 7.3. Possible Service States" id="tab-services-ntsysv-states"><h6>Table 7.3. Possible Service States</h6><div class="table-contents"><table summary="Possible Service States" border="1"><colgroup><col width="14%" /><col width="86%" /></colgroup><thead><tr><th>
+ Symbol
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span class="guilabel"><strong>[*]</strong></span>
+ </td><td>
+ The service is enabled.
+ </td></tr><tr><td>
+ <span class="guilabel"><strong>[ ]</strong></span>
+ </td><td>
+ The service is disabled.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" title="7.2.2.1. Enabling the Service" id="s3-services-ntsysv-enabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-ntsysv-enabling">7.2.2.1. Enabling the Service</h4></div></div></div><div class="para">
+ To enable a service, navigate through the list using the <span class="keycap"><strong>Up</strong></span> and <span class="keycap"><strong>Down</strong></span> arrows keys, and select it with the <span class="keycap"><strong>Spacebar</strong></span>. An asterisk (<span class="guilabel"><strong>*</strong></span>) should appear in the brackets. Once you are done, use <span class="keycap"><strong>Tab</strong></span> to navigate to the <span class="guibutton"><strong>Ok</strong></span> button, and confirm the changes by pressing <span class="keycap"><strong>Enter</strong></span>.
+ </div><div class="para">
+ Please, keep in mind that <span class="application"><strong>ntsysv</strong></span> does not actually run the service. If you need to start the service immediately, use the <code class="command">service</code> command as described in <a class="xref" href="#s3-services-running-running" title="7.3.1.1. Running the Service">Section 7.3.1.1, “Running the Service”</a>.
+ </div></div><div class="section" title="7.2.2.2. Disabling the Service" id="s3-services-ntsysv-disabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-ntsysv-disabling">7.2.2.2. Disabling the Service</h4></div></div></div><div class="para">
+ To disable a service, navigate through the list using the <span class="keycap"><strong>Up</strong></span> and <span class="keycap"><strong>Down</strong></span> arrows keys, and toggle its status with the <span class="keycap"><strong>Spacebar</strong></span>. An asterisk (<span class="guilabel"><strong>*</strong></span>) in the brackets should disappear. Once you are done, use <span class="keycap"><strong>Tab</strong></span> to navigate to the <span class="guibutton"><strong>Ok</strong></span> button, and confirm the changes by pressing <span class="keycap"><strong>Enter</strong></span>.
+ </div><div class="para">
+ Please, keep in mind that <span class="application"><strong>ntsysv</strong></span> does not actually stop the service. If you need to stop the service immediately, use the <code class="command">service</code> command as described in <a class="xref" href="#s3-services-running-stopping" title="7.3.1.2. Stopping the Service">Section 7.3.1.2, “Stopping the Service”</a>.
+ </div></div><div class="section" title="7.2.2.3. Selecting the Runlevels" id="s3-services-ntsysv-selecting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-ntsysv-selecting">7.2.2.3. Selecting the Runlevels</h4></div></div></div><div class="para">
+ By default, the <span class="application"><strong>ntsysv</strong></span> utility affects the current runlevel only. To enable or disable services for other runlevels, run the command with the additional <code class="option">--level</code> option followed by the string of numbers from 0 to 6 representing each runlevel you want to configure. For example, to configure runlevels 3 and 5, type:
+ </div><pre class="screen">~]# <code class="command">ntsysv --level 35</code></pre></div></div><div class="section" title="7.2.3. Using the chkconfig Utility" id="s2-services-chkconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-chkconfig">7.2.3. Using the <code class="command">chkconfig</code> Utility</h3></div></div></div><a id="id556587" class="indexterm"></a><a id="id556605" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>chkconfig</strong></span> utility is a command line application to configure which services are to be started in selected runlevels. It also allows you to list all available services along with their current setting. Note that with the exception of listing, you must have superuser privileges to use this command. To obtain them, log in as root by typing:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="section" title="7.2.3.1. Listing the Services" id="s3-services-chkconfig-listing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-chkconfig-listing">7.2.3.1. Listing the Services</h4></div></div></div><div class="para">
+ To display a list of system services (i.e., both the services from the <code class="filename">/etc/rc.d/init.d/</code> directory, and the services controlled by <span class="application"><strong>xinetd</strong></span>), either type <code class="command">chkconfig --list</code>, or use <code class="command">chkconfig</code> with no additional arguments. You should be presented with an output similar to this:
+ </div><div class="example" title="Example 7.1. Listing the services" id="ex-services-chkconfig-listing-all"><h6>Example 7.1. Listing the services</h6><div class="example-contents"><pre class="screen">~]# <code class="command">chkconfig --list</code>
+NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off
+abrtd 0:off 1:off 2:off 3:on 4:off 5:on 6:off
+acpid 0:off 1:off 2:on 3:on 4:on 5:on 6:off
+anamon 0:off 1:off 2:off 3:off 4:off 5:off 6:off
+atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
+auditd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
+avahi-daemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+wpa_supplicant 0:off 1:off 2:off 3:off 4:off 5:off 6:off
+
+xinetd based services:
+ chargen-dgram: off
+ chargen-stream: off
+ cvs: off
+ daytime-dgram: off
+ daytime-stream: off
+ discard-dgram: off
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+ time-stream: off</pre></div></div><br class="example-break" /><div class="para">
+ As you can see, each line consists of the name of the service followed by its status (<span class="emphasis"><em>on</em></span> or <span class="emphasis"><em>off</em></span>) for each of the seven numbered runlevels. For example, in the listing above, <span class="application"><strong>NetworkManager</strong></span> is enabled for runlevel 2, 3, 4, and 5, while <span class="application"><strong>abrtd</strong></span> runs in runlevel 3 and 5. The <span class="application"><strong>xinetd</strong></span> based services are listed at the end, being either <span class="emphasis"><em>on</em></span>, or <span class="emphasis"><em>off</em></span>.
+ </div><div class="para">
+ To display the current settings for selected service only, use <code class="command">chkconfig --list</code> followed by the name of the service:
+ </div><div class="example" title="Example 7.2. Listing a single service" id="ex-services-chkconfig-listing-single"><h6>Example 7.2. Listing a single service</h6><div class="example-contents"><pre class="screen">~]# <code class="command">chkconfig --list sshd</code>
+sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off</pre></div></div><br class="example-break" /><div class="para">
+ You can also use <code class="command">chkconfig --list <em class="replaceable"><code><service></code></em></code> to display the status of a service that is managed by <span class="application"><strong>xinetd</strong></span>. In that case, the output will simply contain the information whether the service is enabled or disabled:
+ </div><div class="example" title="Example 7.3. Listing a service that is managed by xinetd" id="ex-services-chkconfig-listing-xinetd"><h6>Example 7.3. Listing a service that is managed by <span class="application">xinetd</span></h6><div class="example-contents"><pre class="screen">~]# <code class="command">chkconfig --list rsync</code>
+rsync off</pre></div></div><br class="example-break" /></div><div class="section" title="7.2.3.2. Enabling the Service" id="s3-services-chkconfig-enabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-chkconfig-enabling">7.2.3.2. Enabling the Service</h4></div></div></div><div class="para">
+ To enable the service for runlevels 2, 3, 4, and 5 at the same time, type <code class="command">chkconfig <em class="replaceable"><code><service></code></em> on</code>. For instance:
+ </div><pre class="screen">~]# <code class="command">chkconfig httpd on</code></pre><div class="para">
+ To enable the service for certain runlevels only, add the <code class="option">--level</code> option followed by the string of numbers from 0 to 6 representing each runlevel in which you want the service to run. For example, to enable the <span class="application"><strong>abrtd</strong></span> for runlevels 3 and 5, type:
+ </div><pre class="screen">~]# <code class="command">chkconfig abrtd on --level 35</code></pre><div class="para">
+ The service will be started the next time you enter one of these runlevels. If you need to start the service immediately, use the <code class="command">service</code> command as described in <a class="xref" href="#s3-services-running-running" title="7.3.1.1. Running the Service">Section 7.3.1.1, “Running the Service”</a>.
+ </div><div class="para">
+ To enable the service that is managed by <span class="application"><strong>xinetd</strong></span>, use <code class="command">chkconfig <em class="replaceable"><code><service></code></em> on</code> only, as the <code class="option">--level</code> option is not allowed:
+ </div><pre class="screen">~]# <code class="command">chkconfig rsync on</code></pre><div class="para">
+ If the <span class="application"><strong>xinetd</strong></span> daemon is running, the service is immediately enabled without having to restart the daemon manually.
+ </div></div><div class="section" title="7.2.3.3. Disabling the Service" id="s3-services-chkconfig-disabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-chkconfig-disabling">7.2.3.3. Disabling the Service</h4></div></div></div><div class="para">
+ To disable the service for runlevels 2, 3, 4, and 5 at the same time, type <code class="command">chkconfig <em class="replaceable"><code><service></code></em> off</code>. For instance:
+ </div><pre class="screen">~]# <code class="command">chkconfig httpd off</code></pre><div class="para">
+ To disable the service for certain runlevels only, add the <code class="option">--level</code> option followed by the string of numbers from 0 to 6 representing each runlevel in which you do <span class="emphasis"><em>not</em></span> want the service to run. For example, to disable the <span class="application"><strong>abrtd</strong></span> for runlevels 2 and 4, type:
+ </div><pre class="screen">~]# <code class="command">chkconfig abrtd off --level 24</code></pre><div class="para">
+ The service will be stopped the next time you enter one of these runlevels. If you need to stop the service immediately, use the <code class="command">service</code> command as described in <a class="xref" href="#s3-services-running-stopping" title="7.3.1.2. Stopping the Service">Section 7.3.1.2, “Stopping the Service”</a>.
+ </div><div class="para">
+ To disable the service that is managed by <span class="application"><strong>xinetd</strong></span>, use <code class="command">chkconfig <em class="replaceable"><code><service></code></em> off</code> only, as the <code class="option">--level</code> option is not allowed:
+ </div><pre class="screen">~]# <code class="command">chkconfig rsync off</code></pre><div class="para">
+ If the <span class="application"><strong>xinetd</strong></span> daemon is running, the service is immediately disabled without having to restart the daemon manually.
+ </div></div></div></div><div class="section" title="7.3. Running the Services" id="s1-services-running"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-services-running">7.3. Running the Services</h2></div></div></div><div class="section" title="7.3.1. Using the service Utility" id="s2-services-service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-service">7.3.1. Using the <span class="application"><strong>service</strong></span> Utility</h3></div></div></div><a id="id536719" class="indexterm"></a><a id="id568465" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>service</strong></span> utility enables you to start, stop, or restart the services from the <code class="filename">/etc/init.d/</code> directory. To use it, make sure you have superuser privileges:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ If you are running a graphical user interface, you can also use the <span class="application"><strong>Service Configuration</strong></span> utility. See <a class="xref" href="#s2-services-serviceconf" title="7.2.1. Using the Service Configuration Utility">Section 7.2.1, “Using the <span class="application"><strong>Service Configuration</strong></span> Utility”</a> for more information.
+ </div></div></div><div class="section" title="7.3.1.1. Running the Service" id="s3-services-running-running"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-running-running">7.3.1.1. Running the Service</h4></div></div></div><div class="para">
+ To run the service, type <code class="command">service <em class="replaceable"><code><service_name></code></em> start</code>. For example:
+ </div><pre class="screen">~]# <code class="command">service httpd start</code>
+Starting httpd: [ OK ]</pre></div><div class="section" title="7.3.1.2. Stopping the Service" id="s3-services-running-stopping"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-running-stopping">7.3.1.2. Stopping the Service</h4></div></div></div><div class="para">
+ To stop the service, type <code class="command">service <em class="replaceable"><code><service_name></code></em> stop</code>. For example:
+ </div><pre class="screen">~]# <code class="command">service httpd stop</code>
+Stopping httpd: [ OK ]</pre></div><div class="section" title="7.3.1.3. Restarting the Service" id="s3-services-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-running-restarting">7.3.1.3. Restarting the Service</h4></div></div></div><div class="para">
+ To restart the service, type <code class="command">service <em class="replaceable"><code><service_name></code></em> restart</code>. For example:
+ </div><pre class="screen">~]# <code class="command">service httpd restart</code>
+Stopping httpd: [ OK ]
+Starting httpd: [ OK ]</pre></div><div class="section" title="7.3.1.4. Checking the Service Status" id="s3-services-running-checking"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-running-checking">7.3.1.4. Checking the Service Status</h4></div></div></div><div class="para">
+ To check the current status of the service, type <code class="command">service <em class="replaceable"><code><service_name></code></em> status</code>. For example:
+ </div><div class="example" title="Example 7.4. Checking the status of httpd" id="ex-services-running-checking-single"><h6>Example 7.4. Checking the status of <span class="application">httpd</span></h6><div class="example-contents"><pre class="screen">~]# <code class="command">service httpd status</code>
+httpd (pid 7474) is running...</pre></div></div><br class="example-break" /><div class="para">
+ You can also display the status of all available services at once using the <code class="option">--status-all</code> option:
+ </div><div class="example" title="Example 7.5. Checking the status of all services" id="ex-services-running-checking-all"><h6>Example 7.5. Checking the status of all services</h6><div class="example-contents"><pre class="screen">~]# <code class="command">service --status-all</code>
+abrt (pid 1492) is running...
+acpid (pid 1305) is running...
+atd (pid 1540) is running...
+auditd (pid 1103) is running...
+automount (pid 1315) is running...
+Avahi daemon is running
+cpuspeed is stopped
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+wpa_supplicant (pid 1227) is running...</pre></div></div><br class="example-break" /></div></div></div><div class="section" title="7.4. Additional Resources" id="s1-services-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-services-additional-resources">7.4. Additional Resources</h2></div></div></div><div class="section" title="7.4.1. Installed Documentation" id="s2-services-additional-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-additional-resources-installed">7.4.1. Installed Documentation</h3></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="command">man chkconfig</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">chkconfig</code> utility containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ntsysv</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">ntsysv</code> utility containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man service</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">service</code> utility containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man system-config-services</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">system-config-services</code> utility containing the full documentation on its usage.
+ </div></dd></dl></div></div><div class="section" title="7.4.2. Related Books" id="s2-services-additional-resources-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-additional-resources-books">7.4.2. Related Books</h3></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a href="http://docs.fedoraproject.org/en-US/Fedora/14/html/Security_Guide/index.html"><em class="citetitle">Security Guide</em></a> </span></dt><dd><div class="para">
+ A guide to securing Fedora. It contains valuable information on how to set up the firewall, as well as the configuration of <span class="application"><strong>SELinux</strong></span>.
+ </div></dd></dl></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 8. Authentication Configuration" id="ch-Authentication_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. Authentication Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-The_Authentication_Configuration_Tool">8.1. The Authentication Configuration Tool</a></span></dt><dt><span class="section"><a href="#chap-SSSD_User_Guide-Introduction">8.2. The System Security Services Daemon (SSSD)</a></span></dt></dl></div><div class="section" title="8.1. The Authentication Configuration Tool" id="sect-The_Authentication_Configuration_Tool"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-The_Authentication_Configuration_Tool">8.1. The Authentication Configuration Tool</h2></div></div></div><a id="id485435" class="indexterm"></a><a id="id1556006" class=
"indexterm"></a><div class="para">
+ When a user logs in to a Fedora system, the username and password combination must be verified, or <em class="firstterm">authenticated</em>, as a valid and active user. Sometimes the information to verify the user is located on the local system, and other times the system defers the authentication to a user database on a remote system.
+ </div><div class="para">
+ The <span class="application"><strong>Authentication Configuration Tool</strong></span> provides a graphical interface for configuring user information retrieval from <em class="firstterm">Lightweight Directory Access Protocol</em> (LDAP), <em class="firstterm"> Network Information Service</em> (NIS), and <em class="firstterm">Winbind</em> user account databases. This tool also allows you to configure Kerberos to be used as the authentication protocol when using LDAP or NIS.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you configured a medium or high security level during installation (or with the <span class="application"><strong>Security Level Configuration Tool</strong></span>), then the firewall will prevent NIS authentication. For more information about firewalls, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/14/html/Security_Guide/sect-Security_Guide-Firewalls.html"><em class="citetitle"><span class="quote">“<span class="quote">Firewalls</span>”</span></em> section</a> of the Fedora 14 <a href="http://docs.fedoraproject.org/en-US/Fedora/14/html/Security_Guide/index.html"><em class="citetitle">Security Guide</em></a>.
+ </div></div></div><a id="id740152" class="indexterm"></a><a id="id740138" class="indexterm"></a><div class="para">
+ To start the graphical version of the <span class="application"><strong>Authentication Configuration Tool</strong></span> from the desktop, click <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Authentication</strong></span> or type the command <code class="command">system-config-authentication</code> at a shell prompt (for example, in an <span class="application"><strong>XTerm</strong></span> or a <span class="application"><strong>GNOME</strong></span> terminal).
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ After exiting the authentication program, any changes you made take effect immediately.
+ </div></div></div><div class="section" title="8.1.1. Identity & Authentication" id="sect-The_Authentication_Configuration_Tool-Identity_and_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">8.1.1. Identity & Authentication</h3></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Identity & Authentication</strong></span> tab allows you to configure how users should be authenticated, and has several options for each method of authentication. To select which user account database should be used, select an option from the drop-down list.
+ </div><div class="figure" title="Figure 8.1. Identity & Authentication; changing the option in the User Account Database drop-down list changes the contents of the tab."><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/authconfig_LDAP_kerb.png" align="middle" alt="Identity & Authentication; changing the option in the User Account Database drop-down list changes the contents of the tab." /></div></div><h6>Figure 8.1. <span class="guilabel">Identity & Authentication</span>; changing the option in the <span class="guilabel">User Account Database</span> drop-down list changes the contents of the tab.</h6></div><br class="figure-break" /><div class="para">
+ The following list explains what each option configures:
+ </div><h4 id="id834228">LDAP</h4><a id="id834227" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>LDAP</strong></span> option instructs the system to retrieve user information via LDAP. It contains the following specifications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP Search Base DN</strong></span> — Specifies that user information should be retrieved using the listed Distinguished Name (DN).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP Server</strong></span> — Specifies the address of the <code class="systemitem">LDAP</code> server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Use TLS to encrypt connections</strong></span> — When enabled, <code class="systemitem">Transport Layer Security</code> (TLC) will be used to encrypt passwords sent to the <code class="systemitem">LDAP</code> server. The <span class="guibutton"><strong>Download CA Certificate</strong></span> option allows you to specify a URL from which to download a valid <em class="firstterm">Certificate Authority certificate</em> (CA). A valid CA certificate must be in the <em class="firstterm">Privacy Enhanced Mail</em> (PEM) format.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <span class="guilabel"><strong>Use TLS to encrypt connections</strong></span> option must not be ticked if an <code class="systemitem">ldaps://</code> server address is specified in the <span class="guilabel"><strong>LDAP Server</strong></span> field.
+ </div></div></div><div class="para">
+ For more information about CA Certificates, refer to <a class="xref" href="#s2-apache-mod_ssl-certificates" title="11.6.1. An Overview of Certificates and Security">Section 11.6.1, “An Overview of Certificates and Security”</a>.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">openldap-clients</code> package must be installed for this option to work.
+ </div><div class="para">
+ LDAP provides the following methods of authentication:
+ </div><div class="itemizedlist"><ul><li class="listitem"><a id="id825997" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Kerberos password</strong></span> — This option enables Kerberos authentication. It contains the following specifications:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Realm</strong></span> — Configures the realm for the Kerberos server. The realm is the network that uses Kerberos, composed of one or more KDCs and a potentially large number of clients.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>KDCs</strong></span> — Defines the Key Distribution Centers (KDC), which are servers that issue Kerberos tickets.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Admin Servers</strong></span> — Specifies the administration server(s) running <code class="command">kadmind</code>.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The <span class="guimenu"><strong>Kerberos Settings</strong></span> dialog also allows you to use DNS to resolve hosts to realms and locate KDCs for realms.
+ </div><div class="para">
+ The <code class="filename">krb5-libs</code> and <code class="filename">krb5-workstation</code> packages must be installed for this option to work. For more information about Kerberos, refer to section <em class="citetitle">Using Kerberos</em> of the Fedora 14 <em class="citetitle">Managing Single Sign-On and Smart Cards</em> guide.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP password</strong></span> — This option instructs standard PAM-enabled applications to use LDAP authentication with options specified in the User Account Configuration of LDAP. When using this option, you must provide an <code class="systemitem">ldaps://</code> server address or use TLS for LDAP authentication.
+ </div></li></ul></div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The SSSD service is used as a client for LDAP and Kerberos servers. Thus, offline login is enabled and supported by default. No user interaction is needed to set up the SSSD service with the <span class="application"><strong>Authentication Configuration Tool</strong></span>. For more information about the SSSD service, refer to <a class="xref" href="#chap-SSSD_User_Guide-Introduction" title="8.2. The System Security Services Daemon (SSSD)">Section 8.2, “The System Security Services Daemon (SSSD)”</a>
+ </div></div></div><h4 id="id1338073">NIS</h4><a id="id1338069" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>NIS</strong></span> option configures the system to connect to a NIS server (as an NIS client) for user and password authentication. To configure this option, specify the NIS domain and NIS server. If the NIS server is not specified, the daemon attempts to find it via broadcast.
+ </div><div class="para">
+ The <span class="package">ypbind</span> package must be installed for this option to work. If the NIS user account databse is used, the <code class="systemitem">portmap</code> and <code class="systemitem">ypbind</code> services are started and are also enabled to start at boot time.
+ </div><div class="para">
+ For more information about NIS, refer to <a href="http://docs.fedoraproject.org/en-US/Fedora/14/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_NIS.html">section <em class="citetitle"><span class="quote">“<span class="quote">Securing NIS</span>”</span></em></a> of the Fedora 14 <em class="citetitle">Security Guide</em>.
+ </div><div class="para">
+ NIS provides the following methods of authentication:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Kerberos password</strong></span> — This option enables Kerberos authentication. For more information about configuration of the Kerberos authentication method, refer to the previous section on LDAP.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id588596" class="indexterm"></a>
+ <span class="guilabel"><strong>NIS password</strong></span> — This option enables NIS authentication. NIS can provide authentication information to outside processes to authenticate users.
+ </div></li></ul></div><h4 id="id800460">Winbind</h4><a id="id800446" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Winbind</strong></span> option configures the system to connect to a Windows Active Directory or a Windows domain controller. User information from the specified directory or domain controller can then be accessed, and server authentication options can be configured. It contains the following specifications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind Domain</strong></span> — Specifies the Windows Active Directory or domain controller to connect to.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Security Model</strong></span> — Allows you to select a security model, which configures the Samba client mode of operation. The drop-down list allows you to select any of the following:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>ads</strong></span> — This mode instructs Samba to act as a domain member in an Active Directory Server (ADS) realm. To operate in this mode, the <code class="filename">krb5-server</code> package must be installed, and Kerberos must be configured properly.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>domain</strong></span> — In this mode, Samba will attempt to validate the username/password by authenticating it through a Windows NT Primary or Backup Domain Controller, similar to how a Windows NT Server would.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>server</strong></span> — In this mode, Samba will attempt to validate the username/password by authenticating it through another SMB server (for example, a Windows NT Server). If the attempt fails, the <span class="guilabel"><strong>user</strong></span> mode will take effect instead.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>user</strong></span> — This is the default mode. With this level of security, a client must first log in with a valid username and password. Encrypted passwords can also be used in this security mode.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind ADS Realm</strong></span> — When the <span class="guilabel"><strong>ads</strong></span> Security Model is selected, this allows you to specify the ADS Realm the Samba server should act as a domain member of.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind Domain Controllers</strong></span> — Use this option to specify which domain controller <code class="command">winbind</code> should use.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Template Shell</strong></span> — When filling out the user information for a Windows NT user, the <code class="command">winbindd</code> daemon uses the value chosen here to to specify the login shell for that user.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Allow offline login</strong></span> — By checking this option, you allow authentication information to be stored in a local cache (provided by SSSD). This information is then used when a user attempts to authenticate while offline.
+ </div></li></ul></div><a id="id440360" class="indexterm"></a><div class="para">
+ Winbind provides only one method of authentication, <span class="guilabel"><strong>Winbind password</strong></span>. This method of authentication uses the options specified in the User Account Configuration of Winbind to connect to a Windows Active Directory or a Windows domain controller.
+ </div></div><div class="section" title="8.1.2. Advanced Options" id="sect-The_Authentication_Configuration_Tool-Advanced_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-The_Authentication_Configuration_Tool-Advanced_Options">8.1.2. Advanced Options</h3></div></div></div><div class="para">
+ This tab allows you to configure advanced options, as listed below.
+ </div><div class="figure" title="Figure 8.2. Advanced Options"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/authconfig_advanced.png" align="middle" width="444" alt="Advanced Options" /></div></div><h6>Figure 8.2. <span class="guilabel">Advanced Options</span></h6></div><br class="figure-break" /><h4 id="id708231">Local Authentication Options</h4><div class="itemizedlist"><ul><li class="listitem"><a id="id708220" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Enable fingerprint reader support</strong></span> — By checking this option, you enable fingerprint authentication to log in by scanning your finger with the fingerprint reader.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Enable local access control</strong></span> — When enabled, <code class="filename">/etc/security/access.conf</code> is consulted for authorization of a user.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Password Hashing Algorithm</strong></span> — This option lets you specify which hashing or cryptographic algorithm should be used to encrypt locally stored passwords.
+ </div></li></ul></div><h4 id="id738158">Other Authentication Options</h4><div class="para">
+ <span class="guilabel"><strong>Create home directories on the first login</strong></span> — When enabled, the user's home directory is automatically created when they log in if it does not already exist.
+ </div><h4 id="id738146">Smart Card Authentication Options</h4><a id="id738142" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Enable smart card support</strong></span> — This option enables smart card authentication. Smart card authentication allows you to log in using a certificate and a key associated with a smart card.
+ </div><div class="para">
+ When the <span class="guilabel"><strong>Enable smart card support</strong></span> option is checked, the following options can be specified:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Card Removal Action</strong></span> — This option defines what action the system performs when the card is removed from the card reader during an active session. Two alternatives are available:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Ignore</strong></span> — The card removal is ignored and the system continues to function as normal.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Lock</strong></span> — The current session is immediately locked.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Require smart card login</strong></span> — Requires the user to login and authenticate with a smart card. It essentially disables any other type of password authentication. This option should not be selected until after you have successfully logged in using a smart card.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The <span class="package">pam_pkcs11</span> and the <span class="package">coolkey</span> packages must be installed for this option to work. For more information about smart cards, refer to the Fedora 14 <em class="citetitle">Managing Single Sign-On and Smart Cards</em> guide. <div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ You can restore all of the options specified in the <span class="application"><strong>Authentication Configuration Tool</strong></span> to the previous configuration setup by clicking <span class="guibutton"><strong>Revert</strong></span>.
+ </div></div></div>
+
+ </div></div><div class="section" title="8.1.3. Command Line Version" id="sect-The_Authentication_Configuration_Tool-Command_Line_Version"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-The_Authentication_Configuration_Tool-Command_Line_Version">8.1.3. Command Line Version</h3></div></div></div><a id="id970972" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Authentication Configuration Tool</strong></span> also supports a command line interface. The command line version can be used in a configuration script or a kickstart script. The authentication options are summarized in <a class="xref" href="#tb-authconfig-cmd-line" title="Table 8.1. Command Line Options">Table 8.1, “Command Line Options”</a>.
+ </div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ These options can also be found in the <code class="command">authconfig</code> man page or by typing <code class="command">authconfig --help</code> at the shell prompt.
+ </div></div></div><div class="table" title="Table 8.1. Command Line Options" id="tb-authconfig-cmd-line"><h6>Table 8.1. Command Line Options</h6><div class="table-contents"><table summary="Command Line Options" border="1"><colgroup><col width="60%" /><col width="40%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">--enableshadow, --useshadow</code>
+ </td><td>
+ Enable shadow passwords
+ </td></tr><tr><td>
+ <code class="command">--disableshadow</code>
+ </td><td>
+ Disable shadow passwords
+ </td></tr><tr><td>
+ <code class="command">--passalgo=<em class="replaceable"><code><descrypt|bigcrypt|md5|sha256|sha512></code></em></code>
+ </td><td>
+ Hash/crypt algorithm to be used
+ </td></tr><tr><td>
+ <code class="command">--enablenis</code>
+ </td><td>
+ Enable NIS for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disablenis</code>
+ </td><td>
+ Disable NIS for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--nisdomain=<em class="replaceable"><code><domain></code></em> </code>
+ </td><td>
+ Specify an NIS domain
+ </td></tr><tr><td>
+ <code class="command">--nisserver=<em class="replaceable"><code><server></code></em> </code>
+ </td><td>
+ Specify an NIS server
+ </td></tr><tr><td>
+ <code class="command">--enableldap</code>
+ </td><td>
+ Enable LDAP for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disableldap</code>
+ </td><td>
+ Disable LDAP for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--enableldaptls</code>
+ </td><td>
+ Enable use of TLS with LDAP
+ </td></tr><tr><td>
+ <code class="command">--disableldaptls</code>
+ </td><td>
+ Disable use of TLS with LDAP
+ </td></tr><tr><td>
+ <code class="command">--enablerfc2307bis</code>
+ </td><td>
+ Enable use of RFC-2307bis schema for LDAP user information lookups
+ </td></tr><tr><td>
+ <code class="command">--disablerfc2307bis</code>
+ </td><td>
+ Disable use of RFC-2307bis schema for LDAP user information lookups
+ </td></tr><tr><td>
+ <code class="command">--enableldapauth</code>
+ </td><td>
+ Enable LDAP for authentication
+ </td></tr><tr><td>
+ <code class="command">--disableldapauth</code>
+ </td><td>
+ Disable LDAP for authentication
+ </td></tr><tr><td>
+ <code class="command">--ldapserver=<em class="replaceable"><code><server></code></em> </code>
+ </td><td>
+ Specify an LDAP server
+ </td></tr><tr><td>
+ <code class="command">--ldapbasedn=<em class="replaceable"><code><dn></code></em> </code>
+ </td><td>
+ Specify an LDAP base DN (Distinguished Name)
+ </td></tr><tr><td>
+ <code class="command">--ldaploadcacert=<em class="replaceable"><code><URL></code></em> </code>
+ </td><td>
+ Load a CA certificate from the specified URL
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5</code>
+ </td><td>
+ Enable Kerberos for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5</code>
+ </td><td>
+ Disable Kerberos for authentication
+ </td></tr><tr><td>
+ <code class="command">--krb5kdc=<em class="replaceable"><code><server></code></em> </code>
+ </td><td>
+ Specify Kerberos KDC server
+ </td></tr><tr><td>
+ <code class="command">--krb5adminserver=<em class="replaceable"><code><server></code></em> </code>
+ </td><td>
+ Specify Kerberos administration server
+ </td></tr><tr><td>
+ <code class="command">--krb5realm=<em class="replaceable"><code><realm></code></em> </code>
+ </td><td>
+ Specify Kerberos realm
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5kdcdns</code>
+ </td><td>
+ Enable use of DNS to find Kerberos KDCs
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5kdcdns</code>
+ </td><td>
+ Disable use of DNS to find Kerberos KDCs
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5realmdns</code>
+ </td><td>
+ Enable use of DNS to find Kerberos realms
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5realmdns</code>
+ </td><td>
+ Disable use of DNS to find Kerberos realms
+ </td></tr><tr><td>
+ <code class="command">--enablewinbind</code>
+ </td><td>
+ Enable winbind for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disablewinbind</code>
+ </td><td>
+ Disable winbind for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--enablewinbindauth</code>
+ </td><td>
+ Enable winbindauth for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablewinbindauth</code>
+ </td><td>
+ Disable winbindauth for authentication
+ </td></tr><tr><td>
+ <code class="command">--winbindseparator=<em class="replaceable"><code><\></code></em> </code>
+ </td><td>
+ Character used to separate the domain and user part of winbind usernames if <code class="command">winbindusedefaultdomain</code> is not enabled
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplatehomedir=<em class="replaceable"><code></home/%D/%U></code></em> </code>
+ </td><td>
+ Directory that winbind users have as their home
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplateprimarygroup=<em class="replaceable"><code><nobody></code></em> </code>
+ </td><td>
+ Group that winbind users have as their primary group
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplateshell=<em class="replaceable"><code></bin/false></code></em> </code>
+ </td><td>
+ Shell that winbind users have as their default login shell
+ </td></tr><tr><td>
+ <code class="command">--enablewinbindusedefaultdomain</code>
+ </td><td>
+ Configures winbind to assume that users with no domain in their usernames are domain users
+ </td></tr><tr><td>
+ <code class="command">--disablewinbindusedefaultdomain</code>
+ </td><td>
+ Configures winbind to assume that users with no domain in their usernames are not domain users
+ </td></tr><tr><td>
+ <code class="command">--winbindjoin=<em class="replaceable"><code><Administrator></code></em> </code>
+ </td><td>
+ Joins the winbind domain or ADS realm as the specified administrator
+ </td></tr><tr><td>
+ <code class="command">--enablewinbindoffline</code>
+ </td><td>
+ Configures winbind to allow offline login
+ </td></tr><tr><td>
+ <code class="command">--disablewinbindoffline</code>
+ </td><td>
+ Configures winbind to prevent offline login
+ </td></tr><tr><td>
+ <code class="command">--smbsecurity=<em class="replaceable"><code><user|server|domain|ads></code></em></code>
+ </td><td>
+ Security mode to use for the Samba and Winbind services
+ </td></tr><tr><td>
+ <code class="command">--smbrealm=<em class="replaceable"><code><realm></code></em></code>
+ </td><td>
+ Default realm for Samba and Winbind services when <span class="guilabel"><strong>security</strong></span> is set to <span class="guimenuitem"><strong>ads</strong></span>
+ </td></tr><tr><td>
+ <code class="command">--enablewins</code>
+ </td><td>
+ Enable Wins for hostname resolution
+ </td></tr><tr><td>
+ <code class="command">--disablewins</code>
+ </td><td>
+ Disable Wins for hostname resolution
+ </td></tr><tr><td>
+ <code class="command">--enablesssd</code>
+ </td><td>
+ Enable SSSD for user information
+ </td></tr><tr><td>
+ <code class="command">--disablesssd</code>
+ </td><td>
+ Disable SSSD for user information
+ </td></tr><tr><td>
+ <code class="command">--enablecache</code>
+ </td><td>
+ Enable <code class="command">nscd</code>
+ </td></tr><tr><td>
+ <code class="command">--disablecache</code>
+ </td><td>
+ Disable <code class="command">nscd</code>
+ </td></tr><tr><td>
+ <code class="command">--enablelocauthorize</code>
+ </td><td>
+ Local authorization is sufficient for local users
+ </td></tr><tr><td>
+ <code class="command">--disablelocauthorize</code>
+ </td><td>
+ Local users are also authorized through a remote service
+ </td></tr><tr><td>
+ <code class="command">--enablesysnetauth</code>
+ </td><td>
+ Authenticate system accounts with network services
+ </td></tr><tr><td>
+ <code class="command">--disablesysnetauth</code>
+ </td><td>
+ Authenticate system accounts with local files only
+ </td></tr><tr><td>
+ <code class="command">--enablepamaccess</code>
+ </td><td>
+ Check <code class="filename">/etc/security/access.conf</code> during account authorization
+ </td></tr><tr><td>
+ <code class="command">--disablepamaccess</code>
+ </td><td>
+ Do not check <code class="filename">/etc/security/access.conf</code> during account authorization
+ </td></tr><tr><td>
+ <code class="command">--enablemkhomedir</code>
+ </td><td>
+ Create a home directory for a user on the first login
+ </td></tr><tr><td>
+ <code class="command">--disablemkhomedir</code>
+ </td><td>
+ Do not create a home directory for a user on the first login
+ </td></tr><tr><td>
+ <code class="command">--enablesmartcard</code>
+ </td><td>
+ Enable authentication with a smart card
+ </td></tr><tr><td>
+ <code class="command">--disablesmartcard</code>
+ </td><td>
+ Disable authentication with a smart card
+ </td></tr><tr><td>
+ <code class="command">--enablerequiresmartcard</code>
+ </td><td>
+ Require smart card for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablerequiresmartcard</code>
+ </td><td>
+ Do not require smart card for authentication
+ </td></tr><tr><td>
+ <code class="command">--smartcardmodule=<em class="replaceable"><code><module></code></em></code>
+ </td><td>
+ Default smart card module to use
+ </td></tr><tr><td>
+ <code class="command">--smartcardaction=<em class="replaceable"><code><0=Lock|1=Ignore></code></em></code>
+ </td><td>
+ Action to be taken when smart card removal is detected
+ </td></tr><tr><td>
+ <code class="command">--enablefingerprint</code>
+ </td><td>
+ Enable fingerprint authentication
+ </td></tr><tr><td>
+ <code class="command">--disablefingerprint</code>
+ </td><td>
+ Disnable fingerprint authentication
+ </td></tr><tr><td>
+ <code class="command">--nostart</code>
+ </td><td>
+ Do not start or stop the <code class="command">portmap</code>, <code class="command">ypbind</code>, or <code class="command">nscd</code> services even if they are configured
+ </td></tr><tr><td>
+ <code class="command">--test</code>
+ </td><td>
+ Do not update the configuration files, only print the new settings
+ </td></tr><tr><td>
+ <code class="command">--update, --kickstart</code>
+ </td><td>
+ Opposite of <code class="command">--test</code>, update configuration files with changed settings
+ </td></tr><tr><td>
+ <code class="command">--updateall</code>
+ </td><td>
+ Update all configuration files
+ </td></tr><tr><td>
+ <code class="command">--probe</code>
+ </td><td>
+ Probe and display network defaults
+ </td></tr><tr><td>
+ <code class="command">--savebackup=<em class="replaceable"><code><name></code></em></code>
+ </td><td>
+ Save a backup of all configuration files
+ </td></tr><tr><td>
+ <code class="command">--restorebackup=<em class="replaceable"><code><name></code></em></code>
+ </td><td>
+ Restore a backup of all configuration files
+ </td></tr><tr><td>
+ <code class="command">--restorelastbackup</code>
+ </td><td>
+ Restore the backup of configuration files saved before the previous configuration change
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div><div xml:lang="en-US" class="section" title="8.2. The System Security Services Daemon (SSSD)" id="chap-SSSD_User_Guide-Introduction" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="chap-SSSD_User_Guide-Introduction">8.2. The System Security Services Daemon (SSSD)</h2></div></div></div><div class="para">
+ This section provides an introduction to the <em class="firstterm">System Security Services Daemon (SSSD)</em>, the main features that it provides, and discusses the requirements and any limitations of a typical SSSD deployment.
+ </div><div class="para">
+ This section also describes how to configure SSSD, and how to use the features that it provides. It provides information on the types of services that it supports and how to configure them, and introduces and describes the most important configuration options. Sample configuration files are also provided to help you optimize your deployment.
+ </div><div class="section" title="8.2.1. What is SSSD?" id="sect-SSSD_User_Guide-Introduction-What_is_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-SSSD_User_Guide-Introduction-What_is_SSSD">8.2.1. What is SSSD?</h3></div></div></div><div class="para">
+ The System Security Services Daemon (SSSD) is a service which provides access to different identity and authentication providers. You can configure SSSD to use a native LDAP domain (that is, an LDAP identity provider with LDAP authentication), or an LDAP identity provider with Kerberos authentication. It provides an NSS and PAM interface to the system, and a pluggable back-end system to connect to multiple different account sources.
+ </div><div class="para">
+ SSSD is also extensible; you can configure it to use new identity sources and authentication mechanisms should they arise. In addition, SSSD is fully IPv6-compatible, provided that it is built against <span class="package">c-ares 1.7.1</span> or later and <span class="package">krb5-libs 1.8.1</span> or later.
+ </div></div><div class="section" title="8.2.2. SSSD Features" id="sect-SSSD_User_Guide-Introduction-SSSD_Features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-SSSD_User_Guide-Introduction-SSSD_Features">8.2.2. SSSD Features</h3></div></div></div><div class="section" title="8.2.2.1. Offline Authentication" id="sect-SSSD_User_Guide-SSSD_Features-Offline_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Offline_Authentication">8.2.2.1. Offline Authentication</h4></div></div></div><div class="para">
+ One of the primary benefits of SSSD is offline authentication. This solves the case of users having a separate corporate account and a local machine account because of the common requirement to implement a Virtual Private Network (<abbr class="abbrev">VPN</abbr>).
+ </div><div class="para">
+ SSSD can cache remote identities and authentication credentials. This means that you can still authenticate with these remote identities even when a machine is offline. In an SSSD system, you only need to manage one account.
+ </div></div><div class="section" title="8.2.2.2. Server Load Reduction" id="sect-SSSD_User_Guide-SSSD_Features-Server_Load_Reduction"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Server_Load_Reduction">8.2.2.2. Server Load Reduction</h4></div></div></div><div class="para">
+ The use of SSSD also helps to reduce the load on identification servers. For example, using <span class="package">nss_ldap</span>, every client application that needs to request user information opens its own connection to the LDAP server. Managing these multiple connections can lead to a heavy load on the LDAP server. In an SSSD system, only the SSSD Data Provider process actually communicates with the LDAP server, reducing the load to one connection per client system.
+ </div></div><div class="section" title="8.2.2.3. Support for Multiple Domains" id="sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">8.2.2.3. Support for Multiple Domains</h4></div></div></div><a id="id719447" class="indexterm"></a><div class="para">
+ You can use SSSD to specify multiple domains of the same type. Compare this to an <code class="filename">nsswitch.conf</code> file configuration, with which you can only request user information from a single server of any particular type (LDAP, NIS, etc.). With SSSD, you can create multiple domains of the same, or of different types of identity provider.
+ </div><div class="para">
+ Beginning with version 0.6.0, SSSD maintains a separate database file for each domain. This means that each domain has its own cache, and in the event that problems occur and maintenance is necessary, it is very easy to purge the cache for a single domain, by stopping <code class="systemitem">sssd</code> and deleting the corresponding cache file. These cache files are stored in the <code class="filename">/var/lib/sss/db/</code> directory.
+ </div><div class="para">
+ All cache files are named according to the domain that they represent, for example <code class="filename">cache_<em class="replaceable"><code>DOMAINNAME</code></em>.ldb</code>.
+ </div><div class="formalpara"><h5 class="formalpara" id="id669186">Considerations Associated with Deleting Cache Files</h5><a id="id669177" class="indexterm"></a>
+ Deleting a domain's cache file can have some unexpected side effects. You should be aware of the following before you proceed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Deleting the cache file also deletes all user data (both identification and cached credentials). Consequently, you should not proceed unless you are online and can authenticate with your username against the domain's servers, because offline authentication will fail.
+ </div></li><li class="listitem"><div class="para">
+ If you are online and change your configuration to reference a different identity provider, SSSD will recognize users from both providers until the cached entries from the original provider time out.
+ </div><div class="para">
+ To avoid this situation, you can either purge the cache or use a different domain name for the new provider (this is the recommended practice). Changing the domain name means that when you restart SSSD it will create a new cache file (with the new name) and the old file will be ignored.
+ </div></li></ul></div></div><div class="section" title="8.2.2.4. Support for LDAP Referrals"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id664771">8.2.2.4. Support for LDAP Referrals</h4></div></div></div><div class="para">
+ SSSD supports two types of LDAP referrals: object-level referrals and subtree referrals. These referral types and the extent of SSSD support is outlined below.
+ </div><div class="section" title="8.2.2.4.1. Object-level Referrals"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id664778">8.2.2.4.1. Object-level Referrals</h5></div></div></div><div class="para">
+ SSSD provides full support for object-level referrals within the same LDAP server, correctly handling any differences in the distinguished name (DN) that might exist as part of the LDAP server referral configuration.
+ </div><div class="para">
+ SSSD provides partial support for object-level referrals between different LDAP servers, and requires that the full DN of an LDAP request be identical on each server. SSSD does not support referrals to different DN paths on other servers.
+ </div></div><div class="section" title="8.2.2.4.2. Subtree Referrals"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id468322">8.2.2.4.2. Subtree Referrals</h5></div></div></div><div class="para">
+ SSSD provides a similar level of support for subtree referrals as it does for object-level referrals. That is, it supports referrals to a changed DN on the local system or to an identical DN on a remote system. The difference with subtree referrals, however, is the ability to set up identical subtrees on each LDAP server and to then configure referrals between these subtrees.
+ </div></div><div class="section" title="8.2.2.4.3. Enabling LDAP Referrals"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id664751">8.2.2.4.3. Enabling LDAP Referrals</h5></div></div></div><div class="para">
+ To take advantage of the SSSD LDAP referral functionality, you need to set the <code class="option">ldap_referrals</code> option to <code class="literal">TRUE</code> in the LDAP domain configuration section of the <code class="filename">/etc/sssd/sssd.conf</code> file. This will enable anonymous access to the second LDAP server.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ SSSD only supports LDAP referrals when it is compiled with OpenLDAP version 2.4.13 or later.
+ </div></div></div></div></div><div class="section" title="8.2.2.5. Differentiating Like-named Users" id="sect-SSSD_User_Guide-SSSD_Features-Differentiating_Like_named_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Differentiating_Like_named_Users">8.2.2.5. Differentiating Like-named Users</h4></div></div></div><div class="para">
+ SSSD supports the differentiation of like-named users in different domains. For example, you can differentiate the user <code class="systemitem">kate</code> in the <code class="systemitem">ldap.example.com</code> domain from the user <code class="systemitem">kate</code> in the <code class="systemitem">ldap.myhome.com</code> domain. You can use SSSD to make requests using fully-qualified usernames. If you request information for <code class="systemitem">kate</code>, you will receive the information from whichever domain is listed first in the look-up order. If you request information for <code class="systemitem">kate at ldap.myhome.com</code>, however, you will receive the correct user information.
+ </div><div class="para">
+ SSSD also provides a <code class="option">filter_users</code> option, which you can use to exclude certain users from being fetched from the database. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for full details about this option.
+ </div></div><div class="section" title="8.2.2.6. Integration with IPA" id="sect-SSSD_User_Guide-SSSD_Features-Integration_with_IPA"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Integration_with_IPA">8.2.2.6. Integration with IPA</h4></div></div></div><div class="para">
+ Beyond the offline authentication, multiple domain management and other features already described, SSSD is also designed to integrate with and enhance the functionality of IPA clients. In an environment with the latest version of IPA installed, SSSD provides additional functionality, including support for dynamic DNS updates, host-based access control, and password migration from an LDAP-only environment into the LDAP/Kerberos 5 environment employed by IPA.
+ </div><div class="section" title="8.2.2.6.1. Support for Dynamic DNS Updates"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id479601">8.2.2.6.1. Support for Dynamic DNS Updates</h5></div></div></div><div class="para">
+ Because the IP address of IPA clients can change, SSSD provides the ability to dynamically update the client's DNS entry on the IPA server. Using a combination of Kerberos and GSS-TSIG (Generic Security Service Algorithm for Secret Key Transaction), IPA can determine the identity of the host machine, authenticate it, and allow that machine to edit its own DNS record. These changes are then stored in the LDAP back end.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Using this authentication system means that each IPA client can only edit its own DNS record; it cannot edit the DNS record of any other client.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="id462811">Setting up Dynamic DNS Updates</h5>
+ The SSSD configuration file provides two options used for setting up dynamic DNS updates: <code class="option">ipa_dyndns_update</code>, used to enable dynamic DNS updates; and <code class="option">ipa_dyndns_iface</code>, which specifies the interface whose IP address should be used for dynamic DNS updates.
+ </div><div class="para">
+ Refer to the <em class="citetitle">sssd-ipa</em> manual page for more information about these options, and how to configure dynamic DNS updates.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Support for dynamic DNS updates is only available on IPA version 2 or later, and with DNS correctly configured.
+ </div></div></div></div></div></div><div class="section" title="8.2.3. Setting Up SSSD" id="chap-SSSD_User_Guide-Setting_Up_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="chap-SSSD_User_Guide-Setting_Up_SSSD">8.2.3. Setting Up SSSD</h3></div></div></div><div class="para">
+ This section describes how to install SSSD, how to run the service, and how to configure it for each type of supported information provider.
+ </div><div class="section" title="8.2.3.1. Installing SSSD" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Installing_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Installing_SSSD">8.2.3.1. Installing SSSD</h4></div></div></div><div class="para">
+ Run the following command to install SSSD and any dependencies, including the SSSD client:
+ </div><div class="para">
+ <code class="command"># yum install sssd</code>
+ </div><div class="para">
+ SSSD requires very few dependencies and should install very quickly, depending on the speed of your network connection.
+ </div><div class="section" title="8.2.3.1.1. Upgrading from a Previous Version" id="sect-SSSD_User_Guide-Installing_SSSD-Upgrading_from_a_Previous_Version"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Installing_SSSD-Upgrading_from_a_Previous_Version">8.2.3.1.1. Upgrading from a Previous Version</h5></div></div></div><div class="formalpara" id="form-SSSD_User_Guide-Upgrading_from_a_Previous_Version-Upgrading_Using_RPM_Packages"><h5 class="formalpara">Upgrading Using RPM Packages</h5>
+ If you are upgrading using RPM packages, the script will run automatically when you upgrade to the new version. This will upgrade the <code class="filename">/etc/sssd/sssd.conf</code> file to the new format, and copy the existing version to <code class="filename">/etc/sssd/sssd.conf.bak</code>.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Upgrading_from_a_Previous_Version-Upgrading_Manually"><h5 class="formalpara">Upgrading Manually</h5>
+ It may be necessary to run the upgrade script manually, either because you built SSSD from source files, or because you are using a platform that does not support the use of RPM packages. The synopsis for the script is as follows:
+ </div><div class="cmdsynopsis"><p><code class="command">upgrade_config.py</code> [
+ -f INFILE
+ ] [
+ -o OUTFILE
+ ] [
+ -verbose
+ ] [
+ --no-backup
+ ]</p></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>-f INFILE</code></em> — the configuration file to upgrade. If not specified, this defaults to <code class="filename">/etc/sssd/sssd.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>-o OUTFILE</code></em> — the name of the upgraded configuration file. If not specified, this defaults to <code class="filename">/etc/sssd/sssd.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>-verbose</code></em> — produce more verbose output during the upgrade process
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>--no-backup</code></em> — do not produce a back-up file. If not specified, this defaults to <code class="filename"><em class="parameter"><code>INFILE</code></em>.bak</code>
+ </div></li></ul></div></div><div class="section" title="8.2.3.1.2. Starting and Stopping SSSD" id="sect-SSSD_User_Guide-Installing_SSSD-Starting_and_Stopping_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Installing_SSSD-Starting_and_Stopping_SSSD">8.2.3.1.2. Starting and Stopping SSSD</h5></div></div></div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Before you start SSSD for the first time, you need to configure at least one domain. Refer to <a class="xref" href="#chap-SSSD_User_Guide-Configuring_Domains" title="8.2.5. Configuring Domains">Section 8.2.5, “Configuring Domains”</a> for information on how to configure an SSSD domain.
+ </div></div></div><div class="para">
+ You can use either the <code class="command">service</code> command or the <code class="filename">/etc/init.d/sssd</code> script to control SSSD. For example, run the following command to start <code class="systemitem">sssd</code>:
+ </div><div class="para">
+ <code class="command"># service sssd start</code>
+ </div><div class="para">
+ By default, SSSD is configured not to start automatically. There are two ways to change this behavior; if you use the Authentication Configuration tool to configure SSSD, it will reconfigure the default behavior so that SSSD starts when the machine boots. Alternatively, you can use the <code class="command">chkconfig</code> command, as follows:
+ </div><div class="para">
+ <code class="command"># chkconfig sssd on</code>
+ </div></div></div><div class="section" title="8.2.3.2. Configuring SSSD" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Configuring_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Configuring_SSSD">8.2.3.2. Configuring SSSD</h4></div></div></div><div class="para">
+ The global configuration of SSSD is stored in the <code class="filename">/etc/sssd/sssd.conf</code> file. This file consists of various sections, each of which contains a number of key/value pairs. Some keys accept multiple values; use commas to separate multiple values for such keys. This configuration file uses data types of <span class="type">string</span> (no quotes required), <span class="type">integer</span> and <span class="type">Boolean</span> (with values of <code class="literal">TRUE</code> or <code class="literal">FALSE</code>). Comments are indicated by either a hash sign (#) or a semicolon (;) in the first column. The following example illustrates some of this syntax:
+ </div><pre class="programlisting">[section]
+# Keys with single values
+key1 = value
+key2 = val2
+
+# Keys with multiple values
+key10 = val10,val11
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ You can use the <em class="parameter"><code>-c</code></em> (or <em class="parameter"><code>--config</code></em>) parameter on the command line to specify a different configuration file for SSSD.
+ </div></div></div><div class="para">
+ The format of the configuration file is described in <a class="xref" href="#sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format" title="8.2.8. SSSD Configuration File Format">Section 8.2.8, “SSSD Configuration File Format”</a>
+ </div><div class="para">
+ Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more information on global SSSD configuration options.
+ </div><div class="section" title="8.2.3.2.1. Configuring NSS" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS">8.2.3.2.1. Configuring NSS</h5></div></div></div><div class="para">
+ SSSD provides a new NSS module, <code class="systemitem">sssd_nss</code>, so that you can configure your system to use SSSD to retrieve user information. Edit the <code class="filename">/etc/nsswitch.conf</code> file for your system to use the <code class="systemitem">sss</code> name database. For example:
+ </div><pre class="programlisting">passwd: files sss
+group: files sss
+</pre></div><div class="section" title="8.2.3.2.2. Configuring PAM" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM">8.2.3.2.2. Configuring PAM</h5></div></div></div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Use extreme care when changing your PAM configuration. A mistake in the PAM configuration file can lock you out of the system completely. Always back up your configuration files before performing any changes, and keep a session open so that you can revert any changes you make should the need arise.
+ </div></div></div><div class="para">
+ To enable your system to use SSSD for PAM, you need to edit the default PAM configuration file. On Fedora—based systems, this is the <code class="filename">/etc/pam.d/system-auth</code> file. Edit this file to reflect the following example, and then restart <code class="systemitem">sssd</code>:
+ </div><pre class="programlisting">#%PAM-1.0
+# This file is auto-generated.
+# User changes will be destroyed the next time authconfig is run.
+auth required pam_env.so
+auth sufficient pam_unix.so nullok try_first_pass
+auth requisite pam_succeed_if.so uid >= 500 quiet
+auth sufficient pam_sss.so use_first_pass
+auth required pam_deny.so
+
+account required pam_unix.so broken_shadow
+account sufficient pam_localuser.so
+account sufficient pam_succeed_if.so uid < 500 quiet
+account [default=bad success=ok user_unknown=ignore] pam_sss.so
+account required pam_permit.so
+
+password requisite pam_cracklib.so try_first_pass retry=3
+password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok
+password sufficient pam_sss.so use_authtok
+password required pam_deny.so
+
+session required pam_mkhomedir.so umask=0022 skel=/etc/skel/
+session optional pam_keyinit.so revoke
+session required pam_limits.so
+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
+session sufficient pam_sss.so
+session required pam_unix.so
+</pre><div class="section" title="8.2.3.2.2.1. Using Custom Home Directories with SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="id465044">8.2.3.2.2.1. Using Custom Home Directories with SSSD</h6></div></div></div><div class="para">
+ If your LDAP users have home directories that are not in <code class="filename">/home</code>, and if your system is configured to create home directories the first time your users log in, then these directories will be created with the wrong permissions. For example, instead of a typical home directory such as <code class="filename">/home/<username></code>, your users might have home directories that include their locale, such as <code class="filename">/home/<locale>/<username></code>. If this is true for your system, the following steps need to be taken (preemptively):
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Apply the correct SELinux context and permissions from the <code class="filename">/home</code> directory to the home directory that you use on your system. In the example above, the following command would achieve this result (replace the directory names with those that apply to your system):
+<pre class="screen"># semanage fcontext -a -e /home /home/locale</pre>
+
+ </div></li><li class="listitem"><div class="para">
+ Ensure the <span class="package">oddjob-mkhomedir</span> package is installed on your system and then re-run the Authentication Configuration tool.
+ </div><div class="para">
+ This package provides the <code class="systemitem">pam_oddjob_mkhomedir.so</code> library, which the Authentication Configuration tool will then use to create your custom home directories. You need to use this library to create your home directories, and not the default <code class="systemitem">pam_mkhomedir.so</code> library, because the latter cannot create SELinux labels.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The Authentication Configuration tool will automatically use the <code class="systemitem">pam_oddjob_mkhomedir.so</code> library if it is available. Otherwise, it will default to using <code class="systemitem">pam_mkhomedir.so</code>.
+ </div></div></div></li></ol></div><div class="para">
+ If the preceding steps were not performed before the custom home directories were created, you can use the following commands to correct the permissions and SELinux contexts (again, replace the directory names with those that apply to your system):
+<pre class="screen"># semanage fcontext -a -e /home /home/locale
+# restorecon -R -v /home/locale</pre>
+
+ </div></div><div class="section" title="8.2.3.2.2.2. Using "include" Statements in PAM Configurations" id="form-SSSD_User_Guide-Configuring_PAM-Using_include_Statements_in_PAM_Configurations"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="form-SSSD_User_Guide-Configuring_PAM-Using_include_Statements_in_PAM_Configurations">8.2.3.2.2.2. Using "include" Statements in PAM Configurations</h6></div></div></div><div class="para">
+ Recent PAM implementations allow you to use <code class="literal">include</code> statements in PAM configurations. For example:
+ </div><pre class="programlisting">...
+session include system-auth
+session optional pam_console.so
+...
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ In the preceding example, if a <em class="parameter"><code>sufficient</code></em> condition from <code class="filename">system-auth</code> returns <span class="returnvalue">PAM_SUCCESS</span>, <code class="filename">pam_console.so</code> will not be executed.
+ </div></div></div></div></div><div class="section" title="8.2.3.2.3. Configuring Access Control"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id777113">8.2.3.2.3. Configuring Access Control</h5></div></div></div><a id="id437436" class="indexterm"></a><div class="para">
+ SSSD provides a rudimentary access control mechanism, offering two solutions based on the value of the <code class="option">access_provider</code> option in the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> section in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="section" title="8.2.3.2.3.1. The Simple Access Provider"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="id734737">8.2.3.2.3.1. The Simple Access Provider</h6></div></div></div><div class="para">
+ The first of these solutions is known as the <em class="firstterm">Simple Access Provider</em>, and is based on the implementation of access or deny lists of usernames. To enable the Simple Access Provider, you need to set the <code class="option">access_provider</code> option to <code class="literal">simple</code>, and then add usernames as a comma-separated list to either the <code class="option">simple_allow_users</code> or <code class="option">simple_deny_users</code> options.
+ </div><div class="formalpara"><h5 class="formalpara" id="id439165">Using the Simple Access Provider</h5>
+ By using the Simple Access Provider, you can continue to support a number of network logins to maintain common network accounts on company or department laptops, but you might want to restrict the use of a particular laptop to one or two users. This means that even if a different user authenticated successfully against the same authentication provider, the Simple Access Provider would prevent that user from gaining access.
+ </div><div class="para">
+ The following example demonstrates the use of the Simple Access Provider to grant access to two users. This example assumes that SSSD is correctly configured and <code class="systemitem">example.com</code> is one of the domains specified in the <code class="literal">[sssd]</code> section, and only shows the Simple Access Provider-specific options.
+ </div><pre class="screen">[domain/example.com]
+access_provider = simple
+simple_allow_users = user1, user2</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The Local ID provider does not support <code class="option">simple</code> as an access provider.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="id675109">Access Control Rules</h5><a id="id558438" class="indexterm"></a>
+ The Simple Access Provider adheres to the following three rules to determine which users should or should not be granted access:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If both lists are empty, access is granted.
+ </div></li><li class="listitem"><div class="para">
+ If <code class="option">simple_allow_users</code> is set, only users from this list are allowed access. This setting supersedes the <code class="option">simple_deny_users</code> list (which would be redundant).
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="option">simple_allow_users</code> list is empty, users are allowed access unless they appear in the <code class="option">simple_deny_users</code> list.
+ </div></li></ul></div>
+ <div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Defining both <code class="option">simple_allow_users</code> and <code class="option">simple_deny_users</code> is a configuration error. If this occurs, SSSD will output an error to the <code class="filename">/var/log/sssd/sssd_default.log</code> log file when loading the back end, but continue to start normally. Future versions of SSSD will output an error and fail to start.
+ </div></div></div>
+
+ </div></div><div class="section" title="8.2.3.2.3.2. The LDAP Access Provider"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="id582795">8.2.3.2.3.2. The LDAP Access Provider</h6></div></div></div><div class="para">
+ The second access control solution uses the LDAP server itself as the access provider (<code class="option">access_provider=ldap</code>) and the associated filter option (<code class="option">ldap_access_filter</code>) to specify which users are granted access to the specified host. Note that these two options are codependent; if you use LDAP as your access provider then you must specify a value for the <code class="option">ldap_access_filter</code> option, otherwise all users will be denied access. If you are not using LDAP as your access provider, then the <code class="option">ldap_access_filter</code> option has no effect.
+ </div><div class="formalpara"><h5 class="formalpara" id="id735098">Using the LDAP Access Provider</h5>
+ The following example demonstrates the use of the LDAP Access Provider to grant access to members of the "allowedusers" group in LDAP. This example assumes that SSSD is correctly configured and <code class="systemitem">example.com</code> is one of the domains specified in the <code class="literal">[sssd]</code> section, and only shows the LDAP Access Provider-specific options.
+ </div><pre class="screen">[domain/example.com]
+access_provider = ldap
+ldap_access_filter = memberOf=cn=allowedusers,ou=Groups,dc=example,dc=com</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Offline caching for this feature is limited to determining whether or not the user's last online login attempt was successful. If they were granted access during their last login, they will continue to be granted access while offline, and vice-versa.
+ </div></div></div><div class="para">
+ Refer to the <em class="citetitle">sssd-ldap</em> manual page for more information about using the LDAP Access Provider.
+ </div></div></div><div class="section" title="8.2.3.2.4. Configuring Failover" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover">8.2.3.2.4. Configuring Failover</h5></div></div></div><div class="para">
+ The failover feature allows back ends to automatically switch to a different server if the primary server fails. These servers are entered as a case-insensitive, comma-separated list in the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> sections of the <code class="filename">/etc/sssd/sssd.conf</code> file, and listed in order of preference. This list can contain any number of servers.
+ </div><div class="para">
+ For example, if you have configured a native LDAP domain, you could specify the following as your <em class="parameter"><code>ldap_uri</code></em> values:
+ </div><pre class="screen">ldap_uri = ldap://ldap0.mydomain.org, ldap://ldap1.mydomain.org, ldap://ldap2.mydomain.org</pre><div class="para">
+ In this configuration, <code class="uri">ldap://ldap0.mydomain.org</code> functions as the primary server. If this server fails, the SSSD failover mechanism first attempts to connect to <code class="uri">ldap1.mydomain.org</code>, and if that server is unavailable, it then attempts to connect to <code class="uri">ldap2.mydomain.org</code>.
+ </div><div class="para">
+ If the parameter that specifies which server to connect to for the specific domain (for example, <em class="parameter"><code>ldap_uri</code></em>, <em class="parameter"><code>krb5_kdcip</code></em>, …) is not specified, the back end defaults to using <em class="replaceable"><code>Use service discovery</code></em>. Refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover" title="8.2.3.2.4.1. Using SRV Records with Failover">Section 8.2.3.2.4.1, “Using SRV Records with Failover”</a> for more information on service discovery.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Do not use multiple <em class="parameter"><code>ldap_uri</code></em> parameters to specify your failover servers. The failover servers must be entered as a comma-separated list of values for a single <em class="parameter"><code>ldap_uri</code></em> parameter. If you enter multiple <em class="parameter"><code>ldap_uri</code></em> parameters, SSSD only recognizes the last entry.
+ </div><div class="para">
+ Future versions of SSSD will throw an error upon receiving additional <em class="parameter"><code>ldap_uri</code></em> entries.
+ </div></div></div><div class="section" title="8.2.3.2.4.1. Using SRV Records with Failover" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">8.2.3.2.4.1. Using SRV Records with Failover</h6></div></div></div><div class="para">
+ SSSD also supports the use of SRV records in its failover configuration. This means that you can specify a server that is later resolved into a list of specific servers using SRV requests. The <em class="parameter"><code>priority</code></em> and <em class="parameter"><code>weight</code></em> attributes of SRV records provide further opportunity for specifying which servers should be contacted first in the event that the primary server fails.
+ </div><div class="para">
+ For every service with which you want to use service discovery, you need to add a special DNS record to your DNS server using the following form:
+ </div><pre class="screen">_<em class="replaceable"><code>service</code></em>._<em class="replaceable"><code>protocol</code></em>._<em class="replaceable"><code>domain TTL priority weight port hostname</code></em></pre><div class="para">
+ A typical configuration would contain multiple such records, each with a different priority (for failover) and different weights (for load balancing).
+ </div><div class="para">
+ The client then makes an SRV DNS query to retrieve a list of host names, their priorities, and weights. These queries are of the form _<em class="replaceable"><code>service</code></em>._<em class="replaceable"><code>protocol</code></em>._<em class="replaceable"><code>domain</code></em>, for example, <code class="literal">_ldap._tcp._redhat.com</code>. The client then sorts this list according to the priorities and weights, and connects to the first server in this sorted list.
+ </div><div class="para">
+ For more information on SRV records, refer to <a href="http://tools.ietf.org/html/rfc2782">RFC 2782</a>.
+ </div></div><div class="section" title="8.2.3.2.4.2. How the Failover Mechanism Works" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-How_the_Failover_Mechanism_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-How_the_Failover_Mechanism_Works">8.2.3.2.4.2. How the Failover Mechanism Works</h6></div></div></div><div class="para">
+ The failover mechanism distinguishes between machines and services. The back end first tries to resolve the hostname of a given machine; if this resolution attempt fails, the machine is considered offline. No further attempts are made to connect to this machine for any other service. If the resolution attempt succeeds, the back end tries to connect to a service on this machine. If the service connection attempt fails, then only this particular service is considered offline and the back end automatically switches over to the next service. The machine is still considered online and might still be tried for another service.
+ </div><div class="para">
+ The failover mechanism does not handle DNS A records with multiple IP addresses; instead it only uses the first address. DNS round-robin cannot be used for failover. Further, providing multiple A records does not provide failover. Only the first A record is used, and if a lookup attempt on the first record fails then the system attempts no further lookups. To find multiple servers with a single request, and thus implementing failover, SSSD relies on SRV resource records, as explained in <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover" title="8.2.3.2.4.1. Using SRV Records with Failover">Section 8.2.3.2.4.1, “Using SRV Records with Failover”</a>.
+ </div><div class="para">
+ Further connection attempts are made to machines or services marked as offline after a specified period of time; this is currently hard coded to 30 seconds. If there are no more machines to try, the back end as a whole switches to offline mode, and then attempts to reconnect every 30 seconds.
+ </div></div></div></div></div><div class="section" title="8.2.4. Configuring Services" id="chap-SSSD_User_Guide-Configuring_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="chap-SSSD_User_Guide-Configuring_Services">8.2.4. Configuring Services</h3></div></div></div><div class="para">
+ Individual pieces of SSSD functionality are provided by special SSSD services that are started and stopped together with SSSD. The services provided by SSSD have their own configuration sections. The <code class="literal">[sssd]</code> section also lists the services that are active and should be started when <code class="systemitem">sssd</code> starts within the <code class="command">services</code> directive.
+ </div><div class="para">
+ SSSD currently provides several services:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">NSS</code> — An NSS provider service that answers NSS requests from the <code class="systemitem">sssd_nss</code> module.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">PAM</code> — A PAM provider service that manages a PAM conversation through the <code class="systemitem">sssd_pam</code> PAM module.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">monitor</code> — A special service that monitors all other SSSD services, and starts or restarts them as needed. Its options are specified in the <code class="literal">[sssd]</code> section of the <code class="filename">/etc/sssd/sssd.conf</code> configuration file.
+ </div></li></ul></div><div class="section" title="8.2.4.1. Configuration Options" id="sect-SSSD_User_Guide-Configuring_Services-Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Configuring_Services-Configuration_Options">8.2.4.1. Configuration Options</h4></div></div></div><div class="para">
+ The following sections cover the most important SSSD configuration options. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page that ships with SSSD for information on all the available configuration options.
+ </div><div class="section" title="8.2.4.1.1. General Configuration Options" id="sect-SSSD_User_Guide-Configuration_Options-General_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuration_Options-General_Configuration_Options">8.2.4.1.1. General Configuration Options</h5></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">debug_level <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Sets the debug level for a particular service. This is a per-service setting (that is, it can appear in any of the <code class="literal">[service/<NAME>]</code> sections in the SSSD configuration file).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">reconnection_retries <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ In the event of a data provider crash or restart, this specifies the number of times that a service should attempt to reconnect.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If a <code class="systemitem">DNS</code> lookup fails to return an <code class="systemitem">IPv4</code> address for a hostname, SSSD attempts to look up an <code class="systemitem">IPv6</code> address before returning a failure. Note that this only ensures that the async resolver identifies the correct address; there is currently a bug in the LDAP code that prevents SSSD from connecting to an LDAP server over IPv6. This is being investigated separately.
+ </div></div></div></li></ul></div></div><div class="section" title="8.2.4.1.2. NSS Configuration Options" id="sect-SSSD_User_Guide-Configuration_Options-NSS_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuration_Options-NSS_Configuration_Options">8.2.4.1.2. NSS Configuration Options</h5></div></div></div><div class="para">
+ Use the following options to configure the <code class="systemitem">Name Service Switch (NSS)</code> service. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for full details about each option.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">enum_cache_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long (in seconds) <span class="package">sssd_nss</span> should cache enumerations (requests for information about all users).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_cache_nowait_percentage <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long <span class="package">sssd_nss</span> should return cached entries before initiating an out-of-band cache refresh (<code class="literal">0</code> disables this feature).
+ </div><div class="para">
+ You can configure the entry cache to automatically update entries in the background if they are requested beyond a percentage of the <code class="option">entry_cache_timeout</code> value for the domain.
+ </div><div class="para">
+ Valid values for this option are <code class="literal">0-99</code>, and represent a percentage of the <code class="option">entry_cache_timeout</code> value for each domain.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_negative_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long (in seconds) <span class="package">sssd_nss</span> should cache negative cache hits (that is, queries for invalid database entries, such as nonexistent ones) before asking the back end again.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">filter_users, filter_groups <span class="type">(string)</span> </code>
+ </div><div class="para">
+ Exclude certain users from being fetched from the sss NSS database. This is particularly useful for system accounts such as <code class="systemitem">root</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">filter_users_in_groups <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ If set to <code class="literal">TRUE</code>, specifies that users listed in the <code class="option">filter_users</code> list do not appear in group memberships when performing group lookups. If set to <code class="literal">FALSE</code>, group lookups return all users that are members of that group. If not specified, defaults to <code class="literal">TRUE</code>.
+ </div></li></ul></div></div><div class="section" title="8.2.4.1.3. PAM Configuration Options" id="sect-SSSD_User_Guide-Configuration_Options-PAM_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuration_Options-PAM_Configuration_Options">8.2.4.1.3. PAM Configuration Options</h5></div></div></div><div class="para">
+ Use the following options to configure the <code class="systemitem">Pluggable Authentication Module (<acronym class="acronym">PAM</acronym>)</code> service.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">offline_credentials_expiration <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ If the authentication provider is offline, specifies for how long to allow cached log-ins (in days). This value is measured from the last successful online log-in. If not specified, defaults to <code class="literal">0</code> (no limit).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">offline_failed_login_attempts <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ If the authentication provider is offline, specifies how many failed log in attempts are allowed. If not specified, defaults to <code class="literal">0</code> (no limit).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">offline_failed_login_delay <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the time in minutes after the value of <code class="option">offline_failed_login_attempts</code> has been reached before a new log in attempt is possible.
+ </div><div class="para">
+ If set to <code class="literal">0</code>, the user cannot authenticate offline if the value of <code class="option">offline_failed_login_attempts</code> has been reached. Only a successful online authentication can re-enable offline authentication. If not specified, defaults to <code class="literal">5</code>.
+ </div></li></ul></div></div></div></div><div class="section" title="8.2.5. Configuring Domains" id="chap-SSSD_User_Guide-Configuring_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="chap-SSSD_User_Guide-Configuring_Domains">8.2.5. Configuring Domains</h3></div></div></div><div class="para">
+ A domain is a database of user information. SSSD can use more than one domain at the same time, but at least one must be configured for SSSD to start. Using SSSD domains, it is possible to use several LDAP servers providing several unique namespaces. You can specify not only where users' identity information is stored, but how users authenticate against each of the specified domains.
+ </div><div class="para">
+ SSSD supports the following identity and authentication combinations:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a class="link" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain" title="8.2.5.2. Configuring an LDAP Domain">LDAP/LDAP</a>
+ </div><div class="para">
+ This combination uses an LDAP back end as both the identity and authentication provider.
+ </div></li><li class="listitem"><div class="para">
+ <a class="link" href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication" title="8.2.6. Setting Up Kerberos Authentication">LDAP/KRB5</a>
+ </div><div class="para">
+ This combination uses an LDAP back end as the identity provider, and uses Kerberos to provide authentication.
+ </div></li><li class="listitem"><div class="para">
+ proxy
+ </div><div class="para">
+ Specifying a proxy identity or authentication provider uses an existing NSS library or customized PAM stack, but takes advantage of the SSSD caching mechanism.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The following example assumes that SSSD is correctly configured and FOO is one of the domains in the <code class="literal">[sssd]</code> section. This example shows only the configuration of Kerberos authentication; it does not include any identity provider.
+ </div><pre class="screen">[domain/FOO]
+auth_provider = krb5
+krb5_kdcip = 192.168.1.1
+krb5_realm = EXAMPLE.COM</pre><div class="section" title="8.2.5.1. Domain Configuration Options" id="sect-SSSD_User_Guide-Configuring_Domains-Domain_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Domain_Configuration_Options">8.2.5.1. Domain Configuration Options</h4></div></div></div><div class="para">
+ You can add new domain configurations to the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> sections of the <code class="filename">/etc/sssd/sssd.conf</code> file, and then add the list of domains to the <em class="parameter"><code>domains</code></em> attribute of the <code class="literal">[sssd]</code> section, in the order you want them to be queried.
+ </div><div class="section" title="8.2.5.1.1. General Domain Configuration Options" id="sect-SSSD_User_Guide-Domain_Configuration_Options-General_Domain_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Domain_Configuration_Options-General_Domain_Configuration_Options">8.2.5.1.1. General Domain Configuration Options</h5></div></div></div><div class="para">
+ You can use the following configuration options in a domain configuration section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">min_id,max_id <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the UID and GID limits for the domain. If a domain contains entries that are outside these limits, they are ignored.
+ </div><div class="para">
+ The default value for <code class="option">min_id</code> is <code class="literal">1</code>; the default value for <code class="option">max_id</code> is <code class="literal">0</code> (unbounded).
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If <code class="option">min_id</code> is unspecified, it defaults to <code class="literal">1</code> for any back end. This default was chosen to provide compatibility with existing systems and to ease any migration attempts. LDAP administrators should be aware that granting identities in this range may conflict with users in the local <code class="filename">/etc/passwd</code> file. To avoid these conflicts, <code class="option">min_id</code> should be set to <code class="literal">1000</code> or higher wherever possible.
+ </div><div class="para">
+ The <code class="option">min_id</code> option determines the minimum acceptable value for both UID and GID numbers. Accounts with either UID or GID values below the <code class="option">min_id</code> value are filtered out and not made available on the client.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">enumerate <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not to enumerate (list) the users and groups of a domain.
+ </div><div class="para">
+ Enumeration means that the entire set of available users and groups on the remote source is cached on the local machine. When enumeration is disabled, users and groups are only cached as they are requested. For performance reasons, it is recommended that you disable enumeration for domains with many users and groups.
+ </div><div class="para">
+ The default value for this parameter is <code class="literal">FALSE</code>. Set this value to <code class="literal">TRUE</code> to enable enumeration of users and groups of a domain.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the timeout in seconds for this particular domain.
+ </div><div class="para">
+ This is used to ensure that the backend process is alive and capable of answering requests. The default value for this parameter is <code class="literal">10</code> seconds. Raising this timeout might prove useful for slower back ends, such as distant LDAP servers.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you set <code class="option">timeout = 0</code>, SSSD reverts to the default value; you cannot force a timeout value of zero, because this would force the <code class="systemitem">sssd</code> daemon into a loop.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">cache_credentials <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not to store user credentials in the local SSSD domain database cache.
+ </div><div class="para">
+ The default value for this parameter is <code class="literal">FALSE</code>. You should set this value to <code class="literal">TRUE</code> for domains other than local if you want to enable offline authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">id_provider <span class="type">(string)</span> </code>
+ </div><div class="para">
+ Specifies the data provider identity back end to use for this domain. Currently supported identity back ends are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ proxy — Support a legacy <code class="systemitem">NSS</code> provider (for example, <span class="package">nss_nis</span>).
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ SSSD needs to know which legacy NSS library to load in order to start successfully. If you set <code class="option">id_provider</code> to <code class="literal">proxy</code>, ensure that you also specify a value for <code class="option">proxy_lib_name</code>. Refer to <a class="xref" href="#sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain" title="8.2.5.4. Configuring a Proxy Domain">Section 8.2.5.4, “Configuring a Proxy Domain”</a> for information on this attribute.
+ </div></div></div></li><li class="listitem"><div class="para">
+ local — <code class="systemitem">SSSD</code> internal local provider.
+ </div></li><li class="listitem"><div class="para">
+ ldap — <code class="systemitem">LDAP</code> provider.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_cache_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long the domain's data provider should cache positive cache hits (that is, queries for valid database entries) before asking the database again.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">use_fully_qualified_names <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not requests to this domain require fully-qualified domain names.
+ </div><div class="para">
+ If set to <code class="literal">TRUE</code>, all requests to this domain must use fully-qualified domain names. It also means that the output from the request displays the fully-qualified name.
+ </div><div class="para">
+ The ability to restrict requests in this way means that if you know you have multiple domains with conflicting usernames, then there is no doubt about which username the query will resolve.
+ </div><div class="para">
+ Consider the following examples, in which the IPA domain database contains a user named <code class="systemitem">ipauser01</code>, and the <em class="parameter"><code>use_fully_qualified_names</code></em> attribute is set to <code class="literal">TRUE</code>:
+ </div><pre class="screen">
+<code class="command"># getent passwd ipauser01</code>
+[no output]
+<code class="command"># getent passwd ipauser01 at IPA</code>
+ipauser01 at IPA:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+</pre><div class="para">
+ In the following examples, using the same IPA domain and user, the <em class="parameter"><code>use_fully_qualified_names</code></em> attribute is set to <code class="literal">FALSE</code>:
+ </div><pre class="screen">
+<code class="command"># getent passwd ipauser01</code>
+ipauser01:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+<code class="command"># getent passwd ipauser01 at IPA</code>
+ipauser01:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If <em class="parameter"><code>use_fully_qualified_names</code></em> is set to <code class="literal">FALSE</code>, you can continue to use the fully-qualified name in your requests, but only the simplified version is displayed in the output.
+ </div><div class="para">
+ SSSD can only parse <code class="systemitem">name at domain</code>, not <code class="systemitem">name at realm</code>. You can, however, use the same name for both your domain and your realm.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">auth_provider <span class="type">(string)</span> </code>
+ </div><div class="para">
+ The authentication provider used for the domain. The default value for this option is the value of <code class="option">id_provider</code> if it is set and can handle authentication requests.
+ </div><div class="para">
+ Currently supported authentication providers are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ldap — for native LDAP authentication. Refer to the sssd-ldap(5) manual page for more information on configuring LDAP.
+ </div></li><li class="listitem"><div class="para">
+ krb5 — for Kerberos authentication. Refer to the sssd-krb5(5) manual page for more information on configuring Kerberos.
+ </div></li><li class="listitem"><div class="para">
+ proxy — for relaying authentication to some other PAM target.
+ </div></li><li class="listitem"><div class="para">
+ none — explicitly disables authentication.
+ </div></li></ul></div>
+
+ </div></li></ul></div></div><div class="section" title="8.2.5.1.2. Proxy Configuration Options" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Proxy_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Proxy_Configuration_Options">8.2.5.1.2. Proxy Configuration Options</h5></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">proxy_pam_target</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">auth_provider</code> option is set to <code class="literal">proxy</code>, and specifies the target to which <acronym class="acronym">PAM</acronym> must proxy.
+ </div><div class="para">
+ This option has no default value. If proxy authentication is required, you need to specify your own <acronym class="acronym">PAM</acronym> target. This corresponds to a file containing <acronym class="acronym">PAM</acronym> stack information in the system's default <acronym class="acronym">PAM</acronym> configuration directory. On Fedora-based systems, this is the <code class="filename">/etc/pam.d/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">proxy_lib_name</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">id_provider</code> option is set to <code class="literal">proxy</code>, and specifies which existing NSS library to proxy identity requests through.
+ </div><div class="para">
+ This option has no default value. You need to manually specify an existing library to take advantage of this option. For example, set this value to <code class="literal">nis</code> to use the existing <code class="filename">libnss_nis.so</code> file.
+ </div></li></ul></div></div></div><div class="section" title="8.2.5.2. Configuring an LDAP Domain" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">8.2.5.2. Configuring an LDAP Domain</h4></div></div></div><a id="id531425" class="indexterm"></a><div class="para">
+ An LDAP domain is one where the <code class="option">id_provider</code> option is set to <code class="literal">ldap</code> (<code class="option">id_provider = ldap</code>). Such a domain requires a running LDAP server against which to authenticate. This can be an open source LDAP server such as OpenLDAP or Microsoft Active Directory. SSSD currently supports Microsoft Active Directory 2003 (+Services For UNIX) and Active Directory 2008 (+Subsystem for UNIX-based applications). In all cases, the client configuration is stored in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-How_to_Authenticate_Against_an_LDAP_Server"><h5 class="formalpara">How to Authenticate Against an LDAP Server</h5>
+ SSSD does not support authentication over an unencrypted channel. Consequently, if you want to authenticate against an LDAP server, either <code class="systemitem">TLS/SSL</code>, <code class="systemitem">LDAPS</code>, or <code class="systemitem">LDAP+GSSAPI</code> is required. If the LDAP server is used only as an identity provider, an encrypted channel is not needed.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file to reflect the following example:
+ </div><pre class="screen"># A native LDAP domain
+[domain/LDAP]
+enumerate = false
+cache_credentials = TRUE
+
+id_provider = ldap
+auth_provider = ldap
+ldap_schema = rfc2307
+chpass_provider = ldap
+
+ldap_uri = ldap://ldap.mydomain.org
+ldap_search_base = dc=mydomain,dc=org
+tls_reqcert = demand
+ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
+</pre><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-Selecting_an_LDAP_Schema"><h5 class="formalpara">Selecting an LDAP Schema</h5><a id="id597171" class="indexterm"></a>
+ You can set the <em class="parameter"><code>ldap_schema</code></em> attribute to either <code class="literal">rfc2307</code> or <code class="literal">rfc2307bis</code>. These schema define how groups in <acronym class="acronym">LDAP</acronym> are specified. In <em class="citetitle">RFC 2307</em>, group objects use a multi-valued attribute, <em class="parameter"><code>memberuid</code></em>, which lists the names of the users that belong to that group. In <em class="citetitle">RFC 2307bis</em>, instead of the <em class="parameter"><code>memberuid</code></em>, group objects use the <em class="parameter"><code>member</code></em> attribute. Rather than just the name of the user, this attribute contains the full Distinguished Name (DN) of another object in the LDAP database. This means that groups can have other groups as members. That is, it adds support for nested groups.
+ </div><div class="para">
+ SSSD assumes that your LDAP server is using <em class="citetitle">RFC 2307</em>. If your LDAP server is using <em class="citetitle">RFC 2307bis</em>, and you do not update the <code class="filename">/etc/sssd/sssd.conf</code> file accordingly, this can impact how your users and groups are displayed. It also means that some groups will not be available and network resources may be inaccessible even though you have permissions to use them.
+ </div><div class="para">
+ For example, when using <em class="citetitle">RFC 2307bis</em> and you have configured both primary and secondary groups, or are using nested groups, you can use the <code class="command">id</code> command to display these groups:
+ </div><pre class="screen">[f12server at ipaserver ~]$ id
+uid=500(f12server) gid=500(f12server) groups=500(f12server),510(f12tester)
+</pre><div class="para">
+ If instead you have configured your client to use <em class="citetitle">RFC 2307</em> then only the primary group is displayed.
+ </div><div class="para">
+ Changes to this setting only affect how SSSD determines the groups to which a user belongs; there is no negative effect on the actual user data. If you do not know the correct value for this attribute, consult your System Administrator.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-Specifying_Timeout_Values"><h5 class="formalpara">Specifying Timeout Values</h5><a id="id591918" class="indexterm"></a>
+ SSSD supports a number of timeout values that apply when configuring an <acronym class="acronym">LDAP</acronym> domain. These are described below.
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">ldap_search_timeout (integer)</code> — Specifies the timeout (in seconds) that <acronym class="acronym">LDAP</acronym> searches are allowed to run before they are cancelled and cached results are returned (and offline mode is entered). If not specified:
+ </div><div class="para">
+ Defaults to five when <code class="option">enumerate</code> = <code class="literal">False</code>
+ </div><div class="para">
+ Defaults to 30 when <code class="option">enumerate</code> = <code class="literal">True</code>. This option is forced to a minimum of 30 in this case.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This option is subject to change in future versions of SSSD, where it may be replaced by a series of timeouts for specific look-up types.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">ldap_network_timeout (integer)</code> — Specifies the timeout (in seconds) after which the <code class="function">poll(2)</code>/<code class="function">select(2)</code> following a <code class="function">connect(2)</code> returns in case of no activity.
+ </div><div class="para">
+ If not specified, defaults to five.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ldap_opt_timeout (integer)</code> — Specifies the timeout (in seconds) after which calls to synchronous <acronym class="acronym">LDAP</acronym> APIs will abort if no response is received. This option also controls the timeout when communicating with the KDC in case of a SASL bind.
+ </div><div class="para">
+ If not specified, defaults to five.
+ </div></li></ul></div>
+
+ </div></div><div class="section" title="8.2.5.3. Configuring a Microsoft Active Directory Domain" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain">8.2.5.3. Configuring a Microsoft Active Directory Domain</h4></div></div></div><a id="id428096" class="indexterm"></a><div class="para">
+ You can configure SSSD to use Microsoft Active Directory as an LDAP back end, providing both identity and authentication services. If you are using Active Directory 2003, SSSD requires that you install Windows Services for UNIX (SFU) on the machine where Active Directory is installed. If instead you are using Active Directory 2008, you need to install the Subsystem for UNIX-based Applications (SUA) on the Active Directory machine.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ SFU is not supported on 64-bit operating systems. Refer to <a href="http://support.microsoft.com/kb/920751">http://support.microsoft.com/kb/920751</a> for more information about which Windows systems can provide a suitable platform for an SSSD LDAP back end.
+ </div></div></div><div class="section" title="8.2.5.3.1. Configuring Active Directory 2003 as an LDAP Back End" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2003"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2003">8.2.5.3.1. Configuring Active Directory 2003 as an LDAP Back End</h5></div></div></div><div class="para">
+ The example <code class="filename">/etc/sssd/sssd.conf</code> file that ships with SSSD contains the following sample configuration for Active Directory 2003:
+ </div><pre class="screen"># Example LDAP domain where the LDAP server is an Active Directory 2003 server.
+
+[domain/AD]
+description = LDAP domain with AD server
+enumerate = false
+min_id = 1000
+;
+id_provider = ldap
+auth_provider = ldap
+ldap_uri = ldap://your.ad.server.com
+ldap_schema = rfc2307bis
+ldap_search_base = dc=example,dc=com
+ldap_default_bind_dn = cn=Administrator,cn=Users,dc=example,dc=com
+ldap_default_authtok_type = password
+ldap_default_authtok = YOUR_PASSWORD
+ldap_user_object_class = person
+ldap_user_name = msSFU30Name
+ldap_user_uid_number = msSFU30UidNumber
+ldap_user_gid_number = msSFU30GidNumber
+ldap_user_home_directory = msSFU30HomeDirectory
+ldap_user_shell = msSFU30LoginShell
+ldap_user_principal = userPrincipalName
+ldap_group_object_class = group
+ldap_group_name = msSFU30Name
+ldap_group_gid_number = msSFU30GidNumber</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This configuration is specific to Windows Active Directory 2003. Refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008" title="8.2.5.3.2. Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends">Section 8.2.5.3.2, “Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends”</a> for information on how to configure Active Directory 2003 R2 and Active Directory 2008.
+ </div></div></div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The above configuration assumes that the certificates are stored in the default location (that is, in <code class="filename">/etc/openldap/cacerts</code>) and that the <code class="function">c_rehash</code> function has been used to create the appropriate symlinks.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="id700111">More Information</h5>
+ Refer to the <em class="citetitle">sssd-ldap(5)</em> manual page for a full description of all the options that apply to <acronym class="acronym">LDAP</acronym> domains.
+ </div></div><div class="section" title="8.2.5.3.2. Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008">8.2.5.3.2. Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends</h5></div></div></div><div class="para">
+ The configuration of <code class="filename">/etc/sssd/sssd.conf</code> to support Active Directory 2003 R2 or Active Directory 2008 as a back end is similar to that for AD 2003. The following example configuration highlights the necessary changes.
+ </div><pre class="screen"># Example LDAP domain where the LDAP server is an Active Directory 2003 R2 or an Active Directory 2008 server.
+
+[domain/AD]
+description = LDAP domain with AD server
+; debug_level = 9
+enumerate = false
+
+id_provider = ldap
+auth_provider = ldap
+chpass_provider = ldap
+
+ldap_uri = ldap://your.ad.server.com
+ldap_tls_cacertdir = /etc/openldap/cacerts
+ldap_tls_cacert = /etc/openldap/cacerts/test.cer
+ldap_search_base = dc=example,dc=com
+ldap_default_bind_dn = cn=Administrator,cn=Users,dc=example,dc=com
+ldap_default_authtok_type = password
+ldap_default_authtok = YOUR_PASSWORD
+ldap_pwd_policy = none
+ldap_user_object_class = user
+ldap_group_object_class = group</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The above configuration assumes that the certificates are stored in the default location (that is, in <code class="filename">/etc/openldap/cacerts</code>) and that the <code class="function">c_rehash</code> function has been used to create the appropriate symlinks.
+ </div></div></div></div></div><div class="section" title="8.2.5.4. Configuring a Proxy Domain" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">8.2.5.4. Configuring a Proxy Domain</h4></div></div></div><a id="id464891" class="indexterm"></a><div class="para">
+ SSSD currently only supports LDAP and Kerberos as authentication providers. If you prefer to use SSSD (for example, to take advantage of its caching functionality), but SSSD does not support your authentication method, you can set up a proxy authentication provider. This could be the case if you use fingerprint scanners or smart cards as part of your authentication process.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">proxy_pam_target</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">auth_provider</code> option is set to <code class="literal">proxy</code>, and specifies the proxy target that <acronym class="acronym">PAM</acronym> proxies to.
+ </div><div class="para">
+ This option has no default value. If proxy authentication is required, you need to specify your own <acronym class="acronym">PAM</acronym> target. This corresponds to a file containing <acronym class="acronym">PAM</acronym> stack information in the system's default <acronym class="acronym">PAM</acronym> configuration directory. On Fedora—based systems, this is the <code class="filename">/etc/pam.d/</code> directory.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Ensure that your proxy PAM stack does <span class="emphasis"><em>not</em></span> recursively include <code class="filename">pam_sss.so</code>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">proxy_lib_name</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">id_provider</code> option is set to <code class="literal">proxy</code>, and specifies which existing NSS library to proxy identity requests through.
+ </div><div class="para">
+ This option has no default value. You need to manually specify an existing library to take advantage of this option. For example, set this value to <code class="literal">nis</code> to use the existing <code class="filename">libnss_nis.so</code> file.
+ </div></li></ul></div></div></div><div class="section" title="8.2.6. Setting Up Kerberos Authentication" id="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">8.2.6. Setting Up Kerberos Authentication</h3></div></div></div><a id="id1614674" class="indexterm"></a><div class="para">
+ In order to set up Kerberos authentication, you need to know the address of your <em class="firstterm">key distribution center</em> (KDC) and the Kerberos domain. The client configuration is then stored in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="para">
+ The Kerberos 5 authentication back end does not contain an identity provider and must be paired with one in order to function properly (for example, <code class="option">id_provider = ldap</code>). Some information required by the Kerberos 5 authentication back end must be supplied by the identity provider, such as the user's <em class="firstterm">Kerberos Principal Name</em> (UPN). The identity provider configuration should contain an entry to specify this UPN. Refer to the manual page for the applicable identity provider for details on how to configure the UPN.
+ </div><div class="para">
+ If the UPN is not available in the identity back end, SSSD will construct a UPN using the format <code class="systemitem">username at krb5_realm</code>.
+ </div><div class="para">
+ SSSD assumes that the Kerberos KDC is also a Kerberos kadmin server. However, it is very common for production environments to have multiple, read-only replicas of the KDC, but only a single kadmin server (because password changes and similar procedures are comparitively rare). To manage this type of configuration, you can use the <code class="option">krb5_kpasswd</code> option to specify where your password changing service is running, or if it is running on a non-default port. Refer to the <em class="citetitle">sssd-krb5(5)</em> manual page for more information about this and all Kerberos configuration options.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Setting_Up_Kerberos_Authentication-How_to_Set_up_Kerberos_Authentication"><h5 class="formalpara">How to Set Up Kerberos Authentication</h5>
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file to reflect the following example:
+ </div><pre class="screen"># A domain with identities provided by LDAP and authentication by Kerberos
+[domain/KRBDOMAIN]
+enumerate = false
+id_provider = ldap
+chpass_provider = krb5
+ldap_uri = ldap://ldap.mydomain.org
+ldap_search_base = dc=mydomain,dc=org
+tls_reqcert = demand
+ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
+
+auth_provider = krb5
+krb5_kdcip = 192.168.1.1
+krb5_realm = EXAMPLE.COM
+krb5_changepw_principal = kadmin/changepw
+krb5_ccachedir = /tmp
+krb5_ccname_template = FILE:%d/krb5cc_%U_XXXXXX
+krb5_auth_timeout = 15
+</pre><div class="para">
+ This example describes the minimum options that must be configured when using Kerberos authentication. Refer to the <em class="citetitle">sssd-krb5(5)</em> manual page for a full description of all the options that apply to configuring Kerberos authentication.
+ </div></div><div class="section" title="8.2.7. Troubleshooting" id="chap-SSSD_User_Guide-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="chap-SSSD_User_Guide-Troubleshooting">8.2.7. Troubleshooting</h3></div></div></div><div class="para">
+ This section lists some of the issues you may encounter when implementing SSSD, the possible causes of these issues, and how to resolve them. If you find further issues that are not covered here, refer to the <em class="citetitle">We Need Feedback</em> section in the <em class="citetitle">Preface</em> for information on how to file a bug report.
+ </div><div class="section" title="8.2.7.1. Using SSSD Log Files" id="sect-SSSD_User_Guide-Troubleshooting-Using_SSSD_Log_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Troubleshooting-Using_SSSD_Log_Files">8.2.7.1. Using SSSD Log Files</h4></div></div></div><div class="para">
+ SSSD uses a number of log files to report information about its operation, and this information can help to resolve issues in the event of SSSD failure or unexpected behavior. The default location for these log files on Fedora—based systems is the <code class="filename">/var/log/sssd/</code> directory.
+ </div><div class="para">
+ SSSD produces a log file for each back end (that is, one log file for each domain specified in the <code class="filename">/etc/sssd/sssd.conf</code> file), as well as an <code class="filename">sssd_pam.log</code> and an <code class="filename">sssd_nss.log</code> file. This level of granularity can help you to quickly isolate and resolve any errors or issues you might experience with SSSD.
+ </div><div class="para">
+ You should also examine the <code class="filename">/var/log/secure</code> file, which logs authentication failures and the reason for the failure. For example, if you see <span class="errortext">Reason 4: System Error</span> reported against any failure, you should increase the debug level of the log files.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Using_SSSD_Log_Files-Producing_More_Verbose_Log_Files"><h5 class="formalpara">Producing More Verbose Log Files</h5>
+ If you are unable to identify and resolve any problems with SSSD after inspection of the default log files, you can configure SSSD to produce more verbose files. You can set the <code class="option">debug_level</code> option in the <code class="filename">/etc/sssd/sssd.conf</code> for the domain that is causing concern, and then restart SSSD. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more information on how to set the <code class="option">debug_level</code> for a specific domain.
+ </div><div class="para">
+ All log files include timestamps on debug messages by default. This can make it easier to understand any errors that may occur, why they occurred, and how to address them. If necessary, you can disable these timestamps by setting the appropriate parameter to <code class="literal">FALSE</code> in the <code class="filename">/etc/sssd/sssd.conf</code> file:
+ </div><pre class="screen">--debug-timestamps=FALSE
+</pre></div><div class="section" title="8.2.7.2. Problems with SSSD Configuration" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Configuration">8.2.7.2. Problems with SSSD Configuration</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ SSSD fails to start
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ SSSD requires at least one properly configured domain before the service will start. Without such a domain, you might see the following error message when trying to start SSSD with the following command:
+ </div><div class="para">
+ <code class="command"># sssd -d4</code>
+ </div><pre class="screen">[sssd] [ldb] (3): server_sort:Unable to register control with rootdse!
+
+[sssd] [confdb_get_domains] (0): No domains configured, fatal error!
+[sssd] [get_monitor_config] (0): No domains configured.
+</pre><div class="para">
+ You can ignore the <span class="errortext">"Unable to register control with rootdse!"</span> message, as it is erroneous. The other messages, however, indicate that SSSD is unable to locate any properly configured domains.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file and ensure you have at least one properly configured domain, and then try to start SSSD.
+ </div></li><li class="listitem"><div class="para">
+ SSSD requires at least one available service provider before it will start. With no available service providers, you might see the following error message when trying to start SSSD with the following command:
+ </div><div class="para">
+ <code class="command"># sssd -d4</code>
+ </div><pre class="screen">[sssd] [ldb] (3): server_sort:Unable to register control with rootdse!
+
+[sssd] [get_monitor_config] (0): No services configured!
+</pre><div class="para">
+ You can ignore the <span class="errortext">"Unable to register control with rootdse!"</span> message, as it is erroneous. The other message, however, indicates that SSSD is unable to locate any available service providers.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file and ensure you have at least one available service providers, and then try to start SSSD.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ SSSD requires that service providers be configured as a comma-separated list in a single <em class="parameter"><code>services</code></em> entry in the <code class="filename">/etc/sssd/sssd.conf</code> file. If services are listed in multiple entries, only the last entry is recognized by SSSD.
+ </div></div></div></li><li class="listitem"><div class="para">
+ Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more options that might assist in troubleshooting issues with SSSD.
+ </div></li></ul></div></li></ul></div></div><div class="section" title="8.2.7.3. Problems with SSSD Service Configuration" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Service_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Service_Configuration">8.2.7.3. Problems with SSSD Service Configuration</h4></div></div></div><div class="section" title="8.2.7.3.1. Problems with NSS" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_NSS"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_NSS">8.2.7.3.1. Problems with NSS</h5></div></div></div><div class="para">
+ This section describes some common problems with <code class="systemitem">NSS</code>, their symptoms, and how to resolve them.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">NSS</code> fails to return user information
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Ensure that NSS is running
+ </div><div class="para">
+ <code class="command"># service sssd status</code>
+ </div><div class="para">
+ This command should return results similar to the following:
+ </div><pre class="screen">sssd (pid 21762) is running...
+</pre></li><li class="listitem"><div class="para">
+ Ensure that you have correctly configured the <code class="literal">[nss]</code> section of the <code class="filename">/etc/sssd/sssd.conf</code> file. For example, ensure that you have not misconfigured the <em class="parameter"><code>filter_users</code></em> or <em class="parameter"><code>filter_groups</code></em> attributes. Refer to the <em class="citetitle">NSS configuration options</em> section of the <em class="citetitle">sssd.conf(5)</em> manual page for information on how to configure these attributes.
+ </div></li><li class="listitem"><div class="para">
+ Ensure that you have included <code class="systemitem">nss</code> in the list of services that <code class="systemitem">sssd</code> should start
+ </div></li><li class="listitem"><div class="para">
+ Ensure that you have correctly configured the <code class="filename">/etc/nsswitch.conf</code> file. Refer to the section <a class="xref" href="#sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS" title="8.2.3.2.1. Configuring NSS">Section 8.2.3.2.1, “Configuring NSS”</a> for information on how to correctly configure this file.
+ </div></li></ul></div></li></ul></div></div><div class="section" title="8.2.7.3.2. Problems with PAM" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_PAM">8.2.7.3.2. Problems with PAM</h5></div></div></div><div class="para">
+ This section describes some common problems with <code class="systemitem">PAM</code>, their symptoms, and how to resolve them.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Setting the password for the local SSSD user prompts twice for the password
+ </div><div class="para">
+ When attempting to change a local SSSD user's password, you might see output similar to the following:
+ </div><pre class="screen">[root at clientF11 tmp]# passwd user1000
+Changing password for user user1000.
+New password:
+Retype new password:
+New Password:
+Reenter new Password:
+passwd: all authentication tokens updated successfully.
+</pre><div class="para">
+ This is the result of an incorrect PAM configuration. Refer to <a class="xref" href="#sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM" title="8.2.3.2.2. Configuring PAM">Section 8.2.3.2.2, “Configuring PAM”</a>, and ensure that the <em class="parameter"><code>use_authtok</code></em> option is correctly configured in your <code class="filename">/etc/pam.d/system-auth</code> file.
+ </div></li></ul></div></div><div class="section" title="8.2.7.3.3. Problems with NFS and NSCD"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id971123">8.2.7.3.3. Problems with NFS and NSCD</h5></div></div></div><div class="para">
+ SSSD is not designed to be used with the <code class="systemitem">nscd</code> daemon, and will likely generate warnings in the SSSD log files. Even though SSSD does not directly conflict with <code class="systemitem">nscd</code>, the use of both at the same time can result in unexpected behavior (specifically with how long entries are being cached).
+ </div><div class="para">
+ If you are using Network Manager to manage your network connections, it may take several minutes for the network interface to come up. During this time, various services will attempt to start. If these services start before the network is up (that is, the DNS servers cannot yet be reached) they will fail to identify the forward or reverse DNS entries they might need. These services will be reading an incorrect or possibly empty <code class="filename">resolv.conf</code> file. This file is typically only read once, and so any changes made to this file are not automatically applied.
+ </div><div class="para">
+ This can result in the failure of some system services, and in particular can cause NFS locking to fail on the machine where the <code class="systemitem">nscd</code> service is running, unless that service is manually restarted.
+ </div><div class="para">
+ One method of working around this problem is to enable caching for <em class="parameter"><code>hosts</code></em> and <em class="parameter"><code>services</code></em> in the <code class="filename">/etc/nscd.conf</code> file, and to rely on the SSSD cache for the <em class="parameter"><code>passwd</code></em> and <em class="parameter"><code>group</code></em> entries. With <code class="systemitem">nscd</code> answering <em class="parameter"><code>hosts</code></em> and <em class="parameter"><code>services</code></em> requests, these entries would have been cached and returned by <code class="systemitem">nscd</code> during the boot process.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Later versions of SSSD should negate any need for NSCD.
+ </div></div></div></div></div><div class="section" title="8.2.7.4. Problems with SSSD Domain Configuration" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Domain_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Domain_Configuration">8.2.7.4. Problems with SSSD Domain Configuration</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ NSS returns incorrect user information
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If your search for user information returns incorrect data, ensure that you do not have conflicting usernames in separate domains. If you use multiple domains, it is recommended that you set the <em class="parameter"><code>use_fully_qualified_domains</code></em> attribute to <code class="literal">TRUE</code> in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div></li></ul></div>
+
+ </div></li></ul></div></div><div class="section" title="8.2.7.5. Additional Resources" id="sect-SSSD_User_Guide-Troubleshooting-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Troubleshooting-Additional_Resources">8.2.7.5. Additional Resources</h4></div></div></div><div class="section" title="8.2.7.5.1. Manual Pages" id="sect-SSSD_User_Guide-Additional_Resources-Manual_Pages"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Additional_Resources-Manual_Pages">8.2.7.5.1. Manual Pages</h5></div></div></div><div class="para">
+ SSSD ships with a number of manual pages, all of which provide additional information about specific aspects of SSSD, such as configuration files, commands, and available options. SSSD currently provides the following manual pages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">sssd.conf(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-ipa(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-krb5(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-ldap(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd(8)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd_krb5_locator_plugin(8)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">pam_sss(8)</code>
+ </div></li></ul></div><div class="para">
+ You should refer to these manual pages for detailed information about all aspects of SSSD, its configuration, and associated tools and commands.
+ </div></div><div class="section" title="8.2.7.5.2. Mailing Lists" id="sect-SSSD_User_Guide-Additional_Resources-Mailing_Lists"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Additional_Resources-Mailing_Lists">8.2.7.5.2. Mailing Lists</h5></div></div></div><div class="para">
+ You can subscribe to the SSSD mailing list to follow and become involved in the development of SSSD, or to ask questions about any issues you may be experiencing with your SSSD deployment.
+ </div><div class="para">
+ Visit <a href="https://fedorahosted.org/mailman/listinfo/sssd-devel">https://fedorahosted.org/mailman/listinfo/sssd-devel</a> to subscribe to this mailing list.
+ </div></div></div></div><div class="section" title="8.2.8. SSSD Configuration File Format" id="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">8.2.8. SSSD Configuration File Format</h3></div></div></div><div class="para">
+ The following listing describes the current version (Version 2) of the SSSD configuration file format.
+ </div><pre class="programlisting">[sssd]
+config_file_version = 2
+services = nss, pam
+domains = mybox.example.com, ldap.example.com, ipa.example.com, nis.example.com
+# sbus_timeout = 300
+
+[nss]
+nss_filter_groups = root
+nss_filter_users = root
+nss_entry_cache_timeout = 30
+nss_enum_cache_timeout = 30
+
+[domain/mybox.example.com]
+domain_type = local
+enumerate = true
+min_id = 1000
+# max_id = 2000
+
+local_default_shell = /bin/bash
+local_default_homedir = /home
+
+# Possible overrides
+# id_provider = local
+# auth_provider = local
+# authz_provider = local
+# passwd_provider = local
+
+[domain/ldap.example.com]
+domain_type = ldap
+server = ldap.example.com, ldap3.example.com, 10.0.0.2
+# ldap_uri = ldaps://ldap.example.com:9093
+# ldap_use_tls = ssl
+ldap_search_base = dc=ldap,dc=example,dc=com
+enumerate = false
+
+# Possible overrides
+# id_provider = ldap
+# id_server = ldap2.example.com
+# auth_provider = krb5
+# auth_server = krb5.example.com
+# krb5_realm = KRB5.EXAMPLE.COM
+
+[domain/ipa.example.com]
+domain_type = ipa
+server = ipa.example.com, ipa2.example.com
+enumerate = false
+
+# Possible overrides
+# id_provider = ldap
+# id_server = ldap2.example.com
+# auth_provider = krb5
+# auth_server = krb5.example.com
+# krb5_realm = KRB5.EXAMPLE.COM
+
+[domain/nis.example.com]
+id_provider = proxy
+proxy_lib = nis
+auth_provider = proxy
+proxy_auth_target = nis_pam_proxy
+</pre></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 9. OpenSSH" id="ch-OpenSSH" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. OpenSSH</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-ssh-protocol">9.1. The SSH Protocol</a></span></dt><dt><span class="section"><a href="#s1-ssh-configuration">9.2. An OpenSSH Configuration</a></span></dt><dt><span class="section"><a href="#s1-ssh-clients">9.3. OpenSSH Clients</a></span></dt><dt><span class="section"><a href="#s1-ssh-beyondshell">9.4. More Than a Secure Shell</a></span></dt><dt><span class="section"><a href="#s1-openssh-additional-resources">9.5. Additional Resources</a></span></dt></dl></div><a id="id469800" class="indexterm"></a><div class="para">
+ <code class="systemitem">SSH</code> (Secure Shell) is a protocol which facilitates secure communications between two systems using a client/server architecture and allows users to log into server host systems remotely. Unlike other remote communication protocols, such as <code class="systemitem">FTP</code> or <code class="systemitem">Telnet</code>, SSH encrypts the login session, rendering the connection difficult for intruders to collect unencrypted passwords.
+ </div><div class="para">
+ The <span class="application"><strong>ssh</strong></span> program is designed to replace older, less secure terminal applications used to log into remote hosts, such as <code class="command">telnet</code> or <code class="command">rsh</code>. A related program called <code class="command">scp</code> replaces older programs designed to copy files between hosts, such as <code class="command">rcp</code>. Because these older applications do not encrypt passwords transmitted between the client and the server, avoid them whenever possible. Using secure methods to log into remote systems decreases the risks for both the client system and the remote host.
+ </div><div class="para">
+ Fedora includes the general OpenSSH package (<code class="filename">openssh</code>) as well as the OpenSSH server (<code class="filename">openssh-server</code>) and client (<code class="filename">openssh-clients</code>) packages. Note, the OpenSSH packages require the OpenSSL package (<code class="filename">openssl</code>) which installs several important cryptographic libraries, enabling OpenSSH to provide encrypted communications.
+ </div><div class="section" title="9.1. The SSH Protocol" id="s1-ssh-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ssh-protocol">9.1. The SSH Protocol</h2></div></div></div><div class="section" title="9.1.1. Why Use SSH?" id="s2-ssh-why"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-why">9.1.1. Why Use SSH?</h3></div></div></div><a id="id709623" class="indexterm"></a><div class="para">
+ Potential intruders have a variety of tools at their disposal enabling them to disrupt, intercept, and re-route network traffic in an effort to gain access to a system. In general terms, these threats can be categorized as follows:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Interception of communication between two systems</span></dt><dd><div class="para">
+ The attacker can be somewhere on the network between the communicating parties, copying any information passed between them. He may intercept and keep the information, or alter the information and send it on to the intended recipient.
+ </div><div class="para">
+ This attack is usually performed using a <em class="firstterm">packet sniffer</em>, a rather common network utility that captures each packet flowing through the network, and analyzes its content.
+ </div></dd><dt class="varlistentry"><span class="term">Impersonation of a particular host</span></dt><dd><div class="para">
+ Attacker's system is configured to pose as the intended recipient of a transmission. If this strategy works, the user's system remains unaware that it is communicating with the wrong host.
+ </div><div class="para">
+ This attack can be performed using a technique known as <em class="firstterm">DNS poisoning</em>, or via so-called <em class="firstterm">IP spoofing</em>. In the first case, the intruder uses a cracked DNS server to point client systems to a maliciously duplicated host. In the second case, the intruder sends falsified network packets that appear to be from a trusted host.
+ </div></dd></dl></div><div class="para">
+ Both techniques intercept potentially sensitive information and, if the interception is made for hostile reasons, the results can be disastrous. If SSH is used for remote shell login and file copying, these security threats can be greatly diminished. This is because the SSH client and server use digital signatures to verify their identity. Additionally, all communication between the client and server systems is encrypted. Attempts to spoof the identity of either side of a communication does not work, since each packet is encrypted using a key known only by the local and remote systems.
+ </div></div><div class="section" title="9.1.2. Main Features" id="s2-ssh-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-features">9.1.2. Main Features</h3></div></div></div><a id="id701405" class="indexterm"></a><a id="id672882" class="indexterm"></a><div class="para">
+ The SSH protocol provides the following safeguards:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">No one can pose as the intended server</span></dt><dd><div class="para">
+ After an initial connection, the client can verify that it is connecting to the same server it had connected to previously.
+ </div></dd><dt class="varlistentry"><span class="term">No one can capture the authentication information</span></dt><dd><div class="para">
+ The client transmits its authentication information to the server using strong, 128-bit encryption.
+ </div></dd><dt class="varlistentry"><span class="term">No one can intercept the communication</span></dt><dd><div class="para">
+ All data sent and received during a session is transferred using 128-bit encryption, making intercepted transmissions extremely difficult to decrypt and read.
+ </div></dd></dl></div><div class="para">
+ Additionally, it also offers the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">It provides secure means to use graphical applications over a network</span></dt><dd><div class="para">
+ Using a technique called <em class="firstterm">X11 forwarding</em>, the client can forward <em class="firstterm">X11</em> (<em class="firstterm">X Window System</em>) applications from the server.
+ </div></dd><dt class="varlistentry"><span class="term">It provides a way to secure otherwise insecure protocols</span></dt><dd><div class="para">
+ The SSH protocol encrypts everything it sends and receives. Using a technique called <em class="firstterm">port forwarding</em>, an SSH server can become a conduit to securing otherwise insecure protocols, like <acronym class="acronym">POP</acronym>, and increasing overall system and data security.
+ </div></dd><dt class="varlistentry"><span class="term">It can be used to create a secure channel</span></dt><dd><div class="para">
+ The OpenSSH server and client can be configured to create a tunnel similar to a virtual private network for traffic between server and client machines.
+ </div></dd><dt class="varlistentry"><span class="term">It supports the Kerberos authentication</span></dt><dd><div class="para">
+ OpenSSH servers and clients can be configured to authenticate using the <acronym class="acronym">GSSAPI</acronym> (Generic Security Services Application Program Interface) implementation of the Kerberos network authentication protocol.
+ </div></dd></dl></div></div><div class="section" title="9.1.3. Protocol Versions" id="s2-ssh-versions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-versions">9.1.3. Protocol Versions</h3></div></div></div><a id="id1691334" class="indexterm"></a><a id="id1691346" class="indexterm"></a><div class="para">
+ Two varieties of SSH currently exist: version 1, and newer version 2. The OpenSSH suite under Fedora uses SSH version 2, which has an enhanced key exchange algorithm not vulnerable to the known exploit in version 1. However, for compatibility reasons, the OpenSSH suite does support version 1 connections as well.
+ </div><div class="important" title="Important: Avoid Using SSH Version 1"><div class="admonition_header"><h2>Important: Avoid Using SSH Version 1</h2></div><div class="admonition"><div class="para">
+ To ensure maximum security for your connection, it is recommended that only SSH version 2-compatible servers and clients are used whenever possible.
+ </div></div></div></div><div class="section" title="9.1.4. Event Sequence of an SSH Connection" id="s2-ssh-conn"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-conn">9.1.4. Event Sequence of an SSH Connection</h3></div></div></div><a id="id644639" class="indexterm"></a><div class="para">
+ The following series of events help protect the integrity of SSH communication between two hosts.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ A cryptographic handshake is made so that the client can verify that it is communicating with the correct server.
+ </div></li><li class="listitem"><div class="para">
+ The transport layer of the connection between the client and remote host is encrypted using a symmetric cipher.
+ </div></li><li class="listitem"><div class="para">
+ The client authenticates itself to the server.
+ </div></li><li class="listitem"><div class="para">
+ The remote client interacts with the remote host over the encrypted connection.
+ </div></li></ol></div><div class="section" title="9.1.4.1. Transport Layer" id="s2-ssh-protocol-conn-transport"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-ssh-protocol-conn-transport">9.1.4.1. Transport Layer</h4></div></div></div><a id="id707796" class="indexterm"></a><div class="para">
+ The primary role of the transport layer is to facilitate safe and secure communication between the two hosts at the time of authentication and during subsequent communication. The transport layer accomplishes this by handling the encryption and decryption of data, and by providing integrity protection of data packets as they are sent and received. The transport layer also provides compression, speeding the transfer of information.
+ </div><div class="para">
+ Once an SSH client contacts a server, key information is exchanged so that the two systems can correctly construct the transport layer. The following steps occur during this exchange:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Keys are exchanged
+ </div></li><li class="listitem"><div class="para">
+ The public key encryption algorithm is determined
+ </div></li><li class="listitem"><div class="para">
+ The symmetric encryption algorithm is determined
+ </div></li><li class="listitem"><div class="para">
+ The message authentication algorithm is determined
+ </div></li><li class="listitem"><div class="para">
+ The hash algorithm is determined
+ </div></li></ul></div><div class="para">
+ During the key exchange, the server identifies itself to the client with a unique <em class="firstterm">host key</em>. If the client has never communicated with this particular server before, the server's host key is unknown to the client and it does not connect. OpenSSH gets around this problem by accepting the server's host key. This is done after the user is notified and has both accepted and verified the new host key. In subsequent connections, the server's host key is checked against the saved version on the client, providing confidence that the client is indeed communicating with the intended server. If, in the future, the host key no longer matches, the user must remove the client's saved version before a connection can occur.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ It is possible for an attacker to masquerade as an SSH server during the initial contact since the local system does not know the difference between the intended server and a false one set up by an attacker. To help prevent this, verify the integrity of a new SSH server by contacting the server administrator before connecting for the first time or in the event of a host key mismatch.
+ </div></div></div><div class="para">
+ SSH is designed to work with almost any kind of public key algorithm or encoding format. After an initial key exchange creates a hash value used for exchanges and a shared secret value, the two systems immediately begin calculating new keys and algorithms to protect authentication and future data sent over the connection.
+ </div><div class="para">
+ After a certain amount of data has been transmitted using a given key and algorithm (the exact amount depends on the SSH implementation), another key exchange occurs, generating another set of hash values and a new shared secret value. Even if an attacker is able to determine the hash and shared secret value, this information is only useful for a limited period of time.
+ </div></div><div class="section" title="9.1.4.2. Authentication" id="s2-ssh-protocol-authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-ssh-protocol-authentication">9.1.4.2. Authentication</h4></div></div></div><a id="id629720" class="indexterm"></a><div class="para">
+ Once the transport layer has constructed a secure tunnel to pass information between the two systems, the server tells the client the different authentication methods supported, such as using a private key-encoded signature or typing a password. The client then tries to authenticate itself to the server using one of these supported methods.
+ </div><div class="para">
+ SSH servers and clients can be configured to allow different types of authentication, which gives each side the optimal amount of control. The server can decide which encryption methods it supports based on its security model, and the client can choose the order of authentication methods to attempt from the available options.
+ </div></div><div class="section" title="9.1.4.3. Channels" id="s2-ssh-protocol-connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-ssh-protocol-connection">9.1.4.3. Channels</h4></div></div></div><a id="id584597" class="indexterm"></a><div class="para">
+ After a successful authentication over the SSH transport layer, multiple channels are opened via a technique called <em class="firstterm">multiplexing</em><sup>[<a id="id670403" href="#ftn.id670403" class="footnote">3</a>]</sup>. Each of these channels handles communication for different terminal sessions and for forwarded X11 sessions.
+ </div><div class="para">
+ Both clients and servers can create a new channel. Each channel is then assigned a different number on each end of the connection. When the client attempts to open a new channel, the clients sends the channel number along with the request. This information is stored by the server and is used to direct communication to that channel. This is done so that different types of sessions do not affect one another and so that when a given session ends, its channel can be closed without disrupting the primary SSH connection.
+ </div><div class="para">
+ Channels also support <em class="firstterm">flow-control</em>, which allows them to send and receive data in an orderly fashion. In this way, data is not sent over the channel until the client receives a message that the channel is open.
+ </div><div class="para">
+ The client and server negotiate the characteristics of each channel automatically, depending on the type of service the client requests and the way the user is connected to the network. This allows great flexibility in handling different types of remote connections without having to change the basic infrastructure of the protocol.
+ </div></div></div></div><div class="section" title="9.2. An OpenSSH Configuration" id="s1-ssh-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ssh-configuration">9.2. An OpenSSH Configuration</h2></div></div></div><div class="para">
+ In order to perform tasks described in this section, you must have superuser privileges. To obtain them, log in as root by typing:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="section" title="9.2.1. Configuration Files" id="s2-ssh-configuration-configs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-configuration-configs">9.2.1. Configuration Files</h3></div></div></div><a id="id758969" class="indexterm"></a><div class="para">
+ There are two different sets of configuration files: those for client programs (that is, <code class="command">ssh</code>, <code class="command">scp</code>, and <code class="command">sftp</code>), and those for the server (the <code class="command">sshd</code> daemon).
+ </div><a id="id435454" class="indexterm"></a><div class="para">
+ System-wide SSH configuration information is stored in the <code class="filename">/etc/ssh/</code> directory. See <a class="xref" href="#table-ssh-configuration-configs-system" title="Table 9.1. System-wide configuration files">Table 9.1, “System-wide configuration files”</a> for a description of its content.
+ </div><div class="table" title="Table 9.1. System-wide configuration files" id="table-ssh-configuration-configs-system"><h6>Table 9.1. System-wide configuration files</h6><div class="table-contents"><table summary="System-wide configuration files" border="1"><colgroup><col width="38%" /><col width="63%" /></colgroup><thead><tr><th>
+ Configuration File
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc/ssh/moduli</code>
+ </td><td>
+ Contains Diffie-Hellman groups used for the Diffie-Hellman key exchange which is critical for constructing a secure transport layer. When keys are exchanged at the beginning of an SSH session, a shared, secret value is created which cannot be determined by either party alone. This value is then used to provide host authentication.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_config</code>
+ </td><td>
+ The default SSH client configuration file. Note that it is overridden by <code class="filename">~/.ssh/config</code> if it exists.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/sshd_config</code>
+ </td><td>
+ The configuration file for the <code class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_dsa_key</code>
+ </td><td>
+ The DSA private key used by the <code class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_dsa_key.pub</code>
+ </td><td>
+ The DSA public key used by the <code class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_key</code>
+ </td><td>
+ The RSA private key used by the <code class="command">sshd</code> daemon for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_key.pub</code>
+ </td><td>
+ The RSA public key used by the <code class="command">sshd</code> daemon for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_rsa_key</code>
+ </td><td>
+ The RSA private key used by the <code class="command">sshd</code> daemon for version 2 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_rsa_key.pub</code>
+ </td><td>
+ The RSA public key used by the <code class="command">sshd</code> for version 2 of the SSH protocol.
+ </td></tr></tbody></table></div></div><br class="table-break" /><a id="id2226572" class="indexterm"></a><div class="para">
+ User-specific SSH configuration information is stored in the user's home directory within the <code class="filename">~/.ssh/</code> directory. See <a class="xref" href="#table-ssh-configuration-configs-user" title="Table 9.2. User-specific configuration files">Table 9.2, “User-specific configuration files”</a> for a description of its content.
+ </div><div class="table" title="Table 9.2. User-specific configuration files" id="table-ssh-configuration-configs-user"><h6>Table 9.2. User-specific configuration files</h6><div class="table-contents"><table summary="User-specific configuration files" border="1"><colgroup><col width="38%" /><col width="63%" /></colgroup><thead><tr><th>
+ Configuration File
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">~/.ssh/authorized_keys</code>
+ </td><td>
+ Holds a list of authorized public keys for servers. When the client connects to a server, the server authenticates the client by checking its signed public key stored within this file.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_dsa</code>
+ </td><td>
+ Contains the DSA private key of the user.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_dsa.pub</code>
+ </td><td>
+ The DSA public key of the user.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_rsa</code>
+ </td><td>
+ The RSA private key used by <code class="command">ssh</code> for version 2 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_rsa.pub</code>
+ </td><td>
+ The RSA public key used by <code class="command">ssh</code> for version 2 of the SSH protocol
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/identity</code>
+ </td><td>
+ The RSA private key used by <code class="command">ssh</code> for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/identity.pub</code>
+ </td><td>
+ The RSA public key used by <code class="command">ssh</code> for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/known_hosts</code>
+ </td><td>
+ Contains DSA host keys of SSH servers accessed by the user. This file is very important for ensuring that the SSH client is connecting the correct SSH server.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Refer to the <code class="command">ssh_config</code> and <code class="command">sshd_config</code> man pages for information concerning the various directives available in the SSH configuration files.
+ </div></div><div class="section" title="9.2.2. Starting an OpenSSH Server" id="s2-ssh-configuration-sshd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-configuration-sshd">9.2.2. Starting an OpenSSH Server</h3></div></div></div><a id="id1622491" class="indexterm"></a><div class="note" title="Note: Make Sure You Have Relevant Packages Installed"><div class="admonition_header"><h2>Note: Make Sure You Have Relevant Packages Installed</h2></div><div class="admonition"><div class="para">
+ To run an OpenSSH server, you must have the <span class="package">openssh-server</span> and <span class="package">openssh</span> packages installed. Refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><a id="id863456" class="indexterm"></a><div class="para">
+ To start the <code class="command">sshd</code> daemon, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service sshd start</code></pre><a id="id570579" class="indexterm"></a><div class="para">
+ To stop the running <code class="command">sshd</code> daemon, use the following command:
+ </div><pre class="screen">~]# <code class="command">service sshd stop</code></pre><div class="para">
+ If you want the daemon to start automatically at the boot time, type:
+ </div><pre class="screen">~]# <code class="command">chkconfig sshd on</code></pre><div class="para">
+ This will enable the service for all runlevels. For more configuration options, refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for the detailed information on how to manage services.
+ </div><div class="para">
+ Note that if you reinstall the system, a new set of identification keys will be created. As a result, clients who had connected to the system with any of the OpenSSH tools before the reinstall will see the following message:
+ </div><pre class="screen">@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
+Someone could be eavesdropping on you right now (man-in-the-middle attack)!
+It is also possible that the RSA host key has just been changed.</pre><div class="para">
+ To prevent this, you can backup the relevant files from the <code class="filename">/etc/ssh/</code> directory (see <a class="xref" href="#table-ssh-configuration-configs-system" title="Table 9.1. System-wide configuration files">Table 9.1, “System-wide configuration files”</a> for a complete list), and restore them whenever you reinstall the system.
+ </div></div><div class="section" title="9.2.3. Requiring SSH for Remote Connections" id="s2-ssh-configuration-requiring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-configuration-requiring">9.2.3. Requiring SSH for Remote Connections</h3></div></div></div><a id="id509239" class="indexterm"></a><a id="id739162" class="indexterm"></a><div class="para">
+ For SSH to be truly effective, using insecure connection protocols should be prohibited. Otherwise, a user's password may be protected using SSH for one session, only to be captured later while logging in using Telnet. Some services to disable include <code class="command">telnet</code>, <code class="command">rsh</code>, <code class="command">rlogin</code>, and <code class="command">vsftpd</code>.
+ </div><div class="para">
+ To disable these services, type the following commands at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">chkconfig telnet off</code>
+~]# <code class="command">chkconfig rsh off</code>
+~]# <code class="command">chkconfig rlogin off</code>
+~]# <code class="command">chkconfig vsftpd off</code></pre><div class="para">
+ For more information on runlevels and configuring services in general, refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div></div><div class="section" title="9.2.4. Using a Key-Based Authentication" id="s2-ssh-configuration-keypairs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-configuration-keypairs">9.2.4. Using a Key-Based Authentication</h3></div></div></div><a id="id448521" class="indexterm"></a><div class="para">
+ To improve the system security even further, you can enforce the use the key-based authentication by disabling the standard password authentication. To do so, open the <code class="filename">/etc/ssh/sshd_config</code> configuration file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, and change the <code class="option">PasswordAuthentication</code> option as follows:
+ </div><pre class="screen">PasswordAuthentication no</pre><div class="para">
+ To be able to use <code class="command">ssh</code>, <code class="command">scp</code>, or <code class="command">sftp</code> to connect to the server from a client machine, generate an authorization key pair by following the steps below. Note that keys must be generated for each user separately.
+ </div><div class="para">
+ Fedora 14 uses SSH Protocol 2 and RSA keys by default (see <a class="xref" href="#s2-ssh-versions" title="9.1.3. Protocol Versions">Section 9.1.3, “Protocol Versions”</a> for more information).
+ </div><div class="important" title="Important: Do Not Generate Key Pairs as root"><div class="admonition_header"><h2>Important: Do Not Generate Key Pairs as root</h2></div><div class="admonition"><div class="para">
+ If you complete the steps as root, only root will be able to use the keys.
+ </div></div></div><div class="note" title="Tip: Backup Your ~/.ssh/ Directory"><div class="admonition_header"><h2>Tip: Backup Your <code class="filename">~/.ssh/</code> Directory</h2></div><div class="admonition"><div class="para">
+ If you reinstall your system and want to keep previously generated key pair, backup the <code class="filename">~/.ssh/</code> directory. After reinstalling, copy it back to your home directory. This process can be done for all users on your system, including root.
+ </div></div></div><div class="section" title="9.2.4.1. Generating Key Pairs" id="s3-ssh-configuration-keypairs-generating"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-ssh-configuration-keypairs-generating">9.2.4.1. Generating Key Pairs</h4></div></div></div><a id="id816397" class="indexterm"></a><a id="id648200" class="indexterm"></a><div class="para">
+ To generate an RSA key pair for version 2 of the SSH protocol, follow these steps:
+ </div><a id="id648219" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Generate an RSA key pair by typing the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">ssh-keygen -t rsa</code>
+Generating public/private rsa key pair.
+Enter file in which to save the key (/home/john/.ssh/id_rsa):</pre></li><li class="step" title="Step 2"><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to confirm the default location (that is, <code class="filename">~/.ssh/id_rsa</code>) for the newly created key.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so. For security reasons, avoid using the same password as you use to log in to your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/id_rsa.
+Your public key has been saved in /home/john/.ssh/id_rsa.pub.
+The key fingerprint is:
+e7:97:c7:e2:0e:f9:0e:fc:c4:d7:cb:e5:31:11:92:14 john at penguin.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| E. |
+| . . |
+| o . |
+| . .|
+| S . . |
+| + o o ..|
+| * * +oo|
+| O +..=|
+| o* o.|
++-----------------+</pre></li><li class="step" title="Step 4"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code class="command">chmod 755 ~/.ssh</code></pre></li><li class="step" title="Step 5"><div class="para">
+ Copy the content of <code class="filename">~/.ssh/id_rsa.pub</code> into the <code class="filename">~/.ssh/authorized_keys</code> on the machine to which you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step" title="Step 6"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/authorized_keys</code> file using the following command:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><a id="id775573" class="indexterm"></a><a id="id775585" class="indexterm"></a><div class="para">
+ To generate a DSA key pair for version 2 of the SSH protocol, follow these steps:
+ </div><a id="id775604" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Generate a DSA key pair by typing the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">ssh-keygen -t dsa</code>
+Generating public/private dsa key pair.
+Enter file in which to save the key (/home/john/.ssh/id_dsa):</pre></li><li class="step" title="Step 2"><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to confirm the default location (that is, <code class="filename">~/.ssh/id_dsa</code>) for the newly created key.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so. For security reasons, avoid using the same password as you use to log in to your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/id_dsa.
+Your public key has been saved in /home/john/.ssh/id_dsa.pub.
+The key fingerprint is:
+81:a1:91:a8:9f:e8:c5:66:0d:54:f5:90:cc:bc:cc:27 john at penguin.example.com
+The key's randomart image is:
++--[ DSA 1024]----+
+| .oo*o. |
+| ...o Bo |
+| .. . + o. |
+|. . E o |
+| o..o S |
+|. o= . |
+|. + |
+| . |
+| |
++-----------------+</pre></li><li class="step" title="Step 4"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code class="command">chmod 775 ~/.ssh</code></pre></li><li class="step" title="Step 5"><div class="para">
+ Copy the content of <code class="filename">~/.ssh/id_dsa.pub</code> into the <code class="filename">~/.ssh/authorized_keys</code> on the machine to which you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step" title="Step 6"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/authorized_keys</code> file using the following command:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><a id="id588245" class="indexterm"></a><a id="id588257" class="indexterm"></a><div class="para">
+ To generate an RSA key pair for version 1 of the SSH protocol, follow these steps:
+ </div><a id="id580205" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Generate an RSA key pair by typing the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">ssh-keygen -t rsa1</code>
+Generating public/private rsa1 key pair.
+Enter file in which to save the key (/home/john/.ssh/identity):</pre></li><li class="step" title="Step 2"><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to confirm the default location (that is, <code class="filename">~/.ssh/identity</code>) for the newly created key.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so. For security reasons, avoid using the same password as you use to log into your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/identity.
+Your public key has been saved in /home/john/.ssh/identity.pub.
+The key fingerprint is:
+cb:f6:d5:cb:6e:5f:2b:28:ac:17:0c:e4:62:e4:6f:59 john at penguin.example.com
+The key's randomart image is:
++--[RSA1 2048]----+
+| |
+| . . |
+| o o |
+| + o E |
+| . o S |
+| = + . |
+| . = . o . .|
+| . = o o..o|
+| .o o o=o.|
++-----------------+</pre></li><li class="step" title="Step 4"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code class="command">chmod 755 ~/.ssh</code></pre></li><li class="step" title="Step 5"><div class="para">
+ Copy the content of <code class="filename">~/.ssh/identity.pub</code> into the <code class="filename">~/.ssh/authorized_keys</code> on the machine to which you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step" title="Step 6"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/authorized_keys</code> file using the following command:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><div class="para">
+ Refer to <a class="xref" href="#s3-ssh-configuration-keypairs-agent" title="9.2.4.2. Configuring ssh-agent">Section 9.2.4.2, “Configuring <code class="command">ssh-agent</code>”</a> for information on how to set up your system to remember the passphrase.
+ </div><div class="important" title="Important: Never Share Your Private Key"><div class="admonition_header"><h2>Important: Never Share Your Private Key</h2></div><div class="admonition"><div class="para">
+ The private key is for your personal use only, and it is important that you never give it to anyone.
+ </div></div></div></div><div class="section" title="9.2.4.2. Configuring ssh-agent" id="s3-ssh-configuration-keypairs-agent"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-ssh-configuration-keypairs-agent">9.2.4.2. Configuring <code class="command">ssh-agent</code></h4></div></div></div><a id="id442334" class="indexterm"></a><a id="id442350" class="indexterm"></a><div class="para">
+ To store your passphrase so that you do not have to enter it each time you initiate a connection with a remote machine, you can use the <code class="command">ssh-agent</code> authentication agent. If you are running GNOME, you can configure it to prompt you for your passphrase whenever you log in and remember it during the whole session. Otherwise you can store the passphrase for a certain shell prompt.
+ </div><div class="para">
+ To save your passphrase during your GNOME session, follow these steps:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Make sure you have the <span class="package">openssh-askpass</span> package installed. If not, refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Startup Applications</strong></span> from the panel. The <span class="application"><strong>Startup Applications Preferences</strong></span> will be started, and the tab containing a list of available startup programs will be shown by default.
+ </div><div class="figure" title="Figure 9.1. Startup Applications Preferences" id="fig-ssh-startup-applications"><div class="figure-contents"><div class="mediaobject"><img src="images/ssh-startup-applications.png" alt="Startup Applications Preferences" /><div class="longdesc"><div class="para">
+ <span class="application"><strong>Startup Applications Preferences</strong></span>
+ </div></div></div></div><h6>Figure 9.1. <span class="application">Startup Applications Preferences</span></h6></div><br class="figure-break" /></li><li class="step" title="Step 3"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button on the right, and enter <strong class="userinput"><code>/usr/bin/ssh-add</code></strong> in the <span class="guilabel"><strong>Command</strong></span> field.
+ </div><a id="id583338" class="indexterm"></a><a id="id842819" class="indexterm"></a><div class="figure" title="Figure 9.2. Adding new application" id="fig-ssh-startup-applications-add"><div class="figure-contents"><div class="mediaobject"><img src="images/ssh-startup-applications-add.png" alt="Adding new application" /><div class="longdesc"><div class="para">
+ Adding new application
+ </div></div></div></div><h6>Figure 9.2. Adding new application</h6></div><br class="figure-break" /></li><li class="step" title="Step 4"><div class="para">
+ Click <span class="guibutton"><strong>Add</strong></span> and make sure the check box next to the newly added item is selected.
+ </div><div class="figure" title="Figure 9.3. Enabling the application" id="fig-ssh-startup-applications-check"><div class="figure-contents"><div class="mediaobject"><img src="images/ssh-startup-applications-check.png" alt="Enabling the application" /><div class="longdesc"><div class="para">
+ Enabling the application
+ </div></div></div></div><h6>Figure 9.3. Enabling the application</h6></div><br class="figure-break" /></li><li class="step" title="Step 5"><div class="para">
+ Log out and then log back in. A dialog box will appear prompting you for your passphrase. From this point on, you should not be prompted for a password by <code class="command">ssh</code>, <code class="command">scp</code>, or <code class="command">sftp</code>.
+ </div><div class="figure" title="Figure 9.4. Entering a passphrase" id="fig-ssh-passphrase-prompt"><div class="figure-contents"><div class="mediaobject"><img src="images/ssh-passphrase-prompt.png" alt="Entering a passphrase" /><div class="longdesc"><div class="para">
+ Entering a passphrase
+ </div></div></div></div><h6>Figure 9.4. Entering a passphrase</h6></div><br class="figure-break" /></li></ol></div><div class="para">
+ To save your passphrase for a certain shell prompt, use the following command:
+ </div><pre class="screen">~]$ <code class="command">ssh-add</code>
+Enter passphrase for /home/john/.ssh/id_rsa:</pre><div class="para">
+ Note that when you log out, your passphrase will be forgotten. You must execute the command each time you log in to a virtual console or a terminal window.
+ </div></div></div></div><div class="section" title="9.3. OpenSSH Clients" id="s1-ssh-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ssh-clients">9.3. OpenSSH Clients</h2></div></div></div><a id="id531590" class="indexterm"></a><div class="note" title="Note: Make Sure You Have Relevant Packages Installed"><div class="admonition_header"><h2>Note: Make Sure You Have Relevant Packages Installed</h2></div><div class="admonition"><div class="para">
+ To connect to an OpenSSH server from a client machine, you must have the <span class="package">openssh-clients</span> and <span class="package">openssh</span> packages installed. Refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><div class="section" title="9.3.1. Using the ssh Utility" id="s2-ssh-clients-ssh"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-clients-ssh">9.3.1. Using the <code class="command">ssh</code> Utility</h3></div></div></div><a id="id819875" class="indexterm"></a><a id="id819891" class="indexterm"></a><div class="para">
+ <code class="command">ssh</code> allows you to log in to a remote machine and execute commands there. It is a secure replacement for the <code class="command">rlogin</code>, <code class="command">rsh</code>, and <code class="command">telnet</code> programs.
+ </div><div class="para">
+ Similarly to <code class="command">telnet</code>, to log in to a remote machine named <code class="systemitem">penguin.example.com</code>, type the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">ssh penguin.example.com</code></pre><div class="para">
+ This will log you in with the same username you are using on a local machine. If you want to specify a different one, use a command in the <code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em></code> form. For example, to log in as <code class="systemitem">john</code>, type:
+ </div><pre class="screen">~]$ <code class="command">ssh john at penguin.example.com</code></pre><div class="para">
+ The first time you initiate a connection, you will be presented with a message similar to this:
+ </div><pre class="screen">The authenticity of host 'penguin.example.com' can't be established.
+RSA key fingerprint is 94:68:3a:3a:bc:f3:9a:9b:01:5d:b3:07:38:e2:11:0c.
+Are you sure you want to continue connecting (yes/no)?</pre><div class="para">
+ Type <strong class="userinput"><code>yes</code></strong> to confirm. You will see a notice that the server has been added to the list of known hosts, and a prompt asking for your password:
+ </div><pre class="screen">Warning: Permanently added 'penguin.example.com' (RSA) to the list of known hosts.
+john at penguin.example.com's password:</pre><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If the SSH server's host key changes, the client notifies the user that the connection cannot proceed until the server's host key is deleted from the <code class="filename">~/.ssh/known_hosts</code> file. To do so, open the file in a text editor, and remove a line containing the remote machine name at the beginning. Before doing this, however, contact the system administrator of the SSH server to verify the server is not compromised.
+ </div></div></div><div class="para">
+ After entering the password, you will be provided with a shell prompt for the remote machine.
+ </div><div class="para">
+ Alternatively, the <code class="command">ssh</code> program can be used to execute a command on the remote machine without logging in to a shell prompt. The syntax for that is <code class="command">ssh [<em class="replaceable"><code>username</code></em>@]<em class="replaceable"><code>hostname</code></em> <em class="replaceable"><code>command</code></em></code>. For example, if you want to execute the <code class="command">whoami</code> command on <code class="systemitem">penguin.example.com</code>, type:
+ </div><pre class="screen">~]$ <code class="command">ssh john at penguin.example.com whoami</code>
+john at penguin.example.com's password:
+john</pre><div class="para">
+ After you enter the correct password, the username will be displayed, and you will return to your local shell prompt.
+ </div></div><div class="section" title="9.3.2. Using the scp Utility" id="s2-ssh-clients-scp"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-clients-scp">9.3.2. Using the <code class="command">scp</code> Utility</h3></div></div></div><a id="id725714" class="indexterm"></a><a id="id453668" class="indexterm"></a><a id="id453688" class="indexterm"></a><div class="para">
+ <code class="command">scp</code> can be used to transfer files between machines over a secure, encrypted connection. In its design, it is very similar to <code class="command">rcp</code>.
+ </div><div class="para">
+ To transfer a local file to a remote system, use a command in the following form:
+ </div><pre class="screen"><code class="command">scp <em class="replaceable"><code>localfile</code></em> <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em>:<em class="replaceable"><code>remotefile</code></em></code></pre><div class="para">
+ For example, if you want to transfer <code class="filename">taglist.vim</code> to a remote machine named <code class="systemitem">penguin.example.com</code>, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">scp taglist.vim john at penguin.example.com:.vim/plugin/taglist.vim</code>
+john at penguin.example.com's password:
+taglist.vim 100% 144KB 144.5KB/s 00:00</pre><div class="para">
+ Multiple files can be specified at once. To transfer the contents of <code class="filename">.vim/plugin/</code> to the same directory on the remote machine <code class="systemitem">penguin.example.com</code>, type the following command:
+ </div><pre class="screen">~]$ <code class="command">scp .vim/plugin/* john at penguin.example.com:.vim/plugin/</code>
+john at penguin.example.com's password:
+closetag.vim 100% 13KB 12.6KB/s 00:00
+snippetsEmu.vim 100% 33KB 33.1KB/s 00:00
+taglist.vim 100% 144KB 144.5KB/s 00:00</pre><div class="para">
+ To transfer a remote file to the local system, use the following syntax:
+ </div><pre class="screen"><code class="command">scp <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em>:<em class="replaceable"><code>remotefile</code></em> <em class="replaceable"><code>localfile</code></em></code></pre><div class="para">
+ For instance, to download the <code class="filename">.vimrc</code> configuration file from the remote machine, type:
+ </div><pre class="screen">~]$ <code class="command">scp john at penguin.example.com:.vimrc .vimrc</code>
+john at penguin.example.com's password:
+.vimrc 100% 2233 2.2KB/s 00:00</pre></div><div class="section" title="9.3.3. Using the sftp Utility" id="s2-ssh-clients-sftp"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-clients-sftp">9.3.3. Using the <code class="command">sftp</code> Utility</h3></div></div></div><a id="id517099" class="indexterm"></a><a id="id2226179" class="indexterm"></a><div class="para">
+ The <code class="command">sftp</code> utility can be used to open a secure, interactive FTP session. In its design, it is similar to <code class="command">ftp</code> except that it uses a secure, encrypted connection.
+ </div><div class="para">
+ To connect to a remote system, use a command in the following form:
+ </div><pre class="screen"><code class="command">sftp <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em></code></pre><div class="para">
+ For example, to log in to a remote machine named <code class="systemitem">penguin.example.com</code> with <code class="systemitem">john</code> as a username, type:
+ </div><pre class="screen">~]$ <code class="command">sftp john at penguin.example.com</code>
+john at penguin.example.com's password:
+Connected to penguin.example.com.
+sftp></pre><div class="para">
+ After you enter the correct password, you will be presented with a prompt. The <code class="command">sftp</code> utility accepts a set of commands similar to those used by <code class="command">ftp</code> (see <a class="xref" href="#table-ssh-clients-sftp" title="Table 9.3. A selection of available sftp commands">Table 9.3, “A selection of available <code class="command">sftp</code> commands”</a>).
+ </div><div class="table" title="Table 9.3. A selection of available sftp commands" id="table-ssh-clients-sftp"><h6>Table 9.3. A selection of available <code class="command">sftp</code> commands</h6><div class="table-contents"><table summary="A selection of available sftp commands" border="1"><colgroup><col width="38%" /><col width="63%" /></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">ls</code> [<em class="replaceable"><code>directory</code></em>]
+ </td><td>
+ List the content of a remote <em class="replaceable"><code>directory</code></em>. If none is supplied, a current working directory is used by default.
+ </td></tr><tr><td>
+ <code class="command">cd</code> <em class="replaceable"><code>directory</code></em>
+ </td><td>
+ Change the remote working directory to <em class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">mkdir</code> <em class="replaceable"><code>directory</code></em>
+ </td><td>
+ Create a remote <em class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">rmdir</code> <em class="replaceable"><code>path</code></em>
+ </td><td>
+ Remove a remote <em class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">put</code> <em class="replaceable"><code>localfile</code></em> [<em class="replaceable"><code>remotefile</code></em>]
+ </td><td>
+ Transfer <em class="replaceable"><code>localfile</code></em> to a remote machine.
+ </td></tr><tr><td>
+ <code class="command">get</code> <em class="replaceable"><code>remotefile</code></em> [<em class="replaceable"><code>localfile</code></em>]
+ </td><td>
+ Transfer <em class="replaceable"><code>remotefile</code></em> from a remote machine.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ For a complete list of available commands, refer to the <code class="command">sftp</code> man page.
+ </div></div></div><div class="section" title="9.4. More Than a Secure Shell" id="s1-ssh-beyondshell"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ssh-beyondshell">9.4. More Than a Secure Shell</h2></div></div></div><div class="para">
+ A secure command line interface is just the beginning of the many ways SSH can be used. Given the proper amount of bandwidth, X11 sessions can be directed over an SSH channel. Or, by using TCP/IP forwarding, previously insecure port connections between systems can be mapped to specific SSH channels.
+ </div><div class="section" title="9.4.1. X11 Forwarding" id="s2-ssh-beyondshell-x11"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-beyondshell-x11">9.4.1. X11 Forwarding</h3></div></div></div><a id="id523875" class="indexterm"></a><div class="para">
+ To open an X11 session over an SSH connection, use a command in the following form:
+ </div><pre class="screen"><code class="command">ssh -Y <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em></code></pre><div class="para">
+ For example, to log in to a remote machine named <code class="systemitem">penguin.example.com</code> with <code class="systemitem">john</code> as a username, type:
+ </div><pre class="screen">~]$ <code class="command">ssh -Y john at penguin.example.com</code>
+john at penguin.example.com's password:</pre><div class="para">
+ When an X program is run from the secure shell prompt, the SSH client and server create a new secure channel, and the X program data is sent over that channel to the client machine transparently.
+ </div><div class="para">
+ X11 forwarding can be very useful. For example, X11 forwarding can be used to create a secure, interactive session of the <span class="application"><strong>Printer Configuration</strong></span> utility. To do this, connect to the server using <span class="application"><strong>ssh</strong></span> and type:
+ </div><pre class="screen">~]$ <code class="command">system-config-printer &</code></pre><div class="para">
+ The <span class="application"><strong>Printer Configuration Tool</strong></span> will appear, allowing the remote user to safely configure printing on the remote system.
+ </div></div><div class="section" title="9.4.2. Port Forwarding" id="s2-ssh-beyondshell-tcpip"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-beyondshell-tcpip">9.4.2. Port Forwarding</h3></div></div></div><a id="id616164" class="indexterm"></a><div class="para">
+ SSH can secure otherwise insecure <code class="systemitem">TCP/IP</code> protocols via port forwarding. When using this technique, the SSH server becomes an encrypted conduit to the SSH client.
+ </div><div class="para">
+ Port forwarding works by mapping a local port on the client to a remote port on the server. SSH can map any port from the server to any port on the client. Port numbers do not need to match for this technique to work.
+ </div><div class="note" title="Note: Using Reserved Port Numbers"><div class="admonition_header"><h2>Note: Using Reserved Port Numbers</h2></div><div class="admonition"><div class="para">
+ Setting up port forwarding to listen on ports below 1024 requires root level access.
+ </div></div></div><div class="para">
+ To create a TCP/IP port forwarding channel which listens for connections on the <code class="systemitem">localhost</code>, use a command in the following form:
+ </div><pre class="screen"><code class="command">ssh -L <em class="replaceable"><code>local-port</code></em>:<em class="replaceable"><code>remote-hostname</code></em>:<em class="replaceable"><code>remote-port</code></em> <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em></code></pre><div class="para">
+ For example, to check email on a server called <code class="systemitem">mail.example.com</code> using <code class="systemitem">POP3</code> through an encrypted connection, use the following command:
+ </div><pre class="screen">~]$ <code class="command">ssh -L 1100:mail.example.com:110 mail.example.com</code></pre><div class="para">
+ Once the port forwarding channel is in place between the client machine and the mail server, direct a POP3 mail client to use port <code class="literal">1100</code> on the <code class="systemitem">localhost</code> to check for new email. Any requests sent to port <code class="literal">1100</code> on the client system will be directed securely to the <code class="systemitem">mail.example.com</code> server.
+ </div><div class="para">
+ If <code class="systemitem">mail.example.com</code> is not running an SSH server, but another machine on the same network is, SSH can still be used to secure part of the connection. However, a slightly different command is necessary:
+ </div><pre class="screen">~]$ <code class="command">ssh -L 1100:mail.example.com:110 other.example.com</code></pre><div class="para">
+ In this example, POP3 requests from port <code class="literal">1100</code> on the client machine are forwarded through the SSH connection on port <code class="literal">22</code> to the SSH server, <code class="systemitem">other.example.com</code>. Then, <code class="systemitem">other.example.com</code> connects to port <code class="literal">110</code> on <code class="systemitem">mail.example.com</code> to check for new email. Note that when using this technique, only the connection between the client system and <code class="systemitem">other.example.com</code> SSH server is secure.
+ </div><div class="para">
+ Port forwarding can also be used to get information securely through network firewalls. If the firewall is configured to allow SSH traffic via its standard port (that is, port 22) but blocks access to other ports, a connection between two hosts using the blocked ports is still possible by redirecting their communication over an established SSH connection.
+ </div><div class="important" title="Important: A Connection Is Only as Secure as a Client System"><div class="admonition_header"><h2>Important: A Connection Is Only as Secure as a Client System</h2></div><div class="admonition"><div class="para">
+ Using port forwarding to forward connections in this manner allows any user on the client system to connect to that service. If the client system becomes compromised, the attacker also has access to forwarded services.
+ </div><div class="para">
+ System administrators concerned about port forwarding can disable this functionality on the server by specifying a <code class="option">No</code> parameter for the <code class="option">AllowTcpForwarding</code> line in <code class="filename">/etc/ssh/sshd_config</code> and restarting the <code class="command">sshd</code> service.
+ </div></div></div></div></div><div class="section" title="9.5. Additional Resources" id="s1-openssh-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-openssh-additional-resources">9.5. Additional Resources</h2></div></div></div><a id="id1127324" class="indexterm"></a><a id="id554769" class="indexterm"></a><div class="para">
+ The OpenSSH and OpenSSL projects are in constant development, and the most up-to-date information for them is available from their websites. The man pages for OpenSSH and OpenSSL tools are also good sources of detailed information.
+ </div><div class="section" title="9.5.1. Installed Documentation" id="s2-openssh-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-openssh-installed-docs">9.5.1. Installed Documentation</h3></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="command">man ssh</code></span></dt><dd><div class="para">
+ The manual page for <span class="application"><strong>ssh</strong></span> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man scp</code></span></dt><dd><div class="para">
+ The manual page for <span class="application"><strong>scp</strong></span> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sftp</code></span></dt><dd><div class="para">
+ The manual page for <span class="application"><strong>sftp</strong></span> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sshd</code></span></dt><dd><div class="para">
+ The manual page for <span class="application"><strong>sshd</strong></span> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ssh-keygen</code></span></dt><dd><div class="para">
+ The manual page for <span class="application"><strong>ssh-keygen</strong></span> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ssh_config</code></span></dt><dd><div class="para">
+ The manual page with full description of available SSH client configuration options.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sshd_config</code></span></dt><dd><div class="para">
+ The manual page with full description of available SSH daemon configuration options.
+ </div></dd></dl></div></div><div class="section" title="9.5.2. Useful Websites" id="s2-openssh-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-openssh-useful-websites">9.5.2. Useful Websites</h3></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><a href="http://www.openssh.com/">http://www.openssh.com/</a></span></dt><dd><div class="para">
+ The OpenSSH home page containing further documentation, frequently asked questions, links to the mailing lists, bug reports, and other useful resources.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.openssl.org/">http://www.openssl.org/</a></span></dt><dd><div class="para">
+ The OpenSSL home page containing further documentation, frequently asked questions, links to the mailing lists, and other useful resources.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.freesshd.com/">http://www.freesshd.com/</a></span></dt><dd><div class="para">
+ Another implementation of an SSH server.
+ </div></dd></dl></div></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote"><p><sup>[<a id="ftn.id670403" href="#id670403" class="para">3</a>] </sup>
+ A multiplexed connection consists of several signals being sent over a shared, common medium. With SSH, different channels are sent over a common secure connection.
+ </p></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 10. The BIND DNS Server" id="ch-The_BIND_DNS_Server" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. The BIND DNS Server</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-bind-introduction">10.1. Introduction to DNS</a></span></dt><dt><span class="section"><a href="#s1-bind-namedconf">10.2. Configuring the <code class="command">named</code> Service</a></span></dt><dt><span class="section"><a href="#s1-bind-zone">10.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="#s1-bind-rndc">10.4. Using the <code class="command">rndc</code> Utility</a></span></dt><dt><span class="section"><a href="#s1-bind-dig">10.5. Using the <code class="command">dig</code> Utility</a></span></dt><dt><span class="section"><a href="#s1-bind-features">10.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="#s1-bind-
mistakes">10.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="#s1-bind-additional-resources">10.8. Additional Resources</a></span></dt></dl></div><a id="id500647" class="indexterm"></a><a id="id675882" class="indexterm"></a><div class="para">
+ <code class="systemitem">DNS</code> (Domain Name System), also known as a <em class="firstterm">nameserver</em>, is a network system that associates hostnames with their respective IP addresses. For users, this has the advantage that they can refer to machines on the network by names that are usually easier to remember than the numerical network addresses. For system administrators, using the nameserver allows them to change the IP address for a host without ever affecting the name-based queries, or to decide which machines handle these queries.
+ </div><a id="id2216416" class="indexterm"></a><div class="para">
+ This chapter covers <code class="systemitem">BIND</code> (Berkeley Internet Name Domain), the DNS server included in Fedora. It focuses on the structure of its configuration files, and describes how to administer it both locally and remotely.
+ </div><div class="section" title="10.1. Introduction to DNS" id="s1-bind-introduction"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-introduction">10.1. Introduction to DNS</h2></div></div></div><a id="id2221385" class="indexterm"></a><div class="para">
+ DNS is usually implemented using one or more centralized servers that are authoritative for certain domains. When a client host requests information from a nameserver, it usually connects to port 53. The nameserver then attempts to resolve the name requested. If it does not have an authoritative answer, or does not already have the answer cached from an earlier query, it queries other nameservers, called <em class="firstterm">root nameservers</em>, to determine which nameservers are authoritative for the name in question, and then queries them to get the requested name.
+ </div><div class="section" title="10.1.1. Nameserver Zones" id="s2-bind-introduction-zones"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-introduction-zones">10.1.1. Nameserver Zones</h3></div></div></div><a id="id758454" class="indexterm"></a><a id="id709192" class="indexterm"></a><a id="id804648" class="indexterm"></a><a id="id729102" class="indexterm"></a><div class="para">
+ In a DNS server such as BIND, all information is stored in basic data elements called <em class="firstterm">resource records</em> (RR). The resource record is usually a <em class="firstterm">fully qualified domain name</em> (FQDN) of a host, and is broken down into multiple sections organized into a tree-like hierarchy. This hierarchy consists of a main trunk, primary branches, secondary branches, and so on.
+ </div><div class="example" title="Example 10.1. A simple resource record" id="example-bind-introduction-zones-rr"><h6>Example 10.1. A simple resource record</h6><div class="example-contents"><pre class="screen">bob.sales.example.com</pre></div></div><br class="example-break" /><a id="id1771046" class="indexterm"></a><div class="para">
+ Each level of the hierarchy is divided by a period (that is, <code class="literal">.</code>). In <a class="xref" href="#example-bind-introduction-zones-rr" title="Example 10.1. A simple resource record">Example 10.1, “A simple resource record”</a>, <code class="literal">com</code> defines the <em class="firstterm">top-level domain</em>, <code class="literal">example</code> its subdomain, and <code class="literal">sales</code> the subdomain of <code class="literal">example</code>. In this case, <code class="literal">bob</code> identifies a resource record that is part of the <code class="systemitem">sales.example.com</code> domain. With the exception of the part furthest to the left (that is, <code class="literal">bob</code>), each of these sections is called a <em class="firstterm">zone</em> and defines a specific <em class="firstterm">namespace</em>.
+ </div><a id="id550713" class="indexterm"></a><a id="id550729" class="indexterm"></a><div class="para">
+ Zones are defined on authoritative nameservers through the use of <em class="firstterm">zone files</em>, which contain definitions of the resource records in each zone. Zone files are stored on <em class="firstterm">primary nameservers</em> (also called <em class="firstterm">master nameservers</em>), where changes are made to the files, and <em class="firstterm">secondary nameservers</em> (also called <em class="firstterm">slave nameservers</em>), which receive zone definitions from the primary nameservers. Both primary and secondary nameservers are authoritative for the zone and look the same to clients. Depending on the configuration, any nameserver can also serve as a primary or secondary server for multiple zones at the same time.
+ </div></div><div class="section" title="10.1.2. Nameserver Types" id="s2-bind-introduction-nameservers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-introduction-nameservers">10.1.2. Nameserver Types</h3></div></div></div><div class="para">
+ There are two nameserver configuration types:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id533977" class="indexterm"></a>
+ <a id="id533992" class="indexterm"></a>
+ <a id="id534004" class="indexterm"></a>
+ <a id="id493102" class="indexterm"></a>
+ <a id="id493114" class="indexterm"></a>
+ <a id="id493130" class="indexterm"></a>
+ authoritative </span></dt><dd><div class="para">
+ Authoritative nameservers answer to resource records that are part of their zones only. This category includes both primary (master) and secondary (slave) nameservers.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id841612" class="indexterm"></a>
+ <a id="id841628" class="indexterm"></a>
+ recursive </span></dt><dd><div class="para">
+ Recursive nameservers offer resolution services, but they are not authoritative for any zone. Answers for all resolutions are cached in a memory for a fixed period of time, which is specified by the retrieved resource record.
+ </div></dd></dl></div><div class="para">
+ Although a nameserver can be both authoritative and recursive at the same time, it is recommended not to combine the configuration types. To be able to perform their work, authoritative servers should be available to all clients all the time. On the other hand, since the recursive lookup takes far more time than authoritative responses, recursive servers should be available to a restricted number of clients only, otherwise they are prone to distributed denial of service (DDoS) attacks.
+ </div></div><div class="section" title="10.1.3. BIND as a Nameserver" id="s2-bind-introduction-bind"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-introduction-bind">10.1.3. BIND as a Nameserver</h3></div></div></div><a id="id710981" class="indexterm"></a><a id="id679332" class="indexterm"></a><a id="id679349" class="indexterm"></a><a id="id556159" class="indexterm"></a><a id="id556174" class="indexterm"></a><a id="id556187" class="indexterm"></a><div class="para">
+ BIND consists of a set of DNS-related programs. It contains a monolithic nameserver called <code class="systemitem">named</code>, an administration utility called <code class="command">rndc</code>, and a debugging tool called <code class="command">dig</code>. Refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for more information on how to run a service in Fedora.
+ </div></div></div><div class="section" title="10.2. Configuring the named Service" id="s1-bind-namedconf"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-namedconf">10.2. Configuring the <code class="command">named</code> Service</h2></div></div></div><a id="id484437" class="indexterm"></a><div class="para">
+ When the <code class="systemitem">named</code> service is started, it reads the configuration from the files as described in <a class="xref" href="#table-bind-namedconf-files" title="Table 10.1. The named service configuration files">Table 10.1, “The <code class="systemitem">named</code> service configuration files”</a>.
+ </div><a id="id484471" class="indexterm"></a><a id="id556641" class="indexterm"></a><a id="id556659" class="indexterm"></a><div class="table" title="Table 10.1. The named service configuration files" id="table-bind-namedconf-files"><h6>Table 10.1. The <code class="systemitem">named</code> service configuration files</h6><div class="table-contents"><table summary="The named service configuration files" border="1"><colgroup><col width="38%" /><col width="63%" /></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc/named.conf</code>
+ </td><td>
+ The main configuration file.
+ </td></tr><tr><td>
+ <code class="filename">/etc/named/</code>
+ </td><td>
+ An auxiliary directory for configuration files that are included in the main configuration file.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The configuration file consists of a collection of statements with nested options surrounded by opening and closing curly brackets (that is, <code class="literal">{</code> and <code class="literal">}</code>). Note that when editing the file, you have to be careful not to make any syntax error, otherwise the <code class="systemitem">named</code> service will not start. A typical <code class="filename">/etc/named.conf</code> file is organized as follows:
+ </div><pre class="screen"><em class="replaceable"><code>statement-1</code></em> ["<em class="replaceable"><code>statement-1-name</code></em>"] [<em class="replaceable"><code>statement-1-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-2</code></em> ["<em class="replaceable"><code>statement-2-name</code></em>"] [<em class="replaceable"><code>statement-2-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-N</code></em> ["<em class="replaceable"><code>statement-N-name</code></em>"] [<em class="replaceable"><code>statement-N-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};</pre><div class="note" title="Note: Running BIND in a Chroot Environment"><div class="admonition_header"><h2>Note: Running BIND in a Chroot Environment</h2></div><div class="admonition"><div class="para">
+ If you have installed the <span class="package">bind-chroot</span> package, the BIND service will run in the <code class="filename">/var/named/chroot</code> environment. In that case, the initialization script will mount the above configuration files using the <code class="command">mount --bind</code> command, so that you can manage the configuration outside this environment.
+ </div></div></div><div class="section" title="10.2.1. Common Statement Types" id="s2-bind-namedconf-state"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-namedconf-state">10.2.1. Common Statement Types</h3></div></div></div><div class="para">
+ The following types of statements are commonly used in <code class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id541629" class="indexterm"></a>
+ <code class="option">acl</code> </span></dt><dd><div class="para">
+ The <code class="option">acl</code> (Access Control List) statement allows you to define groups of hosts, so that they can be permitted or denied access to the nameserver. It takes the following form:
+ </div><pre class="screen">acl <em class="replaceable"><code>acl-name</code></em> {
+ <em class="replaceable"><code>match-element</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>acl-name</code></em> statement name is the name of the access control list, and the <em class="replaceable"><code>match-element</code></em> option is usually an individual IP address (such as <code class="literal">10.0.1.1</code>) or a CIDR network notation (for example, <code class="literal">10.0.1.0/24</code>). For a list of already defined keywords, see <a class="xref" href="#table-bind-namedconf-common-acl" title="Table 10.2. Predefined access control lists">Table 10.2, “Predefined access control lists”</a>.
+ </div><div class="table" title="Table 10.2. Predefined access control lists" id="table-bind-namedconf-common-acl"><h6>Table 10.2. Predefined access control lists</h6><div class="table-contents"><table summary="Predefined access control lists" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Keyword
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">any</code>
+ </td><td>
+ Matches every IP address.
+ </td></tr><tr><td>
+ <code class="option">localhost</code>
+ </td><td>
+ Matches any IP address that is in use by the local system.
+ </td></tr><tr><td>
+ <code class="option">localnets</code>
+ </td><td>
+ Matches any IP address on any network to which the local system is connected.
+ </td></tr><tr><td>
+ <code class="option">none</code>
+ </td><td>
+ Does not match any IP address.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="option">acl</code> statement can be especially useful with conjunction with other statements such as <code class="option">options</code>. <a class="xref" href="#example-bind-namedconf-common-acl" title="Example 10.2. Using acl in conjunction with options">Example 10.2, “Using <code class="option">acl</code> in conjunction with <code class="option">options</code>”</a> defines two access control lists, <code class="literal">black-hats</code> and <code class="literal">red-hats</code>, and adds <code class="literal">black-hats</code> on the blacklist while granting <code class="literal">red-hats</code> a normal access.
+ </div><div class="example" title="Example 10.2. Using acl in conjunction with options" id="example-bind-namedconf-common-acl"><h6>Example 10.2. Using <code class="option">acl</code> in conjunction with <code class="option">options</code></h6><div class="example-contents"><pre class="screen">acl black-hats {
+ 10.0.2.0/24;
+ 192.168.0.0/24;
+ 1234:5678::9abc/24;
+};
+acl red-hats {
+ 10.0.1.0/24;
+};
+options {
+ blackhole { black-hats; };
+ allow-query { red-hats; };
+ allow-query-cache { red-hats; };
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id485547" class="indexterm"></a>
+ <code class="option">include</code> </span></dt><dd><div class="para">
+ The <code class="option">include</code> statement allows you to include files in the <code class="filename">/etc/named.conf</code>, so that potentially sensitive data can be placed in a separate file with restricted permissions. It takes the following form:
+ </div><pre class="screen">include "<em class="replaceable"><code>file-name</code></em>"</pre><div class="para">
+ The <em class="replaceable"><code>file-name</code></em> statement name is an absolute path to a file.
+ </div><div class="example" title="Example 10.3. Including a file to /etc/named.conf" id="example-bind-namedconf-common-include"><h6>Example 10.3. Including a file to <code class="filename">/etc/named.conf</code></h6><div class="example-contents"><pre class="screen">include "/etc/named.rfc1912.zones";</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id702174" class="indexterm"></a>
+ <code class="option">options</code> </span></dt><dd><div class="para">
+ The <code class="option">options</code> statement allows you to define global server configuration options as well as to set defaults for other statements. It can be used to specify the location of the <code class="systemitem">named</code> working directory, the types of queries allowed, and much more. It takes the following form:
+ </div><pre class="screen">options {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ For a list of frequently used <em class="replaceable"><code>option</code></em> directives, see <a class="xref" href="#table-bind-namedconf-common-options" title="Table 10.3. Commonly used options">Table 10.3, “Commonly used options”</a> below.
+ </div><div class="table" title="Table 10.3. Commonly used options" id="table-bind-namedconf-common-options"><h6>Table 10.3. Commonly used options</h6><div class="table-contents"><table summary="Commonly used options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow-query</code>
+ </td><td>
+ Specifies which hosts are allowed to query the nameserver for authoritative resource records. It accepts an access control lists, a collection of IP addresses, or networks in the CIDR notation. All hosts are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">allow-query-cache</code>
+ </td><td>
+ Specifies which hosts are allowed to query the nameserver for non-authoritative data such as recursive queries. Only <code class="literal">localhost</code> and <code class="literal">localnets</code> are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">blackhole</code>
+ </td><td>
+ Specifies which hosts are <span class="emphasis"><em>not</em></span> allowed to query the nameserver. This option should be used when particular host or network floods the server with requests. The default option is <code class="literal">none</code>.
+ </td></tr><tr><td>
+ <code class="option">directory</code>
+ </td><td>
+ Specifies a working directory for the <code class="systemitem">named</code> service. The default option is <code class="literal">/var/named/</code>.
+ </td></tr><tr><td>
+ <code class="option">dnssec-enable</code>
+ </td><td>
+ Specifies whether to return DNSSEC related resource records. The default option is <code class="literal">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">dnssec-validation</code>
+ </td><td>
+ Specifies whether to prove that resource records are authentic via DNSSEC. The default option is <code class="option">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">forwarders</code>
+ </td><td>
+ Specifies a list of valid IP addresses for nameservers to which the requests should be forwarded for resolution.
+ </td></tr><tr><td>
+ <code class="option">forward</code>
+ </td><td>
+ <div class="para">
+ Specifies the behavior of the <code class="option">forwarders</code> directive. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">first</code> — The server will query the nameservers listed in the <code class="option">forwarders</code> directive before attempting to resolve the name on its own.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">only</code> — When unable to query the nameservers listed in the <code class="option">forwarders</code> directive, the server will not attempt to resolve the name on its own.
+ </div></li></ul></div>
+
+ </td></tr><tr><td>
+ <code class="option">listen-on</code>
+ </td><td>
+ Specifies the IPv4 network interface on which to listen for queries. On a DNS server that also acts as a gateway, you can use this option to answer queries originating from a single network only. All IPv4 interfaces are used by default.
+ </td></tr><tr><td>
+ <code class="option">listen-on-v6</code>
+ </td><td>
+ Specifies the IPv6 network interface on which to listen for queries. On a DNS server that also acts as a gateway, you can use this option to answer queries originating from a single network only. All IPv6 interfaces are used by default.
+ </td></tr><tr><td>
+ <code class="option">max-cache-size</code>
+ </td><td>
+ Specifies the maximum amount of memory to be used for server caches. When the limit is reached, the server causes records to expire prematurely so that the limit is not exceeded. In a server with multiple views, the limit applies separately to the cache of each view. The default option is <code class="literal">32M</code>.
+ </td></tr><tr><td>
+ <code class="option">notify</code>
+ </td><td>
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">yes</code> — The server will notify all secondary nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">no</code> — The server will <span class="emphasis"><em>not</em></span> notify any secondary nameserver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master-only</code> — The server will notify primary server for the zone only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">explicit</code> — The server will notify only the secondary servers that are specified in the <code class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td>
+ <code class="option">pid-file</code>
+ </td><td>
+ Specifies the location of the process ID file created by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <code class="option">recursion</code>
+ </td><td>
+ Specifies whether to act as a recursive server. The default option is <code class="literal">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">statistics-file</code>
+ </td><td>
+ Specifies an alternate location for statistics files. The <code class="filename">/var/named/named.stats</code> file is used by default.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="important" title="Important: Restrict Recursive Servers to Selected Clients Only"><div class="admonition_header"><h2>Important: Restrict Recursive Servers to Selected Clients Only</h2></div><div class="admonition"><div class="para">
+ To prevent distributed denial of service (DDoS) attacks, it is recommended that you use the <code class="option">allow-query-cache</code> option to restrict recursive DNS services for a particular subset of clients only.
+ </div></div></div><div class="para">
+ Refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#s2-bind-installed-docs" title="10.8.1. Installed Documentation">Section 10.8.1, “Installed Documentation”</a>, and the <code class="filename">named.conf</code> manual page for a complete list of available options.
+ </div><div class="example" title="Example 10.4. Using the options statement" id="example-bind-namedconf-common-options"><h6>Example 10.4. Using the <code class="option">options</code> statement</h6><div class="example-contents"><pre class="screen">options {
+ allow-query { localhost; };
+ listen-on port 53 { 127.0.0.1; };
+ listen-on-v6 port 53 { ::1; };
+ max-cache-size 256M;
+ directory "/var/named";
+ statistics-file "/var/named/data/named_stats.txt";
+
+ recursion yes;
+ dnssec-enable yes;
+ dnssec-validation yes;
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id454947" class="indexterm"></a>
+ <code class="option">zone</code> </span></dt><dd><div class="para">
+ The <code class="option">zone</code> statement allows you to define the characteristics of a zone, such as the location of its configuration file and zone-specific options, and can be used to override the global <code class="option">options</code> statements. It takes the following form:
+ </div><pre class="screen">zone <em class="replaceable"><code>zone-name</code></em> [<em class="replaceable"><code>zone-class</code></em>] {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is the name of the zone, <em class="replaceable"><code>zone-class</code></em> is the optional class of the zone, and <em class="replaceable"><code>option</code></em> is a <code class="option">zone</code> statement option as described in <a class="xref" href="#table-bind-namedconf-common-zone" title="Table 10.4. Commonly used options">Table 10.4, “Commonly used options”</a>.
+ </div><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is particularly important, as it is the default value assigned for the <code class="option">$ORIGIN</code> directive used within the corresponding zone file located in the <code class="filename">/var/named/</code> directory. The <code class="systemitem">named</code> daemon appends the name of the zone to any non-fully qualified domain name listed in the zone file. For example, if a <code class="option">zone</code> statement defines the namespace for <code class="literal">example.com</code>, use <code class="literal">example.com</code> as the <em class="replaceable"><code>zone-name</code></em> so that it is placed at the end of hostnames within the <code class="literal">example.com</code> zone file.
+ </div><div class="para">
+ For more information about zone files, refer to <a class="xref" href="#s1-bind-zone" title="10.3. Editing Zone Files">Section 10.3, “Editing Zone Files”</a>.
+ </div><div class="table" title="Table 10.4. Commonly used options" id="table-bind-namedconf-common-zone"><h6>Table 10.4. Commonly used options</h6><div class="table-contents"><table summary="Commonly used options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow-query</code>
+ </td><td>
+ Specifies which clients are allowed to request information about this zone. This option overrides global <code class="option">allow-query</code> option. All query requests are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">allow-transfer</code>
+ </td><td>
+ Specifies which secondary servers are allowed to request a transfer of the zone's information. All transfer requests are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">allow-update</code>
+ </td><td>
+ <div class="para">
+ Specifies which hosts are allowed to dynamically update information in their zone. The default option is to deny all dynamic update requests.
+ </div>
+ <div class="para">
+ Note that you should be careful when allowing hosts to update information about their zone. Do not set IP addresses in this option unless the server is in the trusted network. Instead, use TSIG key as described in <a class="xref" href="#s2-bind-features-tsig" title="10.6.3. Transaction SIGnatures (TSIG)">Section 10.6.3, “Transaction SIGnatures (TSIG)”</a>.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="option">file</code>
+ </td><td>
+ Specifies the name of the file in the <code class="systemitem">named</code> working directory that contains the zone's configuration data.
+ </td></tr><tr><td>
+ <code class="option">masters</code>
+ </td><td>
+ Specifies from which IP addresses to request authoritative zone information. This option is used only if the zone is defined as <code class="option">type</code> <code class="option">slave</code>.
+ </td></tr><tr><td>
+ <code class="option">notify</code>
+ </td><td>
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">yes</code> — The server will notify all secondary nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">no</code> — The server will <span class="emphasis"><em>not</em></span> notify any secondary nameserver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master-only</code> — The server will notify primary server for the zone only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">explicit</code> — The server will notify only the secondary servers that are specified in the <code class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td>
+ <code class="option">type</code>
+ </td><td>
+ <div class="para">
+ Specifies the zone type. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">delegation-only</code> — Enforces the delegation status of infrastructure zones such as COM, NET, or ORG. Any answer that is received without an explicit or implicit delegation is treated as <code class="literal">NXDOMAIN</code>. This option is only applicable in TLDs or root zone files used in recursive or caching implementations.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">forward</code> — Forwards all requests for information about this zone to other nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">hint</code> — A special type of zone used to point to the root nameservers which resolve queries when a zone is not otherwise known. No configuration beyond the default is necessary with a <code class="option">hint</code> zone.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master</code> — Designates the nameserver as authoritative for this zone. A zone should be set as the <code class="option">master</code> if the zone's configuration files reside on the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">slave</code> — Designates the nameserver as a slave server for this zone. Master server is specified in <code class="option">masters</code> directive.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Most changes to the <code class="filename">/etc/named.conf</code> file of a primary or secondary nameserver involve adding, modifying, or deleting <code class="option">zone</code> statements, and only a small subset of <code class="option">zone</code> statement options is usually needed for a nameserver to work efficiently.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-namedconf-common-zone-primary" title="Example 10.5. A zone statement for a primary nameserver">Example 10.5, “A <code class="option">zone</code> statement for a primary nameserver”</a>, the zone is identified as <code class="literal">example.com</code>, the type is set to <code class="literal">master</code>, and the <code class="systemitem">named</code> service is instructed to read the <code class="filename">/var/named/example.com.zone</code> file. It also allows only a secondary nameserver (<code class="literal">192.168.0.2</code>) to transfer the zone.
+ </div><div class="example" title="Example 10.5. A zone statement for a primary nameserver" id="example-bind-namedconf-common-zone-primary"><h6>Example 10.5. A <code class="option">zone</code> statement for a primary nameserver</h6><div class="example-contents"><pre class="screen">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-transfer { 192.168.0.2; };
+};</pre></div></div><br class="example-break" /><div class="para">
+ A secondary server's <code class="option">zone</code> statement is slightly different. The type is set to <code class="literal">slave</code>, and the <code class="literal">masters</code> directive is telling <code class="systemitem">named</code> the IP address of the master server.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-namedconf-common-zone-secondary" title="Example 10.6. A zone statement for a secondary nameserver">Example 10.6, “A <code class="option">zone</code> statement for a secondary nameserver”</a>, the <code class="systemitem">named</code> service is configured to query the primary server at the <code class="literal">192.168.0.1</code> IP address for information about the <code class="literal">example.com</code> zone. The received information is then saved to the <code class="filename">/var/named/slaves/example.com.zone</code> file. Note that you have to put all slave zones to <code class="filename">/var/named/slaves</code> directory, otherwise the service will fail to transfer the zone.
+ </div><div class="example" title="Example 10.6. A zone statement for a secondary nameserver" id="example-bind-namedconf-common-zone-secondary"><h6>Example 10.6. A <code class="option">zone</code> statement for a secondary nameserver</h6><div class="example-contents"><pre class="screen">zone "example.com" {
+ type slave;
+ file "slaves/example.com.zone";
+ masters { 192.168.0.1; };
+};</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" title="10.2.2. Other Statement Types" id="s2-bind-namedconf-state-other"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-namedconf-state-other">10.2.2. Other Statement Types</h3></div></div></div><div class="para">
+ The following types of statements are less commonly used in <code class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id448602" class="indexterm"></a>
+ <code class="option">controls</code> </span></dt><dd><div class="para">
+ The <code class="option">controls</code> statement allows you to configure various security requirements necessary to use the <code class="command">rndc</code> command to administer the <code class="systemitem">named</code> service.
+ </div><div class="para">
+ Refer to <a class="xref" href="#s1-bind-rndc" title="10.4. Using the rndc Utility">Section 10.4, “Using the <code class="command">rndc</code> Utility”</a> for more information on the <code class="command">rndc</code> utility and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id707674" class="indexterm"></a>
+ <code class="option">key</code> </span></dt><dd><div class="para">
+ The <code class="option">key</code> statement allows you to define a particular key by name. Keys are used to authenticate various actions, such as secure updates or the use of the <code class="command">rndc</code> command. Two options are used with <code class="option">key</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">algorithm <em class="replaceable"><code>algorithm-name</code></em></code> — The type of algorithm to be used (for example, <code class="literal">hmac-md5</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">secret "<em class="replaceable"><code>key-value</code></em>"</code> — The encrypted key.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref" href="#s1-bind-rndc" title="10.4. Using the rndc Utility">Section 10.4, “Using the <code class="command">rndc</code> Utility”</a> for more information on the <code class="command">rndc</code> utility and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id821276" class="indexterm"></a>
+ <code class="option">logging</code> </span></dt><dd><div class="para">
+ The <code class="option">logging</code> statement allows you to use multiple types of logs, so called <em class="firstterm">channels</em>. By using the <code class="option">channel</code> option within the statement, you can construct a customized type of log with its own file name (<code class="option">file</code>), size limit (<code class="option">size</code>), versioning (<code class="option">version</code>), and level of importance (<code class="option">severity</code>). Once a customized channel is defined, a <code class="option">category</code> option is used to categorize the channel and begin logging when the <code class="systemitem">named</code> service is restarted.
+ </div><div class="para">
+ By default, <code class="systemitem">named</code> sends standard messages to the <code class="systemitem">rsyslog</code> daemon, which places them in <code class="filename">/var/log/messages</code>. Several standard channels are built into BIND with various severity levels, such as <code class="literal">default_syslog</code> (which handles informational logging messages) and <code class="literal">default_debug</code> (which specifically handles debugging messages). A default category, called <code class="literal">default</code>, uses the built-in channels to do normal logging without any special configuration.
+ </div><div class="para">
+ Customizing the logging process can be a very detailed process and is beyond the scope of this chapter. For information on creating custom BIND logs, refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#s2-bind-installed-docs" title="10.8.1. Installed Documentation">Section 10.8.1, “Installed Documentation”</a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id487528" class="indexterm"></a>
+ <code class="option">server</code> </span></dt><dd><div class="para">
+ The <code class="option">server</code> statement allows you to specify options that affect how the <code class="systemitem">named</code> service should respond to remote nameservers, especially with regard to notifications and zone transfers.
+ </div><div class="para">
+ The <code class="option">transfer-format</code> option controls the number of resource records that are sent with each message. It can be either <code class="literal">one-answer</code> (only one resource record), or <code class="literal">many-answers</code> (multiple resource records). Note that while the <code class="literal">many-answers</code> option is more efficient, it is not supported by older versions of BIND.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id735358" class="indexterm"></a>
+ <code class="option">trusted-keys</code> </span></dt><dd><div class="para">
+ The <code class="option">trusted-keys</code> statement allows you to specify assorted public keys used for secure DNS (DNSSEC). Refer to <a class="xref" href="#s2-bind-features-dnssec" title="10.6.4. DNS Security Extensions (DNSSEC)">Section 10.6.4, “DNS Security Extensions (DNSSEC)”</a> for more information on this topic.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id437318" class="indexterm"></a>
+ <code class="option">view</code> </span></dt><dd><div class="para">
+ The <code class="option">view</code> statement allows you to create special views depending upon which network the host querying the nameserver is on. This allows some hosts to receive one answer regarding a zone while other hosts receive totally different information. Alternatively, certain zones may only be made available to particular trusted hosts while non-trusted hosts can only make queries for other zones.
+ </div><div class="para">
+ Multiple views can be used as long as their names are unique. The <code class="option">match-clients</code> option allows you to specify the IP addresses that apply to a particular view. If the <code class="option">options</code> statement is used within a view, it overrides the already configured global options. Finally, most <code class="option">view</code> statements contain multiple <code class="option">zone</code> statements that apply to the <code class="option">match-clients</code> list.
+ </div><div class="para">
+ Note that the order in which the <code class="option">view</code> statements are listed is important, as the first statement that matches a particular client's IP address is used. For more information on this topic, refer to <a class="xref" href="#s2-bind-features-views" title="10.6.1. Multiple Views">Section 10.6.1, “Multiple Views”</a>.
+ </div></dd></dl></div></div><div class="section" title="10.2.3. Comment Tags" id="s2-bind-namedconf-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-namedconf-comm">10.2.3. Comment Tags</h3></div></div></div><a id="id740270" class="indexterm"></a><div class="para">
+ Additionally to statements, the <code class="filename">/etc/named.conf</code> file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to a user. The following are valid comment tags:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="literal">//</code></span></dt><dd><div class="para">
+ Any text after the <code class="literal">//</code> characters to the end of the line is considered a comment. For example:
+ </div><pre class="screen">notify yes; // notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"><code class="literal">#</code></span></dt><dd><div class="para">
+ Any text after the <code class="literal">#</code> character to the end of the line is considered a comment. For example:
+ </div><pre class="screen">notify yes; # notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"><code class="literal">/*</code> and <code class="literal">*/</code></span></dt><dd><div class="para">
+ Any block of text enclosed in <code class="literal">/*</code> and <code class="literal">*/</code> is considered a comment. For example:
+ </div><pre class="screen">notify yes; /* notify all secondary nameservers */</pre></dd></dl></div></div></div><div class="section" title="10.3. Editing Zone Files" id="s1-bind-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-zone">10.3. Editing Zone Files</h2></div></div></div><a id="id448076" class="indexterm"></a><a id="id448096" class="indexterm"></a><a id="id434801" class="indexterm"></a><a id="id434821" class="indexterm"></a><div class="para">
+ As outlined in <a class="xref" href="#s2-bind-introduction-zones" title="10.1.1. Nameserver Zones">Section 10.1.1, “Nameserver Zones”</a>, zone files contain information about a namespace. They are stored in the <code class="systemitem">named</code> working directory located in <code class="filename">/var/named/</code> by default, and each zone file is named according to the <code class="option">file</code> option in the <code class="option">zone</code> statement, usually in a way that relates to the domain in question and identifies the file as containing zone data, such as <code class="filename">example.com.zone</code>.
+ </div><div class="table" title="Table 10.5. The named service zone files" id="table-bind-zone-files"><h6>Table 10.5. The <code class="systemitem">named</code> service zone files</h6><div class="table-contents"><table summary="The named service zone files" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/var/named/</code>
+ </td><td>
+ The working directory for the <code class="systemitem">named</code> service. The nameserver is <span class="emphasis"><em>not</em></span> allowed to write to this directory.
+ </td></tr><tr><td>
+ <code class="filename">/var/named/slaves/</code>
+ </td><td>
+ The directory for secondary zones. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <code class="filename">/var/named/dynamic/</code>
+ </td><td>
+ The directory for other files, such as dynamic DNS (DDNS) zones or managed DNSSEC keys. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <code class="filename">/var/named/data/</code>
+ </td><td>
+ The directory for various statistics and debugging files. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ A zone file consists of directives and resource records. Directives tell the nameserver to perform tasks or apply special settings to the zone, resource records define the parameters of the zone and assign identities to individual hosts. While the directives are optional, the resource records are required in order to provide name service to a zone.
+ </div><div class="para">
+ All directives and resource records should be entered on individual lines.
+ </div><div class="section" title="10.3.1. Common Directives" id="s2-bind-zone-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-zone-directives">10.3.1. Common Directives</h3></div></div></div><div class="para">
+ Directives begin with the dollar sign character (that is, <code class="literal">$</code>) followed by the name of the directive, and usually appear at the top of the file. The following directives are commonly used in zone files:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id543900" class="indexterm"></a>
+ <code class="command">$INCLUDE</code> </span></dt><dd><div class="para">
+ The <code class="command">$INCLUDE</code> directive allows you to include another file at the place where it appears, so that other zone settings can be stored in a separate zone file.
+ </div><div class="example" title="Example 10.7. Using the $INCLUDE directive" id="example-bind-zone-directive-include"><h6>Example 10.7. Using the <code class="command">$INCLUDE</code> directive</h6><div class="example-contents"><pre class="screen">$INCLUDE /var/named/penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id720999" class="indexterm"></a>
+ <code class="command">$ORIGIN</code> </span></dt><dd><div class="para">
+ The <code class="command">$ORIGIN</code> directive allows you to append the domain name to unqualified records, such as those with the hostname only. Note that the use of this directive is not necessary if the zone is specified in <code class="filename">/etc/named.conf</code>, since the zone name is used by default.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-zone-directive-origin" title="Example 10.8. Using the $ORIGIN directive">Example 10.8, “Using the <code class="command">$ORIGIN</code> directive”</a>, any names used in resource records that do not end in a trailing period (that is, the <code class="literal">.</code> character) are appended with <code class="literal">example.com</code>.
+ </div><div class="example" title="Example 10.8. Using the $ORIGIN directive" id="example-bind-zone-directive-origin"><h6>Example 10.8. Using the <code class="command">$ORIGIN</code> directive</h6><div class="example-contents"><pre class="screen">$ORIGIN example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id791748" class="indexterm"></a>
+ <code class="command">$TTL</code> </span></dt><dd><div class="para">
+ The <code class="command">$TTL</code> directive allows you to set the default <em class="firstterm">Time to Live</em> (TTL) value for the zone, that is, how long is a zone record valid. Each resource record can contain its own TTL value, which overrides this directive.
+ </div><div class="para">
+ Increasing this value allows remote nameservers to cache the zone information for a longer period of time, reducing the number of queries for the zone and lengthening the amount of time required to proliferate resource record changes.
+ </div><div class="example" title="Example 10.9. Using the $TTL directive" id="example-bind-zone-directive-ttl"><h6>Example 10.9. Using the <code class="command">$TTL</code> directive</h6><div class="example-contents"><pre class="screen">$TTL 1D</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" title="10.3.2. Common Resource Records" id="s3-bind-zone-rr"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s3-bind-zone-rr">10.3.2. Common Resource Records</h3></div></div></div><div class="para">
+ The following resource records are commonly used in zone files:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id1050691" class="indexterm"></a>
+ <code class="command">A</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Address</em> record specifies an IP address to be assigned to a name. It takes the following form:
+ </div><pre class="screen"><em class="replaceable"><code>hostname</code></em> IN A <em class="replaceable"><code>IP-address</code></em></pre><div class="para">
+ If the <em class="replaceable"><code>hostname</code></em> value is omitted, the record will point to the last specified <em class="replaceable"><code>hostname</code></em>.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-zone-rr-a" title="Example 10.10. Using the A resource record">Example 10.10, “Using the <code class="command">A</code> resource record”</a>, the requests for <code class="systemitem">server1.example.com</code> are pointed to <code class="literal">10.0.1.3</code> or <code class="literal">10.0.1.5</code>.
+ </div><div class="example" title="Example 10.10. Using the A resource record" id="example-bind-zone-rr-a"><h6>Example 10.10. Using the <code class="command">A</code> resource record</h6><div class="example-contents"><pre class="screen">server1 IN A 10.0.1.3
+ IN A 10.0.1.5</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1553359" class="indexterm"></a>
+ <code class="command">CNAME</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Canonical Name</em> record maps one name to another. Because of this, this type of record is sometimes referred to as an <em class="firstterm">alias record</em>. It takes the following form:
+ </div><pre class="screen"><em class="replaceable"><code>alias-name</code></em> IN CNAME <em class="replaceable"><code>real-name</code></em></pre><div class="para">
+ <code class="command">CNAME</code> records are most commonly used to point to services that use a common naming scheme, such as <code class="literal">www</code> for Web servers. However, there are multiple restrictions for their usage:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ CNAME records should not point to other CNAME records. This is mainly to avoid possible infinite loops.
+ </div></li><li class="listitem"><div class="para">
+ CNAME records should not contain other resource record types (such as A, NS, MX, etc.). The only exception are DNSSEC related records (that is, RRSIG, NSEC, etc.) when the zone is signed.
+ </div></li><li class="listitem"><div class="para">
+ Other resource record that point to the fully qualified domain name (FQDN) of a host (that is, NS, MX, PTR) should not point to a CNAME record.
+ </div></li></ul></div><div class="para">
+ In <a class="xref" href="#example-bind-zone-rr-cname" title="Example 10.11. Using the CNAME resource record">Example 10.11, “Using the <code class="command">CNAME</code> resource record”</a>, the <code class="command">A</code> record binds a hostname to an IP address, while the <code class="command">CNAME</code> record points the commonly used <code class="literal">www</code> hostname to it.
+ </div><div class="example" title="Example 10.11. Using the CNAME resource record" id="example-bind-zone-rr-cname"><h6>Example 10.11. Using the <code class="command">CNAME</code> resource record</h6><div class="example-contents"><pre class="screen">server1 IN A 10.0.1.5
+www IN CNAME server1</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id489602" class="indexterm"></a>
+ <code class="command">MX</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Mail Exchange</em> record specifies where the mail sent to a particular namespace controlled by this zone should go. It takes the following form:
+ </div><pre class="screen">IN MX <em class="replaceable"><code>preference-value</code></em> <em class="replaceable"><code>email-server-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>email-server-name</code></em> is a fully qualified domain name (FQDN). The <em class="replaceable"><code>preference-value</code></em> allows numerical ranking of the email servers for a namespace, giving preference to some email systems over others. The <code class="command">MX</code> resource record with the lowest <em class="replaceable"><code>preference-value</code></em> is preferred over the others. However, multiple email servers can possess the same value to distribute email traffic evenly among them.
+ </div><div class="para">
+ In <a class="xref" href="#example-bind-zone-rr-mx" title="Example 10.12. Using the MX resource record">Example 10.12, “Using the <code class="command">MX</code> resource record”</a>, the first <code class="systemitem">mail.example.com</code> email server is preferred to the <code class="systemitem">mail2.example.com</code> email server when receiving email destined for the <code class="systemitem">example.com</code> domain.
+ </div><div class="example" title="Example 10.12. Using the MX resource record" id="example-bind-zone-rr-mx"><h6>Example 10.12. Using the <code class="command">MX</code> resource record</h6><div class="example-contents"><pre class="screen">example.com. IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id659022" class="indexterm"></a>
+ <code class="command">NS</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Nameserver</em> record announces authoritative nameservers for a particular zone. It takes the following form:
+ </div><pre class="screen">IN NS <em class="replaceable"><code>nameserver-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>nameserver-name</code></em> should be a fully qualified domain name (FQDN). Note that when two nameservers are listed as authoritative for the domain, it is not important whether these nameservers are secondary nameservers, or if one of them is a primary server. They are both still considered authoritative.
+ </div><div class="example" title="Example 10.13. Using the NS resource record" id="example-bind-zone-rr-ns"><h6>Example 10.13. Using the <code class="command">NS</code> resource record</h6><div class="example-contents"><pre class="screen">IN NS dns1.example.com.
+IN NS dns2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id529109" class="indexterm"></a>
+ <code class="command">PTR</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Pointer</em> record points to another part of the namespace. It takes the following form:
+ </div><pre class="screen"><em class="replaceable"><code>last-IP-digit</code></em> IN PTR <em class="replaceable"><code>FQDN-of-system</code></em></pre><div class="para">
+ The <em class="replaceable"><code>last-IP-digit</code></em> directive is the last number in an IP address, and the <em class="replaceable"><code>FQDN-of-system</code></em> is a fully qualified domain name (FQDN).
+ </div><div class="para">
+ <code class="command">PTR</code> records are primarily used for reverse name resolution, as they point IP addresses back to a particular name. Refer to <a class="xref" href="#s2-bind-configuration-zone-reverse" title="10.3.4.2. A Reverse Name Resolution Zone File">Section 10.3.4.2, “A Reverse Name Resolution Zone File”</a> for more examples of <code class="command">PTR</code> records in use.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id566341" class="indexterm"></a>
+ <code class="command">SOA</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Start of Authority</em> record announces important authoritative information about a namespace to the nameserver. Located after the directives, it is the first resource record in a zone file. It takes the following form:
+ </div><pre class="screen">@ IN SOA <em class="replaceable"><code>primary-name-server</code></em> <em class="replaceable"><code>hostmaster-email</code></em> (
+ <em class="replaceable"><code>serial-number</code></em>
+ <em class="replaceable"><code>time-to-refresh</code></em>
+ <em class="replaceable"><code>time-to-retry</code></em>
+ <em class="replaceable"><code>time-to-expire</code></em>
+ <em class="replaceable"><code>minimum-TTL</code></em> )</pre><div class="para">
+ The directives are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="literal">@</code> symbol places the <code class="command">$ORIGIN</code> directive (or the zone's name if the <code class="command">$ORIGIN</code> directive is not set) as the namespace being defined by this <code class="command">SOA</code> resource record.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>primary-name-server</code></em> directive is the hostname of the primary nameserver that is authoritative for this domain.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>hostmaster-email</code></em> directive is the email of the person to contact about the namespace.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>serial-number</code></em> directive is a numerical value incremented every time the zone file is altered to indicate it is time for the <code class="systemitem">named</code> service to reload the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-refresh</code></em> directive is the numerical value secondary nameservers use to determine how long to wait before asking the primary nameserver if any changes have been made to the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-retry</code></em> directive is a numerical value used by secondary nameservers to determine the length of time to wait before issuing a refresh request in the event that the primary nameserver is not answering. If the primary server has not replied to a refresh request before the amount of time specified in the <em class="replaceable"><code>time-to-expire</code></em> directive elapses, the secondary servers stop responding as an authority for requests concerning that namespace.
+ </div></li><li class="listitem"><div class="para">
+ In BIND 4 and 8, the <em class="replaceable"><code>minimum-TTL</code></em> directive is the amount of time other nameservers cache the zone's information. In BIND 9, it defines how long negative answers are cached for. Caching of negative answers can be set to a maximum of 3 hours (that is, <code class="option">3H</code>).
+ </div></li></ul></div><div class="para">
+ When configuring BIND, all times are specified in seconds. However, it is possible to use abbreviations when specifying units of time other than seconds, such as minutes (<code class="literal">M</code>), hours (<code class="literal">H</code>), days (<code class="literal">D</code>), and weeks (<code class="literal">W</code>). <a class="xref" href="#tb-bind-seconds" title="Table 10.6. Seconds compared to other time units">Table 10.6, “Seconds compared to other time units”</a> shows an amount of time in seconds and the equivalent time in another format.
+ </div><div class="table" title="Table 10.6. Seconds compared to other time units" id="tb-bind-seconds"><h6>Table 10.6. Seconds compared to other time units</h6><div class="table-contents"><table summary="Seconds compared to other time units" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th>
+ Seconds
+ </th><th>
+ Other Time Units
+ </th></tr></thead><tbody><tr><td>
+ 60
+ </td><td>
+ <code class="literal">1M</code>
+ </td></tr><tr><td>
+ 1800
+ </td><td>
+ <code class="literal">30M</code>
+ </td></tr><tr><td>
+ 3600
+ </td><td>
+ <code class="literal">1H</code>
+ </td></tr><tr><td>
+ 10800
+ </td><td>
+ <code class="literal">3H</code>
+ </td></tr><tr><td>
+ 21600
+ </td><td>
+ <code class="literal">6H</code>
+ </td></tr><tr><td>
+ 43200
+ </td><td>
+ <code class="literal">12H</code>
+ </td></tr><tr><td>
+ 86400
+ </td><td>
+ <code class="literal">1D</code>
+ </td></tr><tr><td>
+ 259200
+ </td><td>
+ <code class="literal">3D</code>
+ </td></tr><tr><td>
+ 604800
+ </td><td>
+ <code class="literal">1W</code>
+ </td></tr><tr><td>
+ 31536000
+ </td><td>
+ <code class="literal">365D</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 10.14. Using the SOA resource record" id="example-bind-zone-rr-soa"><h6>Example 10.14. Using the <code class="command">SOA</code> resource record</h6><div class="example-contents"><pre class="screen">@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" title="10.3.3. Comment Tags" id="s2-bind-zone-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-zone-comm">10.3.3. Comment Tags</h3></div></div></div><a id="id1711651" class="indexterm"></a><div class="para">
+ Additionally to resource records and directives, a zone file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to the user. Any text after the semicolon character (that is, <code class="literal">;</code>) to the end of the line is considered a comment. For example:
+ </div><pre class="screen"> 604800 ; expire after 1 week</pre></div><div class="section" title="10.3.4. Example Usage" id="s2-bind-zone-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-zone-examples">10.3.4. Example Usage</h3></div></div></div><div class="para">
+ The following examples show the basic usage of zone files.
+ </div><div class="section" title="10.3.4.1. A Simple Zone File" id="s3-bind-zone-examples-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-zone-examples-basic">10.3.4.1. A Simple Zone File</h4></div></div></div><a id="id763920" class="indexterm"></a><div class="para">
+ <a class="xref" href="#example-bind-zone-examples-basic" title="Example 10.15. A simple zone file">Example 10.15, “A simple zone file”</a> demonstrates the use of standard directives and <code class="command">SOA</code> values.
+ </div><div class="example" title="Example 10.15. A simple zone file" id="example-bind-zone-examples-basic"><h6>Example 10.15. A simple zone file</h6><div class="example-contents"><pre class="screen">$ORIGIN example.com.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+;
+ IN NS dns1.example.com.
+ IN NS dns2.example.com.
+dns1 IN A 10.0.1.1
+ IN AAAA aaaa:bbbb::1
+dns2 IN A 10.0.1.2
+ IN AAAA aaaa:bbbb::2
+;
+;
+@ IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.
+mail IN A 10.0.1.5
+ IN AAAA aaaa:bbbb::5
+mail2 IN A 10.0.1.6
+ IN AAAA aaaa:bbbb::6
+;
+;
+; This sample zone file illustrates sharing the same IP addresses
+; for multiple services:
+;
+services IN A 10.0.1.10
+ IN AAAA aaaa:bbbb::10
+ IN A 10.0.1.11
+ IN AAAA aaaa:bbbb::11
+
+ftp IN CNAME services.example.com.
+www IN CNAME services.example.com.
+;
+;</pre></div></div><br class="example-break" /><div class="para">
+ In this example, the authoritative nameservers are set as <code class="systemitem">dns1.example.com</code> and <code class="systemitem">dns2.example.com</code>, and are tied to the <code class="systemitem">10.0.1.1</code> and <code class="systemitem">10.0.1.2</code> IP addresses respectively using the <code class="command">A</code> record.
+ </div><div class="para">
+ The email servers configured with the <code class="command">MX</code> records point to <code class="systemitem">mail</code> and <code class="systemitem">mail2</code> via <code class="command">A</code> records. Since these names do not end in a trailing period (that is, the <code class="literal">.</code> character), the <code class="command">$ORIGIN</code> domain is placed after them, expanding them to <code class="systemitem">mail.example.com</code> and <code class="systemitem">mail2.example.com</code>.
+ </div><div class="para">
+ Services available at the standard names, such as <code class="systemitem">www.example.com</code> (<acronym class="acronym">WWW</acronym>), are pointed at the appropriate servers using the <code class="command">CNAME</code> record.
+ </div><div class="para">
+ This zone file would be called into service with a <code class="command">zone</code> statement in the <code class="filename">/etc/named.conf</code> similar to the following:
+ </div><pre class="screen">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-update { none; };
+};</pre></div><div class="section" title="10.3.4.2. A Reverse Name Resolution Zone File" id="s2-bind-configuration-zone-reverse"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-bind-configuration-zone-reverse">10.3.4.2. A Reverse Name Resolution Zone File</h4></div></div></div><a id="id636834" class="indexterm"></a><div class="para">
+ A reverse name resolution zone file is used to translate an IP address in a particular namespace into an fully qualified domain name (FQDN). It looks very similar to a standard zone file, except that the <code class="command">PTR</code> resource records are used to link the IP addresses to a fully qualified domain name as shown in <a class="xref" href="#example-bind-zone-examples-reverse" title="Example 10.16. A reverse name resolution zone file">Example 10.16, “A reverse name resolution zone file”</a>.
+ </div><div class="example" title="Example 10.16. A reverse name resolution zone file" id="example-bind-zone-examples-reverse"><h6>Example 10.16. A reverse name resolution zone file</h6><div class="example-contents"><pre class="screen">$ORIGIN 1.0.10.in-addr.arpa.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+@ IN NS dns1.example.com.
+;
+1 IN PTR dns1.example.com.
+2 IN PTR dns2.example.com.
+;
+5 IN PTR server1.example.com.
+6 IN PTR server2.example.com.
+;
+3 IN PTR ftp.example.com.
+4 IN PTR ftp.example.com.</pre></div></div><br class="example-break" /><div class="para">
+ In this example, IP addresses <code class="systemitem">10.0.1.1</code> through <code class="systemitem">10.0.1.6</code> are pointed to the corresponding fully qualified domain name.
+ </div><div class="para">
+ This zone file would be called into service with a <code class="option">zone</code> statement in the <code class="filename">/etc/named.conf</code> file similar to the following:
+ </div><pre class="screen">zone "1.0.10.in-addr.arpa" IN {
+ type master;
+ file "example.com.rr.zone";
+ allow-update { none; };
+};</pre><div class="para">
+ There is very little difference between this example and a standard <code class="command">zone</code> statement, except for the zone name. Note that a reverse name resolution zone requires the first three blocks of the IP address reversed followed by <code class="command">.in-addr.arpa</code>. This allows the single block of IP numbers used in the reverse name resolution zone file to be associated with the zone.
+ </div></div></div></div><div class="section" title="10.4. Using the rndc Utility" id="s1-bind-rndc"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-rndc">10.4. Using the <code class="command">rndc</code> Utility</h2></div></div></div><a id="id1622914" class="indexterm"></a><div class="para">
+ The <code class="command">rndc</code> utility is a command line tool that allows you to administer the <code class="systemitem">named</code> service, both locally and from a remote machine. Its usage is as follows:
+ </div><pre class="screen"><code class="command">rndc</code> [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>command</code></em> [<em class="replaceable"><code>command-option</code></em>]</pre><div class="section" title="10.4.1. Configuring the Utility" id="s2-bind-rndc-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-configuration">10.4.1. Configuring the Utility</h3></div></div></div><div class="para">
+ To prevent unauthorized access to the service, <code class="systemitem">named</code> must be configured to listen on the selected port (that is, <code class="literal">953</code> by default), and an identical key must be used by both the service and the <code class="command">rndc</code> utility.
+ </div><div class="table" title="Table 10.7. Relevant files" id="table-bind-rndc-configuration-files"><h6>Table 10.7. Relevant files</h6><div class="table-contents"><table summary="Relevant files" border="1"><colgroup><col width="38%" /><col width="63%" /></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <a id="id486109" class="indexterm"></a>
+ <code class="filename">/etc/named.conf</code>
+ </td><td>
+ The default configuration file for the <code class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <a id="id1051876" class="indexterm"></a>
+ <code class="filename">/etc/rndc.conf</code>
+ </td><td>
+ The default configuration file for the <code class="command">rndc</code> utility.
+ </td></tr><tr><td>
+ <a id="id1376396" class="indexterm"></a>
+ <code class="filename">/etc/rndc.key</code>
+ </td><td>
+ The default key location.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">rndc</code> configuration is located in <code class="filename">/etc/rndc.conf</code>. If the file does not exist, the utility will use the key located in <code class="filename">/etc/rndc.key</code>, which was generated automatically during the installation process using the <code class="command">rndc-confgen -a</code> command.
+ </div><div class="para">
+ The <code class="systemitem">named</code> service is configured using the <code class="option">controls</code> statement in the <code class="filename">/etc/named.conf</code> configuration file as described in <a class="xref" href="#s2-bind-namedconf-state-other" title="10.2.2. Other Statement Types">Section 10.2.2, “Other Statement Types”</a>. Unless this statement is present, only the connections from the loopback address (that is, <code class="systemitem">127.0.0.1</code>) will be allowed, and the key located in <code class="filename">/etc/rndc.key</code> will be used.
+ </div><div class="para">
+ For more information on this topic, refer to manual pages and the <em class="citetitle">BIND 9 Administrator Reference Manual</em> listed in <a class="xref" href="#s1-bind-additional-resources" title="10.8. Additional Resources">Section 10.8, “Additional Resources”</a>.
+ </div><div class="important" title="Important: Set the Correct Permissions"><div class="admonition_header"><h2>Important: Set the Correct Permissions</h2></div><div class="admonition"><div class="para">
+ To prevent unprivileged users from sending control commands to the service, make sure only root is allowed to read the <code class="filename">/etc/rndc.key</code> file:
+ </div><pre class="screen">~]# <code class="command">chmod o-rwx /etc/rndc.key</code></pre></div></div></div><div class="section" title="10.4.2. Checking the Service Status" id="s2-bind-rndc-status"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-status">10.4.2. Checking the Service Status</h3></div></div></div><div class="para">
+ To check the current status of the <code class="systemitem">named</code> service, use the following command:
+ </div><pre class="screen">~]# <code class="command">rndc status</code>
+version: 9.7.0-P2-RedHat-9.7.0-5.P2.el6
+CPUs found: 1
+worker threads: 1
+number of zones: 16
+debug level: 0
+xfers running: 0
+xfers deferred: 0
+soa queries in progress: 0
+query logging is OFF
+recursive clients: 0/0/1000
+tcp clients: 0/100
+server is up and running</pre></div><div class="section" title="10.4.3. Reloading the Configuration and Zones" id="s2-bind-rndc-reload"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-reload">10.4.3. Reloading the Configuration and Zones</h3></div></div></div><div class="para">
+ To reload both the configuration file and zones, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">rndc reload</code>
+server reload successful</pre><div class="para">
+ This will reload the zones while keeping all previously cached responses, so that you can make changes to the zone files without losing all stored name resolutions.
+ </div><div class="para">
+ To reload a single zone, specify its name after the <code class="command">reload</code> command, for example:
+ </div><pre class="screen">~]# <code class="command">rndc reload localhost</code>
+zone reload up-to-date</pre><div class="para">
+ Finally, to reload the configuration file and newly added zones only, type:
+ </div><pre class="screen">~]# <code class="command">rndc reconfig</code></pre><div class="note" title="Note: Modyfying Zones with Dynamic DNS"><div class="admonition_header"><h2>Note: Modyfying Zones with Dynamic DNS</h2></div><div class="admonition"><div class="para">
+ If you intend to manually modify a zone that uses Dynamic DNS (DDNS), make sure you run the <code class="command">freeze</code> command first:
+ </div><pre class="screen">~]# <code class="command">rndc freeze localhost</code></pre><div class="para">
+ Once you are finished, run the <code class="command">thaw</code> command to allow the DDNS again and reload the zone:
+ </div><pre class="screen">~]# <code class="command">rndc thaw localhost</code>
+The zone reload and thaw was successful.</pre></div></div></div><div class="section" title="10.4.4. Updating Zone Keys" id="s2-bind-rndc-sign"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-sign">10.4.4. Updating Zone Keys</h3></div></div></div><div class="para">
+ To update the DNSSEC keys and sign the zone, use the <code class="command">sign</code> command. For example:
+ </div><pre class="screen">~]# <code class="command">rndc sign localhost</code></pre><div class="para">
+ Note that to sign a zone with the above command, the <code class="option">auto-dnssec</code> option has to be set to <code class="literal">maintain</code> in the zone statement. For instance:
+ </div><pre class="screen">zone "localhost" IN {
+ type master;
+ file "named.localhost";
+ allow-update { none; };
+ auto-dnssec maintain;
+};</pre></div><div class="section" title="10.4.5. Enabling the DNSSEC Validation" id="s2-bind-rndc-validation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-validation">10.4.5. Enabling the DNSSEC Validation</h3></div></div></div><div class="para">
+ To enable the DNSSEC validation, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">rndc validation on</code></pre><div class="para">
+ Similarly, to disable this option, type:
+ </div><pre class="screen">~]# <code class="command">rndc validation off</code></pre><div class="para">
+ Refer to the <code class="option">options</code> statement described in <a class="xref" href="#s2-bind-namedconf-state" title="10.2.1. Common Statement Types">Section 10.2.1, “Common Statement Types”</a> for information on how configure this option in <code class="filename">/etc/named.conf</code>.
+ </div></div><div class="section" title="10.4.6. Enabling the Query Logging" id="s2-bind-rndc-querylog"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-querylog">10.4.6. Enabling the Query Logging</h3></div></div></div><div class="para">
+ To enable (or disable in case it is currently enabled) the query logging, run the following command:
+ </div><pre class="screen">~]# <code class="command">rndc querylog</code></pre><div class="para">
+ To check the current setting, use the <code class="command">status</code> command as described in <a class="xref" href="#s2-bind-rndc-status" title="10.4.2. Checking the Service Status">Section 10.4.2, “Checking the Service Status”</a>.
+ </div></div></div><div class="section" title="10.5. Using the dig Utility" id="s1-bind-dig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-dig">10.5. Using the <code class="command">dig</code> Utility</h2></div></div></div><a id="id706374" class="indexterm"></a><div class="para">
+ The <code class="command">dig</code> utility is a command line tool that allows you to perform DNS lookups and debug a nameserver configuration. Its typical usage is as follows:
+ </div><pre class="screen"><code class="command">dig</code> [@<em class="replaceable"><code>server</code></em>] [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>name</code></em> <em class="replaceable"><code>type</code></em></pre><div class="para">
+ Refer to <a class="xref" href="#s3-bind-zone-rr" title="10.3.2. Common Resource Records">Section 10.3.2, “Common Resource Records”</a> for a list of common <em class="replaceable"><code>type</code></em>s.
+ </div><div class="section" title="10.5.1. Looking Up a Nameserver" id="s2-bind-dig-ns"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-dig-ns">10.5.1. Looking Up a Nameserver</h3></div></div></div><div class="para">
+ To look up a nameserver for a particular domain, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> NS</pre><div class="para">
+ In <a class="xref" href="#example-bind-dig-ns" title="Example 10.17. A Sample Nameserver Lookup">Example 10.17, “A Sample Nameserver Lookup”</a>, the <code class="command">dig</code> utility is used to display nameservers for <code class="systemitem">example.com</code>.
+ </div><div class="example" title="Example 10.17. A Sample Nameserver Lookup" id="example-bind-dig-ns"><h6>Example 10.17. A Sample Nameserver Lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com NS</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com NS
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57883
+;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN NS
+
+;; ANSWER SECTION:
+example.com. 99374 IN NS a.iana-servers.net.
+example.com. 99374 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:04:06 2010
+;; MSG SIZE rcvd: 77</pre></div></div><br class="example-break" /></div><div class="section" title="10.5.2. Looking Up an IP Address" id="s2-bind-dig-a"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-dig-a">10.5.2. Looking Up an IP Address</h3></div></div></div><div class="para">
+ To look up an IP address assigned to a particular domain, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> A</pre><div class="para">
+ In <a class="xref" href="#example-bind-dig-a" title="Example 10.18. A Sample IP Address Lookup">Example 10.18, “A Sample IP Address Lookup”</a>, the <code class="command">dig</code> utility is used to display the IP address of <code class="systemitem">example.com</code>.
+ </div><div class="example" title="Example 10.18. A Sample IP Address Lookup" id="example-bind-dig-a"><h6>Example 10.18. A Sample IP Address Lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com A</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com A
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4849
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN A
+
+;; ANSWER SECTION:
+example.com. 155606 IN A 192.0.32.10
+
+;; AUTHORITY SECTION:
+example.com. 99175 IN NS a.iana-servers.net.
+example.com. 99175 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:07:25 2010
+;; MSG SIZE rcvd: 93</pre></div></div><br class="example-break" /></div><div class="section" title="10.5.3. Looking Up a Hostname" id="s2-bind-dig-x"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-dig-x">10.5.3. Looking Up a Hostname</h3></div></div></div><div class="para">
+ To look up a hostname for a particular IP address, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <code class="option">-x</code> <em class="replaceable"><code>address</code></em></pre><div class="para">
+ In <a class="xref" href="#example-bind-dig-x" title="Example 10.19. A Sample Hostname Lookup">Example 10.19, “A Sample Hostname Lookup”</a>, the <code class="command">dig</code> utility is used to display the hostname assigned to <code class="systemitem">192.0.32.10</code>.
+ </div><div class="example" title="Example 10.19. A Sample Hostname Lookup" id="example-bind-dig-x"><h6>Example 10.19. A Sample Hostname Lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig -x 192.0.32.10</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> -x 192.0.32.10
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29683
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 6
+
+;; QUESTION SECTION:
+;10.32.0.192.in-addr.arpa. IN PTR
+
+;; ANSWER SECTION:
+10.32.0.192.in-addr.arpa. 21600 IN PTR www.example.com.
+
+;; AUTHORITY SECTION:
+32.0.192.in-addr.arpa. 21600 IN NS b.iana-servers.org.
+32.0.192.in-addr.arpa. 21600 IN NS c.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS d.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS ns.icann.org.
+32.0.192.in-addr.arpa. 21600 IN NS a.iana-servers.net.
+
+;; ADDITIONAL SECTION:
+a.iana-servers.net. 13688 IN A 192.0.34.43
+b.iana-servers.org. 5844 IN A 193.0.0.236
+b.iana-servers.org. 5844 IN AAAA 2001:610:240:2::c100:ec
+c.iana-servers.net. 12173 IN A 139.91.1.10
+c.iana-servers.net. 12173 IN AAAA 2001:648:2c30::1:10
+ns.icann.org. 12884 IN A 192.0.34.126
+
+;; Query time: 156 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:25:15 2010
+;; MSG SIZE rcvd: 310</pre></div></div><br class="example-break" /></div></div><div class="section" title="10.6. Advanced Features of BIND" id="s1-bind-features"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-features">10.6. Advanced Features of BIND</h2></div></div></div><div class="para">
+ Most BIND implementations only use the <code class="systemitem">named</code> service to provide name resolution services or to act as an authority for a particular domain. However, BIND version 9 has a number of advanced features that allow for a more secure and efficient DNS service.
+ </div><div class="important" title="Important: Make Sure the Feature is Supported"><div class="admonition_header"><h2>Important: Make Sure the Feature is Supported</h2></div><div class="admonition"><div class="para">
+ Before attempting to use advanced features like DNSSEC, TSIG, or IXFR, make sure that the particular feature is supported by all nameservers in the network environment, especially when you use older versions of BIND or non-BIND servers.
+ </div></div></div><div class="para">
+ All of the features mentioned are discussed in greater detail in the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="#s2-bind-installed-docs" title="10.8.1. Installed Documentation">Section 10.8.1, “Installed Documentation”</a>.
+ </div><div class="section" title="10.6.1. Multiple Views" id="s2-bind-features-views"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-views">10.6.1. Multiple Views</h3></div></div></div><a id="id772810" class="indexterm"></a><div class="para">
+ Optionally, different information can be presented to a client depending on the network a request originates from. This is primarily used to deny sensitive DNS entries from clients outside of the local network, while allowing queries from clients inside the local network.
+ </div><div class="para">
+ To configure multiple views, add the <code class="command">view</code> statement to the <code class="filename">/etc/named.conf</code> configuration file. Use the <code class="option">match-clients</code> option to match IP addresses or entire networks and give them special options and zone data.
+ </div></div><div class="section" title="10.6.2. Incremental Zone Transfers (IXFR)" id="s2-bind-features-ixfr"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-ixfr">10.6.2. Incremental Zone Transfers (IXFR)</h3></div></div></div><a id="id470220" class="indexterm"></a><div class="para">
+ <em class="firstterm">Incremental Zone Transfers</em> (<em class="firstterm">IXFR</em>) allow a secondary nameserver to only download the updated portions of a zone modified on a primary nameserver. Compared to the standard transfer process, this makes the notification and update process much more efficient.
+ </div><a id="id518671" class="indexterm"></a><div class="para">
+ Note that IXFR is only available when using dynamic updating to make changes to master zone records. If manually editing zone files to make changes, <em class="firstterm">Automatic Zone Transfer</em> (<em class="firstterm">AXFR</em>) is used.
+ </div></div><div class="section" title="10.6.3. Transaction SIGnatures (TSIG)" id="s2-bind-features-tsig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-tsig">10.6.3. Transaction SIGnatures (TSIG)</h3></div></div></div><a id="id774971" class="indexterm"></a><div class="para">
+ <em class="firstterm">Transaction SIGnatures</em> (TSIG) ensure that a shared secret key exists on both primary and secondary nameserver before allowing a transfer. This strengthens the standard IP address-based method of transfer authorization, since attackers would not only need to have access to the IP address to transfer the zone, but they would also need to know the secret key.
+ </div><div class="para">
+ Since version 9, BIND also supports <em class="firstterm">TKEY</em>, which is another shared secret key method of authorizing zone transfers.
+ </div><div class="important" title="Important: Secure the Transfer"><div class="admonition_header"><h2>Important: Secure the Transfer</h2></div><div class="admonition"><div class="para">
+ When communicating over an insecure network, do not rely on IP address-based authentication only.
+ </div></div></div></div><div class="section" title="10.6.4. DNS Security Extensions (DNSSEC)" id="s2-bind-features-dnssec"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-dnssec">10.6.4. DNS Security Extensions (DNSSEC)</h3></div></div></div><a id="id762693" class="indexterm"></a><div class="para">
+ <em class="firstterm">Domain Name System Security Extensions</em> (<em class="firstterm">DNSSEC</em>) provide origin authentication of DNS data, authenticated denial of existence, and data integrity. When a particular domain is marked as secure, the <code class="literal">SERFVAIL</code> response is returned for each resource record that fails the validation.
+ </div><a id="id506983" class="indexterm"></a><div class="para">
+ Note that to debug a DNSSEC-signed domain or a DNSSEC-aware resolver, you can use the <code class="command">dig</code> utility as described in <a class="xref" href="#s1-bind-dig" title="10.5. Using the dig Utility">Section 10.5, “Using the <code class="command">dig</code> Utility”</a>. Useful options are <code class="option">+dnssec</code> (requests DNSSEC-related resource records by setting the DNSSEC OK bit), <code class="option">+cd</code> (tells recursive nameserver not to validate the response), and <code class="option">+bufsize=512</code> (changes the packet size to 512B to get through some firewalls).
+ </div></div><div class="section" title="10.6.5. Internet Protocol version 6 (IPv6)" id="s2-bind-features-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-ipv6">10.6.5. Internet Protocol version 6 (IPv6)</h3></div></div></div><a id="id756378" class="indexterm"></a><div class="para">
+ <em class="firstterm">Internet Protocol version 6</em> (<em class="firstterm">IPv6</em>) is supported through the use of <code class="option">AAAA</code> resource records, and the <code class="option">listen-on-v6</code> directive as described in <a class="xref" href="#table-bind-namedconf-common-options" title="Table 10.3. Commonly used options">Table 10.3, “Commonly used options”</a>.
+ </div></div></div><div class="section" title="10.7. Common Mistakes to Avoid" id="s1-bind-mistakes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-mistakes">10.7. Common Mistakes to Avoid</h2></div></div></div><a id="id624554" class="indexterm"></a><div class="para">
+ The following is a list of advices how to avoid common mistakes users make when configuring a nameserver:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Use semicolons and curly brackets correctly</span></dt><dd><div class="para">
+ An omitted semicolon or unmatched curly bracket in the <code class="filename">/etc/named.conf</code> file can prevent the <code class="systemitem">named</code> service from starting.
+ </div></dd><dt class="varlistentry"><span class="term">Use period (that is, the <code class="literal">.</code> character) correctly</span></dt><dd><div class="para">
+ In zone files, a period at the end of a domain name denotes a fully qualified domain name. If omitted, the <code class="systemitem">named</code> service will append the name of the zone or the value of <code class="option">$ORIGIN</code> to complete it.
+ </div></dd><dt class="varlistentry"><span class="term">Increment the serial number when editing a zone file</span></dt><dd><div class="para">
+ If the serial number is not incremented, the primary nameserver will have the correct, new information, but the secondary nameservers will never be notified of the change, and will not attempt to refresh their data of that zone.
+ </div></dd><dt class="varlistentry"><span class="term">Configure the firewall</span></dt><dd><div class="para">
+ If a firewall is blocking connections from the <code class="systemitem">named</code> service to other nameservers, the recommended best practice is to change the firewall settings whenever possible.
+ </div><div class="warning" title="Warning: Avoid Using Fixed UDP Source Ports" id="warning-Warning-Avoid_Using_Fixed_UDP_Source_Ports"><div class="admonition_header"><h2>Warning: Avoid Using Fixed UDP Source Ports</h2></div><div class="admonition"><div class="para">
+ According to the recent research in DNS security, using a fixed UDP source port for DNS queries is a potential security vulnerability that could allow an attacker to conduct cache-poisoning attacks more easily. To prevent this, configure your firewall to allow queries from a random UDP source port.
+ </div></div></div></dd></dl></div></div><div class="section" title="10.8. Additional Resources" id="s1-bind-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-additional-resources">10.8. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding BIND.
+ </div><div class="section" title="10.8.1. Installed Documentation" id="s2-bind-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-installed-docs">10.8.1. Installed Documentation</h3></div></div></div><a id="id431504" class="indexterm"></a><div class="para">
+ BIND features a full range of installed documentation covering many different topics, each placed in its own subject directory. For each item below, replace <em class="replaceable"><code>version</code></em> with the version of the <span class="package">bind</span> package installed on the system:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/</code></span></dt><dd><div class="para">
+ The main directory containing the most recent documentation.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/arm/</code></span></dt><dd><div class="para">
+ The directory containing the <em class="citetitle">BIND 9 Administrator Reference Manual</em> in HTML and SGML formats, which details BIND resource requirements, how to configure different types of nameservers, how to perform load balancing, and other advanced topics. For most new users of BIND, this is the best place to start.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/draft/</code></span></dt><dd><div class="para">
+ The directory containing assorted technical documents that review issues related to the DNS service, and propose some methods to address them.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/misc/</code></span></dt><dd><div class="para">
+ The directory designed to address specific advanced issues. Users of BIND version 8 should consult the <code class="filename">migration</code> document for specific changes they must make when moving to BIND 9. The <code class="filename">options</code> file lists all of the options implemented in BIND 9 that are used in <code class="filename">/etc/named.conf</code>.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/rfc/</code></span></dt><dd><div class="para">
+ The directory providing every RFC document related to BIND.
+ </div></dd></dl></div><div class="para">
+ There is also a number of man pages for the various applications and configuration files involved with BIND:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="command">man rndc</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">rndc</code> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man named</code></span></dt><dd><div class="para">
+ The manual page for <code class="systemitem">named</code> containing the documentation on assorted arguments that can be used to control the BIND nameserver daemon.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man lwresd</code></span></dt><dd><div class="para">
+ The manual page for <code class="systemitem">lwresd</code> containing the full documentation on the lightweight resolver daemon and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man named.conf</code></span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="systemitem">named</code> configuration file.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man rndc.conf</code></span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="command">rndc</code> configuration file.
+ </div></dd></dl></div></div><div class="section" title="10.8.2. Useful Websites" id="s2-bind-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-useful-websites">10.8.2. Useful Websites</h3></div></div></div><a id="id785635" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><a href="http://www.isc.org/software/bind">http://www.isc.org/software/bind</a></span></dt><dd><div class="para">
+ The home page of the BIND project containing information about current releases as well as a PDF version of the <em class="citetitle">BIND 9 Administrator Reference Manual</em>.
+ </div></dd></dl></div></div><div class="section" title="10.8.3. Related Books" id="s2-bind-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-related-books">10.8.3. Related Books</h3></div></div></div><a id="id555401" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><em class="citetitle">DNS and BIND</em> by Paul Albitz and Cricket Liu; O'Reilly & Associates</span></dt><dd><div class="para">
+ A popular reference that explains both common and esoteric BIND configuration options, and provides strategies for securing a DNS server.
+ </div></dd><dt class="varlistentry"><span class="term"><em class="citetitle">The Concise Guide to DNS and BIND</em> by Nicolai Langfeldt; Que</span></dt><dd><div class="para">
+ Looks at the connection between multiple network services and BIND, with an emphasis on task-oriented, technical topics.
+ </div></dd></dl></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 11. The Apache HTTP Server" id="ch-The_Apache_HTTP_Server" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 11. The Apache HTTP Server</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-apache-version2">11.1. The Apache HTTP Server 2.2</a></span></dt><dt><span class="section"><a href="#s1-apache-running">11.2. Running the <code class="systemitem">httpd</code> Service</a></span></dt><dt><span class="section"><a href="#s1-apache-editing">11.3. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="#s1-apache-dso">11.4. Working with Modules</a></span></dt><dt><span class="section"><a href="#s1-apache-virtualhosts">11.5. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="#s1-apache-mod_ssl">11.6. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="#s1-
apache-resources">11.7. Additional Resources</a></span></dt></dl></div><a id="id696086" class="indexterm"></a><a id="id417257" class="indexterm"></a><div class="para">
+ <code class="systemitem">HTTP</code> (Hypertext Transfer Protocol) server, or a <em class="firstterm">web server</em>, is a network service that serves content to a client over the web. This typically means web pages, but any other documents can be served as well.
+ </div><a id="id670081" class="indexterm"></a><div class="para">
+ This chapter focuses on the <span class="application"><strong>Apache HTTP Server 2.2</strong></span>, a robust, full-featured open source web server developed by the <a href="http://www.apache.org/">Apache Software Foundation</a>, that is included in Fedora 14. It describes the basic configuration of the <code class="systemitem">httpd</code> service, and covers advanced topics such as adding server modules, setting up virtual hosts, or configuring the secure HTTP server.
+ </div><div class="section" title="11.1. The Apache HTTP Server 2.2" id="s1-apache-version2"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-version2">11.1. The Apache HTTP Server 2.2</h2></div></div></div><div class="para">
+ There are important differences between the Apache HTTP Server 2.2 and version 2.0, and if you are upgrading from a previous release of Fedora, you will need to update the <code class="systemitem">httpd</code> service configuration accordingly. This section reviews some of the newly added features, outlines important changes, and guides you through the update of older configuration files.
+ </div><div class="section" title="11.1.1. New Features" id="s2-apache-version2-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-version2-features">11.1.1. New Features</h3></div></div></div><a id="id456898" class="indexterm"></a><div class="para">
+ The Apache HTTP Server version 2.2 introduces the following enhancements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a id="id520333" class="indexterm"></a>
+ <a id="id741983" class="indexterm"></a>
+ Improved caching modules, that is, <code class="systemitem">mod_cache</code> and <code class="systemitem">mod_disk_cache</code>.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id415110" class="indexterm"></a>
+ Support for proxy load balancing, that is, the <code class="systemitem">mod_proxy_balancer</code> module.
+ </div></li><li class="listitem"><div class="para">
+ Support for large files on 32-bit architectures, allowing the web server to handle files greater than 2GB.
+ </div></li><li class="listitem"><div class="para">
+ A new structure for authentication and authorization support, replacing the authentication modules provided in previous versions.
+ </div></li></ul></div></div><div class="section" title="11.1.2. Notable Changes" id="s2-apache-version2-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-version2-changes">11.1.2. Notable Changes</h3></div></div></div><a id="id677773" class="indexterm"></a><div class="para">
+ Since version 2.0, few changes have been made to the default <code class="systemitem">httpd</code> service configuration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a id="id683398" class="indexterm"></a>
+ <a id="id683419" class="indexterm"></a>
+ The following modules are no longer loaded by default: <code class="systemitem">mod_cern_meta</code> and <code class="systemitem">mod_asis</code>.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id822545" class="indexterm"></a>
+ The following module is newly loaded by default: <code class="systemitem">mod_ext_filter</code>.
+ </div></li></ul></div></div><div class="section" title="11.1.3. Updating the Configuration" id="s1-apache-version2-migrating"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-apache-version2-migrating">11.1.3. Updating the Configuration</h3></div></div></div><a id="id525624" class="indexterm"></a><div class="para">
+ To update the configuration files from the Apache HTTP Server version 2.0, take the following steps:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Make sure all module names are correct, since they may have changed. Adjust the <code class="option">LoadModule</code> directive for each module that has been renamed.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Recompile all third party modules before attempting to load them. This typically means authentication and authorization modules.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ <a id="id648354" class="indexterm"></a>
+ If you use the <code class="systemitem">mod_userdir</code> module, make sure the <code class="option">UserDir</code> directive indicating a directory name (typically <code class="literal">public_html</code>) is provided.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ If you use the Apache HTTP Secure Server, edit the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> to enable the Secure Sockets Layer (SSL) protocol.
+ </div></li></ol></div><div class="para">
+ Note that you can check the configuration for possible errors by using the following command:
+ </div><pre class="screen">~]# <code class="command">service httpd configtest</code>
+Syntax OK</pre><div class="para">
+ For more information on upgrading the Apache HTTP Server configuration from version 2.0 to 2.2, refer to <a href="http://httpd.apache.org/docs/2.2/upgrading.html">http://httpd.apache.org/docs/2.2/upgrading.html</a>.
+ </div></div></div><div class="section" title="11.2. Running the httpd Service" id="s1-apache-running"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-running">11.2. Running the <code class="systemitem">httpd</code> Service</h2></div></div></div><div class="para">
+ This section describes how to start, stop, restart, and check the current status of the Apache HTTP Server. To be able to use the <code class="systemitem">httpd</code> service, make sure you have the <span class="package">httpd</span> installed. You can do so by using the following command:
+ </div><pre class="screen">~]# <code class="command">yum install httpd</code></pre><div class="para">
+ For more information on the concept of runlevels and how to manage system services in Fedora in general, refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div><div class="section" title="11.2.1. Starting the Service" id="s2-apache-running-starting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-running-starting">11.2.1. Starting the Service</h3></div></div></div><a id="id1038275" class="indexterm"></a><div class="para">
+ To run the <code class="systemitem">httpd</code> service, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service httpd start</code>
+Starting httpd: [ OK ]</pre><div class="para">
+ If you want the service to start automatically at the boot time, use the following command:
+ </div><pre class="screen">~]# <code class="command">chkconfig httpd on</code></pre><div class="para">
+ This will enable the service for runlevel 2, 3, 4, and 5. Alternatively, you can use the <span class="application"><strong>Service Configuration</strong></span> utility as described in <a class="xref" href="#s3-services-serviceconf-enabling" title="7.2.1.1. Enabling the Service">Section 7.2.1.1, “Enabling the Service”</a>.
+ </div><div class="note" title="Note: Using the Secure Server"><div class="admonition_header"><h2>Note: Using the Secure Server</h2></div><div class="admonition"><div class="para">
+ If running the Apache HTTP Server as a secure server, a password may be required after the machine boots if using an encrypted private SSL key.
+ </div></div></div></div><div class="section" title="11.2.2. Stopping the Service" id="s2-apache-running-stopping"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-running-stopping">11.2.2. Stopping the Service</h3></div></div></div><a id="id465145" class="indexterm"></a><div class="para">
+ To stop the running <code class="systemitem">httpd</code> service, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service httpd stop</code>
+Stopping httpd: [ OK ]</pre><div class="para">
+ To prevent the service from starting automatically at the boot time, type:
+ </div><pre class="screen">~]# <code class="command">chkconfig httpd off</code></pre><div class="para">
+ This will disable the service for all runlevels. Alternatively, you can use the <span class="application"><strong>Service Configuration</strong></span> utility as described in <a class="xref" href="#s3-services-serviceconf-disabling" title="7.2.1.2. Disabling the Service">Section 7.2.1.2, “Disabling the Service”</a>.
+ </div></div><div class="section" title="11.2.3. Restarting the Service" id="s3-apache-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s3-apache-running-restarting">11.2.3. Restarting the Service</h3></div></div></div><a id="id622984" class="indexterm"></a><div class="para">
+ There are three different ways to restart the running <code class="systemitem">httpd</code> service:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ To restart the service completely, type:
+ </div><pre class="screen">~]# <code class="command">service httpd restart</code>
+Stopping httpd: [ OK ]
+Starting httpd: [ OK ]</pre><div class="para">
+ This will stop the running <code class="systemitem">httpd</code> service, and then start it again. Use this command after installing or removing a dynamically loaded module such as PHP.
+ </div></li><li class="listitem"><div class="para">
+ To only reload the configuration, type:
+ </div><pre class="screen">~]# <code class="command">service httpd reload</code></pre><div class="para">
+ This will cause the running <code class="systemitem">httpd</code> service to reload the configuration file. Note that any requests being currently processed will be interrupted, which may cause a client browser to display an error message or render a partial page.
+ </div></li><li class="listitem"><div class="para">
+ To reload the configuration without affecting active requests, type:
+ </div><pre class="screen">~]# <code class="command">service httpd graceful</code></pre><div class="para">
+ This will cause the running <code class="systemitem">httpd</code> service to reload the configuration file. Note that any requests being currently processed will use the old configuration.
+ </div></li></ol></div><div class="para">
+ Alternatively, you can use the <span class="application"><strong>Service Configuration</strong></span> utility as described in <a class="xref" href="#s3-services-serviceconf-restarting" title="7.2.1.5. Restarting the Running Service">Section 7.2.1.5, “Restarting the Running Service”</a>.
+ </div></div><div class="section" title="11.2.4. Checking the Service Status" id="s3-apache-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s3-apache-running-status">11.2.4. Checking the Service Status</h3></div></div></div><a id="id734401" class="indexterm"></a><div class="para">
+ To check whether the service is running, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service httpd status</code>
+httpd (pid 19014) is running...</pre><div class="para">
+ Alternatively, you can use the <span class="application"><strong>Service Configuration</strong></span> utility as described in <a class="xref" href="#s2-services-serviceconf" title="7.2.1. Using the Service Configuration Utility">Section 7.2.1, “Using the <span class="application"><strong>Service Configuration</strong></span> Utility”</a>.
+ </div></div></div><div class="section" title="11.3. Editing the Configuration Files" id="s1-apache-editing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-editing">11.3. Editing the Configuration Files</h2></div></div></div><div class="para">
+ When the <code class="systemitem">httpd</code> service is started, by default, it reads the configuration from locations that are listed in <a class="xref" href="#table-apache-editing-files" title="Table 11.1. The httpd service configuration files">Table 11.1, “The <code class="systemitem">httpd</code> service configuration files”</a>.
+ </div><div class="table" title="Table 11.1. The httpd service configuration files" id="table-apache-editing-files"><h6>Table 11.1. The <code class="systemitem">httpd</code> service configuration files</h6><div class="table-contents"><table summary="The httpd service configuration files" border="1"><colgroup><col width="33%" /><col width="67%" /></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <a id="id742215" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf/httpd.conf</code>
+ </td><td>
+ The main configuration file.
+ </td></tr><tr><td>
+ <a id="id2228468" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf.d/</code>
+ </td><td>
+ An auxiliary directory for configuration files that are included in the main configuration file.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Although the default configuration should be suitable for most situations, it is a good idea to become at least familiar with some of the more important configuration options. Note that for any changes to take effect, the web server has to be restarted first. Refer to <a class="xref" href="#s3-apache-running-restarting" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a> for more information on how to restart the <code class="systemitem">httpd</code> service.
+ </div><a id="id821492" class="indexterm"></a><div class="para">
+ To check the configuration for possible errors, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service httpd configtest</code>
+Syntax OK</pre><div class="para">
+ To make the recovery from mistakes easier, it is recommended that you make a copy of the original file before editing it.
+ </div><div class="section" title="11.3.1. Common httpd.conf Directives" id="s2-apache-httpdconf-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-httpdconf-directives">11.3.1. Common <code class="filename">httpd.conf</code> Directives</h3></div></div></div><a id="id520763" class="indexterm"></a><div class="para">
+ The following directives are commonly used in the <code class="filename">/etc/httpd/conf/httpd.conf</code> configuration file:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id520799" class="indexterm"></a>
+ <code class="option"><Directory></code> </span></dt><dd><div class="para">
+ The <code class="option"><Directory></code> directive allows you to apply certain directives to a particular directory only. It takes the following form:
+ </div><pre class="screen"><Directory <em class="replaceable"><code>directory</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Directory></pre><div class="para">
+ The <em class="replaceable"><code>directory</code></em> can be either a full path to an existing directory in the local file system, or a wildcard expression.
+ </div><div class="para">
+ This directive can be used to configure additional <code class="literal">cgi-bin</code> directories for server-side scripts located outside the directory that is specified by <code class="option">ScriptAlias</code>. In this case, the <code class="option">ExecCGI</code> and <code class="option">AddHandler</code> directives must be supplied, and the permissions on the target directory must be set correctly (that is, <code class="literal">0755</code>).
+ </div><div class="example" title="Example 11.1. Using the <Directory> directive" id="example-apache-httpdconf-directory"><h6>Example 11.1. Using the <code class="option"><Directory></code> directive</h6><div class="example-contents"><pre class="screen"><Directory /var/www/html>
+ Options Indexes FollowSymLinks
+ AllowOverride None
+ Order allow,deny
+ Allow from all
+</Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id470240" class="indexterm"></a>
+ <code class="option"><IfDefine></code> </span></dt><dd><div class="para">
+ The <code class="option">IfDefine</code> directive allows you to use certain directives only when a particular parameter is supplied on the command line. It takes the following form:
+ </div><pre class="screen"><IfDefine [<span class="optional">!</span>]<em class="replaceable"><code>parameter</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</IfDefine></pre><div class="para">
+ The <em class="replaceable"><code>parameter</code></em> can be supplied at a shell prompt using the <code class="option">-D</code><em class="replaceable"><code>parameter</code></em> command line option (for example, <code class="command">httpd -DEnableHome</code>). If the optional exclamation mark (that is, <code class="literal">!</code>) is present, the enclosed directives are used only when the parameter is <span class="emphasis"><em>not</em></span> specified.
+ </div><div class="example" title="Example 11.2. Using the <IfDefine> directive" id="example-apache-httpdconf-ifdefine"><h6>Example 11.2. Using the <code class="option"><IfDefine></code> directive</h6><div class="example-contents"><pre class="screen"><IfDefine EnableHome>
+ UserDir public_html
+</IfDefine></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id457443" class="indexterm"></a>
+ <code class="option"><IfModule></code> </span></dt><dd><div class="para">
+ The <code class="option"><IfModule></code> directive allows you to use certain directive only when a particular module is loaded. It takes the following form:
+ </div><pre class="screen"><IfModule [<span class="optional">!</span>]<em class="replaceable"><code>module</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</IfModule></pre><div class="para">
+ The <em class="replaceable"><code>module</code></em> can be identified either by its name, or by the filename. If the optional exclamation mark (that is, <code class="literal">!</code>) is present, the enclosed directives are used only when the module is <span class="emphasis"><em>not</em></span> loaded.
+ </div><div class="example" title="Example 11.3. Using the <IfModule> directive" id="example-apache-httpdconf-ifmodule"><h6>Example 11.3. Using the <code class="option"><IfModule></code> directive</h6><div class="example-contents"><pre class="screen"><IfModule mod_disk_cache.c>
+ CacheEnable disk /
+ CacheRoot /var/cache/mod_proxy
+</IfModule></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id722787" class="indexterm"></a>
+ <code class="option"><Location></code> </span></dt><dd><div class="para">
+ The <code class="option"><Location></code> directive allows you to apply certain directives to a particular URL only. It takes the following form:
+ </div><pre class="screen"><Location <em class="replaceable"><code>url</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Location></pre><div class="para">
+ The <em class="replaceable"><code>url</code></em> can be either a path relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/server-info</code>), or an external URL such as <code class="literal">http://example.com/server-info</code>.
+ </div><div class="example" title="Example 11.4. Using the <Location> directive" id="example-apache-httpdconf-location"><h6>Example 11.4. Using the <code class="option"><Location></code> directive</h6><div class="example-contents"><pre class="screen"><Location /server-info>
+ SetHandler server-info
+ Order deny,allow
+ Deny from all
+ Allow from .example.com
+</Location></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id834001" class="indexterm"></a>
+ <code class="option"><Proxy></code> </span></dt><dd><div class="para">
+ The <code class="option"><Proxy></code> directive allows you to apply certain directives to the proxy server only. It takes the following form:
+ </div><pre class="screen"><Proxy <em class="replaceable"><code>pattern</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Proxy></pre><div class="para">
+ The <em class="replaceable"><code>pattern</code></em> can be an external URL, or a wildcard expression (for example, <code class="literal">http://example.com/*</code>).
+ </div><div class="example" title="Example 11.5. Using the <Proxy> directive" id="example-apache-httpdconf-proxy"><h6>Example 11.5. Using the <code class="option"><Proxy></code> directive</h6><div class="example-contents"><pre class="screen"><Proxy *>
+ Order deny,allow
+ Deny from all
+ Allow from .example.com
+</Proxy></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id461076" class="indexterm"></a>
+ <code class="option"><VirtualHost></code> </span></dt><dd><div class="para">
+ The <code class="option"><VirtualHost></code> directive allows you apply certain directives to particular virtual hosts only. It takes the following form:
+ </div><pre class="screen"><VirtualHost <em class="replaceable"><code>address</code></em>[<span class="optional">:<em class="replaceable"><code>port</code></em></span>]…>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</VirtualHost></pre><div class="para">
+ The <em class="replaceable"><code>address</code></em> can be an IP address, a fully qualified domain name, or a special form as described in <a class="xref" href="#table-apache-httpdconf-virtualhost" title="Table 11.2. Available <VirtualHost> options">Table 11.2, “Available <code class="option"><VirtualHost></code> options”</a>.
+ </div><div class="table" title="Table 11.2. Available <VirtualHost> options" id="table-apache-httpdconf-virtualhost"><h6>Table 11.2. Available <code class="option"><VirtualHost></code> options</h6><div class="table-contents"><table summary="Available <VirtualHost> options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">*</code>
+ </td><td>
+ Represents all IP addresses.
+ </td></tr><tr><td>
+ <code class="option">_default_</code>
+ </td><td>
+ Represents unmatched IP addresses.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.6. Using the <VirtualHost> directive" id="example-apache-httpdconf-virtualhost"><h6>Example 11.6. Using the <code class="option"><VirtualHost></code> directive</h6><div class="example-contents"><pre class="screen"><VirtualHost *:80>
+ ServerAdmin webmaster at penguin.example.com
+ DocumentRoot /www/docs/penguin.example.com
+ ServerName penguin.example.com
+ ErrorLog logs/penguin.example.com-error_log
+ CustomLog logs/penguin.example.com-access_log common
+</VirtualHost></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id537196" class="indexterm"></a>
+ <code class="option">AccessFileName</code> </span></dt><dd><div class="para">
+ The <code class="option">AccessFileName</code> directive allows you to specify the file to be used to customize access control information for each directory. It takes the following form:
+ </div><pre class="screen">AccessFileName <em class="replaceable"><code>filename</code></em>…</pre><a id="id488858" class="indexterm"></a><a id="id488876" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>filename</code></em> is a name of the file to look for in the requested directory. By default, the server looks for <code class="filename">.htaccess</code>.
+ </div><a id="id2218427" class="indexterm"></a><a id="id2218446" class="indexterm"></a><div class="para">
+ For security reasons, the directive is typically followed by the <code class="literal">Files</code> tag to prevent the files beginning with <code class="filename">.ht</code> from being accessed by web clients. This includes the <code class="filename">.htaccess</code> and <code class="filename">.htpasswd</code> files.
+ </div><div class="example" title="Example 11.7. Using the AccessFileName directive" id="example-apache-httpdconf-accessfilename"><h6>Example 11.7. Using the <code class="option">AccessFileName</code> directive</h6><div class="example-contents"><pre class="screen">AccessFileName .htaccess
+
+<Files ~ "^\.ht">
+ Order allow,deny
+ Deny from all
+ Satisfy All
+</Files></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id719705" class="indexterm"></a>
+ <code class="option">Action</code> </span></dt><dd><div class="para">
+ The <code class="option">Action</code> directive allows you to specify a CGI script to be executed when a certain media type is requested. It takes the following form:
+ </div><pre class="screen">Action <em class="replaceable"><code>content-type</code></em> <em class="replaceable"><code>path</code></em></pre><div class="para">
+ The <em class="replaceable"><code>content-type</code></em> has to be a valid MIME type such as <code class="literal">text/html</code>, <code class="literal">image/png</code>, or <code class="literal">application/pdf</code>. The <em class="replaceable"><code>path</code></em> refers to an existing CGI script, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/cgi-bin/process-image.cgi</code>).
+ </div><div class="example" title="Example 11.8. Using the Action directive" id="example-apache-httpdconf-action"><h6>Example 11.8. Using the <code class="option">Action</code> directive</h6><div class="example-contents"><pre class="screen">Action image/png /cgi-bin/process-image.cgi</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id674060" class="indexterm"></a>
+ <code class="option">AddDescription</code> </span></dt><dd><div class="para">
+ The <code class="option">AddDescription</code> directive allows you to specify a short description to be displayed in server-generated directory listings for a given file. It takes the following form:
+ </div><pre class="screen">AddDescription "<em class="replaceable"><code>description</code></em>" <em class="replaceable"><code>filename</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>description</code></em> should be a short text enclosed in double quotes (that is, <code class="literal">"</code>). The <em class="replaceable"><code>filename</code></em> can be a full filename, a file extension, or a wildcard expression.
+ </div><div class="example" title="Example 11.9. Using the AddDescription directive" id="example-apache-httpdconf-adddescription"><h6>Example 11.9. Using the <code class="option">AddDescription</code> directive</h6><div class="example-contents"><pre class="screen">AddDescription "GZIP compressed tar archive" .tgz</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id2230319" class="indexterm"></a>
+ <code class="option">AddEncoding</code> </span></dt><dd><div class="para">
+ The <code class="option">AddEncoding</code> directive allows you to specify an encoding type for a particular file extension. It takes the following form:
+ </div><pre class="screen">AddEncoding <em class="replaceable"><code>encoding</code></em> <em class="replaceable"><code>extension</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>encoding</code></em> has to be a valid MIME encoding such as <code class="literal">x-compress</code>, <code class="literal">x-gzip</code>, etc. The <em class="replaceable"><code>extension</code></em> is a case sensitive file extension, and is conventionally written with a leading dot (for example, <code class="literal">.gz</code>).
+ </div><div class="para">
+ This directive is typically used to instruct web browsers to uncompress certain file types as they are downloaded.
+ </div><div class="example" title="Example 11.10. Using the AddEncoding directive" id="example-apache-httpdconf-addencoding"><h6>Example 11.10. Using the <code class="option">AddEncoding</code> directive</h6><div class="example-contents"><pre class="screen">AddEncoding x-gzip .gz .tgz</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id835417" class="indexterm"></a>
+ <code class="option">AddHandler</code> </span></dt><dd><div class="para">
+ The <code class="option">AddHandler</code> directive allows you to map certain file extensions to a selected handler. It takes the following form:
+ </div><pre class="screen">AddHandler <em class="replaceable"><code>handler</code></em> <em class="replaceable"><code>extension</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>handler</code></em> has to be a name of previously defined handler. The <em class="replaceable"><code>extension</code></em> is a case sensitive file extension, and is conventionally written with a leading dot (for example, <code class="literal">.cgi</code>).
+ </div><div class="para">
+ This directive is typically used to treat files with the <code class="filename">.cgi</code> extension as CGI scripts regardless of the directory they are in. Additionally, it is also commonly used to process server-parsed HTML and image-map files.
+ </div><div class="example" title="Example 11.11. Using the AddHandler option" id="example-apache-httpdconf-addhandler"><h6>Example 11.11. Using the <code class="option">AddHandler</code> option</h6><div class="example-contents"><pre class="screen">AddHandler cgi-script .cgi</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id619393" class="indexterm"></a>
+ <code class="option">AddIcon</code> </span></dt><dd><div class="para">
+ The <code class="option">AddIcon</code> directive allows you to specify an icon to be displayed for a particular file in server-generated directory listings. It takes the following form:
+ </div><pre class="screen">AddIcon <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>pattern</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to an existing icon file, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/icons/folder.png</code>). The <em class="replaceable"><code>pattern</code></em> can be a filename, a file extension, a wildcard expression, or a special form as described in the following table:
+ </div><div class="table" title="Table 11.3. Available AddIcon options" id="table-apache-httpdconf-addicon"><h6>Table 11.3. Available <code class="option">AddIcon</code> options</h6><div class="table-contents"><table summary="Available AddIcon options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">^^DIRECTORY^^</code>
+ </td><td>
+ Represents a directory.
+ </td></tr><tr><td>
+ <code class="option">^^BLANKICON^^</code>
+ </td><td>
+ Represents a blank line.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.12. Using the AddIcon directive" id="example-apache-httpdconf-addicon"><h6>Example 11.12. Using the <code class="option">AddIcon</code> directive</h6><div class="example-contents"><pre class="screen">AddIcon /icons/text.png .txt README</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id478345" class="indexterm"></a>
+ <code class="option">AddIconByEncoding</code> </span></dt><dd><div class="para">
+ The <code class="option">AddIconByEncoding</code> directive allows you to specify an icon to be displayed for a particular encoding type in server-generated directory listings. It takes the following form:
+ </div><pre class="screen">AddIconByEncoding <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>encoding</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to an existing icon file, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/icons/compressed.png</code>). The <em class="replaceable"><code>encoding</code></em> has to be a valid MIME encoding such as <code class="literal">x-compress</code>, <code class="literal">x-gzip</code>, etc.
+ </div><div class="example" title="Example 11.13. Using the AddIconByEncoding directive" id="example-apache-httpdconf-addiconbyencoding"><h6>Example 11.13. Using the <code class="option">AddIconByEncoding</code> directive</h6><div class="example-contents"><pre class="screen">AddIconByEncoding /icons/compressed.png x-compress x-gzip</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id679407" class="indexterm"></a>
+ <code class="option">AddIconByType</code> </span></dt><dd><div class="para">
+ The <code class="option">AddIconByType</code> directive allows you to specify an icon to be displayed for a particular media type in server-generated directory listings. It takes the following form:
+ </div><pre class="screen">AddIconByType <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>content-type</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to an existing icon file, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/icons/text.png</code>). The <em class="replaceable"><code>content-type</code></em> has to be either a valid MIME type (for example, <code class="literal">text/html</code> or <code class="literal">image/png</code>), or a wildcard expression such as <code class="literal">text/*</code>, <code class="literal">image/*</code>, etc.
+ </div><div class="example" title="Example 11.14. Using the AddIconByType directive" id="example-apache-httpdconf-addiconbytype"><h6>Example 11.14. Using the <code class="option">AddIconByType</code> directive</h6><div class="example-contents"><pre class="screen">AddIconByType /icons/video.png video/*</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id700447" class="indexterm"></a>
+ <code class="option">AddLanguage</code> </span></dt><dd><div class="para">
+ The <code class="option">AddLanguage</code> directive allows you to associate a file extension with a specific language. It takes the following form:
+ </div><pre class="screen">AddLanguage <em class="replaceable"><code>language</code></em> <em class="replaceable"><code>extension</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>language</code></em> has to be a valid MIME language such as <code class="literal">cs</code>, <code class="literal">en</code>, or <code class="literal">fr</code>. The <em class="replaceable"><code>extension</code></em> is a case sensitive file extension, and is conventionally written with a leading dot (for example, <code class="literal">.cs</code>).
+ </div><div class="para">
+ This directive is especially useful for web servers that serve content in multiple languages based on the client's language settings.
+ </div><div class="example" title="Example 11.15. Using the AddLanguage directive" id="example-apache-httpdconf-addlanguage"><h6>Example 11.15. Using the <code class="option">AddLanguage</code> directive</h6><div class="example-contents"><pre class="screen">AddLanguage cs .cs .cz</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id486573" class="indexterm"></a>
+ <code class="option">AddType</code> </span></dt><dd><div class="para">
+ The <code class="option">AddType</code> directive allows you to define or override the media type for a particular file extension. It takes the following form:
+ </div><pre class="screen">AddType <em class="replaceable"><code>content-type</code></em> <em class="replaceable"><code>extension</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>content-type</code></em> has to be a valid MIME type such as <code class="literal">text/html</code>, <code class="literal">image/png</code>, etc. The <em class="replaceable"><code>extension</code></em> is a case sensitive file extension, and is conventionally written with a leading dot (for example, <code class="literal">.cs</code>).
+ </div><div class="example" title="Example 11.16. Using the AddType directive" id="example-apache-httpdconf-addtype"><h6>Example 11.16. Using the <code class="option">AddType</code> directive</h6><div class="example-contents"><pre class="screen">AddType application/x-gzip .gz .tgz</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id494346" class="indexterm"></a>
+ <code class="option">Alias</code> </span></dt><dd><div class="para">
+ The <code class="option">Alias</code> directive allows you to refer to files and directories outside the default directory specified by the <code class="option">DocumentRoot</code> directive. It takes the following form:
+ </div><pre class="screen">Alias <em class="replaceable"><code>url-path</code></em> <em class="replaceable"><code>real-path</code></em></pre><div class="para">
+ The <em class="replaceable"><code>url-path</code></em> must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/images/</code>). The <em class="replaceable"><code>real-path</code></em> is a full path to a file or directory in the local file system.
+ </div><a id="id494059" class="indexterm"></a><div class="para">
+ This directive is typically followed by the <code class="option">Directory</code> tag with additional permissions to access the target directory. By default, the <code class="literal">/icons/</code> alias is created so that the icons from <code class="filename">/var/www/icons/</code> are displayed in server-generated directory listings.
+ </div><div class="example" title="Example 11.17. Using the Alias directive" id="example-apache-httpdconf-alias"><h6>Example 11.17. Using the <code class="option">Alias</code> directive</h6><div class="example-contents"><pre class="screen">Alias /icons/ /var/www/icons/
+
+<Directory "/var/www/icons">
+ Options Indexes MultiViews FollowSymLinks
+ AllowOverride None
+ Order allow,deny
+ Allow from all
+<Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id586281" class="indexterm"></a>
+ <code class="option">Allow</code></span></dt><dd><div class="para">
+ The <code class="option">Allow</code> directive allows you to specify which clients have permission to access a given directory. It takes the following form:
+ </div><pre class="screen">Allow from <em class="replaceable"><code>client</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>client</code></em> can be a domain name, an IP address (both full and partial), a <em class="replaceable"><code>network</code></em>/<em class="replaceable"><code>netmask</code></em> pair, or <code class="literal">all</code> for all clients.
+ </div><div class="example" title="Example 11.18. Using the Allow directive" id="example-apache-httpdconf-allow"><h6>Example 11.18. Using the <code class="option">Allow</code> directive</h6><div class="example-contents"><pre class="screen">Allow from 192.168.1.0/255.255.255.0</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id734532" class="indexterm"></a>
+ <code class="option">AllowOverride</code> </span></dt><dd><a id="id714534" class="indexterm"></a><a id="id714552" class="indexterm"></a><div class="para">
+ The <code class="option">AllowOverride</code> directive allows you to specify which directives in a <code class="filename">.htaccess</code> file can override the default configuration. It takes the following form:
+ </div><pre class="screen">AllowOverride <em class="replaceable"><code>type</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>type</code></em> has to be one of the available grouping options as described in <a class="xref" href="#table-apache-httpdconf-allowoverride" title="Table 11.4. Available AllowOverride options">Table 11.4, “Available <code class="option">AllowOverride</code> options”</a>.
+ </div><div class="table" title="Table 11.4. Available AllowOverride options" id="table-apache-httpdconf-allowoverride"><h6>Table 11.4. Available <code class="option">AllowOverride</code> options</h6><div class="table-contents"><table summary="Available AllowOverride options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">All</code>
+ </td><td>
+ All directives in <code class="filename">.htaccess</code> are allowed to override earlier configuration settings.
+ </td></tr><tr><td>
+ <code class="option">None</code>
+ </td><td>
+ No directive in <code class="filename">.htaccess</code> is allowed to override earlier configuration settings.
+ </td></tr><tr><td>
+ <code class="option">AuthConfig</code>
+ </td><td>
+ Allows the use of authorization directives such as <code class="option">AuthName</code>, <code class="option">AuthType</code>, or <code class="option">Require</code>.
+ </td></tr><tr><td>
+ <code class="option">FileInfo</code>
+ </td><td>
+ Allows the use of file type, metadata, and <code class="systemitem">mod_rewrite</code> directives such as <code class="option">DefaultType</code>, <code class="option">RequestHeader</code>, or <code class="option">RewriteEngine</code>, as well as the <code class="option">Action</code> directive.
+ </td></tr><tr><td>
+ <code class="option">Indexes</code>
+ </td><td>
+ Allows the use of directory indexing directives such as <code class="option">AddDescription</code>, <code class="option">AddIcon</code>, or <code class="option">FancyIndexing</code>.
+ </td></tr><tr><td>
+ <code class="option">Limit</code>
+ </td><td>
+ Allows the use of host access directives, that is, <code class="option">Allow</code>, <code class="option">Deny</code>, and <code class="option">Order</code>.
+ </td></tr><tr><td>
+ <code class="option">Options</code>[<span class="optional">=<em class="replaceable"><code>option</code></em>,…</span>]
+ </td><td>
+ Allows the use of the <code class="option">Options</code> directive. Additionally, you can provide a comma-separated list of options to customize which options can be set using this directive.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.19. Using the AllowOverride directive" id="example-apache-httpdconf-allowoverride"><h6>Example 11.19. Using the <code class="option">AllowOverride</code> directive</h6><div class="example-contents"><pre class="screen">AllowOverride FileInfo AuthConfig Limit</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1711872" class="indexterm"></a>
+ <code class="option">BrowserMatch</code> </span></dt><dd><div class="para">
+ The <code class="option">BrowserMatch</code> directive allows you to modify the server behavior based on the client's web browser type. It takes the following form:
+ </div><pre class="screen">BrowserMatch <em class="replaceable"><code>pattern</code></em> <em class="replaceable"><code>variable</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>pattern</code></em> is a regular expression to match the User-Agent HTTP header field. The <em class="replaceable"><code>variable</code></em> is an environment variable that is set when the header field matches the pattern.
+ </div><div class="para">
+ By default, this directive is used to deny connections to specific browsers with known issues, and to disable keepalives and HTTP header flushes for browsers that are known to have problems with these actions.
+ </div><div class="example" title="Example 11.20. Using the BrowserMatch directive" id="example-apache-httpdconf-browsermatch"><h6>Example 11.20. Using the <code class="option">BrowserMatch</code> directive</h6><div class="example-contents"><pre class="screen">BrowserMatch "Mozilla/2" nokeepalive</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id761948" class="indexterm"></a>
+ <code class="option">CacheDefaultExpire</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheDefaultExpire</code> option allows you to set how long to cache a document that does not have any expiration date or the date of its last modification specified. It takes the following form:
+ </div><pre class="screen">CacheDefaultExpire <em class="replaceable"><code>time</code></em></pre><div class="para">
+ The <em class="replaceable"><code>time</code></em> specified in seconds. The default option is <code class="literal">3600</code> (that is, one hour).
+ </div><div class="example" title="Example 11.21. Using the CacheDefaultExpire directive" id="example-apache-httpdconf-cachedefaultexpire"><h6>Example 11.21. Using the <code class="option">CacheDefaultExpire</code> directive</h6><div class="example-contents"><pre class="screen">CacheDefaultExpire 3600</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id552058" class="indexterm"></a>
+ <code class="option">CacheDisable</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheDisable</code> directive allows you to disable caching of certain URLs. It takes the following form:
+ </div><pre class="screen">CacheDisable <em class="replaceable"><code>path</code></em></pre><div class="para">
+ The <em class="replaceable"><code>path</code></em> must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/files/</code>).
+ </div><div class="example" title="Example 11.22. Using the CacheDisable directive" id="example-apache-httpdconf-cachedisable"><h6>Example 11.22. Using the <code class="option">CacheDisable</code> directive</h6><div class="example-contents"><pre class="screen">CacheDisable /temporary</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id670358" class="indexterm"></a>
+ <code class="option">CacheEnable</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheEnable</code> directive allows you to specify a cache type to be used for certain URLs. It takes the following form:
+ </div><pre class="screen">CacheEnable <em class="replaceable"><code>type</code></em> <em class="replaceable"><code>url</code></em></pre><div class="para">
+ The <em class="replaceable"><code>type</code></em> has to be a valid cache type as described in <a class="xref" href="#table-apache-httpdconf-cacheenable" title="Table 11.5. Available cache types">Table 11.5, “Available cache types”</a>. The <em class="replaceable"><code>url</code></em> can be a path relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/images/</code>), a protocol (for example, <code class="literal">ftp://</code>), or an external URL such as <code class="literal">http://example.com/</code>.
+ </div><div class="table" title="Table 11.5. Available cache types" id="table-apache-httpdconf-cacheenable"><h6>Table 11.5. Available cache types</h6><div class="table-contents"><table summary="Available cache types" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Type
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">mem</code>
+ </td><td>
+ The memory-based storage manager.
+ </td></tr><tr><td>
+ <code class="option">disk</code>
+ </td><td>
+ The disk-based storage manager.
+ </td></tr><tr><td>
+ <code class="option">fd</code>
+ </td><td>
+ The file descriptor cache.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.23. Using the CacheEnable directive" id="example-apache-httpdconf-cacheenable"><h6>Example 11.23. Using the <code class="option">CacheEnable</code> directive</h6><div class="example-contents"><pre class="screen">CacheEnable disk /</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id437240" class="indexterm"></a>
+ <code class="option">CacheLastModifiedFactor</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheLastModifiedFactor</code> directive allows you to customize how long to cache a document that does not have any expiration date specified, but that provides information about the date of its last modification. It takes the following form:
+ </div><pre class="screen">CacheLastModifiedFactor <em class="replaceable"><code>number</code></em></pre><div class="para">
+ The <em class="replaceable"><code>number</code></em> is a coefficient to be used to multiply the time that passed since the last modification of the document. The default option is <code class="literal">0.1</code> (that is, one tenth).
+ </div><div class="example" title="Example 11.24. Using the CacheLastModifiedFactor directive" id="example-apache-httpdconf-cachelastmodifiedfactor"><h6>Example 11.24. Using the <code class="option">CacheLastModifiedFactor</code> directive</h6><div class="example-contents"><pre class="screen">CacheLastModifiedFactor 0.1</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id847006" class="indexterm"></a>
+ <code class="option">CacheMaxExpire</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheMaxExpire</code> directive allows you to specify the maximum amount of time to cache a document. It takes the following form:
+ </div><pre class="screen">CacheMaxExpire <em class="replaceable"><code>time</code></em></pre><div class="para">
+ The <em class="replaceable"><code>time</code></em> is specified in seconds. The default option is <code class="literal">86400</code> (that is, one day).
+ </div><div class="example" title="Example 11.25. Using the CacheMaxExpire directive" id="example-apache-httpdconf-cachemaxexpire"><h6>Example 11.25. Using the <code class="option">CacheMaxExpire</code> directive</h6><div class="example-contents"><pre class="screen">CacheMaxExpire 86400</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id734772" class="indexterm"></a>
+ <code class="option">CacheNegotiatedDocs</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheNegotiatedDocs</code> directive allows you to enable caching of the documents that were negotiated on the basis of content. It takes the following form:
+ </div><pre class="screen">CacheNegotiatedDocs <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-cachenegotiateddocs" title="Table 11.6. Available CacheNegotiatedDocs options">Table 11.6, “Available <code class="option">CacheNegotiatedDocs</code> options”</a>. Since the content-negotiated documents may change over time or because of the input from the requester, the default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.6. Available CacheNegotiatedDocs options" id="table-apache-httpdconf-cachenegotiateddocs"><h6>Table 11.6. Available <code class="option">CacheNegotiatedDocs</code> options</h6><div class="table-contents"><table summary="Available CacheNegotiatedDocs options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables caching the content-negotiated documents.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables caching the content-negotiated documents.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.26. Using the CacheNegotiatedDocs directive" id="example-apache-httpdconf-cachenegotiateddocs"><h6>Example 11.26. Using the <code class="option">CacheNegotiatedDocs</code> directive</h6><div class="example-contents"><pre class="screen">CacheNegotiatedDocs On</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1712294" class="indexterm"></a>
+ <code class="option">CacheRoot</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheRoot</code> directive allows you to specify the directory to store cache files in. It takes the following form:
+ </div><pre class="screen">CacheRoot <em class="replaceable"><code>directory</code></em></pre><a id="id1719800" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>directory</code></em> must be a full path to an existing directory in the local file system. The default option is <code class="filename">/var/cache/mod_proxy/</code>.
+ </div><div class="example" title="Example 11.27. Using the CacheRoot directive" id="example-apache-httpdconf-cacheroot"><h6>Example 11.27. Using the <code class="option">CacheRoot</code> directive</h6><div class="example-contents"><pre class="screen">CacheRoot /var/cache/mod_proxy</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id433716" class="indexterm"></a>
+ <code class="option">CustomLog</code> </span></dt><dd><div class="para">
+ The <code class="option">CustomLog</code> directive allows you to specify the log filename and the log file format. It takes the following form:
+ </div><pre class="screen">CustomLog <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>format</code></em></pre><a id="id427921" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to a log file, and must be relative to the directory that is specified by the <code class="option">ServerRoot</code> directive (that is, <code class="filename">/etc/httpd/</code> by default). The <em class="replaceable"><code>format</code></em> has to be either an explicit format string, or a format name that was previously defined using the <code class="option">LogFormat</code> directive.
+ </div><div class="example" title="Example 11.28. Using the CustomLog directive" id="example-apache-httpdconf-customlog"><h6>Example 11.28. Using the <code class="option">CustomLog</code> directive</h6><div class="example-contents"><pre class="screen">CustomLog logs/access_log combined</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id439674" class="indexterm"></a>
+ <code class="option">DefaultIcon</code> </span></dt><dd><div class="para">
+ The <code class="option">DefaultIcon</code> directive allows you to specify an icon to be displayed for a file in server-generated directory listings when no other icon is associated with it. It takes the following form:
+ </div><pre class="screen">DefaultIcon <em class="replaceable"><code>path</code></em></pre><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to an existing icon file, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/icons/unknown.png</code>).
+ </div><div class="example" title="Example 11.29. Using the DefaultIcon directive" id="example-apache-httpdconf-defaulticon"><h6>Example 11.29. Using the <code class="option">DefaultIcon</code> directive</h6><div class="example-contents"><pre class="screen">DefaultIcon /icons/unknown.png</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id831980" class="indexterm"></a>
+ <code class="option">DefaultType</code> </span></dt><dd><div class="para">
+ The <code class="option">DefaultType</code> directive allows you to specify a media type to be used in case the proper MIME type cannot be determined by the server. It takes the following form:
+ </div><pre class="screen">DefaultType <em class="replaceable"><code>content-type</code></em></pre><div class="para">
+ The <em class="replaceable"><code>content-type</code></em> has to be a valid MIME type such as <code class="literal">text/html</code>, <code class="literal">image/png</code>, <code class="literal">application/pdf</code>, etc.
+ </div><div class="example" title="Example 11.30. Using the DefaultType directive" id="example-apache-httpdconf-defaulttype"><h6>Example 11.30. Using the <code class="option">DefaultType</code> directive</h6><div class="example-contents"><pre class="screen">DefaultType text/plain</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id531919" class="indexterm"></a>
+ <code class="option">Deny</code> </span></dt><dd><div class="para">
+ The <code class="option">Deny</code> directive allows you to specify which clients are denied access to a given directory. It takes the following form:
+ </div><pre class="screen">Deny from <em class="replaceable"><code>client</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>client</code></em> can be a domain name, an IP address (both full and partial), a <em class="replaceable"><code>network</code></em>/<em class="replaceable"><code>netmask</code></em> pair, or <code class="literal">all</code> for all clients.
+ </div><div class="example" title="Example 11.31. Using the Deny directive" id="example-apache-httpdconf-deny"><h6>Example 11.31. Using the <code class="option">Deny</code> directive</h6><div class="example-contents"><pre class="screen">Deny from 192.168.1.1</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id2227183" class="indexterm"></a>
+ <code class="option">DirectoryIndex</code> </span></dt><dd><div class="para">
+ The <code class="option">DirectoryIndex</code> directive allows you to specify a document to be served to a client when a directory is requested (that is, when the URL ends with the <code class="literal">/</code> character). It takes the following form:
+ </div><pre class="screen">DirectoryIndex <em class="replaceable"><code>filename</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>filename</code></em> is a name of the file to look for in the requested directory. By default, the server looks for <code class="filename">index.html</code>, and <code class="filename">index.html.var</code>.
+ </div><div class="example" title="Example 11.32. Using the DirectoryIndex directive" id="example-apache-httpdconf-directoryindex"><h6>Example 11.32. Using the <code class="option">DirectoryIndex</code> directive</h6><div class="example-contents"><pre class="screen">DirectoryIndex index.html index.html.var</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id794787" class="indexterm"></a>
+ <code class="option">DocumentRoot</code> </span></dt><dd><div class="para">
+ The <code class="option">DocumentRoot</code> directive allows you to specify the main directory from which the content is served. It takes the following form:
+ </div><pre class="screen">DocumentRoot <em class="replaceable"><code>directory</code></em></pre><a id="id1342258" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>directory</code></em> must be a full path to an existing directory in the local file system. The default option is <code class="filename">/var/www/html/</code>.
+ </div><div class="example" title="Example 11.33. Using the DocumentRoot directive" id="example-apache-httpdconf-documentroot"><h6>Example 11.33. Using the <code class="option">DocumentRoot</code> directive</h6><div class="example-contents"><pre class="screen">DocumentRoot /var/www/html</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id684832" class="indexterm"></a>
+ <code class="option">ErrorDocument</code> </span></dt><dd><div class="para">
+ The <code class="option">ErrorDocument</code> directive allows you to specify a document or a message to be displayed as a response to a particular error. It takes the following form:
+ </div><pre class="screen">ErrorDocument <em class="replaceable"><code>error-code</code></em> <em class="replaceable"><code>action</code></em></pre><div class="para">
+ The <em class="replaceable"><code>error-code</code></em> has to be a valid code such as <code class="literal">403</code> (Forbidden), <code class="literal">404</code> (Not Found), or <code class="literal">500</code> (Internal Server Error). The <em class="replaceable"><code>action</code></em> can be either a URL (both local and external), or a message string enclosed in double quotes (that is, <code class="literal">"</code>).
+ </div><div class="example" title="Example 11.34. Using the ErrorDocument directive" id="example-apache-httpdconf-errordocument"><h6>Example 11.34. Using the <code class="option">ErrorDocument</code> directive</h6><div class="example-contents"><pre class="screen">ErrorDocument 403 "Access Denied"
+ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id801600" class="indexterm"></a>
+ <code class="option">ErrorLog</code> </span></dt><dd><div class="para">
+ The <code class="option">ErrorLog</code> directive allows you to specify a file to which the server errors are logged. It takes the following form:
+ </div><pre class="screen">ErrorLog <em class="replaceable"><code>path</code></em></pre><a id="id1377293" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to a log file, and can be either absolute, or relative to the directory that is specified by the <code class="option">ServerRoot</code> directive (that is, <code class="filename">/etc/httpd/</code> by default). The default option is <code class="filename">logs/error_log</code>
+ </div><div class="example" title="Example 11.35. Using the ErrorLog directive" id="example-apache-httpdconf-errorlog"><h6>Example 11.35. Using the <code class="option">ErrorLog</code> directive</h6><div class="example-contents"><pre class="screen">ErrorLog logs/error_log</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id633813" class="indexterm"></a>
+ <code class="option">ExtendedStatus</code> </span></dt><dd><div class="para">
+ The <code class="option">ExtendedStatus</code> directive allows you to enable detailed server status information. It takes the following form:
+ </div><pre class="screen">ExtendedStatus <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-extendedstatus" title="Table 11.7. Available ExtendedStatus options">Table 11.7, “Available <code class="option">ExtendedStatus</code> options”</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.7. Available ExtendedStatus options" id="table-apache-httpdconf-extendedstatus"><h6>Table 11.7. Available <code class="option">ExtendedStatus</code> options</h6><div class="table-contents"><table summary="Available ExtendedStatus options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables generating the detailed server status.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables generating the detailed server status.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.36. Using the ExtendedStatus directive" id="example-apache-httpdconf-extendedstatus"><h6>Example 11.36. Using the <code class="option">ExtendedStatus</code> directive</h6><div class="example-contents"><pre class="screen">ExtendedStatus On</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id751916" class="indexterm"></a>
+ <code class="option">Group</code> </span></dt><dd><div class="para">
+ The <code class="option">Group</code> directive allows you to specify the group under which the <code class="systemitem">httpd</code> service will run. It takes the following form:
+ </div><pre class="screen">Group <em class="replaceable"><code>group</code></em></pre><div class="para">
+ The <em class="replaceable"><code>group</code></em> has to be an existing UNIX group. The default option is <code class="option">apache</code>.
+ </div><div class="para">
+ Note that <code class="option">Group</code> is no longer supported inside <code class="option"><VirtualHost></code>, and has been replaced by the <code class="option">SuexecUserGroup</code> directive.
+ </div><div class="example" title="Example 11.37. Using the Group directive" id="example-apache-httpdconf-group"><h6>Example 11.37. Using the <code class="option">Group</code> directive</h6><div class="example-contents"><pre class="screen">Group apache</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id778969" class="indexterm"></a>
+ <code class="option">HeaderName</code> </span></dt><dd><div class="para">
+ The <code class="option">HeaderName</code> directive allows you to specify a file to be prepended to the beginning of the server-generated directory listing. It takes the following form:
+ </div><pre class="screen">HeaderName <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ The <em class="replaceable"><code>filename</code></em> is a name of the file to look for in the requested directory. By default, the server looks for <code class="filename">HEADER.html</code>.
+ </div><div class="example" title="Example 11.38. Using the HeaderName directive" id="example-apache-httpdconf-headername"><h6>Example 11.38. Using the <code class="option">HeaderName</code> directive</h6><div class="example-contents"><pre class="screen">HeaderName HEADER.html</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id559543" class="indexterm"></a>
+ <code class="option">HostnameLookups</code> </span></dt><dd><div class="para">
+ The <code class="option">HostnameLookups</code> directive allows you to enable automatic resolving of IP addresses. It takes the following form:
+ </div><pre class="screen">HostnameLookups <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-hostnamelookup" title="Table 11.8. Available HostnameLookups options">Table 11.8, “Available <code class="option">HostnameLookups</code> options”</a>. To conserve resources on the server, the default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.8. Available HostnameLookups options" id="table-apache-httpdconf-hostnamelookup"><h6>Table 11.8. Available <code class="option">HostnameLookups</code> options</h6><div class="table-contents"><table summary="Available HostnameLookups options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables resolving the IP address for each connection so that the hostname can be logged. However, this also adds a significant processing overhead.
+ </td></tr><tr><td>
+ <code class="option">Double</code>
+ </td><td>
+ Enables performing the double-reverse DNS lookup. In comparison to the above option, this adds even more processing overhead.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables resolving the IP address for each connection.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Note that when the presence of hostnames is required in server log files, it is often possible to use one of the many log analyzer tools that perform the DNS lookups more efficiently.
+ </div><div class="example" title="Example 11.39. Using the HostnameLookups directive" id="example-apache-httpdconf-hostnamelookups"><h6>Example 11.39. Using the <code class="option">HostnameLookups</code> directive</h6><div class="example-contents"><pre class="screen">HostnameLookups Off</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1130293" class="indexterm"></a>
+ <code class="option">Include</code> </span></dt><dd><div class="para">
+ The <code class="option">Include</code> directive allows you to include other configuration files. It takes the following form:
+ </div><pre class="screen">Include <em class="replaceable"><code>filename</code></em></pre><a id="id714167" class="indexterm"></a><div class="para">
+ The <code class="option">filename</code> can be an absolute path, a path relative to the directory specified by the <code class="option">ServerRoot</code> directive, or a wildcard expression. All configuration files from the <code class="filename">/etc/httpd/conf.d/</code> directory are loaded by default.
+ </div><div class="example" title="Example 11.40. Using the Include directive" id="example-apache-httpdconf-include"><h6>Example 11.40. Using the <code class="option">Include</code> directive</h6><div class="example-contents"><pre class="screen">Include conf.d/*.conf</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id796685" class="indexterm"></a>
+ <code class="option">IndexIgnore</code> </span></dt><dd><div class="para">
+ The <code class="option">IndexIgnore</code> directive allows you to specify a list of filenames to be omitted from the server-generated directory listings. It takes the following form:
+ </div><pre class="screen">IndexIgnore <em class="replaceable"><code>filename</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>filename</code></em> option can be either a full filename, or a wildcard expression.
+ </div><div class="example" title="Example 11.41. Using the IndexIgnore directive" id="example-apache-httpdconf-indexignore"><h6>Example 11.41. Using the <code class="option">IndexIgnore</code> directive</h6><div class="example-contents"><pre class="screen">IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id419797" class="indexterm"></a>
+ <code class="option">IndexOptions</code> </span></dt><dd><div class="para">
+ The <code class="option">IndexOptions</code> directive allows you to customize the behavior of server-generated directory listings. It takes the following form:
+ </div><pre class="screen">IndexOptions <em class="replaceable"><code>option</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-indexoptions" title="Table 11.9. Available directory listing options">Table 11.9, “Available directory listing options”</a>. The default options are <code class="option">Charset=UTF-8</code>, <code class="option">FancyIndexing</code>, <code class="option">HTMLTable</code>, <code class="option">NameWidth=*</code>, and <code class="option">VersionSort</code>.
+ </div><div class="table" title="Table 11.9. Available directory listing options" id="table-apache-httpdconf-indexoptions"><h6>Table 11.9. Available directory listing options</h6><div class="table-contents"><table summary="Available directory listing options" border="1"><colgroup><col width="33%" /><col width="67%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Charset</code>=<em class="replaceable"><code>encoding</code></em>
+ </td><td>
+ Specifies the character set of a generated web page. The <em class="replaceable"><code>encoding</code></em> has to be a valid character set such as <code class="literal">UTF-8</code> or <code class="literal">ISO-8859-2</code>.
+ </td></tr><tr><td>
+ <code class="option">Type</code>=<em class="replaceable"><code>content-type</code></em>
+ </td><td>
+ Specifies the media type of a generated web page. The <em class="replaceable"><code>content-type</code></em> has to be a valid MIME type such as <code class="literal">text/html</code> or <code class="literal">text/plain</code>.
+ </td></tr><tr><td>
+ <code class="option">DescriptionWidth</code>=<em class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies the width of the description column. The <em class="replaceable"><code>value</code></em> can be either a number of characters, or an asterisk (that is, <code class="literal">*</code>) to adjust the width automatically.
+ </td></tr><tr><td>
+ <code class="option">FancyIndexing</code>
+ </td><td>
+ Enables advanced features such as different icons for certain files or possibility to re-sort a directory listing by clicking on a column header.
+ </td></tr><tr><td>
+ <code class="option">FolderFirst</code>
+ </td><td>
+ Enables listing directories first, always placing them above files.
+ </td></tr><tr><td>
+ <code class="option">HTMLTable</code>
+ </td><td>
+ Enables the use of HTML tables for directory listings.
+ </td></tr><tr><td>
+ <code class="option">IconsAreLinks</code>
+ </td><td>
+ Enables using the icons as links.
+ </td></tr><tr><td>
+ <code class="option">IconHeight</code>=<em class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies an icon height. The <em class="replaceable"><code>value</code></em> is a number of pixels.
+ </td></tr><tr><td>
+ <code class="option">IconWidth</code>=<em class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies an icon width. The <em class="replaceable"><code>value</code></em> is a number of pixels.
+ </td></tr><tr><td>
+ <code class="option">IgnoreCase</code>
+ </td><td>
+ Enables sorting files and directories in a case-sensitive manner.
+ </td></tr><tr><td>
+ <code class="option">IgnoreClient</code>
+ </td><td>
+ Disables accepting query variables from a client.
+ </td></tr><tr><td>
+ <code class="option">NameWidth</code>=<em class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies the width of the filename column. The <em class="replaceable"><code>value</code></em> can be either a number of characters, or an asterisk (that is, <code class="literal">*</code>) to adjust the width automatically.
+ </td></tr><tr><td>
+ <code class="option">ScanHTMLTitles</code>
+ </td><td>
+ Enables parsing the file for a description (that is, the <code class="literal">title</code> element) in case it is not provided by the <code class="option">AddDescription</code> directive.
+ </td></tr><tr><td>
+ <code class="option">ShowForbidden</code>
+ </td><td>
+ Enables listing the files with otherwise restricted access.
+ </td></tr><tr><td>
+ <code class="option">SuppressColumnSorting</code>
+ </td><td>
+ Disables re-sorting a directory listing by clicking on a column header.
+ </td></tr><tr><td>
+ <code class="option">SuppressDescription</code>
+ </td><td>
+ Disables reserving a space for file descriptions.
+ </td></tr><tr><td>
+ <code class="option">SuppressHTMLPreamble</code>
+ </td><td>
+ Disables the use of standard HTML preamble when a file specified by the <code class="option">HeaderName</code> directive is present.
+ </td></tr><tr><td>
+ <code class="option">SuppressIcon</code>
+ </td><td>
+ Disables the use of icons in directory listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressLastModified</code>
+ </td><td>
+ Disables displaying the date of the last modification field in directory listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressRules</code>
+ </td><td>
+ Disables the use of horizontal lines in directory listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressSize</code>
+ </td><td>
+ Disables displaying the file size field in directory listings.
+ </td></tr><tr><td>
+ <code class="option">TrackModified</code>
+ </td><td>
+ Enables returning the <code class="literal">Last-Modified</code> and <code class="literal">ETag</code> values in the HTTP header.
+ </td></tr><tr><td>
+ <code class="option">VersionSort</code>
+ </td><td>
+ Enables sorting files that contain a version number in the expected manner.
+ </td></tr><tr><td>
+ <code class="option">XHTML</code>
+ </td><td>
+ Enables the use of XHTML 1.0 instead of the default HTML 3.2.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.42. Using the IndexOptions directive" id="example-apache-httpdconf-indexoptions"><h6>Example 11.42. Using the <code class="option">IndexOptions</code> directive</h6><div class="example-contents"><pre class="screen">IndexOptions FancyIndexing VersionSort NameWidth=* HTMLTable Charset=UTF-8</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id750542" class="indexterm"></a>
+ <code class="option">KeepAlive</code> </span></dt><dd><div class="para">
+ The <code class="option">KeepAlive</code> directive allows you to enable persistent connections. It takes the following form:
+ </div><pre class="screen">KeepAlive <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-keepalive" title="Table 11.10. Available KeepAlive options">Table 11.10, “Available <code class="option">KeepAlive</code> options”</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.10. Available KeepAlive options" id="table-apache-httpdconf-keepalive"><h6>Table 11.10. Available <code class="option">KeepAlive</code> options</h6><div class="table-contents"><table summary="Available KeepAlive options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables the persistent connections. In this case, the server will accept more than one request per connection.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables the keep-alive connections.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Note that when the persistent connections are enabled, on a busy server, the number of child processes can increase rapidly and eventually reach the maximum limit, slowing down the server significantly. To reduce the risk, it is recommended that you set <code class="option">KeepAliveTimeout</code> to a low number, and monitor the <code class="filename">/var/log/httpd/logs/error_log</code> log file carefully.
+ </div><div class="example" title="Example 11.43. Using the KeepAlive directive" id="example-apache-httpdconf-keepalive"><h6>Example 11.43. Using the <code class="option">KeepAlive</code> directive</h6><div class="example-contents"><pre class="screen">KeepAlive Off</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id846050" class="indexterm"></a>
+ <code class="option">KeepAliveTimeout</code> </span></dt><dd><div class="para">
+ The <code class="option">KeepAliveTimeout</code> directive allows you to specify the amount of time to wait for another request before closing the connection. It takes the following form:
+ </div><pre class="screen">KeepAliveTimeout <em class="replaceable"><code>time</code></em></pre><div class="para">
+ The <em class="replaceable"><code>time</code></em> is specified in seconds. The default option is <code class="literal">15</code>.
+ </div><div class="example" title="Example 11.44. Using the KeepAliveTimeout directive" id="example-apache-httpdconf-keepalivetimeout"><h6>Example 11.44. Using the <code class="option">KeepAliveTimeout</code> directive</h6><div class="example-contents"><pre class="screen">KeepAliveTimeout 15</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id561518" class="indexterm"></a>
+ <code class="option">LanguagePriority</code> </span></dt><dd><div class="para">
+ The <code class="option">LanguagePriority</code> directive allows you to customize the precedence of languages. It takes the following form:
+ </div><pre class="screen">LanguagePriority <em class="replaceable"><code>language</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>language</code></em> has to be a valide MIME language such as <code class="literal">cs</code>, <code class="literal">en</code>, or <code class="literal">fr</code>.
+ </div><div class="para">
+ This directive is especially useful for web servers that serve content in multiple languages based on the client's language settings.
+ </div><div class="example" title="Example 11.45. Using the LanguagePriority directive" id="example-apache-httpdconf-languagepriority"><h6>Example 11.45. Using the <code class="option">LanguagePriority</code> directive</h6><div class="example-contents"><pre class="screen">LanguagePriority sk cs en</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id591104" class="indexterm"></a>
+ <code class="option">Listen</code> </span></dt><dd><div class="para">
+ The <em class="replaceable"><code>Listen</code></em> directive allows you to specify IP addresses or ports to listen to. It takes the following form:
+ </div><pre class="screen">Listen [<span class="optional"><em class="replaceable"><code>ip-address</code></em>:</span>]<em class="replaceable"><code>port</code></em> [<span class="optional"><em class="replaceable"><code>protocol</code></em></span>]</pre><div class="para">
+ The <em class="replaceable"><code>ip-address</code></em> is optional and unless supplied, the server will accept incoming requests on a given <em class="replaceable"><code>port</code></em> from all IP addresses. Since the <em class="replaceable"><code>protocol</code></em> is determined automatically from the port number, it can be usually omitted. The default option is to listen to port <code class="literal">80</code>.
+ </div><div class="para">
+ Note that if the server is configured to listen to a port under 1024, only superuser will be able to start the <code class="systemitem">httpd</code> service.
+ </div><div class="example" title="Example 11.46. Using the Listen directive" id="example-apache-httpdconf-listen"><h6>Example 11.46. Using the <code class="option">Listen</code> directive</h6><div class="example-contents"><pre class="screen">Listen 80</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id770985" class="indexterm"></a>
+ <code class="option">LoadModule</code> </span></dt><dd><div class="para">
+ The <code class="option">LoadModule</code> directive allows you to load a <em class="firstterm">Dynamic Shared Object</em> (<acronym class="acronym">DSO</acronym>) module. It takes the following form:
+ </div><pre class="screen">LoadModule <em class="replaceable"><code>name</code></em> <em class="replaceable"><code>path</code></em></pre><a id="id1689798" class="indexterm"></a><a id="id1689819" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>name</code></em> has to be a valid identifier of the required module. The <em class="replaceable"><code>path</code></em> refers to an existing module file, and must be relative to the directory in which the libraries are placed (that is, <code class="filename">/usr/lib/httpd/</code> on 32-bit and <code class="filename">/usr/lib64/httpd/</code> on 64-bit systems by default).
+ </div><div class="para">
+ Refer to <a class="xref" href="#s1-apache-dso" title="11.4. Working with Modules">Section 11.4, “Working with Modules”</a> for more information on the Apache HTTP Server's DSO support.
+ </div><div class="example" title="Example 11.47. Using the LoadModule directive" id="example-apache-httpdconf-loadmodule"><h6>Example 11.47. Using the <code class="option">LoadModule</code> directive</h6><div class="example-contents"><pre class="screen">LoadModule php5_module modules/libphp5.so</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id858663" class="indexterm"></a>
+ <code class="option">LogFormat</code> </span></dt><dd><div class="para">
+ The <em class="replaceable"><code>LogFormat</code></em> directive allows you to specify a log file format. It takes the following form:
+ </div><pre class="screen">LogFormat <em class="replaceable"><code>format</code></em> <em class="replaceable"><code>name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>format</code></em> is a string consisting of options as described in <a class="xref" href="#table-apache-httpdconf-logformat" title="Table 11.11. Common LogFormat options">Table 11.11, “Common <code class="option">LogFormat</code> options”</a>. The <em class="replaceable"><code>name</code></em> can be used instead of the format string in the <code class="option">CustomLog</code> directive.
+ </div><div class="table" title="Table 11.11. Common LogFormat options" id="table-apache-httpdconf-logformat"><h6>Table 11.11. Common <code class="option">LogFormat</code> options</h6><div class="table-contents"><table summary="Common LogFormat options" border="1"><colgroup><col width="13%" /><col width="88%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">%b</code>
+ </td><td>
+ Represents the size of the response in bytes.
+ </td></tr><tr><td>
+ <code class="option">%h</code>
+ </td><td>
+ Represents the IP address or hostname of a remote client.
+ </td></tr><tr><td>
+ <code class="option">%l</code>
+ </td><td>
+ Represents the remote log name if supplied. If not, a hyphen (that is, <code class="literal">-</code>) is used instead.
+ </td></tr><tr><td>
+ <code class="option">%r</code>
+ </td><td>
+ Represents the first line of the request string as it came from the browser or client.
+ </td></tr><tr><td>
+ <code class="option">%s</code>
+ </td><td>
+ Represents the status code.
+ </td></tr><tr><td>
+ <code class="option">%t</code>
+ </td><td>
+ Represents the date and time of the request.
+ </td></tr><tr><td>
+ <code class="option">%u</code>
+ </td><td>
+ If the authentication is required, it represents the remote user. If not, a hyphen (that is, <code class="literal">-</code>) is used instead.
+ </td></tr><tr><td>
+ <code class="option">%{<em class="replaceable"><code>field</code></em>}</code>
+ </td><td>
+ Represents the content of the HTTP header <em class="replaceable"><code>field</code></em>. The common options include <code class="option">%{Referer}</code> (the URL of the web page that referred the client to the server) and <code class="option">%{User-Agent}</code> (the type of the web browser making the request).
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.48. Using the LogFormat directive" id="example-apache-httpdconf-logformat"><h6>Example 11.48. Using the <code class="option">LogFormat</code> directive</h6><div class="example-contents"><pre class="screen">LogFormat "%h %l %u %t \"%r\" %>s %b" common</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id515287" class="indexterm"></a>
+ <code class="option">LogLevel</code> </span></dt><dd><div class="para">
+ The <code class="option">LogLevel</code> directive allows you to customize the verbosity level of the error log. It takes the following form:
+ </div><pre class="screen">LogLevel <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-loglevel" title="Table 11.12. Available LogLevel options">Table 11.12, “Available <code class="option">LogLevel</code> options”</a>. The default option is <code class="option">warn</code>.
+ </div><div class="table" title="Table 11.12. Available LogLevel options" id="table-apache-httpdconf-loglevel"><h6>Table 11.12. Available <code class="option">LogLevel</code> options</h6><div class="table-contents"><table summary="Available LogLevel options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">emerg</code>
+ </td><td>
+ Only the emergency situations when the server cannot perform its work are logged.
+ </td></tr><tr><td>
+ <code class="option">alert</code>
+ </td><td>
+ All situations when an immediate action is required are logged.
+ </td></tr><tr><td>
+ <code class="option">crit</code>
+ </td><td>
+ All critical conditions are logged.
+ </td></tr><tr><td>
+ <code class="option">error</code>
+ </td><td>
+ All error messages are logged.
+ </td></tr><tr><td>
+ <code class="option">warn</code>
+ </td><td>
+ All warning messages are logged.
+ </td></tr><tr><td>
+ <code class="option">notice</code>
+ </td><td>
+ Even normal, but still significant situations are logged.
+ </td></tr><tr><td>
+ <code class="option">info</code>
+ </td><td>
+ Various informational messages are logged.
+ </td></tr><tr><td>
+ <code class="option">debug</code>
+ </td><td>
+ Various debugging messages are logged.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.49. Using the LogLevel directive" id="example-apache-httpdconf-loglevel"><h6>Example 11.49. Using the <code class="option">LogLevel</code> directive</h6><div class="example-contents"><pre class="screen">LogLevel warn</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id534105" class="indexterm"></a>
+ <code class="option">MaxKeepAliveRequests</code> </span></dt><dd><div class="para">
+ The <code class="option">MaxKeepAliveRequests</code> directive allows you to specify the maximum number of requests for a persistent connection. It takes the following form:
+ </div><pre class="screen">MaxKeepAliveRequests <em class="replaceable"><code>number</code></em></pre><div class="para">
+ A high <em class="replaceable"><code>number</code></em> can improve the performance of the server. Note that using <code class="literal">0</code> allows unlimited number of requests. The default option is <code class="option">100</code>.
+ </div><div class="example" title="Example 11.50. Using the MaxKeepAliveRequests option" id="example-apache-httpdconf-maxkeepaliverequests"><h6>Example 11.50. Using the <code class="option">MaxKeepAliveRequests</code> option</h6><div class="example-contents"><pre class="screen">MaxKeepAliveRequests 100</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1520708" class="indexterm"></a>
+ <code class="option">NameVirtualHost</code> </span></dt><dd><div class="para">
+ The <code class="option">NameVirtualHost</code> directive allows you to specify the IP address and port number for a name-based virtual host. It takes the following form:
+ </div><pre class="screen">NameVirtualHost <em class="replaceable"><code>ip-address</code></em>[<span class="optional">:<em class="replaceable"><code>port</code></em></span>]</pre><div class="para">
+ The <em class="replaceable"><code>ip-address</code></em> can be either a full IP address, or an asterisk (that is, <code class="literal">*</code>) representing all interfaces. Note that IPv6 addresses have to be enclosed in square brackets (that is, <code class="literal">[</code> and <code class="literal">]</code>). The <em class="replaceable"><code>port</code></em> is optional.
+ </div><div class="para">
+ Name-based virtual hosting allows one Apache HTTP Server to serve different domains without using multiple IP addresses.
+ </div><div class="important" title="Important: Using Secure HTTP Connections"><div class="admonition_header"><h2>Important: Using Secure HTTP Connections</h2></div><div class="admonition"><div class="para">
+ Name-based virtual hosts <span class="emphasis"><em>only</em></span> work with non-secure HTTP connections. If using virtual hosts with a secure server, use IP address-based virtual hosts instead.
+ </div></div></div><div class="example" title="Example 11.51. Using the NameVirtualHost directive" id="example-apache-httpdconf-namevirtualhost"><h6>Example 11.51. Using the <code class="option">NameVirtualHost</code> directive</h6><div class="example-contents"><pre class="screen">NameVirtualHost *:80</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id797238" class="indexterm"></a>
+ <code class="option">Options</code> </span></dt><dd><div class="para">
+ The <code class="option">Options</code> directive allows you to specify which server features are available in a particular directory. It takes the following form:
+ </div><pre class="screen">Options <em class="replaceable"><code>option</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-options" title="Table 11.13. Available server features">Table 11.13, “Available server features”</a>.
+ </div><div class="table" title="Table 11.13. Available server features" id="table-apache-httpdconf-options"><h6>Table 11.13. Available server features</h6><div class="table-contents"><table summary="Available server features" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">ExecCGI</code>
+ </td><td>
+ Enables the execution of CGI scripts.
+ </td></tr><tr><td>
+ <code class="option">FollowSymLinks</code>
+ </td><td>
+ Enables following symbolic links in the directory.
+ </td></tr><tr><td>
+ <code class="option">Includes</code>
+ </td><td>
+ Enables server-side includes.
+ </td></tr><tr><td>
+ <code class="option">IncludesNOEXEC</code>
+ </td><td>
+ Enables server-side includes, but does not allow the execution of commands.
+ </td></tr><tr><td>
+ <code class="option">Indexes</code>
+ </td><td>
+ Enables server-generated directory listings.
+ </td></tr><tr><td>
+ <code class="option">MultiViews</code>
+ </td><td>
+ Enables content-negotiated <span class="quote">“<span class="quote">MultiViews</span>”</span>.
+ </td></tr><tr><td>
+ <code class="option">SymLinksIfOwnerMatch</code>
+ </td><td>
+ Enables following symbolic links in the directory when both the link and the target file have the same owner.
+ </td></tr><tr><td>
+ <code class="option">All</code>
+ </td><td>
+ Enables all of the features above with the exception of <code class="option">MultiViews</code>.
+ </td></tr><tr><td>
+ <code class="option">None</code>
+ </td><td>
+ Disables all of the features above.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.52. Using the Options directive" id="example-apache-httpdconf-options"><h6>Example 11.52. Using the <code class="option">Options</code> directive</h6><div class="example-contents"><pre class="screen">Options Indexes FollowSymLinks</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id446656" class="indexterm"></a>
+ <code class="option">Order</code> </span></dt><dd><div class="para">
+ The <code class="option">Order</code> directive allows you to specify the order in which the <code class="option">Allow</code> and <code class="option">Deny</code> directives are evaluated. It takes the following form:
+ </div><pre class="screen">Order <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-order" title="Table 11.14. Available Order options">Table 11.14, “Available <code class="option">Order</code> options”</a>. The default option is <code class="option">allow,deny</code>.
+ </div><div class="table" title="Table 11.14. Available Order options" id="table-apache-httpdconf-order"><h6>Table 11.14. Available <code class="option">Order</code> options</h6><div class="table-contents"><table summary="Available Order options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow,deny</code>
+ </td><td>
+ <code class="option">Allow</code> directives are evaluated first.
+ </td></tr><tr><td>
+ <code class="option">deny,allow</code>
+ </td><td>
+ <code class="option">Deny</code> directives are evaluated first.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.53. Using the Order directive" id="example-apache-httpdconf-order"><h6>Example 11.53. Using the <code class="option">Order</code> directive</h6><div class="example-contents"><pre class="screen">Order allow,deny</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id542384" class="indexterm"></a>
+ <code class="option">PidFile</code> </span></dt><dd><div class="para">
+ The <code class="option">PidFile</code> directive allows you to specify a file to which the <em class="firstterm">process ID</em> (<acronym class="acronym">PID</acronym>) of the server is stored. It takes the following form:
+ </div><pre class="screen">PidFile <em class="replaceable"><code>path</code></em></pre><a id="id1715763" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to a pid file, and can be either absolute, or relative to the directory that is specified by the <code class="option">ServerRoot</code> directive (that is, <code class="filename">/etc/httpd/</code> by default). The default option is <code class="filename">run/httpd.pid</code>.
+ </div><div class="example" title="Example 11.54. Using the PidFile directive" id="example-apache-httpdconf-pidfile"><h6>Example 11.54. Using the <code class="option">PidFile</code> directive</h6><div class="example-contents"><pre class="screen">PidFile run/httpd.pid</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1689682" class="indexterm"></a>
+ <code class="option">ProxyRequests</code> </span></dt><dd><div class="para">
+ The <code class="option">ProxyRequests</code> directive allows you to enable forward proxy requests. It takes the following form:
+ </div><pre class="screen">ProxyRequests <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-proxyrequests" title="Table 11.15. Available ProxyRequests options">Table 11.15, “Available <code class="option">ProxyRequests</code> options”</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.15. Available ProxyRequests options" id="table-apache-httpdconf-proxyrequests"><h6>Table 11.15. Available <code class="option">ProxyRequests</code> options</h6><div class="table-contents"><table summary="Available ProxyRequests options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables forward proxy requests.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables forward proxy requests.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.55. Using the ProxyRequests directive" id="example-apache-httpdconf-proxyrequests"><h6>Example 11.55. Using the <code class="option">ProxyRequests</code> directive</h6><div class="example-contents"><pre class="screen">ProxyRequests On</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id2224649" class="indexterm"></a>
+ <code class="option">ReadmeName</code> </span></dt><dd><div class="para">
+ The <code class="option">ReadmeName</code> directive allows you to specify a file to be appended to the end of the server-generated directory listing. It takes the following form:
+ </div><pre class="screen">ReadmeName <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ The <em class="replaceable"><code>filename</code></em> is a name of the file to look for in the requested directory. By default, the server looks for <code class="filename">README.html</code>.
+ </div><div class="example" title="Example 11.56. Using the ReadmeName directive" id="example-apache-httpdconf-readmename"><h6>Example 11.56. Using the <code class="option">ReadmeName</code> directive</h6><div class="example-contents"><pre class="screen">ReadmeName README.html</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id589705" class="indexterm"></a>
+ <code class="option">Redirect</code> </span></dt><dd><div class="para">
+ The <code class="option">Redirect</code> directive allows you to redirect a client to another URL. It takes the following form:
+ </div><pre class="screen">Redirect [<span class="optional"><em class="replaceable"><code>status</code></em></span>] <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>url</code></em></pre><div class="para">
+ The <em class="replaceable"><code>status</code></em> is optional, and if provided, it has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-redirect" title="Table 11.16. Available status options">Table 11.16, “Available status options”</a>. The <em class="replaceable"><code>path</code></em> refers to the old location, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/docs</code>). The <em class="replaceable"><code>url</code></em> refers to the current location of the content (for example, <code class="literal">http://docs.example.com</code>).
+ </div><div class="table" title="Table 11.16. Available status options" id="table-apache-httpdconf-redirect"><h6>Table 11.16. Available status options</h6><div class="table-contents"><table summary="Available status options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Status
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">permanent</code>
+ </td><td>
+ Indicates that the requested resource has been moved permanently. The <code class="literal">301</code> (Moved Permanently) status code is returned to a client.
+ </td></tr><tr><td>
+ <code class="option">temp</code>
+ </td><td>
+ Indicates that the requested resource has been moved only temporarily. The <code class="literal">302</code> (Found) status code is returned to a client.
+ </td></tr><tr><td>
+ <code class="option">seeother</code>
+ </td><td>
+ Indicates that the requested resource has been replaced. The <code class="literal">303</code> (See Other) status code is returned to a client.
+ </td></tr><tr><td>
+ <code class="option">gone</code>
+ </td><td>
+ Indicates that the requested resource has been removed permanently. The <code class="literal">410</code> (Gone) status is returned to a client.
+ </td></tr></tbody></table></div></div><br class="table-break" /><a id="id551095" class="indexterm"></a><div class="para">
+ Note that for more advanced redirection techniques, you can use the <code class="systemitem">mod_rewrite</code> module that is part of the Apache HTTP Server installation.
+ </div><div class="example" title="Example 11.57. Using the Redirect directive" id="example-apache-httpdconf-redirect"><h6>Example 11.57. Using the <code class="option">Redirect</code> directive</h6><div class="example-contents"><pre class="screen">Redirect permanent /docs http://docs.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id690748" class="indexterm"></a>
+ <code class="option">ScriptAlias</code> </span></dt><dd><div class="para">
+ The <code class="option">ScriptAlias</code> directive allows you to specify the location of CGI scripts. It takes the following form:
+ </div><pre class="screen">ScriptAlias <em class="replaceable"><code>url-path</code></em> <em class="replaceable"><code>real-path</code></em></pre><div class="para">
+ The <em class="replaceable"><code>url-path</code></em> must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/cgi-bin/</code>). The <em class="replaceable"><code>real-path</code></em> is a full path to a file or directory in the local file system.
+ </div><a id="id533468" class="indexterm"></a><div class="para">
+ This directive is typically followed by the <code class="option">Directory</code> tag with additional permissions to access the target directory. By default, the <code class="literal">/cgi-bin/</code> alias is created so that the scripts located in the <code class="filename">/var/www/cgi-bin/</code> are accessible.
+ </div><div class="para">
+ The <code class="option">ScriptAlias</code> directive is used for security reasons to prevent CGI scripts from being viewed as ordinary text documents.
+ </div><div class="example" title="Example 11.58. Using the ScriptAlias directive" id="example-apache-httpdconf-scriptalias"><h6>Example 11.58. Using the <code class="option">ScriptAlias</code> directive</h6><div class="example-contents"><pre class="screen">ScriptAlias /cgi-bin/ /var/www/cgi-bin/
+
+<Directory "/var/www/cgi-bin">
+ AllowOverride None
+ Options None
+ Order allow,deny
+ Allow from all
+</Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id570225" class="indexterm"></a>
+ <code class="option">ServerAdmin</code> </span></dt><dd><div class="para">
+ The <code class="option">ServerAdmin</code> directive allows you to specify the email address of the server administrator to be displayed in server-generated web pages. It takes the following form:
+ </div><pre class="screen">ServerAdmin <em class="replaceable"><code>email</code></em></pre><div class="para">
+ The default option is <code class="literal">root at localhost</code>.
+ </div><div class="para">
+ This directive is commonly set to <code class="literal">webmaster@<em class="replaceable"><code>hostname</code></em></code>, where <em class="replaceable"><code>hostname</code></em> is the address of the server. Once set, alias <code class="literal">webmaster</code> to the person responsible for the web server in <code class="filename">/etc/aliases</code>, and as superuser, run the <code class="command">newaliases</code> command.
+ </div><div class="example" title="Example 11.59. Using the ServerAdmin directive" id="example-apache-httpdconf-serveradmin"><h6>Example 11.59. Using the <code class="option">ServerAdmin</code> directive</h6><div class="example-contents"><pre class="screen">ServerAdmin webmaster at penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id810367" class="indexterm"></a>
+ <code class="option">ServerName</code> </span></dt><dd><div class="para">
+ The <code class="option">ServerName</code> directive allows you to specify the hostname and the port number of a web server. It takes the following form:
+ </div><pre class="screen">ServerName <em class="replaceable"><code>hostname</code></em>[<span class="optional">:<em class="replaceable"><code>port</code></em></span>]</pre><div class="para">
+ The <em class="replaceable"><code>hostname</code></em> has to be a <em class="firstterm">fully qualified domain name</em> (<acronym class="acronym">FQDN</acronym>) of the server. The <em class="replaceable"><code>port</code></em> is optional, but when supplied, it has to match the number specified by the <code class="option">Listen</code> directive.
+ </div><div class="para">
+ When using this directive, make sure that the IP address and server name pair are included in the <code class="filename">/etc/hosts</code> file.
+ </div><div class="example" title="Example 11.60. Using the ServerName directive" id="example-apache-httpdconf-servername"><h6>Example 11.60. Using the <code class="option">ServerName</code> directive</h6><div class="example-contents"><pre class="screen">ServerName penguin.example.com:80</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id557056" class="indexterm"></a>
+ <code class="option">ServerRoot</code> </span></dt><dd><div class="para">
+ The <code class="option">ServerRoot</code> directive allows you to specify the directory in which the server operates. It takes the following form:
+ </div><pre class="screen">ServerRoot <em class="replaceable"><code>directory</code></em></pre><a id="id557098" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>directory</code></em> must be a full path to an existing directory in the local file system. The default option is <code class="filename">/etc/httpd/</code>.
+ </div><div class="example" title="Example 11.61. Using the ServerRoot directive" id="example-apache-httpd-serverroot"><h6>Example 11.61. Using the <code class="option">ServerRoot</code> directive</h6><div class="example-contents"><pre class="screen">ServerRoot /etc/httpd</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id452325" class="indexterm"></a>
+ <code class="option">ServerSignature</code> </span></dt><dd><div class="para">
+ The <code class="option">ServerSignature</code> directive allows you to enable displaying information about the server on server-generated documents. It takes the following form:
+ </div><pre class="screen">ServerSignature <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-serversignature" title="Table 11.17. Available ServerSignature options">Table 11.17, “Available <code class="option">ServerSignature</code> options”</a>. The default option is <code class="option">On</code>.
+ </div><div class="table" title="Table 11.17. Available ServerSignature options" id="table-apache-httpdconf-serversignature"><h6>Table 11.17. Available <code class="option">ServerSignature</code> options</h6><div class="table-contents"><table summary="Available ServerSignature options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables appending the server name and version to server-generated pages.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables appending the server name and version to server-generated pages.
+ </td></tr><tr><td>
+ <code class="option">EMail</code>
+ </td><td>
+ Enables appending the server name, version, and the email address of the system administrator as specified by the <code class="option">ServerAdmin</code> directive to server-generated pages.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.62. Using the ServerSignature directive" id="example-apache-httpdconf-serversignature"><h6>Example 11.62. Using the <code class="option">ServerSignature</code> directive</h6><div class="example-contents"><pre class="screen">ServerSignature On</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id718183" class="indexterm"></a>
+ <code class="option">ServerTokens</code> </span></dt><dd><div class="para">
+ The <code class="option">ServerTokens</code> directive allows you to customize what information are included in the Server response header. It takes the following form:
+ </div><pre class="screen">ServerTokens <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-servertokens" title="Table 11.18. Available ServerTokens options">Table 11.18, “Available <code class="option">ServerTokens</code> options”</a>. The default option is <code class="option">OS</code>.
+ </div><div class="table" title="Table 11.18. Available ServerTokens options" id="table-apache-httpdconf-servertokens"><h6>Table 11.18. Available <code class="option">ServerTokens</code> options</h6><div class="table-contents"><table summary="Available ServerTokens options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Prod</code>
+ </td><td>
+ Includes the product name only (that is, <code class="literal">Apache</code>).
+ </td></tr><tr><td>
+ <code class="option">Major</code>
+ </td><td>
+ Includes the product name and the major version of the server (for example, <code class="literal">2</code>).
+ </td></tr><tr><td>
+ <code class="option">Minor</code>
+ </td><td>
+ Includes the product name and the minor version of the server (for example, <code class="literal">2.2</code>).
+ </td></tr><tr><td>
+ <code class="option">Min</code>
+ </td><td>
+ Includes the product name and the minimal version of the server (for example, <code class="literal">2.2.15</code>).
+ </td></tr><tr><td>
+ <code class="option">OS</code>
+ </td><td>
+ Includes the product name, the minimal version of the server, and the type of the operating system it is running on (for example, <code class="literal">Red Hat</code>).
+ </td></tr><tr><td>
+ <code class="option">Full</code>
+ </td><td>
+ Includes all the information above along with the list of loaded modules.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Note that for security reasons, it is recommended to reveal as little information about the server as possible.
+ </div><div class="example" title="Example 11.63. Using the ServerTokens directive" id="example-apache-httpdconf-servertokens"><h6>Example 11.63. Using the <code class="option">ServerTokens</code> directive</h6><div class="example-contents"><pre class="screen">ServerTokens Prod</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id490609" class="indexterm"></a>
+ <code class="option">SuexecUserGroup</code> </span></dt><dd><div class="para">
+ The <code class="option">SuexecUserGroup</code> directive allows you to specify the user and group under which the CGI scripts will be run. It takes the following form:
+ </div><pre class="screen">SuexecUserGroup <em class="replaceable"><code>user</code></em> <em class="replaceable"><code>group</code></em></pre><div class="para">
+ The <em class="replaceable"><code>user</code></em> has to be an existing user, and the <em class="replaceable"><code>group</code></em> must be a valid UNIX group.
+ </div><div class="para">
+ For security reasons, the CGI scripts should not be run with root privileges. Note that in <code class="option"><VirtualHost></code>, <code class="option">SuexecUserGroup</code> replaces the <code class="option">User</code> and <code class="option">Group</code> directives.
+ </div><div class="example" title="Example 11.64. Using the SuexecUserGroup directive" id="example-apache-httpdconf-suexecusergroup"><h6>Example 11.64. Using the <code class="option">SuexecUserGroup</code> directive</h6><div class="example-contents"><pre class="screen">SuexecUserGroup apache apache</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id534200" class="indexterm"></a>
+ <code class="option">Timeout</code> </span></dt><dd><div class="para">
+ The <code class="option">Timeout</code> directive allows you to specify the amount of time to wait for an event before closing a connection. It takes the following form:
+ </div><pre class="screen">Timeout <em class="replaceable"><code>time</code></em></pre><div class="para">
+ The <em class="replaceable"><code>time</code></em> is specified in seconds. The default option is <code class="literal">60</code>.
+ </div><div class="example" title="Example 11.65. Using the Timeout directive" id="example-apache-httpdconf-timeout"><h6>Example 11.65. Using the <code class="option">Timeout</code> directive</h6><div class="example-contents"><pre class="screen">Timeout 60</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id672333" class="indexterm"></a>
+ <code class="option">TypesConfig</code> </span></dt><dd><div class="para">
+ The <code class="option">TypesConfig</code> allows you to specify the location of the MIME types configuration file. It takes the following form:
+ </div><pre class="screen">TypesConfig <em class="replaceable"><code>path</code></em></pre><a id="id569957" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to an existing MIME types configuration file, and can be either absolute, or relative to the directory that is specified by the <code class="option">ServerRoot</code> directive (that is, <code class="filename">/etc/httpd/</code> by default). The default option is <code class="option">/etc/mime.types</code>.
+ </div><div class="para">
+ Note that instead of editing <code class="filename">/etc/mime.types</code>, the recommended way to add MIME type mapping to the Apache HTTP Server is to use the <code class="option">AddType</code> directive.
+ </div><div class="example" title="Example 11.66. Using the TypesConfig directive" id="example-apache-httpdconf-typesconfig"><h6>Example 11.66. Using the <code class="option">TypesConfig</code> directive</h6><div class="example-contents"><pre class="screen">TypesConfig /etc/mime.types</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1830043" class="indexterm"></a>
+ <code class="option">UseCanonicalName</code> </span></dt><dd><div class="para">
+ The <code class="option">UseCanonicalName</code> allows you to specify the way the server refers to itself. It takes the following form:
+ </div><pre class="screen">UseCanonicalName <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-usecanonicalname" title="Table 11.19. Available UseCanonicalName options">Table 11.19, “Available <code class="option">UseCanonicalName</code> options”</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.19. Available UseCanonicalName options" id="table-apache-httpdconf-usecanonicalname"><h6>Table 11.19. Available <code class="option">UseCanonicalName</code> options</h6><div class="table-contents"><table summary="Available UseCanonicalName options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables the use of the name that is specified by the <code class="option">ServerName</code> directive.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables the use of the name that is specified by the <code class="option">ServerName</code> directive. The hostname and port number provided by the requesting client are used instead.
+ </td></tr><tr><td>
+ <code class="option">DNS</code>
+ </td><td>
+ Disables the use of the name that is specified by the <code class="option">ServerName</code> directive. The hostname determined by a reverse DNS lookup is used instead.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.67. Using the UseCanonicalName directive" id="example-apache-httpdconf-usecanonicalname"><h6>Example 11.67. Using the <code class="option">UseCanonicalName</code> directive</h6><div class="example-contents"><pre class="screen">UseCanonicalName Off</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1552795" class="indexterm"></a>
+ <code class="option">User</code> </span></dt><dd><div class="para">
+ The <code class="option">User</code> directive allows you to specify the user under which the <code class="systemitem">httpd</code> service will run. It takes the following form:
+ </div><pre class="screen">User <em class="replaceable"><code>user</code></em></pre><div class="para">
+ The <em class="replaceable"><code>user</code></em> has to be an existing UNIX user. The default option is <code class="option">apache</code>.
+ </div><div class="para">
+ For security reasons, the <code class="systemitem">httpd</code> service should not be run with root privileges. Note that <code class="option">User</code> is no longer supported inside <code class="option"><VirtualHost></code>, and has been replaced by the <code class="option">SuexecUserGroup</code> directive.
+ </div><div class="example" title="Example 11.68. Using the User directive" id="example-apache-httpdconf-user"><h6>Example 11.68. Using the <code class="option">User</code> directive</h6><div class="example-contents"><pre class="screen">User apache</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id759790" class="indexterm"></a>
+ <code class="option">UserDir</code> </span></dt><dd><div class="para">
+ The <code class="option">UserDir</code> directive allows you to enable serving content from users' home directories. It takes the following form:
+ </div><pre class="screen">UserDir <em class="replaceable"><code>option</code></em></pre><a id="id959771" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>option</code></em> can be either a name of the directory to look for in user's home directory (typically <code class="option">public_html</code>), or a valid keyword as described in <a class="xref" href="#table-apache-httpdconf-userdir" title="Table 11.20. Available UserDir options">Table 11.20, “Available <code class="option">UserDir</code> options”</a>. The default option is <code class="option">disabled</code>.
+ </div><div class="table" title="Table 11.20. Available UserDir options" id="table-apache-httpdconf-userdir"><h6>Table 11.20. Available <code class="option">UserDir</code> options</h6><div class="table-contents"><table summary="Available UserDir options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">enabled</code> <em class="replaceable"><code>user</code></em>…
+ </td><td>
+ Enables serving content from home directories of given <em class="replaceable"><code>user</code></em>s.
+ </td></tr><tr><td>
+ <code class="option">disabled</code> [<span class="optional"><em class="replaceable"><code>user</code></em>…</span>]
+ </td><td>
+ Disables serving content from home directories, either for all users, or, if a space separated list of <em class="replaceable"><code>user</code></em>s is supplied, for given users only.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note" title="Note: Set the Correct Permissions"><div class="admonition_header"><h2>Note: Set the Correct Permissions</h2></div><div class="admonition"><div class="para">
+ In order for the web server to access the content, the permissions on relevant directories and files must be set correctly. Make sure that all users are able to access the home directories, and that they can access and read the content of the directory specified by the <code class="option">UserDir</code> directive. For example:
+ </div><pre class="screen">~]# <code class="command">chmod a+x /home/<em class="replaceable"><code>username</code></em>/</code>
+~]# <code class="command">chmod a+rx /home/<em class="replaceable"><code>username</code></em>/public_html/</code></pre><div class="para">
+ All files in this directory must be set accordingly.
+ </div></div></div><div class="example" title="Example 11.69. Using the UserDir directive" id="example-apache-httpdconf-userdir"><h6>Example 11.69. Using the <code class="option">UserDir</code> directive</h6><div class="example-contents"><pre class="screen">UserDir public_html</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" title="11.3.2. Common ssl.conf Directives" id="s2-apache-sslconf-common"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-sslconf-common">11.3.2. Common <code class="filename">ssl.conf</code> Directives</h3></div></div></div><div class="para">
+ The <em class="firstterm">Secure Sockets Layer</em> (<acronym class="acronym">SSL</acronym>) directives allow you to customize the behavior of the Apache HTTP Secure Server, and in most cases, they are configured appropriately during the installation. Be careful when changing these settings, as incorrect configuration can lead to security vulnerabilities.
+ </div><a id="id439896" class="indexterm"></a><div class="para">
+ The following directive is commonly used in <code class="filename">/etc/httpd/conf.d/ssl.conf</code>:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id692237" class="indexterm"></a>
+ <code class="option">SetEnvIf</code> </span></dt><dd><div class="para">
+ The <code class="option">SetEnvIf</code> directive allows you to set environment variables based on the headers of incoming connections. It takes the following form:
+ </div><pre class="screen">SetEnvIf <em class="replaceable"><code>option</code></em> <em class="replaceable"><code>pattern</code></em> [<span class="optional">!</span>]<em class="replaceable"><code>variable</code></em>[<span class="optional">=<em class="replaceable"><code>value</code></em></span>]…</pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> can be either a HTTP header field, a previously defined environment variable name, or a valid keyword as described in <a class="xref" href="#table-apache-sslconf-setenvif" title="Table 11.21. Available SetEnvIf options">Table 11.21, “Available <code class="option">SetEnvIf</code> options”</a>. The <em class="replaceable"><code>pattern</code></em> is a regular expression. The <em class="replaceable"><code>variable</code></em> is an environment variable that is set when the option matches the pattern. If the optional exclamation mark (that is, <code class="literal">!</code>) is present, the variable is removed instead of being set.
+ </div><div class="table" title="Table 11.21. Available SetEnvIf options" id="table-apache-sslconf-setenvif"><h6>Table 11.21. Available <code class="option">SetEnvIf</code> options</h6><div class="table-contents"><table summary="Available SetEnvIf options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Remote_Host</code>
+ </td><td>
+ Refers to the client's hostname.
+ </td></tr><tr><td>
+ <code class="option">Remote_Addr</code>
+ </td><td>
+ Refers to the client's IP address.
+ </td></tr><tr><td>
+ <code class="option">Server_Addr</code>
+ </td><td>
+ Refers to the server's IP address.
+ </td></tr><tr><td>
+ <code class="option">Request_Method</code>
+ </td><td>
+ Refers to the request method (for example, <code class="literal">GET</code>).
+ </td></tr><tr><td>
+ <code class="option">Request_Protocol</code>
+ </td><td>
+ Refers to the protocol name and version (for example, <code class="literal">HTTP/1.1</code>).
+ </td></tr><tr><td>
+ <code class="option">Request_URI</code>
+ </td><td>
+ Refers to the requested resource.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="option">SetEnvIf</code> directive is used to disable HTTP keepalives, and to allow SSL to close the connection without a closing notification from the client browser. This is necessary for certain web browsers that do not reliably shut down the SSL connection.
+ </div><div class="example" title="Example 11.70. Using the SetEnvIf directive" id="example-apache-sslconf-setenvif"><h6>Example 11.70. Using the <code class="option">SetEnvIf</code> directive</h6><div class="example-contents"><pre class="screen">SetEnvIf User-Agent ".*MSIE.*" \
+ nokeepalive ssl-unclean-shutdown \
+ downgrade-1.0 force-response-1.0</pre></div></div><br class="example-break" /></dd></dl></div><div class="para">
+ Note that for the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file to be present, the <span class="package">mod_ssl</span> needs to be installed. Refer to <a class="xref" href="#s1-apache-mod_ssl" title="11.6. Setting Up an SSL Server">Section 11.6, “Setting Up an SSL Server”</a> for more information on how to install and configure an SSL server.
+ </div></div><div class="section" title="11.3.3. Common Multi-Processing Module Directives" id="s2-apache-mpm-common"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mpm-common">11.3.3. Common Multi-Processing Module Directives</h3></div></div></div><div class="para">
+ The <em class="firstterm">Multi-Processing Module</em> (<acronym class="acronym">MPM</acronym>) directives allow you to customize the behavior of a particular MPM specific server-pool. Since its characteristics differ depending on which MPM is used, the directives are embeded in <code class="option">IfModule</code>. By default, the server-pool is defined for both the <code class="systemitem">prefork</code> and <code class="systemitem">worker</code> MPMs.
+ </div><a id="id592547" class="indexterm"></a><div class="para">
+ The following MPM directives are commonly used in <code class="filename">/etc/httpd/conf/httpd.conf</code>:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id532613" class="indexterm"></a>
+ <code class="option">MaxClients</code> </span></dt><dd><div class="para">
+ The <code class="option">MaxClients</code> directive allows you to specify the maximum number of simultaneously connected clients to process at one time. It takes the following form:
+ </div><pre class="screen">MaxClients <em class="replaceable"><code>number</code></em></pre><div class="para">
+ A high <em class="replaceable"><code>number</code></em> can improve the performance of the server, although it is not recommended to exceed <code class="literal">256</code> when using the <code class="systemitem">prefork</code> MPM.
+ </div><div class="example" title="Example 11.71. Using the MaxClients directive" id="example-apache-mpm-maxclients"><h6>Example 11.71. Using the <code class="option">MaxClients</code> directive</h6><div class="example-contents"><pre class="screen">MaxClients 256</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id582741" class="indexterm"></a>
+ <code class="option">MaxRequestsPerChild</code> </span></dt><dd><div class="para">
+ The <code class="option">MaxRequestsPerChild</code> directive allows you to specify the maximum number of request a child process can serve before it dies. It takes the following form:
+ </div><pre class="screen">MaxRequestsPerChild <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Setting the <em class="replaceable"><code>number</code></em> to <code class="literal">0</code> allows unlimited number of requests.
+ </div><div class="para">
+ The <code class="option">MaxRequestsPerChild</code> directive is used to prevent long-lived processes from causing memory leaks.
+ </div><div class="example" title="Example 11.72. Using the MaxRequestsPerChild directive" id="example-apache-mpm-maxrequestsperchild"><h6>Example 11.72. Using the <code class="option">MaxRequestsPerChild</code> directive</h6><div class="example-contents"><pre class="screen">MaxRequestsPerChild 4000</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id434933" class="indexterm"></a>
+ <code class="option">MaxSpareServers</code> </span></dt><dd><div class="para">
+ The <code class="option">MaxSpareServers</code> directive allows you to specify the maximum number of spare child processes. It takes the following form:
+ </div><pre class="screen">MaxSpareServers <em class="replaceable"><code>number</code></em></pre><div class="para">
+ This directive is used by the <code class="systemitem">prefork</code> MPM only.
+ </div><div class="example" title="Example 11.73. Using the MaxSpareServers directive" id="example-apache-mpm-maxspareservers"><h6>Example 11.73. Using the <code class="option">MaxSpareServers</code> directive</h6><div class="example-contents"><pre class="screen">MaxSpareServers 20</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id2328029" class="indexterm"></a>
+ <code class="option">MaxSpareThreads</code> </span></dt><dd><div class="para">
+ The <code class="option">MaxSpareThreads</code> directive allows you to specify the maximum number of spare server threads. It takes the following form:
+ </div><pre class="screen">MaxSpareThreads <em class="replaceable"><code>number</code></em></pre><div class="para">
+ The <em class="replaceable"><code>number</code></em> must be greater than or equal to the sum of <code class="option">MinSpareThreads</code> and <code class="option">ThreadsPerChild</code>. This directive is used by the <code class="systemitem">worker</code> MPM only.
+ </div><div class="example" title="Example 11.74. Using the MaxSpareThreads directive" id="example-apache-mpm-maxsparethreads"><h6>Example 11.74. Using the <code class="option">MaxSpareThreads</code> directive</h6><div class="example-contents"><pre class="screen">MaxSpareThreads 75</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1553437" class="indexterm"></a>
+ <code class="option">MinSpareServers</code> </span></dt><dd><div class="para">
+ The <code class="option">MinSpareServers</code> directive allows you to specify the minimum number of spare child processes. It takes the following form:
+ </div><pre class="screen">MinSpareServers <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Note that a high <em class="replaceable"><code>number</code></em> can create a heavy processing load on the server. This directive is used by the <code class="systemitem">prefork</code> MPM only.
+ </div><div class="example" title="Example 11.75. Using the MinSpareServers directive" id="example-apache-mpm-minspareservers"><h6>Example 11.75. Using the <code class="option">MinSpareServers</code> directive</h6><div class="example-contents"><pre class="screen">MinSpareServers 5</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id674352" class="indexterm"></a>
+ <code class="option">MinSpareThreads</code> </span></dt><dd><div class="para">
+ The <code class="option">MinSpareThreads</code> directive allows you to specify the minimum number of spare server threads. It takes the following form:
+ </div><pre class="screen">MinSpareThreads <em class="replaceable"><code>number</code></em></pre><div class="para">
+ This directive is used by the <code class="systemitem">worker</code> MPM only.
+ </div><div class="example" title="Example 11.76. Using the MinSpareThreads directive" id="example-apache-mpm-minsparethreads"><h6>Example 11.76. Using the <code class="option">MinSpareThreads</code> directive</h6><div class="example-contents"><pre class="screen">MinSpareThreads 75</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id492083" class="indexterm"></a>
+ <code class="option">StartServers</code> </span></dt><dd><div class="para">
+ The <code class="option">StartServers</code> directive allows you to specify the number of child processes to create when the service is started. It takes the following form:
+ </div><pre class="screen">StartServers <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Since the child processes are dynamically created and terminated according to the current traffic load, it is usually not necessary to change this value.
+ </div><div class="example" title="Example 11.77. Using the StartServers directive" id="example-apache-mpm-startservers"><h6>Example 11.77. Using the <code class="option">StartServers</code> directive</h6><div class="example-contents"><pre class="screen">StartServers 8</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id428481" class="indexterm"></a>
+ <code class="option">ThreadsPerChild</code> </span></dt><dd><div class="para">
+ The <code class="option">ThreadsPerChild</code> directive allows you to specify the number of threads a child process can create. It takes the following form:
+ </div><pre class="screen">ThreadsPerChild <em class="replaceable"><code>number</code></em></pre><div class="para">
+ This directive is used by the <code class="systemitem">worker</code> MPM only.
+ </div><div class="example" title="Example 11.78. Using the ThreadsPerChild directive" id="example-apache-mpm-threadsperchild"><h6>Example 11.78. Using the <code class="option">ThreadsPerChild</code> directive</h6><div class="example-contents"><pre class="screen">ThreadsPerChild 25</pre></div></div><br class="example-break" /></dd></dl></div></div></div><div class="section" title="11.4. Working with Modules" id="s1-apache-dso"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-dso">11.4. Working with Modules</h2></div></div></div><a id="id418852" class="indexterm"></a><a id="id626375" class="indexterm"></a><div class="para">
+ Being a modular application, the <code class="systemitem">httpd</code> service is distributed along with a number of <em class="firstterm">Dynamic Shared Objects</em> (<acronym class="acronym">DSO</acronym>s), which can be dynamically loaded or unloaded at runtime as necessary. By default, these modules are located in <code class="filename">/usr/lib/httpd/modules/</code> on 32-bit and in <code class="filename">/usr/lib64/httpd/modules/</code> on 64-bit systems.
+ </div><div class="section" title="11.4.1. Loading a Module" id="s2-apache-dso-loading"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-dso-loading">11.4.1. Loading a Module</h3></div></div></div><a id="id559853" class="indexterm"></a><div class="para">
+ To load a particular DSO module, use the <code class="option">LoadModule</code> directive as described in <a class="xref" href="#s2-apache-httpdconf-directives" title="11.3.1. Common httpd.conf Directives">Section 11.3.1, “Common <code class="filename">httpd.conf</code> Directives”</a>. Note that modules provided by a separate package often have their own configuration file in the <code class="filename">/etc/httpd/conf.d/</code> directory.
+ </div><div class="example" title="Example 11.79. Loading the mod_ssl DSO" id="example-apache-dso-loading"><h6>Example 11.79. Loading the <code class="systemitem">mod_ssl</code> DSO</h6><div class="example-contents"><pre class="screen">LoadModule ssl_module modules/mod_ssl.so</pre></div></div><br class="example-break" /><div class="para">
+ Once you are finished, restart the web server to reload the configuration. Refer to <a class="xref" href="#s3-apache-running-restarting" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a> for more information on how to restart the <code class="systemitem">httpd</code> service.
+ </div></div><div class="section" title="11.4.2. Writing a Module" id="s2-apache-dso-writing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-dso-writing">11.4.2. Writing a Module</h3></div></div></div><a id="id764003" class="indexterm"></a><div class="para">
+ If you intend to create a new DSO module, make sure you have the <span class="package">httpd-devel</span> package installed. To do so, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">yum install httpd-devel</code></pre><div class="para">
+ This package contains the include files, the header files, and the <span class="application"><strong>APache eXtenSion</strong></span> (<code class="command">apxs</code>) utility required to compile a module.
+ </div><div class="para">
+ Once written, you can build the module with the following command:
+ </div><pre class="screen">~]# <code class="command">apxs -i -a -c <em class="replaceable"><code>module_name</code></em>.c</code></pre><div class="para">
+ If the build was successful, you should be able to load the module the same way as any other module that is distributed with the Apache HTTP Server.
+ </div></div></div><div class="section" title="11.5. Setting Up Virtual Hosts" id="s1-apache-virtualhosts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-virtualhosts">11.5. Setting Up Virtual Hosts</h2></div></div></div><a id="id771232" class="indexterm"></a><a id="id771245" class="indexterm"></a><div class="para">
+ The Apache HTTP Server's built in virtual hosting allows the server to provide different information based on which IP address, hostname, or port is being requested.
+ </div><div class="para">
+ To create a name-based virtual host, find the virtual host container provided in <code class="filename">/etc/httpd/conf/httpd.conf</code> as an example, remove the hash sign (that is, <code class="literal">#</code>) from the beginning of each line, and customize the options according to your requirements as shown in <a class="xref" href="#example-apache-virtualhosts-config" title="Example 11.80. Sampe virtual host configuration">Example 11.80, “Sampe virtual host configuration”</a>.
+ </div><div class="example" title="Example 11.80. Sampe virtual host configuration" id="example-apache-virtualhosts-config"><h6>Example 11.80. Sampe virtual host configuration</h6><div class="example-contents"><pre class="screen">NameVirtualHost penguin.example.com:80
+
+<VirtualHost penguin.example.com:80>
+ ServerAdmin webmaster at penguin.example.com
+ DocumentRoot /www/docs/penguin.example.com
+ ServerName penguin.example.com:80
+ ErrorLog logs/penguin.example.com-error_log
+ CustomLog logs/penguin.example.com-access_log common
+</VirtualHost></pre></div></div><br class="example-break" /><div class="para">
+ Note that <code class="option">ServerName</code> must be a valid DNS name assigned to the machine. The <code class="option"><VirtualHost></code> container is highly customizable, and accepts most of the directives available within the main server configuration. Directives that are <span class="emphasis"><em>not</em></span> supported within this container include <code class="option">User</code> and <code class="option">Group</code>, which were replaced by <code class="option">SuexecUserGroup</code>.
+ </div><div class="note" title="Note: Changing the Port Number"><div class="admonition_header"><h2>Note: Changing the Port Number</h2></div><div class="admonition"><div class="para">
+ If you configure a virtual host to listen on a non-default port, make sure you update the <code class="option">Listen</code> directive in the global settings section of the <code class="filename">/etc/httpd/conf/httpd.conf</code> file accordingly.
+ </div></div></div><div class="para">
+ To activate a newly created virtual host, the web server has to be restarted first. Refer to <a class="xref" href="#s3-apache-running-restarting" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a> for more information on how to restart the <code class="systemitem">httpd</code> service.
+ </div></div><div class="section" title="11.6. Setting Up an SSL Server" id="s1-apache-mod_ssl"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-mod_ssl">11.6. Setting Up an SSL Server</h2></div></div></div><a id="id827217" class="indexterm"></a><a id="id759715" class="indexterm"></a><a id="id759728" class="indexterm"></a><a id="id759743" class="indexterm"></a><a id="id759758" class="indexterm"></a><a id="id1376558" class="indexterm"></a><div class="para">
+ <em class="firstterm">Secure Sockets Layer</em> (<acronym class="acronym">SSL</acronym>) is a cryptographic protocol that allows a server and a client to communicate securely. Along with its extended and improved version called <em class="firstterm">Transport Layer Security</em> (<acronym class="acronym">TLS</acronym>), it ensures both privacy and data integrity. The Apache HTTP Server in combination with <code class="systemitem">mod_ssl</code>, a module that uses the OpenSSL toolkit to provide the SSL/TLS support, is commonly referred to as the <em class="firstterm">SSL server</em>.
+ </div><div class="para">
+ Unlike a regular HTTP connection that can be read and possibly modified by anybody who is able to intercept it, the use of <code class="systemitem">mod_ssl</code> prevents any inspection or modification of the transmitted content. This section provides basic information on how to enable this module in the Apache HTTP Server configuration, and guides you through the process of generating private keys and self-signed certificates.
+ </div><div class="section" title="11.6.1. An Overview of Certificates and Security" id="s2-apache-mod_ssl-certificates"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mod_ssl-certificates">11.6.1. An Overview of Certificates and Security</h3></div></div></div><a id="id705319" class="indexterm"></a><a id="id705336" class="indexterm"></a><div class="para">
+ Secure communication is based on the use of keys. In conventional or <em class="firstterm">symmetric cryptography</em>, both ends of the transaction have the same key they can use to decode each other's transmissions. On the other hand, in public or <em class="firstterm">asymmetric cryptography</em>, two keys co-exist: a <em class="firstterm">private key</em> that is kept a secret, and a <em class="firstterm">public key</em> that is usually shared with the public. While the data encoded with the public key can only be decoded with the private key, data encoded with the private key can in turn only be decoded with the public key.
+ </div><a id="id437474" class="indexterm"></a><a id="id437491" class="indexterm"></a><div class="para">
+ To provide secure communications using SSL, an SSL server must use a digital certificate signed by a <em class="firstterm">Certificate Authority</em> (<acronym class="acronym">CA</acronym>). The certificate lists various attributes of the server (that is, the server hostname, the name of the company, its location, etc.), and the signature produced using the CA's private key. This signature ensures that a particular certificate authority has issued the certificate, and that the certificate has not been modified in any way.
+ </div><div class="para">
+ When a web browser establishes a new SSL connection, it checks the certificate provided by the web server. If the certificate does not have a signature from a trusted CA, or if the hostname listed in the certificate does not match the hostname used to establish the connection, it refuses to communicate with the server and usually presents a user with an appropriate error message.
+ </div><div class="para">
+ By default, most web browsers are configured to trust a set of widely used certificate authorities. Because of this, an appropriate CA should be chosen when setting up a secure server, so that target users can trust the connection, otherwise they will be presented with an error message, and will have to accept the certificate manually. Since encouraging users to override certificate errors can allow an attacker to intercept the connection, you should use a trusted CA whenever possible. For more information on this, see <a class="xref" href="#table-apache-mod_ssl-certificates-authorities" title="Table 11.22. CA lists for most common web browsers">Table 11.22, “CA lists for most common web browsers”</a>.
+ </div><div class="table" title="Table 11.22. CA lists for most common web browsers" id="table-apache-mod_ssl-certificates-authorities"><h6>Table 11.22. CA lists for most common web browsers</h6><div class="table-contents"><table summary="CA lists for most common web browsers" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Web Browser
+ </th><th>
+ Link
+ </th></tr></thead><tbody><tr><td>
+ <span class="application"><strong>Mozilla Firefox</strong></span>
+ </td><td>
+ <a href="http://www.mozilla.org/projects/security/certs/included/">Mozilla root CA list</a>.
+ </td></tr><tr><td>
+ <span class="application"><strong>Opera</strong></span>
+ </td><td>
+ <a href="http://my.opera.com/rootstore/blog/">The Opera Rootstore</a>.
+ </td></tr><tr><td>
+ <span class="application"><strong>Internet Explorer</strong></span>
+ </td><td>
+ <a href="http://support.microsoft.com/kb/931125">Windows root certificate program members</a>.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ When setting up an SSL server, you need to generate a certificate request and a private key, and then send the certificate request, proof of the company's identity, and payment to a certificate authority. Once the CA verifies the certificate request and your identity, it will send you a signed certificate you can use with your server. Alternatively, you can create a self-signed certificate that does not contain a CA signature, and thus should be used for testing purposes only.
+ </div></div><div class="section" title="11.6.2. Enabling the mod_ssl Module" id="s2-apache-mod_ssl-enabling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mod_ssl-enabling">11.6.2. Enabling the <code class="systemitem">mod_ssl</code> Module</h3></div></div></div><div class="para">
+ If you intend to set up an SSL server, make sure you have the <span class="package">mod_ssl</span> (the <code class="systemitem">mod_ssl</code> module) and <span class="package">openssl</span> (the OpenSSL toolkit) packages installed. To do so, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">yum install mod_ssl openssl</code></pre><a id="id553836" class="indexterm"></a><div class="para">
+ This will create the <code class="systemitem">mod_ssl</code> configuration file at <code class="filename">/etc/httpd/conf.d/ssl.conf</code>, which is included in the main Apache HTTP Server configuration file by default. For the module to be loaded, restart the <code class="systemitem">httpd</code> service as described in <a class="xref" href="#s3-apache-running-restarting" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a>.
+ </div></div><div class="section" title="11.6.3. Using an Existing Key and Certificate" id="s2-apache-mod_ssl-keypair"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mod_ssl-keypair">11.6.3. Using an Existing Key and Certificate</h3></div></div></div><a id="id496988" class="indexterm"></a><a id="id497005" class="indexterm"></a><div class="para">
+ If you have a previously created key and certificate, you can configure the SSL server to use these files instead of generating new ones. There are only two situations where this is not possible:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="emphasis"><em>You are changing the IP address or domain name.</em></span>
+ </div><div class="para">
+ Certificates are issued for a particular IP address and domain name pair. If one of these values changes, the certificate becomes invalid.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>You have a certificate from VeriSign, and you are changing the server software.</em></span>
+ </div><div class="para">
+ VeriSign, a widely used certificate authority, issues certificates for a particular software product, IP address, and domain name. Changing the software product renders the certificate invalid.
+ </div></li></ol></div><div class="para">
+ In either of the above cases, you will need to obtain a new certificate. For more information on this topic, refer to <a class="xref" href="#s2-apache-mod_ssl-genkey" title="11.6.4. Generating a New Key and Certificate">Section 11.6.4, “Generating a New Key and Certificate”</a>.
+ </div><div class="para">
+ If you wish to use an existing key and certificate, move the relevant files to the <code class="filename">/etc/pki/tls/private/</code> and <code class="filename">/etc/pki/tls/certs/</code> directories respectively. You can do so by typing the following commands:
+ </div><pre class="screen">~]# <code class="command">mv</code> <code class="filename"><em class="replaceable"><code>key_file</code></em>.key</code> <code class="filename">/etc/pki/tls/private/<em class="replaceable"><code>hostname</code></em>.key</code>
+~]# <code class="command">mv</code> <code class="filename"><em class="replaceable"><code>certificate</code></em>.crt</code> <code class="filename">/etc/pki/tls/certs/<em class="replaceable"><code>hostname</code></em>.crt</code></pre><div class="para">
+ Then add the following lines to the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> configuration file:
+ </div><pre class="screen">SSLCertificateFile /etc/pki/tls/certs/<em class="replaceable"><code>hostname</code></em>.crt
+SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostname</code></em>.key</pre><div class="para">
+ To load the updated configuration, restart the <code class="systemitem">httpd</code> service as described in <a class="xref" href="#s3-apache-running-restarting" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a>.
+ </div><div class="example" title="Example 11.81. Using a key and certificate from the Red Hat Secure Web Server" id="example-apache-mod_ssl-keypair"><h6>Example 11.81. Using a key and certificate from the <span class="application">Red Hat Secure Web Server</span></h6><div class="example-contents"><pre class="screen">~]# <code class="command">mv /etc/httpd/conf/httpsd.key /etc/pki/tls/private/penguin.example.com.key</code>
+~]# <code class="command">mv /etc/httpd/conf/httpsd.crt /etc/pki/tls/certs/penguin.example.com.crt</code></pre></div></div><br class="example-break" /></div><div class="section" title="11.6.4. Generating a New Key and Certificate" id="s2-apache-mod_ssl-genkey"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mod_ssl-genkey">11.6.4. Generating a New Key and Certificate</h3></div></div></div><a id="id1813833" class="indexterm"></a><a id="id431308" class="indexterm"></a><div class="para">
+ In order to generate a new key and certificate pair, you must to have the <span class="package">crypto-utils</span> package installed in your system. You can install it by typing the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">yum install crypto-utils</code></pre><div class="para">
+ This package provides a set of tools to generate and manage SSL certificates and private keys, and includes <span class="application"><strong>genkey</strong></span>, the Red Hat Keypair Generation utility that will guide you through the key generation process.
+ </div><div class="important" title="Important: Replacing an Existing Certificate"><div class="admonition_header"><h2>Important: Replacing an Existing Certificate</h2></div><div class="admonition"><div class="para">
+ If the server already has a valid certificate and you are replacing it with a new one, specify a different serial number. This ensures that client browsers are notified of this change, update to this new certificate as expected, and do not fail to access the page. To create a new certificate with a custom serial number, use the following command instead of <span class="application"><strong>genkey</strong></span>:
+ </div><pre class="screen">~]# <code class="command">openssl req -x509 -new -set_serial <em class="replaceable"><code>number</code></em> -key <em class="replaceable"><code>hostname</code></em>.key -out <em class="replaceable"><code>hostname</code></em>.crt</code></pre></div></div><div class="note" title="Note: Remove a Previously Created Key"><div class="admonition_header"><h2>Note: Remove a Previously Created Key</h2></div><div class="admonition"><div class="para">
+ If there already is a key file for a particular hostname in your system, <span class="application"><strong>genkey</strong></span> will refuse to start. In this case, remove the existing file using the following command:
+ </div><pre class="screen">~]# <code class="command">rm /etc/pki/tls/private/<em class="replaceable"><code>hostname</code></em>.key</code></pre></div></div><div class="para">
+ To run the utility, use the <code class="command">genkey</code> command followed by the appropriate hostname (for example, <code class="systemitem">penguin.example.com</code>):
+ </div><pre class="screen">~]# <code class="command">genkey</code> <em class="replaceable"><code>hostname</code></em></pre><div class="para">
+ To complete the key and certificate creation, take the following steps:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Review the target locations in which the key and certificate will be stored.
+ </div><div class="figure" title="Figure 11.1. Running the genkey utility" id="figure-apache-mod_ssl-genkey-01"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-01.png" alt="Running the genkey utility" /><div class="longdesc"><div class="para">
+ Running the <span class="application"><strong>genkey</strong></span> utility
+ </div></div></div></div><h6>Figure 11.1. Running the <span class="application">genkey</span> utility</h6></div><br class="figure-break" /><div class="para">
+ Use the <span class="keycap"><strong>Tab</strong></span> key to select the <span class="guibutton"><strong>Next</strong></span> button, and press <span class="keycap"><strong>Enter</strong></span> to proceed to the next screen.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Using the <span class="keycap"><strong>Up</strong></span> and <span class="keycap"><strong>down</strong></span> arrow keys, select the suitable key size. Note that while the large key increases the security, it also increases the response time of your server. Because of this, the recommended option is <code class="literal">1024 bits</code>.
+ </div><div class="figure" title="Figure 11.2. Selecting the key size" id="figure-apache-mod_ssl-genkey-02"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-02.png" alt="Selecting the key size" /><div class="longdesc"><div class="para">
+ Selecting the key size
+ </div></div></div></div><h6>Figure 11.2. Selecting the key size</h6></div><br class="figure-break" /><div class="para">
+ Once finished, use the <span class="keycap"><strong>Tab</strong></span> key to select the <span class="guibutton"><strong>Next</strong></span> button, and press <span class="keycap"><strong>Enter</strong></span> to initiate the random bits generation process. Depending on the selected key size, this may take some time.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Decide whether you wish to send a certificate request to a certificate authority.
+ </div><div class="figure" title="Figure 11.3. Generating a certificate request" id="figure-apache-mod_ssl-genkey-03"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-03.png" alt="Generating a certificate request" /><div class="longdesc"><div class="para">
+ Generating a certificate request
+ </div></div></div></div><h6>Figure 11.3. Generating a certificate request</h6></div><br class="figure-break" /><div class="para">
+ Use the <span class="keycap"><strong>Tab</strong></span> key to select <span class="guibutton"><strong>Yes</strong></span> to compose a certificate request, or <span class="guibutton"><strong>No</strong></span> to generate a self-signed certificate. Then press <span class="keycap"><strong>Enter</strong></span> to confirm your choice.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ Using the <span class="keycap"><strong>Spacebar</strong></span> key, enable (<code class="literal">[*]</code>) or disable (<code class="literal">[ ]</code>) the encryption of the private key.
+ </div><div class="figure" title="Figure 11.4. Encrypting the private key" id="figure-apache-mod_ssl-genkey-04"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-04.png" alt="Encrypting the private key" /><div class="longdesc"><div class="para">
+ Encrypting the private key
+ </div></div></div></div><h6>Figure 11.4. Encrypting the private key</h6></div><br class="figure-break" /><div class="para">
+ Use the <span class="keycap"><strong>Tab</strong></span> key to select the <span class="guibutton"><strong>Next</strong></span> button, and press <span class="keycap"><strong>Enter</strong></span> to proceed to the next screen.
+ </div></li><li class="step" title="Step 5"><div class="para">
+ If you have enabled the private key encryption, enter an adequate passphrase. Note that for security reasons, it is not displayed as you type, and it must be at least five characters long.
+ </div><div class="figure" title="Figure 11.5. Entering a passphrase" id="figure-apache-mod_ssl-genkey-05"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-05.png" alt="Entering a passphrase" /><div class="longdesc"><div class="para">
+ Entering a passphrase
+ </div></div></div></div><h6>Figure 11.5. Entering a passphrase</h6></div><br class="figure-break" /><div class="para">
+ Use the <span class="keycap"><strong>Tab</strong></span> key to select the <span class="guibutton"><strong>Next</strong></span> button, and press <span class="keycap"><strong>Enter</strong></span> to proceed to the next screen.
+ </div><div class="important" title="Important: Do Not Forget the Passphrase"><div class="admonition_header"><h2>Important: Do Not Forget the Passphrase</h2></div><div class="admonition"><div class="para">
+ Entering the correct passphrase is required in order for the server to start. If you lose it, you will need to generate a new key and certificate.
+ </div></div></div></li><li class="step" title="Step 6"><div class="para">
+ Customize the certificate details.
+ </div><div class="figure" title="Figure 11.6. Specifying certificate information" id="figure-apache-mod_ssl-genkey-06"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-06.png" alt="Specifying certificate information" /><div class="longdesc"><div class="para">
+ Specifying certificate information
+ </div></div></div></div><h6>Figure 11.6. Specifying certificate information</h6></div><br class="figure-break" /><div class="para">
+ Use the <span class="keycap"><strong>Tab</strong></span> key to select the <span class="guibutton"><strong>Next</strong></span> button, and press <span class="keycap"><strong>Enter</strong></span> to finish the key generation.
+ </div></li><li class="step" title="Step 7"><div class="para">
+ If you have previously enabled the certificate request generation, you will be prompted to send it to a certificate authority.
+ </div><div class="figure" title="Figure 11.7. Instructions on how to send a certificate request" id="figure-apache-mod_ssl-genkey-07"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-07.png" alt="Instructions on how to send a certificate request" /><div class="longdesc"><div class="para">
+ Instructions on how to send a certificate request
+ </div></div></div></div><h6>Figure 11.7. Instructions on how to send a certificate request</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to return to a shell prompt.
+ </div></li></ol></div><div class="para">
+ Once generated, add the key and certificate locations to the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> configuration file:
+ </div><pre class="screen">SSLCertificateFile /etc/pki/tls/certs/<em class="replaceable"><code>hostname</code></em>.crt
+SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostname</code></em>.key</pre><div class="para">
+ Finally, restart the <code class="systemitem">httpd</code> service as described in <a class="xref" href="#s3-apache-running-restarting" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a>, so that the updated configuration is loaded.
+ </div></div></div><div class="section" title="11.7. Additional Resources" id="s1-apache-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-resources">11.7. Additional Resources</h2></div></div></div><div class="para">
+ To learn more about the Apache HTTP Server, refer to the following resources.
+ </div><div class="section" title="11.7.1. Installed Documentation" id="s2-apache-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-resources-installed">11.7.1. Installed Documentation</h3></div></div></div><a id="id487387" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><a href="http://localhost/manual/">http://localhost/manual/</a></span></dt><dd><div class="para">
+ The official documentation for the Apache HTTP Server with the full description of its directives and available modules. Note that in order to access this documentation, you must have the <span class="package">httpd-manual</span> package installed, and the web server must be running.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man httpd</code></span></dt><dd><div class="para">
+ The manual page for the <code class="systemitem">httpd</code> service containing the complete list of its command line options.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man genkey</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">genkey</code> containing the full documentation on its usage.
+ </div></dd></dl></div></div><div class="section" title="11.7.2. Useful Websites" id="s2-apache-resources-web"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-resources-web">11.7.2. Useful Websites</h3></div></div></div><a id="id740077" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><a href="http://httpd.apache.org/">http://httpd.apache.org/</a></span></dt><dd><div class="para">
+ The official website for the Apache HTTP Server with documentation on all the directives and default modules.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.modssl.org/">http://www.modssl.org/</a></span></dt><dd><div class="para">
+ The official website for the <span class="application"><strong>mod_ssl</strong></span> module.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.openssl.org/">http://www.openssl.org/</a></span></dt><dd><div class="para">
+ The OpenSSL home page containing further documentation, frequently asked questions, links to the mailing lists, and other useful resources.
+ </div></dd></dl></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 12. Email" id="ch-email" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 12. Email</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-email-protocols">12.1. Email Protocols</a></span></dt><dt><span class="section"><a href="#s1-email-types">12.2. Email Program Classifications</a></span></dt><dt><span class="section"><a href="#s1-email-mta">12.3. Mail Transport Agents</a></span></dt><dt><span class="section"><a href="#s1-email-mda">12.4. Mail Delivery Agents</a></span></dt><dt><span class="section"><a href="#s1-email-mua">12.5. Mail User Agents</a></span></dt><dt><span class="section"><a href="#s1-email-additional-resources">12.6. Additional Resources</a></span></dt></dl></div><a id="id744292" class="indexterm"></a><div class="para">
+ <em class="firstterm">Email</em> was born in the 1960s. The mailbox was a file in a user's home directory that was readable only by that user. Primitive mail applications appended new text messages to the bottom of the file, making the user wade through the constantly growing file to find any particular message. This system was only capable of sending messages to users on the same system.
+ </div><div class="para">
+ The first network transfer of an electronic mail message file took place in 1971 when a computer engineer named Ray Tomlinson sent a test message between two machines via ARPANET—the precursor to the Internet. Communication via email soon became very popular, comprising 75 percent of ARPANET's traffic in less than two years.
+ </div><div class="para">
+ Today, email systems based on standardized network protocols have evolved into some of the most widely used services on the Internet. Fedora offers many advanced applications to serve and access email.
+ </div><div class="para">
+ This chapter reviews modern email protocols in use today, and some of the programs designed to send and receive email.
+ </div><div class="section" title="12.1. Email Protocols" id="s1-email-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-protocols">12.1. Email Protocols</h2></div></div></div><a id="id490671" class="indexterm"></a><div class="para">
+ Today, email is delivered using a client/server architecture. An email message is created using a mail client program. This program then sends the message to a server. The server then forwards the message to the recipient's email server, where the message is then supplied to the recipient's email client.
+ </div><div class="para">
+ To enable this process, a variety of standard network protocols allow different machines, often running different operating systems and using different email programs, to send and receive email.
+ </div><div class="para">
+ The following protocols discussed are the most commonly used in the transfer of email.
+ </div><div class="section" title="12.1.1. Mail Transport Protocols" id="s2-email-protocols-send"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-protocols-send">12.1.1. Mail Transport Protocols</h3></div></div></div><div class="para">
+ Mail delivery from a client application to the server, and from an originating server to the destination server, is handled by the <em class="firstterm">Simple Mail Transfer Protocol</em> (<em class="firstterm">SMTP</em>).
+ </div><div class="section" title="12.1.1.1. SMTP" id="s3-email-protocols-smtp"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-protocols-smtp">12.1.1.1. SMTP</h4></div></div></div><a id="id797605" class="indexterm"></a><div class="para">
+ The primary purpose of SMTP is to transfer email between mail servers. However, it is critical for email clients as well. To send email, the client sends the message to an outgoing mail server, which in turn contacts the destination mail server for delivery. For this reason, it is necessary to specify an SMTP server when configuring an email client.
+ </div><div class="para">
+ Under Fedora, a user can configure an SMTP server on the local machine to handle mail delivery. However, it is also possible to configure remote SMTP servers for outgoing mail.
+ </div><div class="para">
+ One important point to make about the SMTP protocol is that it does not require authentication. This allows anyone on the Internet to send email to anyone else or even to large groups of people. It is this characteristic of SMTP that makes junk email or <em class="firstterm">spam</em> possible. Imposing relay restrictions limits random users on the Internet from sending email through your SMTP server, to other servers on the internet. Servers that do not impose such restrictions are called <em class="firstterm">open relay</em> servers.
+ </div><div class="para">
+ Fedora provides the Postfix and Sendmail SMTP programs.
+ </div></div></div><div class="section" title="12.1.2. Mail Access Protocols" id="s2-email-protocols-client"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-protocols-client">12.1.2. Mail Access Protocols</h3></div></div></div><div class="para">
+ There are two primary protocols used by email client applications to retrieve email from mail servers: the <em class="firstterm">Post Office Protocol</em> (<em class="firstterm">POP</em>) and the <em class="firstterm">Internet Message Access Protocol</em> (<em class="firstterm">IMAP</em>).
+ </div><div class="section" title="12.1.2.1. POP" id="s3-email-protocols-pop"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-protocols-pop">12.1.2.1. POP</h4></div></div></div><a id="id537657" class="indexterm"></a><div class="para">
+ The default POP server under Fedora is <span class="application"><strong>Dovecot</strong></span> and is provided by the <span class="package">dovecot</span> package.
+ </div><div class="note" title="Note: Installing the dovecot package"><div class="admonition_header"><h2>Note: Installing the <span class="package">dovecot</span> package</h2></div><div class="admonition"><div class="para">
+ In order to use <span class="application"><strong>Dovecot</strong></span>, first ensure the <code class="command">dovecot</code> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install dovecot</code>
+</pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ When using a <code class="systemitem">POP</code> server, email messages are downloaded by email client applications. By default, most <code class="systemitem">POP</code> email clients are automatically configured to delete the message on the email server after it has been successfully transferred, however this setting usually can be changed.
+ </div><div class="para">
+ <code class="systemitem">POP</code> is fully compatible with important Internet messaging standards, such as <em class="firstterm">Multipurpose Internet Mail Extensions</em> (<em class="firstterm">MIME</em>), which allow for email attachments.
+ </div><div class="para">
+ <code class="systemitem">POP</code> works best for users who have one system on which to read email. It also works well for users who do not have a persistent connection to the Internet or the network containing the mail server. Unfortunately for those with slow network connections, <code class="systemitem">POP</code> requires client programs upon authentication to download the entire content of each message. This can take a long time if any messages have large attachments.
+ </div><div class="para">
+ The most current version of the standard <code class="systemitem">POP</code> protocol is <code class="systemitem">POP3</code>.
+ </div><div class="para">
+ There are, however, a variety of lesser-used <code class="systemitem">POP</code> protocol variants:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>APOP</em></span> — <code class="systemitem">POP3</code> with <code class="systemitem">MDS</code> (Monash Directory Service) authentication. An encoded hash of the user's password is sent from the email client to the server rather then sending an unencrypted password.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>KPOP</em></span> — <code class="systemitem">POP3</code> with Kerberos authentication.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>RPOP</em></span> — <code class="systemitem">POP3</code> with <code class="systemitem">RPOP</code> authentication. This uses a per-user ID, similar to a password, to authenticate POP requests. However, this ID is not encrypted, so <code class="systemitem">RPOP</code> is no more secure than standard <code class="systemitem">POP</code>.
+ </div></li></ul></div><div class="para">
+ For added security, it is possible to use <em class="firstterm">Secure Socket Layer</em> (<em class="firstterm">SSL</em>) encryption for client authentication and data transfer sessions. This can be enabled by using the <code class="command">pop3s</code> service, or by using the <code class="command">/usr/sbin/stunnel</code> application. For more information on securing email communication, refer to <a class="xref" href="#s2-email-security" title="12.5.1. Securing Communication">Section 12.5.1, “Securing Communication”</a>.
+ </div></div><div class="section" title="12.1.2.2. IMAP" id="s3-email-protocols-imap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-protocols-imap">12.1.2.2. IMAP</h4></div></div></div><a id="id785189" class="indexterm"></a><div class="para">
+ The default <code class="systemitem">IMAP</code> server under Fedora is <span class="application"><strong>Dovecot</strong></span> and is provided by the <span class="package">dovecot</span> package. Refer to <a class="xref" href="#s3-email-protocols-pop" title="12.1.2.1. POP">Section 12.1.2.1, “POP”</a> for information on how to install <span class="application"><strong>Dovecot</strong></span>.
+ </div><div class="para">
+ When using an <code class="systemitem">IMAP</code> mail server, email messages remain on the server where users can read or delete them. <code class="systemitem">IMAP</code> also allows client applications to create, rename, or delete mail directories on the server to organize and store email.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code> is particularly useful for users who access their email using multiple machines. The protocol is also convenient for users connecting to the mail server via a slow connection, because only the email header information is downloaded for messages until opened, saving bandwidth. The user also has the ability to delete messages without viewing or downloading them.
+ </div><div class="para">
+ For convenience, <code class="systemitem">IMAP</code> client applications are capable of caching copies of messages locally, so the user can browse previously read messages when not directly connected to the <code class="systemitem">IMAP</code> server.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code>, like <code class="systemitem">POP</code>, is fully compatible with important Internet messaging standards, such as MIME, which allow for email attachments.
+ </div><div class="para">
+ For added security, it is possible to use <code class="systemitem">SSL</code> encryption for client authentication and data transfer sessions. This can be enabled by using the <code class="command">imaps</code> service, or by using the <code class="command">/usr/sbin/stunnel</code> program. For more information on securing email communication, refer to <a class="xref" href="#s2-email-security" title="12.5.1. Securing Communication">Section 12.5.1, “Securing Communication”</a>.
+ </div><div class="para">
+ Other free, as well as commercial, IMAP clients and servers are available, many of which extend the IMAP protocol and provide additional functionality.
+ </div></div><div class="section" title="12.1.2.3. Dovecot" id="s3-mail-server-dovecot"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-mail-server-dovecot">12.1.2.3. Dovecot</h4></div></div></div><a id="id516910" class="indexterm"></a><div class="para">
+ The <code class="command">imap-login</code> and <code class="command">pop3-login</code> processes which implement the <code class="systemitem">IMAP</code> and <code class="systemitem">POP3</code> protocols are spawned by the master <code class="systemitem">dovecot</code> daemon included in the <span class="package">dovecot</span> package. The use of <code class="systemitem">IMAP</code> and <code class="systemitem">POP</code> is configured through the <code class="filename">/etc/dovecot/dovecot.conf</code> configuration file; by default <code class="command">dovecot</code> runs <code class="systemitem">IMAP</code> and <code class="systemitem">POP3</code> together with their secure versions using <code class="systemitem">SSL</code>. To configure <code class="command">dovecot</code> to use <code class="systemitem">POP</code>, complete the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/dovecot/dovecot.conf</code> configuration file to make sure the <code class="literal">protocols</code> variable is uncommented (remove the hash sign (<code class="command">#</code>) at the beginning of the line) and contains the <code class="literal">pop3</code> argument. For example:
+ </div><pre class="screen">protocols = imap imaps pop3 pop3s
+</pre><div class="para">
+ When the <code class="literal">protocols</code> variable is left commented out, <code class="command">dovecot</code> will use the default values specified for this variable.
+ </div></li><li class="listitem"><div class="para">
+ Make that change operational for the current session by running the following command:
+ </div><pre class="screen">~]# <code class="command">service dovecot restart</code>
+</pre></li><li class="listitem"><div class="para">
+ Make that change operational after the next reboot by running the command:
+ </div><pre class="screen">~]# <code class="command">chkconfig dovecot on</code>
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Please note that <code class="command">dovecot</code> only reports that it started the <code class="systemitem">IMAP</code> server, but also starts the <code class="systemitem">POP3</code> server.
+ </div></div></div></li></ol></div><div class="para">
+ Unlike <code class="systemitem">SMTP</code>, both <code class="systemitem">IMAP</code> and <code class="systemitem">POP3</code> require connecting clients to authenticate using a username and password. By default, passwords for both protocols are passed over the network unencrypted.
+ </div><div class="para">
+ To configure <code class="systemitem">SSL</code> on <code class="command">dovecot</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/pki/dovecot/dovecot-openssl.conf</code> configuration file as you prefer. However, in a typical installation, this file does not require modification.
+ </div></li><li class="listitem"><div class="para">
+ Rename, move or delete the files <code class="filename">/etc/pki/dovecot/certs/dovecot.pem</code> and <code class="filename">/etc/pki/dovecot/private/dovecot.pem</code>.
+ </div></li><li class="listitem"><div class="para">
+ Execute the <code class="filename">/usr/libexec/dovecot/mkcert.sh</code> script which creates the <code class="command">dovecot</code> self signed certificates. These certificates are copied in the <code class="filename">/etc/pki/dovecot/certs</code> and <code class="filename">/etc/pki/dovecot/private</code> directories. To implement the changes, restart <code class="command">dovecot</code>:
+ </div><pre class="screen">~]# <code class="command">service dovecot restart</code>
+</pre></li></ul></div><div class="para">
+ More details on <code class="command">dovecot</code> can be found online at <a href="http://www.dovecot.org">http://www.dovecot.org</a>.
+ </div></div></div></div><div class="section" title="12.2. Email Program Classifications" id="s1-email-types"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-types">12.2. Email Program Classifications</h2></div></div></div><a id="id506453" class="indexterm"></a><div class="para">
+ In general, all email applications fall into at least one of three classifications. Each classification plays a specific role in the process of moving and managing email messages. While most users are only aware of the specific email program they use to receive and send messages, each one is important for ensuring that email arrives at the correct destination.
+ </div><div class="section" title="12.2.1. Mail Transport Agent" id="s2-email-types-mta"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-types-mta">12.2.1. Mail Transport Agent</h3></div></div></div><a id="id766477" class="indexterm"></a><a id="id766496" class="indexterm"></a><a id="id652694" class="indexterm"></a><div class="para">
+ A <em class="firstterm">Mail Transport Agent</em> (<em class="firstterm">MTA</em>) transports email messages between hosts using <code class="systemitem">SMTP</code>. A message may involve several MTAs as it moves to its intended destination.
+ </div><div class="para">
+ While the delivery of messages between machines may seem rather straightforward, the entire process of deciding if a particular MTA can or should accept a message for delivery is quite complicated. In addition, due to problems from spam, use of a particular MTA is usually restricted by the MTA's configuration or the access configuration for the network on which the MTA resides.
+ </div><div class="para">
+ Many modern email client programs can act as an MTA when sending email. However, this action should not be confused with the role of a true MTA. The sole reason email client programs are capable of sending email like an MTA is because the host running the application does not have its own MTA. This is particularly true for email client programs on non-UNIX-based operating systems. However, these client programs only send outbound messages to an MTA they are authorized to use and do not directly deliver the message to the intended recipient's email server.
+ </div><div class="para">
+ Since Fedora offers two MTAs—<em class="firstterm">Postfix</em> and <em class="firstterm">Sendmail</em>—email client programs are often not required to act as an MTA. Fedora also includes a special purpose MTA called <em class="firstterm">Fetchmail</em>.
+ </div><div class="para">
+ For more information on Postfix, Sendmail, and Fetchmail, refer to <a class="xref" href="#s1-email-mta" title="12.3. Mail Transport Agents">Section 12.3, “Mail Transport Agents”</a>.
+ </div></div><div class="section" title="12.2.2. Mail Delivery Agent" id="s2-email-types-mda"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-types-mda">12.2.2. Mail Delivery Agent</h3></div></div></div><a id="id555369" class="indexterm"></a><a id="id2327392" class="indexterm"></a><a id="id2327406" class="indexterm"></a><div class="para">
+ A <em class="firstterm">Mail Delivery Agent</em> (<em class="firstterm">MDA</em>) is invoked by the MTA to file incoming email in the proper user's mailbox. In many cases, the MDA is actually a <em class="firstterm">Local Delivery Agent</em> (<em class="firstterm">LDA</em>), such as <code class="command">mail</code> or Procmail.
+ </div><div class="para">
+ Any program that actually handles a message for delivery to the point where it can be read by an email client application can be considered an MDA. For this reason, some MTAs (such as Sendmail and Postfix) can fill the role of an MDA when they append new email messages to a local user's mail spool file. In general, MDAs do not transport messages between systems nor do they provide a user interface; MDAs distribute and sort messages on the local machine for an email client application to access.
+ </div></div><div class="section" title="12.2.3. Mail User Agent" id="s2-email-types-mua"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-types-mua">12.2.3. Mail User Agent</h3></div></div></div><a id="id713733" class="indexterm"></a><a id="id713751" class="indexterm"></a><a id="id713766" class="indexterm"></a><div class="para">
+ A <em class="firstterm">Mail User Agent</em> (<em class="firstterm">MUA</em>) is synonymous with an email client application. An MUA is a program that, at the very least, allows a user to read and compose email messages. Many MUAs are capable of retrieving messages via the <code class="systemitem">POP</code> or <code class="systemitem">IMAP</code> protocols, setting up mailboxes to store messages, and sending outbound messages to an MTA.
+ </div><div class="para">
+ MUAs may be graphical, such as <span class="application"><strong>Evolution</strong></span>, or have simple text-based interfaces, such as <span class="application"><strong>pine</strong></span>.
+ </div></div></div><div class="section" title="12.3. Mail Transport Agents" id="s1-email-mta"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-mta">12.3. Mail Transport Agents</h2></div></div></div><div class="para">
+ Fedora offers two primary MTAs: Postfix and Sendmail. Postfix is configured as the default MTA, although it is easy to switch the default MTA to Sendmail. To switch the default MTA to Sendmail, you can either uninstall Postfix or use the following command to switch to Sendmail:
+ </div><pre class="screen">
+<code class="command">~]# alternatives --config mta</code>
+</pre><div class="para">
+ You can also use the following command to to enable/disable the desired service:
+ </div><pre class="screen">~]# <code class="command">chkconfig <em class="replaceable"><code><service></code></em> <em class="replaceable"><code><on/off></code></em></code>
+</pre><div class="section" title="12.3.1. Postfix" id="s2-email-mta-postfix"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-mta-postfix">12.3.1. Postfix</h3></div></div></div><a id="id971079" class="indexterm"></a><a id="id971094" class="indexterm"></a><div class="para">
+ Originally developed at IBM by security expert and programmer Wietse Venema, Postfix is a Sendmail-compatible MTA that is designed to be secure, fast, and easy to configure.
+ </div><div class="para">
+ To improve security, Postfix uses a modular design, where small processes with limited privileges are launched by a <em class="firstterm">master</em> daemon. The smaller, less privileged processes perform very specific tasks related to the various stages of mail delivery and run in a change rooted environment to limit the effects of attacks.
+ </div><div class="para">
+ Configuring Postfix to accept network connections from hosts other than the local computer takes only a few minor changes in its configuration file. Yet for those with more complex needs, Postfix provides a variety of configuration options, as well as third party add ons that make it a very versatile and full-featured MTA.
+ </div><div class="para">
+ The configuration files for Postfix are human readable and support upward of 250 directives. Unlike Sendmail, no macro processing is required for changes to take effect and the majority of the most commonly used options are described in the heavily commented files.
+ </div><div class="section" title="12.3.1.1. The Default Postfix Installation" id="s3-email-mta-postfix-default"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-postfix-default">12.3.1.1. The Default Postfix Installation</h4></div></div></div><a id="id448396" class="indexterm"></a><div class="para">
+ The Postfix executable is <code class="filename">/usr/sbin/postfix</code>. This daemon launches all related processes needed to handle mail delivery.
+ </div><div class="para">
+ Postfix stores its configuration files in the <code class="filename">/etc/postfix/</code> directory. The following is a list of the more commonly used files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">access</code> — Used for access control, this file specifies which hosts are allowed to connect to Postfix.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">main.cf</code> — The global Postfix configuration file. The majority of configuration options are specified in this file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">master.cf</code> — Specifies how Postfix interacts with various processes to accomplish mail delivery.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">transport</code> — Maps email addresses to relay hosts.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">aliases</code> file can be found in the <code class="filename">/etc/</code> directory. This file is shared between Postfix and Sendmail. It is a configurable list required by the mail protocol that describes user ID aliases.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The default <code class="filename">/etc/postfix/main.cf</code> file does not allow Postfix to accept network connections from a host other than the local computer. For instructions on configuring Postfix as a server for other clients, refer to <a class="xref" href="#s3-email-mta-postfix-conf" title="12.3.1.2. Basic Postfix Configuration">Section 12.3.1.2, “Basic Postfix Configuration”</a>.
+ </div></div></div><div class="para">
+ Restart the <code class="systemitem">postfix</code> service after changing any options in the configuration files under the <code class="filename">/etc/postfix</code> directory in order for those changes to take effect:
+<pre class="screen">~]# <code class="command">service postfix restart</code>
+</pre>
+
+ </div></div><div class="section" title="12.3.1.2. Basic Postfix Configuration" id="s3-email-mta-postfix-conf"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-postfix-conf">12.3.1.2. Basic Postfix Configuration</h4></div></div></div><div class="para">
+ By default, Postfix does not accept network connections from any host other than the local host. Perform the following steps as root to enable mail delivery for other hosts on the network:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/postfix/main.cf</code> file with a text editor, such as <code class="command">vi</code>.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">mydomain</code> line by removing the hash sign (<code class="command">#</code>), and replace <em class="replaceable"><code>domain.tld</code></em> with the domain the mail server is servicing, such as <code class="command">example.com</code>.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">myorigin = $mydomain</code> line.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">myhostname</code> line, and replace <em class="replaceable"><code>host.domain.tld</code></em> with the hostname for the machine.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">mydestination = $myhostname, localhost.$mydomain</code> line.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">mynetworks</code> line, and replace <em class="replaceable"><code>168.100.189.0/28</code></em> with a valid network setting for hosts that can connect to the server.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">inet_interfaces = all</code> line.
+ </div></li><li class="listitem"><div class="para">
+ Comment the <code class="command">inet_interfaces = localhost</code> line.
+ </div></li><li class="listitem"><div class="para">
+ Restart the <code class="command">postfix</code> service.
+ </div></li></ul></div><div class="para">
+ Once these steps are complete, the host accepts outside emails for delivery.
+ </div><div class="para">
+ Postfix has a large assortment of configuration options. One of the best ways to learn how to configure Postfix is to read the comments within the <code class="filename">/etc/postfix/main.cf</code> configuration file. Additional resources including information about Postfix configuration, SpamAssassin integration, or detailed descriptions of the <code class="filename">/etc/postfix/main.cf</code> parameters are available online at <a href="http://www.postfix.org/">http://www.postfix.org/</a>.
+ </div></div><div class="section" title="12.3.1.3. Using Postfix with LDAP" id="using-postfix-with-ldap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="using-postfix-with-ldap">12.3.1.3. Using Postfix with LDAP</h4></div></div></div><div class="para">
+ Postfix can use an <code class="systemitem">LDAP</code> directory as a source for various lookup tables (e.g.: <code class="filename">aliases</code>, <code class="filename">virtual</code>, <code class="filename">canonical</code>, etc.). This allows <code class="systemitem">LDAP</code> to store hierarchical user information and Postfix to only be given the result of <code class="systemitem">LDAP</code> queries when needed. By not storing this information locally, administrators can easily maintain it.
+ </div><div class="section" title="12.3.1.3.1. The /etc/aliases lookup example" id="aliases-example"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="aliases-example">12.3.1.3.1. <code class="filename">The /etc/aliases</code> lookup example</h5></div></div></div><div class="para">
+ The following is a basic example for using <code class="systemitem">LDAP</code> to look up the <code class="filename">/etc/aliases</code> file. Make sure your <code class="filename">/etc/postfix/main.cf</code> contains the following:
+ </div><pre class="screen">
+alias_maps = hash:/etc/aliases, ldap:/etc/postfix/ldap-aliases.cf
+</pre><div class="para">
+ Create a <code class="filename">/etc/postfix/ldap-aliases.cf</code> file if you do not have one created already and make sure it contains the following:
+ </div><pre class="screen">
+server_host = <em class="replaceable"><code>ldap.example.com</code></em>
+search_base = dc=<em class="replaceable"><code>example</code></em>, dc=<em class="replaceable"><code>com</code></em>
+</pre><div class="para">
+ where <em class="parameter"><code>ldap.example.com</code></em>, <em class="parameter"><code>example</code></em>, and <em class="parameter"><code>com</code></em> are parameters that need to be replaced with specification of an existing available <code class="systemitem">LDAP</code> server.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The /<code class="filename">etc/postfix/ldap-aliases.cf</code> file can specify various parameters, including parameters that enable <code class="systemitem">LDAP</code> <code class="systemitem">SSL</code> and <code class="systemitem">STARTTLS</code>. For more information, refer to the <code class="command">ldap_table(5)</code> man page.
+ </div></div></div></div></div></div><div class="section" title="12.3.2. Sendmail" id="s2-email-mta-sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-mta-sendmail">12.3.2. Sendmail</h3></div></div></div><a id="id803476" class="indexterm"></a><a id="id803490" class="indexterm"></a><div class="para">
+ Sendmail's core purpose, like other MTAs, is to safely transfer email among hosts, usually using the <code class="systemitem">SMTP</code> protocol. However, Sendmail is highly configurable, allowing control over almost every aspect of how email is handled, including the protocol used. Many system administrators elect to use Sendmail as their MTA due to its power and scalability.
+ </div><div class="section" title="12.3.2.1. Purpose and Limitations" id="s3-email-mta-sendmail-purpose"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-sendmail-purpose">12.3.2.1. Purpose and Limitations</h4></div></div></div><a id="id500480" class="indexterm"></a><a id="id500495" class="indexterm"></a><div class="para">
+ It is important to be aware of what Sendmail is and what it can do, as opposed to what it is not. In these days of monolithic applications that fulfill multiple roles, Sendmail may seem like the only application needed to run an email server within an organization. Technically, this is true, as Sendmail can spool mail to each users' directory and deliver outbound mail for users. However, most users actually require much more than simple email delivery. Users usually want to interact with their email using an MUA, that uses <code class="systemitem">POP</code> or <code class="systemitem">IMAP</code>, to download their messages to their local machine. Or, they may prefer a Web interface to gain access to their mailbox. These other applications can work in conjunction with Sendmail, but they actually exist for different reasons and can operate separately from one another.
+ </div><div class="para">
+ It is beyond the scope of this section to go into all that Sendmail should or could be configured to do. With literally hundreds of different options and rule sets, entire volumes have been dedicated to helping explain everything that can be done and how to fix things that go wrong. Refer to the <a class="xref" href="#s1-email-additional-resources" title="12.6. Additional Resources">Section 12.6, “Additional Resources”</a> for a list of Sendmail resources.
+ </div><div class="para">
+ This section reviews the files installed with Sendmail by default and reviews basic configuration changes, including how to stop unwanted email (spam) and how to extend Sendmail with the <em class="firstterm">Lightweight Directory Access Protocol (LDAP)</em>.
+ </div></div><div class="section" title="12.3.2.2. The Default Sendmail Installation" id="s3-email-mta-sendmail-default"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-sendmail-default">12.3.2.2. The Default Sendmail Installation</h4></div></div></div><a id="id787582" class="indexterm"></a><div class="para">
+ In order to use Sendmail, first ensure the <span class="package">sendmail</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install sendmail</code></pre><div class="para">
+ In order to configure Sendmail, ensure the <span class="package">sendmail-cf</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install sendmail-cf</code></pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div><div class="para">
+ Before using Sendmail, the default MTA has to be switched from Postfix. For more information how to switch the default MTA refer to <a class="xref" href="#s1-email-mta" title="12.3. Mail Transport Agents">Section 12.3, “Mail Transport Agents”</a>.
+ </div><div class="para">
+ The Sendmail executable is <code class="filename">/usr/sbin/sendmail</code>.
+ </div><div class="para">
+ Sendmail's lengthy and detailed configuration file is <code class="filename">/etc/mail/sendmail.cf</code>. Avoid editing the <code class="filename">sendmail.cf</code> file directly. To make configuration changes to Sendmail, edit the <code class="filename">/etc/mail/sendmail.mc</code> file, back up the original <code class="filename">/etc/mail/sendmail.cf</code>, and use the following alternatives to generate a new configuration file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Use the included makefile in <code class="filename">/etc/mail/</code> (<code class="command">~]# make all -C /etc/mail/</code>) to create a new <code class="filename">/etc/mail/sendmail.cf</code> configuration file. All other generated files in <code class="filename">/etc/mail</code> (db files) will be regenerated if needed. The old makemap commands are still usable. The make command will automatically be used by <code class="command">service sendmail start | restart | reload</code>.
+ </div></li><li class="listitem"><div class="para">
+ Alternatively you may use the <code class="command">m4</code> macro processor to create a new <code class="filename">/etc/mail/sendmail.cf</code>. The <code class="command">m4</code> macro processor is not installed by default. Before using it to create <code class="filename">/etc/mail/sendmail.cf</code>, install the <span class="package">m4</span> package as root:
+ </div><pre class="screen">~]# <code class="command">yum install m4</code>
+</pre></li></ul></div><div class="para">
+ More information on configuring Sendmail can be found in <a class="xref" href="#s3-email-mta-sendmail-changes" title="12.3.2.3. Common Sendmail Configuration Changes">Section 12.3.2.3, “Common Sendmail Configuration Changes”</a>.
+ </div><div class="para">
+ Various Sendmail configuration files are installed in the <code class="filename">/etc/mail/</code> directory including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">access</code> — Specifies which systems can use Sendmail for outbound email.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">domaintable</code> — Specifies domain name mapping.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">local-host-names</code> — Specifies aliases for the host.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">mailertable</code> — Specifies instructions that override routing for particular domains.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">virtusertable</code> — Specifies a domain-specific form of aliasing, allowing multiple virtual domains to be hosted on one machine.
+ </div></li></ul></div><div class="para">
+ Several of the configuration files in <code class="filename">/etc/mail/</code>, such as <code class="filename">access</code>, <code class="filename">domaintable</code>, <code class="filename">mailertable</code> and <code class="filename">virtusertable</code>, must actually store their information in database files before Sendmail can use any configuration changes. To include any changes made to these configurations in their database files, run the following command, as root:
+ </div><pre class="screen">~]# <code class="command">makemap hash /etc/mail/<em class="replaceable"><code><name></code></em> < /etc/mail/<em class="replaceable"><code><name></code></em></code>
+</pre><div class="para">
+ where <em class="replaceable"><code><name></code></em> represents the name of the configuration file to be updated. You may also restart the <code class="systemitem">sendmail</code> service for the changes to take effect by running:
+ </div><pre class="screen">~]# <code class="command">service sendmail restart</code>
+</pre><div class="para">
+ For example, to have all emails addressed to the <code class="filename">example.com</code> domain delivered to <code class="email"><a class="email" href="mailto:bob at other-example.com">bob at other-example.com</a></code>
+ , add the following line to the <code class="filename">virtusertable</code> file:
+ </div><pre class="screen">
+<code class="command">@example.com bob at other-example.com</code>
+</pre><div class="para">
+ To finalize the change, the <code class="filename">virtusertable.db</code> file must be updated:
+ </div><pre class="screen">~]# <code class="command">makemap hash /etc/mail/virtusertable < /etc/mail/virtusertable</code>
+</pre><div class="para">
+ Sendmail will create an updated <code class="filename">virtusertable.db</code> file containing the new configuration.
+ </div></div><div class="section" title="12.3.2.3. Common Sendmail Configuration Changes" id="s3-email-mta-sendmail-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-sendmail-changes">12.3.2.3. Common Sendmail Configuration Changes</h4></div></div></div><a id="id1768905" class="indexterm"></a><a id="id1768920" class="indexterm"></a><div class="para">
+ When altering the Sendmail configuration file, it is best not to edit an existing file, but to generate an entirely new <code class="filename">/etc/mail/sendmail.cf</code> file.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Before changing the <code class="filename">sendmail.cf</code> file, it is a good idea to create a backup copy.
+ </div></div></div><div class="para">
+ To add the desired functionality to Sendmail, edit the <code class="filename">/etc/mail/sendmail.mc</code> file as root. Once you are finished, restart the <code class="systemitem">sendmail</code> service and, if the <span class="package">m4</span> package is installed, the <code class="command">m4</code> macro processor will automatically generate a new <code class="filename">sendmail.cf</code> configuration file:
+ </div><pre class="screen">~]# <code class="command">service sendmail restart</code>
+</pre><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The default <code class="filename">sendmail.cf</code> file does not allow Sendmail to accept network connections from any host other than the local computer. To configure Sendmail as a server for other clients, edit the <code class="filename">/etc/mail/sendmail.mc</code> file, and either change the address specified in the <code class="command">Addr=</code> option of the <code class="command">DAEMON_OPTIONS</code> directive from <code class="command">127.0.0.1</code> to the IP address of an active network device or comment out the <code class="command">DAEMON_OPTIONS</code> directive all together by placing <code class="command">dnl</code> at the beginning of the line. When finished, regenerate <code class="filename">/etc/mail/sendmail.cf</code> by restarting the service
+ </div><pre class="screen">~]# <code class="command">service sendmail restart</code>
+</pre></div></div><div class="para">
+ The default configuration which ships with Fedora works for most <code class="systemitem">SMTP</code>-only sites. However, it does not work for <em class="firstterm">UUCP</em> (<em class="firstterm">UNIX-to-UNIX Copy Protocol</em>) sites. If using UUCP mail transfers, the <code class="filename">/etc/mail/sendmail.mc</code> file must be reconfigured and a new <code class="filename">/etc/mail/sendmail.cf</code> file must be generated.
+ </div><div class="para">
+ Consult the <code class="filename">/usr/share/sendmail-cf/README</code> file before editing any files in the directories under the <code class="filename">/usr/share/sendmail-cf</code> directory, as they can affect the future configuration of the <code class="filename">/etc/mail/sendmail.cf</code> file.
+ </div></div><div class="section" title="12.3.2.4. Masquerading" id="s3-email-sendmail-changes-masquerading"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-sendmail-changes-masquerading">12.3.2.4. Masquerading</h4></div></div></div><a id="id524346" class="indexterm"></a><a id="id524360" class="indexterm"></a><div class="para">
+ One common Sendmail configuration is to have a single machine act as a mail gateway for all machines on the network. For instance, a company may want to have a machine called <code class="computeroutput">mail.example.com</code> that handles all of their email and assigns a consistent return address to all outgoing mail.
+ </div><div class="para">
+ In this situation, the Sendmail server must masquerade the machine names on the company network so that their return address is <code class="computeroutput">user at example.com</code> instead of <code class="computeroutput">user at host.example.com</code>.
+ </div><div class="para">
+ To do this, add the following lines to <code class="filename">/etc/mail/sendmail.mc</code>:
+ </div><pre class="screen">
+FEATURE(always_add_domain)dnl
+FEATURE(`masquerade_entire_domain')dnl
+FEATURE(`masquerade_envelope')dnl
+FEATURE(`allmasquerade')dnl
+MASQUERADE_AS(`bigcorp.com.')dnl
+MASQUERADE_DOMAIN(`bigcorp.com.')dnl
+MASQUERADE_AS(bigcorp.com)dnl
+</pre><div class="para">
+ After generating a new <code class="filename">sendmail.cf</code> using the <code class="command">m4</code> macro processor, this configuration makes all mail from inside the network appear as if it were sent from <code class="computeroutput">bigcorp.com</code>.
+ </div></div><div class="section" title="12.3.2.5. Stopping Spam" id="s3-email-sendmail-stopping-spam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-sendmail-stopping-spam">12.3.2.5. Stopping Spam</h4></div></div></div><a id="id757673" class="indexterm"></a><div class="para">
+ Email spam can be defined as unnecessary and unwanted email received by a user who never requested the communication. It is a disruptive, costly, and widespread abuse of Internet communication standards.
+ </div><div class="para">
+ Sendmail makes it relatively easy to block new spamming techniques being employed to send junk email. It even blocks many of the more usual spamming methods by default. Main anti-spam features available in sendmail are <em class="firstterm">header checks</em>, <em class="firstterm">relaying denial</em> (default from version 8.9), <em class="firstterm">access database and sender information checks</em>.
+ </div><div class="para">
+ For example, forwarding of <code class="systemitem">SMTP</code> messages, also called relaying, has been disabled by default since Sendmail version 8.9. Before this change occurred, Sendmail directed the mail host (<code class="filename">x.edu</code>) to accept messages from one party (<code class="filename">y.com</code>) and sent them to a different party (<code class="filename">z.net</code>). Now, however, Sendmail must be configured to permit any domain to relay mail through the server. To configure relay domains, edit the <code class="filename">/etc/mail/relay-domains</code> file and restart Sendmail
+ </div><pre class="screen">~]# <code class="command">service sendmail restart</code>
+</pre><div class="para">
+ However, many times users are bombarded with spam from other servers throughout the Internet. In these instances, Sendmail's access control features available through the <code class="filename">/etc/mail/access</code> file can be used to prevent connections from unwanted hosts. The following example illustrates how this file can be used to both block and specifically allow access to the Sendmail server:
+ </div><pre class="screen">
+<code class="command">badspammer.com ERROR:550 "Go away and do not spam us anymore" tux.badspammer.com OK 10.0 RELAY</code>
+</pre><div class="para">
+ This example shows that any email sent from <code class="filename">badspammer.com</code> is blocked with a 550 RFC-821 compliant error code, with a message sent back to the spammer. Email sent from the <code class="filename">tux.badspammer.com</code> sub-domain, is accepted. The last line shows that any email sent from the 10.0.*.* network can be relayed through the mail server.
+ </div><div class="para">
+ Because the <code class="filename">/etc/mail/access.db</code> file is a database, use the <code class="command">makemap</code> command to update any changes. Do this using the following command as root:
+ </div><pre class="screen">~]# <code class="command">makemap hash /etc/mail/access < /etc/mail/access</code>
+</pre><div class="para">
+ Message header analysis allows you to reject mail based on header contents. <code class="systemitem">SMTP</code> servers store information about an email's journey in the message header. As the message travels from one MTA to another, each puts in a <code class="literal">Received</code> header above all the other <code class="literal">Received</code> headers. It is important to note that this information may be altered by spammers.
+ </div><div class="para">
+ The above examples only represent a small part of what Sendmail can do in terms of allowing or blocking access. Refer to the <code class="filename">/usr/share/sendmail-cf/README</code> for more information and examples.
+ </div><div class="para">
+ Since Sendmail calls the Procmail MDA when delivering mail, it is also possible to use a spam filtering program, such as SpamAssassin, to identify and file spam for users. Refer to <a class="xref" href="#s3-email-mda-spam" title="12.4.2.6. Spam Filters">Section 12.4.2.6, “Spam Filters”</a> for more information about using SpamAssassin.
+ </div></div><div class="section" title="12.3.2.6. Using Sendmail with LDAP" id="s3-email-mta-sendmail-ldap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-sendmail-ldap">12.3.2.6. Using Sendmail with LDAP</h4></div></div></div><a id="id508476" class="indexterm"></a><div class="para">
+ Using <code class="systemitem">LDAP</code> is a very quick and powerful way to find specific information about a particular user from a much larger group. For example, an <code class="systemitem">LDAP</code> server can be used to look up a particular email address from a common corporate directory by the user's last name. In this kind of implementation, <code class="systemitem">LDAP</code> is largely separate from Sendmail, with <code class="systemitem">LDAP</code> storing the hierarchical user information and Sendmail only being given the result of <code class="systemitem">LDAP</code> queries in pre-addressed email messages.
+ </div><div class="para">
+ However, Sendmail supports a much greater integration with <code class="systemitem">LDAP</code>, where it uses <code class="systemitem">LDAP</code> to replace separately maintained files, such as <code class="filename">/etc/aliases</code> and <code class="filename">/etc/mail/virtusertables</code>, on different mail servers that work together to support a medium- to enterprise-level organization. In short, <code class="systemitem">LDAP</code> abstracts the mail routing level from Sendmail and its separate configuration files to a powerful <code class="systemitem">LDAP</code> cluster that can be leveraged by many different applications.
+ </div><div class="para">
+ The current version of Sendmail contains support for <code class="systemitem">LDAP</code>. To extend the Sendmail server using <code class="systemitem">LDAP</code>, first get an <code class="systemitem">LDAP</code> server, such as <span class="application"><strong>OpenLDAP</strong></span>, running and properly configured. Then edit the <code class="filename">/etc/mail/sendmail.mc</code> to include the following:
+ </div><pre class="screen">LDAPROUTE_DOMAIN('<em class="replaceable"><code>yourdomain.com</code></em>')dnl
+FEATURE('ldap_routing')dnl
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This is only for a very basic configuration of Sendmail with <code class="systemitem">LDAP</code>. The configuration can differ greatly from this depending on the implementation of <code class="systemitem">LDAP</code>, especially when configuring several Sendmail machines to use a common <code class="systemitem">LDAP</code> server.
+ </div><div class="para">
+ Consult <code class="filename">/usr/share/sendmail-cf/README</code> for detailed <code class="systemitem">LDAP</code> routing configuration instructions and examples.
+ </div></div></div><div class="para">
+ Next, recreate the <code class="filename">/etc/mail/sendmail.cf</code> file by running the <code class="command">m4</code> macro processor and again restarting Sendmail. Refer to <a class="xref" href="#s3-email-mta-sendmail-changes" title="12.3.2.3. Common Sendmail Configuration Changes">Section 12.3.2.3, “Common Sendmail Configuration Changes”</a> for instructions.
+ </div></div></div><div class="section" title="12.3.3. Fetchmail" id="s2-email-mta-fetchmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-mta-fetchmail">12.3.3. Fetchmail</h3></div></div></div><a id="id522558" class="indexterm"></a><a id="id809035" class="indexterm"></a><div class="para">
+ Fetchmail is an MTA which retrieves email from remote servers and delivers it to the local MTA. Many users appreciate the ability to separate the process of downloading their messages located on a remote server from the process of reading and organizing their email in an MUA. Designed with the needs of dial-up users in mind, Fetchmail connects and quickly downloads all of the email messages to the mail spool file using any number of protocols, including <code class="systemitem">POP3</code> and <code class="systemitem">IMAP</code>. It can even forward email messages to an <code class="systemitem">SMTP</code> server, if necessary.
+ </div><div class="note" title="Note: Installing the fetchmail package"><div class="admonition_header"><h2>Note: Installing the <span class="package">fetchmail</span> package</h2></div><div class="admonition"><div class="para">
+ In order to use <span class="application"><strong>Fetchmail</strong></span>, first ensure the <span class="package">fetchmail</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install fetchmail</code></pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ Fetchmail is configured for each user through the use of a <code class="filename">.fetchmailrc</code> file in the user's home directory. If it does not already exist, create the <code class="filename">.fetchmailrc</code> file in your home directory
+ </div><div class="para">
+ Using preferences in the <code class="filename">.fetchmailrc</code> file, Fetchmail checks for email on a remote server and downloads it. It then delivers it to port <code class="constant">25</code> on the local machine, using the local MTA to place the email in the correct user's spool file. If Procmail is available, it is launched to filter the email and place it in a mailbox so that it can be read by an MUA.
+ </div><div class="section" title="12.3.3.1. Fetchmail Configuration Options" id="s3-email-mda-fetchmail-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-configuration">12.3.3.1. Fetchmail Configuration Options</h4></div></div></div><a id="id827600" class="indexterm"></a><a id="id827615" class="indexterm"></a><div class="para">
+ Although it is possible to pass all necessary options on the command line to check for email on a remote server when executing Fetchmail, using a <code class="filename">.fetchmailrc</code> file is much easier. Place any desired configuration options in the <code class="filename">.fetchmailrc</code> file for those options to be used each time the <code class="command">fetchmail</code> command is issued. It is possible to override these at the time Fetchmail is run by specifying that option on the command line.
+ </div><div class="para">
+ A user's <code class="filename">.fetchmailrc</code> file contains three classes of configuration options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>global options</em></span> — Gives Fetchmail instructions that control the operation of the program or provide settings for every connection that checks for email.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>server options</em></span> — Specifies necessary information about the server being polled, such as the hostname, as well as preferences for specific email servers, such as the port to check or number of seconds to wait before timing out. These options affect every user using that server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>user options</em></span> — Contains information, such as username and password, necessary to authenticate and check for email using a specified email server.
+ </div></li></ul></div><div class="para">
+ Global options appear at the top of the <code class="filename">.fetchmailrc</code> file, followed by one or more server options, each of which designate a different email server that Fetchmail should check. User options follow server options for each user account checking that email server. Like server options, multiple user options may be specified for use with a particular server as well as to check multiple email accounts on the same server.
+ </div><div class="para">
+ Server options are called into service in the <code class="filename">.fetchmailrc</code> file by the use of a special option verb, <code class="command">poll</code> or <code class="command">skip</code>, that precedes any of the server information. The <code class="command">poll</code> action tells Fetchmail to use this server option when it is run, which checks for email using the specified user options. Any server options after a <code class="command">skip</code> action, however, are not checked unless this server's hostname is specified when Fetchmail is invoked. The <code class="command">skip</code> option is useful when testing configurations in the <code class="filename">.fetchmailrc</code> file because it only checks skipped servers when specifically invoked, and does not affect any currently working configurations.
+ </div><div class="para">
+ The following is a sample example of a <code class="filename">.fetchmailrc</code> file:
+ </div><pre class="screen">set postmaster "user1"
+set bouncemail
+
+poll pop.domain.com proto pop3
+ user 'user1' there with password 'secret' is user1 here
+
+poll mail.domain2.com
+ user 'user5' there with password 'secret2' is user1 here
+ user 'user7' there with password 'secret3' is user1 here</pre><div class="para">
+ In this example, the global options specify that the user is sent email as a last resort (<code class="command">postmaster</code> option) and all email errors are sent to the postmaster instead of the sender (<code class="command">bouncemail</code> option). The <code class="command">set</code> action tells Fetchmail that this line contains a global option. Then, two email servers are specified, one set to check using <code class="systemitem">POP3</code>, the other for trying various protocols to find one that works. Two users are checked using the second server option, but all email found for any user is sent to <code class="command">user1</code>'s mail spool. This allows multiple mailboxes to be checked on multiple servers, while appearing in a single MUA inbox. Each user's specific information begins with the <code class="command">user</code> action.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Users are not required to place their password in the <code class="filename">.fetchmailrc</code> file. Omitting the <code class="command">with password '<password>'</code> section causes Fetchmail to ask for a password when it is launched.
+ </div></div></div><div class="para">
+ Fetchmail has numerous global, server, and local options. Many of these options are rarely used or only apply to very specific situations. The <code class="filename">fetchmail</code> man page explains each option in detail, but the most common ones are listed in the following three sections.
+ </div></div><div class="section" title="12.3.3.2. Global Options" id="s3-email-mda-fetchmail-configuration-global"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-configuration-global">12.3.3.2. Global Options</h4></div></div></div><a id="id805739" class="indexterm"></a><a id="id805758" class="indexterm"></a><div class="para">
+ Each global option should be placed on a single line after a <code class="command">set</code> action.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">daemon <em class="replaceable"><code><seconds></code></em> </code> — Specifies daemon-mode, where Fetchmail stays in the background. Replace <em class="replaceable"><code><seconds></code></em> with the number of seconds Fetchmail is to wait before polling the server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">postmaster</code> — Specifies a local user to send mail to in case of delivery problems.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">syslog</code> — Specifies the log file for errors and status messages. By default, this is <code class="filename">/var/log/maillog</code>.
+ </div></li></ul></div></div><div class="section" title="12.3.3.3. Server Options" id="s3-email-mda-fetchmail-configuration-server"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-configuration-server">12.3.3.3. Server Options</h4></div></div></div><a id="id861551" class="indexterm"></a><a id="id639349" class="indexterm"></a><div class="para">
+ Server options must be placed on their own line in <code class="filename">.fetchmailrc</code> after a <code class="command">poll</code> or <code class="command">skip</code> action.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">auth <em class="replaceable"><code><auth-type></code></em> </code> — Replace <em class="replaceable"><code><auth-type></code></em> with the type of authentication to be used. By default, <code class="command">password</code> authentication is used, but some protocols support other types of authentication, including <code class="command">kerberos_v5</code>, <code class="command">kerberos_v4</code>, and <code class="command">ssh</code>. If the <code class="command">any</code> authentication type is used, Fetchmail first tries methods that do not require a password, then methods that mask the password, and finally attempts to send the password unencrypted to authenticate to the server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">interval <em class="replaceable"><code><number></code></em> </code> — Polls the specified server every <code class="command"><em class="replaceable"><code><number></code></em> </code> of times that it checks for email on all configured servers. This option is generally used for email servers where the user rarely receives messages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">port <em class="replaceable"><code><port-number></code></em> </code> — Replace <em class="replaceable"><code><port-number></code></em> with the port number. This value overrides the default port number for the specified protocol.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">proto <em class="replaceable"><code><protocol></code></em> </code> — Replace <em class="replaceable"><code><protocol></code></em> with the protocol, such as <code class="command">pop3</code> or <code class="command">imap</code>, to use when checking for messages on the server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">timeout <em class="replaceable"><code><seconds></code></em> </code> — Replace <em class="replaceable"><code><seconds></code></em> with the number of seconds of server inactivity after which Fetchmail gives up on a connection attempt. If this value is not set, a default of <code class="command">300</code> seconds is assumed.
+ </div></li></ul></div></div><div class="section" title="12.3.3.4. User Options" id="s3-email-fetchmail-configuration-user"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-fetchmail-configuration-user">12.3.3.4. User Options</h4></div></div></div><a id="id1680928" class="indexterm"></a><a id="id1680946" class="indexterm"></a><div class="para">
+ User options may be placed on their own lines beneath a server option or on the same line as the server option. In either case, the defined options must follow the <code class="command">user</code> option (defined below).
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">fetchall</code> — Orders Fetchmail to download all messages in the queue, including messages that have already been viewed. By default, Fetchmail only pulls down new messages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">fetchlimit <em class="replaceable"><code><number></code></em> </code> — Replace <em class="replaceable"><code><number></code></em> with the number of messages to be retrieved before stopping.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">flush</code> — Deletes all previously viewed messages in the queue before retrieving new messages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">limit <em class="replaceable"><code><max-number-bytes></code></em> </code> — Replace <em class="replaceable"><code><max-number-bytes></code></em> with the maximum size in bytes that messages are allowed to be when retrieved by Fetchmail. This option is useful with slow network links, when a large message takes too long to download.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">password '<em class="replaceable"><code><password></code></em>'</code> — Replace <em class="replaceable"><code><password></code></em> with the user's password.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">preconnect "<em class="replaceable"><code><command></code></em>"</code> — Replace <em class="replaceable"><code><command></code></em> with a command to be executed before retrieving messages for the user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">postconnect "<em class="replaceable"><code><command></code></em>"</code> — Replace <em class="replaceable"><code><command></code></em> with a command to be executed after retrieving messages for the user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ssl</code> — Activates SSL encryption.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">user "<em class="replaceable"><code><username></code></em>"</code> — Replace <em class="replaceable"><code><username></code></em> with the username used by Fetchmail to retrieve messages. <span class="emphasis"><em>This option must precede all other user options.</em></span>
+ </div></li></ul></div></div><div class="section" title="12.3.3.5. Fetchmail Command Options" id="s3-email-mda-fetchmail-commands"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-commands">12.3.3.5. Fetchmail Command Options</h4></div></div></div><a id="id2231225" class="indexterm"></a><div class="para">
+ Most Fetchmail options used on the command line when executing the <code class="command">fetchmail</code> command mirror the <code class="filename">.fetchmailrc</code> configuration options. In this way, Fetchmail may be used with or without a configuration file. These options are not used on the command line by most users because it is easier to leave them in the <code class="filename">.fetchmailrc</code> file.
+ </div><div class="para">
+ There may be times when it is desirable to run the <code class="command">fetchmail</code> command with other options for a particular purpose. It is possible to issue command options to temporarily override a <code class="filename">.fetchmailrc</code> setting that is causing an error, as any options specified at the command line override configuration file options.
+ </div></div><div class="section" title="12.3.3.6. Informational or Debugging Options" id="s3-email-mda-fetchmail-commands-info"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-commands-info">12.3.3.6. Informational or Debugging Options</h4></div></div></div><a id="id831908" class="indexterm"></a><div class="para">
+ Certain options used after the <code class="command">fetchmail</code> command can supply important information.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">--configdump</code> — Displays every possible option based on information from <code class="filename">.fetchmailrc</code> and Fetchmail defaults. No email is retrieved for any users when using this option.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-s</code> — Executes Fetchmail in silent mode, preventing any messages, other than errors, from appearing after the <code class="command">fetchmail</code> command.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-v</code> — Executes Fetchmail in verbose mode, displaying every communication between Fetchmail and remote email servers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-V</code> — Displays detailed version information, lists its global options, and shows settings to be used with each user, including the email protocol and authentication method. No email is retrieved for any users when using this option.
+ </div></li></ul></div></div><div class="section" title="12.3.3.7. Special Options" id="s3-email-mda-fetchmail-commands-special"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-commands-special">12.3.3.7. Special Options</h4></div></div></div><a id="id620836" class="indexterm"></a><div class="para">
+ These options are occasionally useful for overriding defaults often found in the <code class="filename">.fetchmailrc</code> file.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-a</code> — Fetchmail downloads all messages from the remote email server, whether new or previously viewed. By default, Fetchmail only downloads new messages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-k</code> — Fetchmail leaves the messages on the remote email server after downloading them. This option overrides the default behavior of deleting messages after downloading them.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-l <em class="replaceable"><code><max-number-bytes></code></em> </code> — Fetchmail does not download any messages over a particular size and leaves them on the remote email server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">--quit</code> — Quits the Fetchmail daemon process.
+ </div></li></ul></div><div class="para">
+ More commands and <code class="filename">.fetchmailrc</code> options can be found in the <code class="command">fetchmail</code> man page.
+ </div></div></div><div class="section" title="12.3.4. Mail Transport Agent (MTA) Configuration" id="s2-email-switchmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-switchmail">12.3.4. Mail Transport Agent (MTA) Configuration</h3></div></div></div><a id="id720056" class="indexterm"></a><a id="id720071" class="indexterm"></a><a id="id493873" class="indexterm"></a><a id="id493891" class="indexterm"></a><a id="id820922" class="indexterm"></a><a id="id820933" class="indexterm"></a><div class="para">
+ A <em class="firstterm">Mail Transport Agent</em> (MTA) is essential for sending email. A <em class="firstterm">Mail User Agent</em> (MUA) such as <span class="application"><strong>Evolution</strong></span>, <span class="application"><strong>Thunderbird</strong></span>, and <span class="application"><strong>Mutt</strong></span>, is used to read and compose email. When a user sends an email from an MUA, the message is handed off to the MTA, which sends the message through a series of MTAs until it reaches its destination.
+ </div><div class="para">
+ Even if a user does not plan to send email from the system, some automated tasks or system programs might use the <code class="command">/bin/mail</code> command to send email containing log messages to the root user of the local system.
+ </div><a id="id724318" class="indexterm"></a><a id="id724329" class="indexterm"></a><div class="para">
+ Fedora 14 provides two MTAs: Postfix and Sendmail. If both are installed, Postfix is the default MTA.
+ </div></div></div><div class="section" title="12.4. Mail Delivery Agents" id="s1-email-mda"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-mda">12.4. Mail Delivery Agents</h2></div></div></div><div class="para">
+ Fedora includes two primary MDAs, Procmail and <code class="command">mail</code>. Both of the applications are considered LDAs and both move email from the MTA's spool file into the user's mailbox. However, Procmail provides a robust filtering system.
+ </div><div class="para">
+ This section details only Procmail. For information on the <code class="command">mail</code> command, consult its man page (<code class="command">man mail</code>).
+ </div><a id="id1043314" class="indexterm"></a><a id="id1043329" class="indexterm"></a><div class="para">
+ Procmail delivers and filters email as it is placed in the mail spool file of the localhost. It is powerful, gentle on system resources, and widely used. Procmail can play a critical role in delivering email to be read by email client applications.
+ </div><div class="para">
+ Procmail can be invoked in several different ways. Whenever an MTA places an email into the mail spool file, Procmail is launched. Procmail then filters and files the email for the MUA and quits. Alternatively, the MUA can be configured to execute Procmail any time a message is received so that messages are moved into their correct mailboxes. By default, the presence of <code class="filename">/etc/procmailrc</code> or of a <code class="filename">~/.procmailrc</code> file (also called an <em class="firstterm">rc</em> file) in the user's home directory invokes Procmail whenever an MTA receives a new message.
+ </div><div class="para">
+ By default, no system-wide <code class="filename">rc</code> files exist in the <code class="filename">/etc/</code> directory and no <code class="filename">.procmailrc</code> files exist in any user's home directory. Therefore, to use Procmail, each user must construct a <code class="filename">.procmailrc</code> file with specific environment variables and rules.
+ </div><div class="para">
+ Whether Procmail acts upon an email message depends upon whether the message matches a specified set of conditions or <em class="firstterm">recipes</em> in the <code class="filename">rc</code> file. If a message matches a recipe, then the email is placed in a specified file, is deleted, or is otherwise processed.
+ </div><div class="para">
+ When Procmail starts, it reads the email message and separates the body from the header information. Next, Procmail looks for a <code class="filename">/etc/procmailrc</code> file and <code class="filename">rc</code> files in the <code class="filename">/etc/procmailrcs</code> directory for default, system-wide, Procmail environmental variables and recipes. Procmail then searches for a <code class="filename">.procmailrc</code> file in the user's home directory. Many users also create additional <code class="filename">rc</code> files for Procmail that are referred to within the <code class="filename">.procmailrc</code> file in their home directory.
+ </div><div class="section" title="12.4.1. Procmail Configuration" id="s2-email-procmail-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-procmail-configuration">12.4.1. Procmail Configuration</h3></div></div></div><a id="id1687691" class="indexterm"></a><a id="id733927" class="indexterm"></a><div class="para">
+ The Procmail configuration file contains important environmental variables. These variables specify things such as which messages to sort and what to do with the messages that do not match any recipes.
+ </div><div class="para">
+ These environmental variables usually appear at the beginning of the <code class="filename">~/.procmailrc</code> file in the following format:
+ </div><pre class="screen">
+<em class="replaceable"><code><env-variable></code></em>="<em class="replaceable"><code><value></code></em>"
+</pre><div class="para">
+ In this example, <code class="command"><em class="replaceable"><code><env-variable></code></em> </code> is the name of the variable and <code class="command"><em class="replaceable"><code><value></code></em> </code> defines the variable.
+ </div><div class="para">
+ There are many environment variables not used by most Procmail users and many of the more important environment variables are already defined by a default value. Most of the time, the following variables are used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">DEFAULT</code> — Sets the default mailbox where messages that do not match any recipes are placed.
+ </div><div class="para">
+ The default <code class="command">DEFAULT</code> value is the same as <code class="command">$ORGMAIL</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">INCLUDERC</code> — Specifies additional <code class="filename">rc</code> files containing more recipes for messages to be checked against. This breaks up the Procmail recipe lists into individual files that fulfill different roles, such as blocking spam and managing email lists, that can then be turned off or on by using comment characters in the user's <code class="filename">~/.procmailrc</code> file.
+ </div><div class="para">
+ For example, lines in a user's <code class="filename">.procmailrc</code> file may look like this:
+ </div><pre class="screen">MAILDIR=$HOME/Msgs INCLUDERC=$MAILDIR/lists.rc INCLUDERC=$MAILDIR/spam.rc</pre><div class="para">
+ To turn off Procmail filtering of email lists but leaving spam control in place, comment out the first <code class="command">INCLUDERC</code> line with a hash sign (<code class="command">#</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">LOCKSLEEP</code> — Sets the amount of time, in seconds, between attempts by Procmail to use a particular lockfile. The default is <code class="constant">8</code> seconds.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">LOCKTIMEOUT</code> — Sets the amount of time, in seconds, that must pass after a lockfile was last modified before Procmail assumes that the lockfile is old and can be deleted. The default is <code class="constant">1024</code> seconds.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">LOGFILE</code> — The file to which any Procmail information or error messages are written.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MAILDIR</code> — Sets the current working directory for Procmail. If set, all other Procmail paths are relative to this directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ORGMAIL</code> — Specifies the original mailbox, or another place to put the messages if they cannot be placed in the default or recipe-required location.
+ </div><div class="para">
+ By default, a value of <code class="command">/var/spool/mail/$LOGNAME</code> is used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SUSPEND</code> — Sets the amount of time, in seconds, that Procmail pauses if a necessary resource, such as swap space, is not available.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SWITCHRC</code> — Allows a user to specify an external file containing additional Procmail recipes, much like the <code class="command">INCLUDERC</code> option, except that recipe checking is actually stopped on the referring configuration file and only the recipes on the <code class="command">SWITCHRC</code>-specified file are used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">VERBOSE</code> — Causes Procmail to log more information. This option is useful for debugging.
+ </div></li></ul></div><div class="para">
+ Other important environmental variables are pulled from the shell, such as <code class="command">LOGNAME</code>, which is the login name; <code class="command">HOME</code>, which is the location of the home directory; and <code class="command">SHELL</code>, which is the default shell.
+ </div><div class="para">
+ A comprehensive explanation of all environments variables, as well as their default values, is available in the <code class="filename">procmailrc</code> man page.
+ </div></div><div class="section" title="12.4.2. Procmail Recipes" id="s2-email-procmail-recipes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-procmail-recipes">12.4.2. Procmail Recipes</h3></div></div></div><a id="id570995" class="indexterm"></a><div class="para">
+ New users often find the construction of recipes the most difficult part of learning to use Procmail. To some extent, this is understandable, as recipes do their message matching using <em class="firstterm">regular expressions</em>, which is a particular format used to specify qualifications for a matching string. However, regular expressions are not very difficult to construct and even less difficult to understand when read. Additionally, the consistency of the way Procmail recipes are written, regardless of regular expressions, makes it easy to learn by example. To see example Procmail recipes, refer to <a class="xref" href="#s3-email-procmail-recipes-examples" title="12.4.2.5. Recipe Examples">Section 12.4.2.5, “Recipe Examples”</a>.
+ </div><div class="para">
+ Procmail recipes take the following form:
+ </div><pre class="screen">:0<em class="replaceable"><code><flags>: <lockfile-name></code></em> * <em class="replaceable"><code><special-condition-character></code></em>
+ <em class="replaceable"><code><condition-1></code></em> * <em class="replaceable"><code><special-condition-character></code></em>
+ <em class="replaceable"><code><condition-2></code></em> * <em class="replaceable"><code><special-condition-character></code></em>
+ <em class="replaceable"><code><condition-N></code></em>
+ <em class="replaceable"><code><special-action-character></code></em>
+ <em class="replaceable"><code><action-to-perform></code></em>
+</pre><div class="para">
+ The first two characters in a Procmail recipe are a colon and a zero. Various flags can be placed after the zero to control how Procmail processes the recipe. A colon after the <code class="command"><em class="replaceable"><code><flags></code></em> </code> section specifies that a lockfile is created for this message. If a lockfile is created, the name can be specified by replacing <code class="command"><em class="replaceable"><code><lockfile-name></code></em> </code>.
+ </div><div class="para">
+ A recipe can contain several conditions to match against the message. If it has no conditions, every message matches the recipe. Regular expressions are placed in some conditions to facilitate message matching. If multiple conditions are used, they must all match for the action to be performed. Conditions are checked based on the flags set in the recipe's first line. Optional special characters placed after the asterisk character (<code class="command">*</code>) can further control the condition.
+ </div><div class="para">
+ The <code class="command"><em class="replaceable"><code><action-to-perform></code></em></code> argument specifies the action taken when the message matches one of the conditions. There can only be one action per recipe. In many cases, the name of a mailbox is used here to direct matching messages into that file, effectively sorting the email. Special action characters may also be used before the action is specified. Refer to <a class="xref" href="#s3-email-procmail-recipes-special" title="12.4.2.4. Special Conditions and Actions">Section 12.4.2.4, “Special Conditions and Actions”</a> for more information.
+ </div><div class="section" title="12.4.2.1. Delivering vs. Non-Delivering Recipes" id="s2-email-procmail-recipes-delivering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-email-procmail-recipes-delivering">12.4.2.1. Delivering vs. Non-Delivering Recipes</h4></div></div></div><a id="id467619" class="indexterm"></a><a id="id467638" class="indexterm"></a><div class="para">
+ The action used if the recipe matches a particular message determines whether it is considered a <em class="firstterm">delivering</em> or <em class="firstterm">non-delivering</em> recipe. A delivering recipe contains an action that writes the message to a file, sends the message to another program, or forwards the message to another email address. A non-delivering recipe covers any other actions, such as a <em class="firstterm">nesting block</em>. A nesting block is a set of actions, contained in braces <code class="command">{</code> <code class="command">}</code>, that are performed on messages which match the recipe's conditions. Nesting blocks can be nested inside one another, providing greater control for identifying and performing actions on messages.
+ </div><div class="para">
+ When messages match a delivering recipe, Procmail performs the specified action and stops comparing the message against any other recipes. Messages that match non-delivering recipes continue to be compared against other recipes.
+ </div></div><div class="section" title="12.4.2.2. Flags" id="s3-email-procmail-recipes-flags"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-procmail-recipes-flags">12.4.2.2. Flags</h4></div></div></div><a id="id439378" class="indexterm"></a><div class="para">
+ Flags are essential to determine how or if a recipe's conditions are compared to a message. The following flags are commonly used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">A</code> — Specifies that this recipe is only used if the previous recipe without an <code class="command">A</code> or <code class="command">a</code> flag also matched this message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">a</code> — Specifies that this recipe is only used if the previous recipe with an <code class="command">A</code> or <code class="command">a</code> flag also matched this message <span class="emphasis"><em>and</em></span> was successfully completed.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">B</code> — Parses the body of the message and looks for matching conditions.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">b</code> — Uses the body in any resulting action, such as writing the message to a file or forwarding it. This is the default behavior.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">c</code> — Generates a carbon copy of the email. This is useful with delivering recipes, since the required action can be performed on the message and a copy of the message can continue being processed in the <code class="filename">rc</code> files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">D</code> — Makes the <code class="command">egrep</code> comparison case-sensitive. By default, the comparison process is not case-sensitive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">E</code> — While similar to the <code class="command">A</code> flag, the conditions in the recipe are only compared to the message if the immediately preceding the recipe without an <code class="command">E</code> flag did not match. This is comparable to an <em class="wordasword">else</em> action.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">e</code> — The recipe is compared to the message only if the action specified in the immediately preceding recipe fails.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">f</code> — Uses the pipe as a filter.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">H</code> — Parses the header of the message and looks for matching conditions. This is the default behavior.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">h</code> — Uses the header in a resulting action. This is the default behavior.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">w</code> — Tells Procmail to wait for the specified filter or program to finish, and reports whether or not it was successful before considering the message filtered.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">W</code> — Is identical to <code class="command">w</code> except that "Program failure" messages are suppressed.
+ </div></li></ul></div><div class="para">
+ For a detailed list of additional flags, refer to the <code class="filename">procmailrc</code> man page.
+ </div></div><div class="section" title="12.4.2.3. Specifying a Local Lockfile" id="s3-email-procmail-recipes-lockfile"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-procmail-recipes-lockfile">12.4.2.3. Specifying a Local Lockfile</h4></div></div></div><a id="id537873" class="indexterm"></a><div class="para">
+ Lockfiles are very useful with Procmail to ensure that more than one process does not try to alter a message simultaneously. Specify a local lockfile by placing a colon (<code class="command">:</code>) after any flags on a recipe's first line. This creates a local lockfile based on the destination file name plus whatever has been set in the <code class="command">LOCKEXT</code> global environment variable.
+ </div><div class="para">
+ Alternatively, specify the name of the local lockfile to be used with this recipe after the colon.
+ </div></div><div class="section" title="12.4.2.4. Special Conditions and Actions" id="s3-email-procmail-recipes-special"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-procmail-recipes-special">12.4.2.4. Special Conditions and Actions</h4></div></div></div><a id="id586935" class="indexterm"></a><a id="id586954" class="indexterm"></a><div class="para">
+ Special characters used before Procmail recipe conditions and actions change the way they are interpreted.
+ </div><div class="para">
+ The following characters may be used after the asterisk character (<code class="command">*</code>) at the beginning of a recipe's condition line:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">!</code> — In the condition line, this character inverts the condition, causing a match to occur only if the condition does not match the message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command"><</code> — Checks if the message is under a specified number of bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">></code> — Checks if the message is over a specified number of bytes.
+ </div></li></ul></div><div class="para">
+ The following characters are used to perform special actions:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">!</code> — In the action line, this character tells Procmail to forward the message to the specified email addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">$</code> — Refers to a variable set earlier in the <code class="filename">rc</code> file. This is often used to set a common mailbox that is referred to by various recipes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">|</code> — Starts a specified program to process the message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">{</code> and <code class="command">}</code> — Constructs a nesting block, used to contain additional recipes to apply to matching messages.
+ </div></li></ul></div><div class="para">
+ If no special character is used at the beginning of the action line, Procmail assumes that the action line is specifying the mailbox in which to write the message.
+ </div></div><div class="section" title="12.4.2.5. Recipe Examples" id="s3-email-procmail-recipes-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-procmail-recipes-examples">12.4.2.5. Recipe Examples</h4></div></div></div><a id="id872331" class="indexterm"></a><div class="para">
+ Procmail is an extremely flexible program, but as a result of this flexibility, composing Procmail recipes from scratch can be difficult for new users.
+ </div><div class="para">
+ The best way to develop the skills to build Procmail recipe conditions stems from a strong understanding of regular expressions combined with looking at many examples built by others. A thorough explanation of regular expressions is beyond the scope of this section. The structure of Procmail recipes and useful sample Procmail recipes can be found at various places on the Internet (such as <a href="http://www.iki.fi/era/procmail/links.html">http://www.iki.fi/era/procmail/links.html</a>). The proper use and adaptation of regular expressions can be derived by viewing these recipe examples. In addition, introductory information about basic regular expression rules can be found in the <code class="filename">grep</code> man page.
+ </div><div class="para">
+ The following simple examples demonstrate the basic structure of Procmail recipes and can provide the foundation for more intricate constructions.
+ </div><div class="para">
+ A basic recipe may not even contain conditions, as is illustrated in the following example:
+ </div><pre class="screen">:0: new-mail.spool</pre><div class="para">
+ The first line specifies that a local lockfile is to be created but does not specify a name, so Procmail uses the destination file name and appends the value specified in the <code class="command">LOCKEXT</code> environment variable. No condition is specified, so every message matches this recipe and is placed in the single spool file called <code class="filename">new-mail.spool</code>, located within the directory specified by the <code class="command">MAILDIR</code> environment variable. An MUA can then view messages in this file.
+ </div><div class="para">
+ A basic recipe, such as this, can be placed at the end of all <code class="filename">rc</code> files to direct messages to a default location.
+ </div><div class="para">
+ The following example matched messages from a specific email address and throws them away.
+ </div><pre class="screen">:0 * ^From: spammer at domain.com /dev/null</pre><div class="para">
+ With this example, any messages sent by <code class="computeroutput">spammer at domain.com</code> are sent to the <code class="filename">/dev/null</code> device, deleting them.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Be certain that rules are working as intended before sending messages to <code class="filename">/dev/null</code> for permanent deletion. If a recipe inadvertently catches unintended messages, and those messages disappear, it becomes difficult to troubleshoot the rule.
+ </div><div class="para">
+ A better solution is to point the recipe's action to a special mailbox, which can be checked from time to time to look for false positives. Once satisfied that no messages are accidentally being matched, delete the mailbox and direct the action to send the messages to <code class="filename">/dev/null</code>.
+ </div></div></div><div class="para">
+ The following recipe grabs email sent from a particular mailing list and places it in a specified folder.
+ </div><pre class="screen">:0: * ^(From|Cc|To).*tux-lug tuxlug</pre><div class="para">
+ Any messages sent from the <code class="computeroutput">tux-lug at domain.com</code> mailing list are placed in the <code class="filename">tuxlug</code> mailbox automatically for the MUA. Note that the condition in this example matches the message if it has the mailing list's email address on the <code class="computeroutput">From</code>, <code class="computeroutput">Cc</code>, or <code class="computeroutput">To</code> lines.
+ </div><div class="para">
+ Consult the many Procmail online resources available in <a class="xref" href="#s1-email-additional-resources" title="12.6. Additional Resources">Section 12.6, “Additional Resources”</a> for more detailed and powerful recipes.
+ </div></div><div class="section" title="12.4.2.6. Spam Filters" id="s3-email-mda-spam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-spam">12.4.2.6. Spam Filters</h4></div></div></div><a id="id1747949" class="indexterm"></a><a id="id1747967" class="indexterm"></a><a id="id623314" class="indexterm"></a><div class="para">
+ Because it is called by Sendmail, Postfix, and Fetchmail upon receiving new emails, Procmail can be used as a powerful tool for combating spam.
+ </div><div class="para">
+ This is particularly true when Procmail is used in conjunction with SpamAssassin. When used together, these two applications can quickly identify spam emails, and sort or destroy them.
+ </div><div class="para">
+ SpamAssassin uses header analysis, text analysis, blacklists, a spam-tracking database, and self-learning Bayesian spam analysis to quickly and accurately identify and tag spam.
+ </div><div class="note" title="Note: Installing the spamassassin package"><div class="admonition_header"><h2>Note: Installing the <span class="package">spamassassin</span> package</h2></div><div class="admonition"><div class="para">
+ In order to use <span class="application"><strong>SpamAssassin</strong></span>, first ensure the <span class="package">spamassassin</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install spamassassin</code></pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ The easiest way for a local user to use SpamAssassin is to place the following line near the top of the <code class="filename">~/.procmailrc</code> file:
+ </div><pre class="screen">
+<code class="command">INCLUDERC=/etc/mail/spamassassin/spamassassin-default.rc</code>
+</pre><div class="para">
+ The <code class="filename">/etc/mail/spamassassin/spamassassin-default.rc</code> contains a simple Procmail rule that activates SpamAssassin for all incoming email. If an email is determined to be spam, it is tagged in the header as such and the title is prepended with the following pattern:
+ </div><pre class="screen">*****SPAM*****</pre><div class="para">
+ The message body of the email is also prepended with a running tally of what elements caused it to be diagnosed as spam.
+ </div><div class="para">
+ To file email tagged as spam, a rule similar to the following can be used:
+ </div><pre class="screen">
+<code class="command">:0 Hw * ^X-Spam-Status: Yes spam</code>
+</pre><div class="para">
+ This rule files all email tagged in the header as spam into a mailbox called <code class="filename">spam</code>.
+ </div><div class="para">
+ Since SpamAssassin is a Perl script, it may be necessary on busy servers to use the binary SpamAssassin daemon (<code class="systemitem">spamd</code>) and the client application (<span class="application"><strong>spamc</strong></span>). Configuring SpamAssassin this way, however, requires root access to the host.
+ </div><div class="para">
+ To start the <code class="systemitem">spamd</code> daemon, type the following command:
+ </div><pre class="screen">~]# <code class="command">service spamassassin start</code>
+</pre><div class="para">
+ To start the SpamAssassin daemon when the system is booted, use an initscript utility, such as the <span class="application"><strong>Services Configuration Tool</strong></span> (<code class="command">system-config-services</code>), to turn on the <code class="computeroutput">spamassassin</code> service. Refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for more information about starting and stopping services.
+ </div><div class="para">
+ To configure Procmail to use the SpamAssassin client application instead of the Perl script, place the following line near the top of the <code class="filename">~/.procmailrc</code> file. For a system-wide configuration, place it in <code class="filename">/etc/procmailrc</code>:
+ </div><pre class="screen">
+<code class="command">INCLUDERC=/etc/mail/spamassassin/spamassassin-spamc.rc</code>
+</pre></div></div></div><div class="section" title="12.5. Mail User Agents" id="s1-email-mua"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-mua">12.5. Mail User Agents</h2></div></div></div><div class="para">
+ Fedora offers a variety of email programs, both, graphical email client programs, such as <span class="application"><strong>Evolution</strong></span>, and text-based email programs such as <code class="command">mutt</code>.
+ </div><div class="para">
+ The remainder of this section focuses on securing communication between a client and a server.
+ </div><div class="section" title="12.5.1. Securing Communication" id="s2-email-security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-security">12.5.1. Securing Communication</h3></div></div></div><div class="para">
+ Popular MUAs included with Fedora, such as <span class="application"><strong>Evolution</strong></span> and <code class="command">mutt</code> offer SSL-encrypted email sessions.
+ </div><a id="id822155" class="indexterm"></a><div class="para">
+ Like any other service that flows over a network unencrypted, important email information, such as usernames, passwords, and entire messages, may be intercepted and viewed by users on the network. Additionally, since the standard <code class="systemitem">POP</code> and <code class="systemitem">IMAP</code> protocols pass authentication information unencrypted, it is possible for an attacker to gain access to user accounts by collecting usernames and passwords as they are passed over the network.
+ </div><div class="section" title="12.5.1.1. Secure Email Clients" id="s3-email-security-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-security-clients">12.5.1.1. Secure Email Clients</h4></div></div></div><a id="id742259" class="indexterm"></a><div class="para">
+ Most Linux MUAs designed to check email on remote servers support SSL encryption. To use SSL when retrieving email, it must be enabled on both the email client and the server.
+ </div><div class="para">
+ SSL is easy to enable on the client-side, often done with the click of a button in the MUA's configuration window or via an option in the MUA's configuration file. Secure <code class="systemitem">IMAP</code> and <code class="systemitem">POP</code> have known port numbers (<code class="constant">993</code> and <code class="constant">995</code>, respectively) that the MUA uses to authenticate and download messages.
+ </div></div><div class="section" title="12.5.1.2. Securing Email Client Communications" id="s3-email-security-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-security-servers">12.5.1.2. Securing Email Client Communications</h4></div></div></div><a id="id651651" class="indexterm"></a><a id="id482111" class="indexterm"></a><div class="para">
+ Offering SSL encryption to <code class="systemitem">IMAP</code> and <code class="systemitem">POP</code> users on the email server is a simple matter.
+ </div><div class="para">
+ First, create an SSL certificate. This can be done in two ways: by applying to a <em class="firstterm">Certificate Authority</em> (<em class="firstterm">CA</em>) for an SSL certificate or by creating a self-signed certificate.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Self-signed certificates should be used for testing purposes only. Any server used in a production environment should use an SSL certificate granted by a CA.
+ </div></div></div><div class="para">
+ To create a self-signed SSL certificate for <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code>, change to the <code class="filename">/etc/pki/dovecot/</code> directory, edit the certificate parameters in the <code class="filename">/etc/pki/dovecot/dovecot-openssl.conf</code> configuration file as you prefer, and type the following commands, as root:
+ </div><pre class="screen">dovecot]# <code class="command">rm -f certs/dovecot.pem private/dovecot.pem</code>
+dovecot]# <code class="command">/usr/libexec/dovecot/mkcert.sh</code>
+</pre><div class="para">
+ Once finished, make sure you have the following configurations in your <code class="filename">/etc/dovecot/conf.d/10-ssl.conf</code> file:
+ </div><pre class="screen">
+ssl_cert = </etc/pki/dovecot/certs/dovecot.pem
+ssl_key = </etc/pki/dovecot/private/dovecot.pem
+</pre><div class="para">
+ Execute the <code class="command">service dovecot restart</code> command to restart the <code class="command">dovecot</code> daemon.
+ </div><div class="para">
+ Alternatively, the <code class="command">stunnel</code> command can be used as an SSL encryption wrapper around the standard, non-secure connections to <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code> services.
+ </div><div class="para">
+ The <code class="command">stunnel</code> utility uses external OpenSSL libraries included with Fedora to provide strong cryptography and to protect the network connections. It is recommended to apply to a CA to obtain an SSL certificate, but it is also possible to create a self-signed certificate.
+ </div><div class="note" title="Note: Installing the stunnel package"><div class="admonition_header"><h2>Note: Installing the <span class="package">stunnel</span> package</h2></div><div class="admonition"><div class="para">
+ In order to use <code class="command">stunnel</code>, first ensure the <span class="package">stunnel</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install stunnel</code></pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ To create a self-signed SSL certificate, change to the <code class="filename">/etc/pki/tls/certs/</code> directory, and type the following command:
+ </div><pre class="screen">certs]# <code class="command">make stunnel.pem</code>
+</pre><div class="para">
+ Answer all of the questions to complete the process.
+ </div><div class="para">
+ Once the certificate is generated, create an <code class="command">stunnel</code> configuration file, for example <code class="filename">/etc/stunnel/mail.conf</code>, with the following content:
+ </div><pre class="screen">cert = /etc/pki/tls/certs/stunnel.pem
+
+[pop3s]
+accept = 995
+connect = 110
+
+[imaps]
+accept = 993
+connect = 143
+</pre><div class="para">
+ Once you start <code class="command">stunnel</code> with the created configuration file using the <code class="command">/usr/bin/stunnel /etc/stunnel/mail.conf</code> command, it will be possible to use an <code class="systemitem">IMAP</code> or a <code class="systemitem">POP</code> email client and connect to the email server using SSL encryption.
+ </div><div class="para">
+ For more information on <code class="command">stunnel</code>, refer to the <code class="command">stunnel</code> man page or the documents in the <code class="filename">/usr/share/doc/stunnel-<em class="replaceable"><code><version-number></code></em> </code>/ directory, where <em class="replaceable"><code><version-number></code></em> is the version number of <code class="command">stunnel</code>.
+ </div></div></div></div><div class="section" title="12.6. Additional Resources" id="s1-email-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-additional-resources">12.6. Additional Resources</h2></div></div></div><a id="id597190" class="indexterm"></a><a id="id597204" class="indexterm"></a><a id="id597219" class="indexterm"></a><a id="id721047" class="indexterm"></a><div class="para">
+ The following is a list of additional documentation about email applications.
+ </div><div class="section" title="12.6.1. Installed Documentation" id="s2-email-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-installed-docs">12.6.1. Installed Documentation</h3></div></div></div><a id="id721076" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Information on configuring Sendmail is included with the <code class="filename">sendmail</code> and <code class="filename">sendmail-cf</code> packages.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/sendmail-cf/README</code> — Contains information on the <code class="command">m4</code> macro processor, file locations for Sendmail, supported mailers, how to access enhanced features, and more.
+ </div></li></ul></div><div class="para">
+ In addition, the <code class="filename">sendmail</code> and <code class="filename">aliases</code> man pages contain helpful information covering various Sendmail options and the proper configuration of the Sendmail <code class="filename">/etc/mail/aliases</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/postfix-<em class="replaceable"><code><version-number></code></em> </code> — Contains a large amount of information about ways to configure Postfix. Replace <em class="replaceable"><code><version-number></code></em> with the version number of Postfix.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/fetchmail-<em class="replaceable"><code><version-number></code></em> </code> — Contains a full list of Fetchmail features in the <code class="filename">FEATURES</code> file and an introductory <code class="filename">FAQ</code> document. Replace <em class="replaceable"><code><version-number></code></em> with the version number of Fetchmail.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/procmail-<em class="replaceable"><code><version-number></code></em> </code> — Contains a <code class="filename">README</code> file that provides an overview of Procmail, a <code class="filename">FEATURES</code> file that explores every program feature, and an <code class="filename">FAQ</code> file with answers to many common configuration questions. Replace <em class="replaceable"><code><version-number></code></em> with the version number of Procmail.
+ </div><div class="para">
+ When learning how Procmail works and creating new recipes, the following Procmail man pages are invaluable:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">procmail</code> — Provides an overview of how Procmail works and the steps involved with filtering email.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">procmailrc</code> — Explains the <code class="filename">rc</code> file format used to construct recipes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">procmailex</code> — Gives a number of useful, real-world examples of Procmail recipes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">procmailsc</code> — Explains the weighted scoring technique used by Procmail to match a particular recipe to a message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/spamassassin-<em class="replaceable"><code><version-number></code></em>/</code> — Contains a large amount of information pertaining to SpamAssassin. Replace <em class="replaceable"><code><version-number></code></em> with the version number of the <code class="filename">spamassassin</code> package.
+ </div></li></ul></div></li></ul></div></div><div class="section" title="12.6.2. Useful Websites" id="s2-email-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-useful-websites">12.6.2. Useful Websites</h3></div></div></div><a id="id702140" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.sendmail.org/">http://www.sendmail.org/</a> — Offers a thorough technical breakdown of Sendmail features, documentation and configuration examples.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.sendmail.com/">http://www.sendmail.com/</a> — Contains news, interviews and articles concerning Sendmail, including an expanded view of the many options available.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.postfix.org/">http://www.postfix.org/</a> — The Postfix project home page contains a wealth of information about Postfix. The mailing list is a particularly good place to look for information.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://fetchmail.berlios.de/">http://fetchmail.berlios.de/</a> — The home page for Fetchmail, featuring an online manual, and a thorough FAQ.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.procmail.org/">http://www.procmail.org/</a> — The home page for Procmail with links to assorted mailing lists dedicated to Procmail as well as various FAQ documents.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://partmaps.org/era/procmail/mini-faq.html">http://partmaps.org/era/procmail/mini-faq.html</a> — An excellent Procmail FAQ, offers troubleshooting tips, details about file locking, and the use of wildcard characters.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.uwasa.fi/~ts/info/proctips.html">http://www.uwasa.fi/~ts/info/proctips.html</a> — Contains dozens of tips that make using Procmail much easier. Includes instructions on how to test <code class="filename">.procmailrc</code> files and use Procmail scoring to decide if a particular action should be taken.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.spamassassin.org/">http://www.spamassassin.org/</a> — The official site of the SpamAssassin project.
+ </div></li></ul></div></div><div class="section" title="12.6.3. Related Books" id="s2-email-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-related-books">12.6.3. Related Books</h3></div></div></div><a id="id650180" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">Sendmail Milters: A Guide for Fighting Spam</em> by Bryan Costales and Marcia Flynt; Addison-Wesley — A good Sendmail guide that can help you customise your mail filters.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Sendmail</em> by Bryan Costales with Eric Allman et al; O'Reilly & Associates — A good Sendmail reference written with the assistance of the original creator of Delivermail and Sendmail.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Removing the Spam: Email Processing and Filtering</em> by Geoff Mulligan; Addison-Wesley Publishing Company — A volume that looks at various methods used by email administrators using established tools, such as Sendmail and Procmail, to manage spam problems.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Internet Email Protocols: A Developer's Guide</em> by Kevin Johnson; Addison-Wesley Publishing Company — Provides a very thorough review of major email protocols and the security they provide.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Managing IMAP</em> by Dianna Mullet and Kevin Mullet; O'Reilly & Associates — Details the steps required to configure an IMAP server.
+ </div></li></ul></div></div></div></div></div><div class="part" title="Part III. System Configuration" id="pt-sysconfig"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part III. System Configuration</h1></div></div></div><div class="partintro" title="System Configuration" id="id632556"><div></div><div class="para">
+ Part of a system administrator's job is configuring the system for various tasks, types of users, and hardware configurations. This section explains how to configure a Fedora system.
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#chap-Date_and_Time_Configuration">13. Date and Time Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool">13.1. Date/Time Properties Tool</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration">13.2. Command Line Configuration</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Keyboard_Configuration">14. Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-keyboard-layout">14.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="#s1-keyboard-indicator">14.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="#s1-keyboard-break">14.3. Setting Up a Typing Break</a></span></dt></dl></dd><dt><span class="chapter"><a href="#Users_and_Groups"
>15. Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-users-configui">15.1. User and Group Configuration</a></span></dt><dt><span class="section"><a href="#s1-users-tools">15.2. User and Group Management Tools</a></span></dt><dt><span class="section"><a href="#s1-users-groups-standard-users">15.3. Standard Users</a></span></dt><dt><span class="section"><a href="#s1-users-groups-standard-groups">15.4. Standard Groups</a></span></dt><dt><span class="section"><a href="#s1-users-groups-private-groups">15.5. User Private Groups</a></span></dt><dt><span class="section"><a href="#s1-users-groups-shadow-utilities">15.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="#s1-users-groups-additional-resources">15.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Automated_Tasks">16. Automated Tasks</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-autotasks-cron-anacron">16.1. Cron and Anac
ron</a></span></dt><dt><span class="section"><a href="#s1-autotasks-at-batch">16.2. At and Batch</a></span></dt><dt><span class="section"><a href="#s1-autotasks-additional-resources">16.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Log_Files">17. Log Files</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-configuring-rsyslog">17.1. Configuring <code class="command">rsyslog</code> </a></span></dt><dt><span class="section"><a href="#s1-rsyslog-performance">17.2. <code class="command">rsyslog</code> Performance</a></span></dt><dt><span class="section"><a href="#s1-logfiles-locating">17.3. Locating Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-viewing">17.4. Viewing Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-adding">17.5. Adding a Log File</a></span></dt><dt><span class="section"><a href="#s1-logfiles-examining">17.6. Monitoring Log Files</a></span></dt><dt><span class=
"section"><a href="#s1-log-files-additional-resources">17.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-The_sysconfig_Directory">18. The sysconfig Directory</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-sysconfig-files">18.1. Files in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="#s1-sysconfig-etcsysconf-dir">18.2. Directories in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="#s1-sysconfig-additional-resources">18.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-proc">19. The <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-proc-virtual">19.1. A Virtual File System</a></span></dt><dt><span class="section"><a href="#s1-proc-topfiles">19.2. Top-level Files within the <code class="filename">proc</co
de> File System</a></span></dt><dt><span class="section"><a href="#s1-proc-directories">19.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dt><span class="section"><a href="#s1-proc-sysctl">19.4. Using the <code class="command">sysctl</code> Command</a></span></dt><dt><span class="section"><a href="#s1-proc-additional-resources">19.5. References</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" title="Chapter 13. Date and Time Configuration" id="chap-Date_and_Time_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 13. Date and Time Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool">13.1. Date/Time Properties Tool</a></span></dt><dt><span class="section"><a href="#sect-Date_and_Time_Configuration-Command_Line_Configuration">13.2. Command Line Configuration</a></span></dt></dl
></div><div class="para">
+ This chapter covers setting the system date and time in Fedora, both manually and using the Network Time Protocol (<abbr class="abbrev">NTP</abbr>), as well as setting the adequate time zone. Two methods are covered: setting the date and time using the <span class="application"><strong>Date/Time Properties</strong></span> tool, and doing so on the command line.
+ </div><div class="section" title="13.1. Date/Time Properties Tool" id="sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool">13.1. Date/Time Properties Tool</h2></div></div></div><div class="para">
+ The <span class="application"><strong>Date/Time Properties</strong></span> tool allows the user to change the system date and time, to configure the time zone used by the system, and to set up the Network Time Protocol daemon to synchronize the system clock with a time server. Note that to use this application, you must be running the <span class="emphasis"><em>X Window System</em></span>.
+ </div><a id="id669657" class="indexterm"></a><div class="para">
+ To start the tool, select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Date & Time</strong></span> from the panel, or type the <code class="command">system-config-date</code> command at a shell prompt (e.g., <span class="emphasis"><em>xterm</em></span> or <span class="emphasis"><em>GNOME Terminal</em></span>). Unless you are already authenticated, you will be prompted to enter the superuser password.
+ </div><div class="figure" title="Figure 13.1. Authentication Query" id="figu-Date_and_Time_Configuration-Authentication"><div class="figure-contents"><div class="mediaobject"><img src="images/date-and-time-authentication.png" alt="Authentication Query" /></div></div><h6>Figure 13.1. Authentication Query</h6></div><br class="figure-break" /><div class="section" title="13.1.1. Date and Time Properties" id="sect-Date_and_Time_Configuration-Date_and_Time"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Date_and_Time_Configuration-Date_and_Time">13.1.1. Date and Time Properties</h3></div></div></div><a id="id2217266" class="indexterm"></a><a id="id646754" class="indexterm"></a><div class="para">
+ As shown in <a class="xref" href="#figu-Date_and_Time_Configuration-Date_and_Time" title="Figure 13.2. Date and Time Properties">Figure 13.2, “Date and Time Properties”</a>, the <span class="application"><strong>Date/Time Properties</strong></span> tool is divided into two separate tabs. The tab containing the configuration of the current date and time is shown by default.
+ </div><div class="figure" title="Figure 13.2. Date and Time Properties" id="figu-Date_and_Time_Configuration-Date_and_Time"><div class="figure-contents"><div class="mediaobject"><img src="images/date-and-time-date_and_time.png" alt="Date and Time Properties" /><div class="longdesc"><div class="para">
+ Date and Time Properties
+ </div></div></div></div><h6>Figure 13.2. Date and Time Properties</h6></div><br class="figure-break" /><div class="para">
+ To set up your system manually, follow these steps:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ <span class="emphasis"><em>Change the current date.</em></span> Use the arrows to the left and right of the month and year to change the month and year respectively. Then click inside the calendar to select the day of the month.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ <span class="emphasis"><em>Change the current time.</em></span> Use the up and down arrow buttons beside the <span class="guilabel"><strong>Hour</strong></span>, <span class="guilabel"><strong>Minute</strong></span>, and <span class="guilabel"><strong>Second</strong></span>, or replace the values directly.
+ </div></li></ol></div><div class="para">
+ Click the <span class="guibutton"><strong>OK</strong></span> button to apply the changes and exit the application.
+ </div></div><div class="section" title="13.1.2. Network Time Protocol Properties" id="sect-Date_and_Time_Configuration-Network_Time_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Date_and_Time_Configuration-Network_Time_Protocol">13.1.2. Network Time Protocol Properties</h3></div></div></div><a id="id827507" class="indexterm"></a><a id="id798776" class="indexterm"></a><a id="id798790" class="indexterm"></a><a id="id832281" class="indexterm"></a><a id="id832299" class="indexterm"></a><div class="para">
+ If you prefer an automatic setup, select the checkbox labeled <span class="guilabel"><strong>Synchronize date and time over the network</strong></span> instead. This will display the list of available NTP servers as shown in <a class="xref" href="#figu-Date_and_Time_Configuration-Network_Time_Protocol" title="Figure 13.3. Network Time Protocol Properties">Figure 13.3, “Network Time Protocol Properties”</a>.
+ </div><div class="figure" title="Figure 13.3. Network Time Protocol Properties" id="figu-Date_and_Time_Configuration-Network_Time_Protocol"><div class="figure-contents"><div class="mediaobject"><img src="images/date-and-time-network_time_protocol.png" alt="Network Time Protocol Properties" /><div class="longdesc"><div class="para">
+ Network Time Protocol Properties
+ </div></div></div></div><h6>Figure 13.3. Network Time Protocol Properties</h6></div><br class="figure-break" /><div class="para">
+ Here you can choose one of the predefined servers, edit a predefined server by clicking the <span class="guibutton"><strong>Edit</strong></span> button, or add a new server name by clicking <span class="guibutton"><strong>Add</strong></span>. In the <span class="guilabel"><strong>Advanced Options</strong></span>, you can also select whether you want to synchronize the system clock before starting the service, and if you wish to use a local time source.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Your system does not start synchronizing with the NTP server until you click the <span class="guibutton"><strong>OK</strong></span> button at the bottom of the window to confirm your changes.
+ </div></div></div><div class="para">
+ Click the <span class="guibutton"><strong>OK</strong></span> button to apply any changes made to the date and time settings and exit the application.
+ </div></div><div class="section" title="13.1.3. Time Zone Properties" id="sect-Date_and_Time_Configuration-Time_Zone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Date_and_Time_Configuration-Time_Zone">13.1.3. Time Zone Properties</h3></div></div></div><a id="id2226994" class="indexterm"></a><div class="para">
+ To configure the system time zone, click the <span class="guilabel"><strong>Time Zone</strong></span> tab as shown in <a class="xref" href="#figu-Date_and_Time_Configuration-Time_Zone" title="Figure 13.4. Time Zone Properties">Figure 13.4, “Time Zone Properties”</a>.
+ </div><div class="figure" title="Figure 13.4. Time Zone Properties" id="figu-Date_and_Time_Configuration-Time_Zone"><div class="figure-contents"><div class="mediaobject"><img src="images/date-and-time-time_zone.png" alt="Time Zone Properties" /><div class="longdesc"><div class="para">
+ Time Zone Properties
+ </div></div></div></div><h6>Figure 13.4. Time Zone Properties</h6></div><br class="figure-break" /><div class="para">
+ There are two common approaches to the time zone selection:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Using the interactive map.</em></span> Click “zoom in” and “zoom out” buttons next to the map, or click on the map itself to zoom into the selected region. Then choose the city specific to your time zone. A red <span class="guilabel"><strong>X</strong></span> appears and the time zone selection changes in the list below the map.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Use the list below the map.</em></span> To make the selection easier, cities and countries are grouped within their specific continents. Note that non-geographic time zones have also been added to address needs in the scientific community.
+ </div></li></ol></div><div class="para">
+ If your system clock is set to use <acronym class="acronym">UTC</acronym>, select the <span class="guibutton"><strong>System clock uses UTC</strong></span> option. UTC stands for the <em class="firstterm">Universal Time, Coordinated</em>, also known as <em class="firstterm">Greenwich Mean Time</em> (<acronym class="acronym">GMT</acronym>). Other time zones are determined by adding or subtracting from the UTC time.
+ </div><div class="para">
+ Click <span class="guibutton"><strong>OK</strong></span> to apply the changes and exit the program.
+ </div></div></div><div class="section" title="13.2. Command Line Configuration" id="sect-Date_and_Time_Configuration-Command_Line_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Date_and_Time_Configuration-Command_Line_Configuration">13.2. Command Line Configuration</h2></div></div></div><div class="para">
+ In case your system does not have the <span class="application"><strong>Date/Time Properties</strong></span> tool installed, or the <span class="emphasis"><em>X Window Server</em></span> is not running, you will have to change the system date and time on the command line. Note that in order to perform actions described in this section, you have to be logged in as a superuser:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="section" title="13.2.1. Date and Time Setup" id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">13.2.1. Date and Time Setup</h3></div></div></div><a id="id625266" class="indexterm"></a><a id="id625283" class="indexterm"></a><a id="id578378" class="indexterm"></a><div class="para">
+ The <code class="command">date</code> command allows the superuser to set the system date and time manually:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ <span class="emphasis"><em>Change the current date.</em></span> Type the command in the following form at a shell prompt, replacing the <em class="replaceable"><code>YYYY</code></em> with a four-digit year, <em class="replaceable"><code>MM</code></em> with a two-digit month, and <em class="replaceable"><code>DD</code></em> with a two-digit day of the month:
+ </div><pre class="screen">~]# <code class="command">date +%D -s <em class="replaceable"><code>YYYY-MM-DD</code></em></code></pre><div class="para">
+ For example, to set the date to 2 June 2010, type:
+ </div><pre class="screen">~]# <code class="command">date +%D -s 2010-06-02</code></pre></li><li class="step" title="Step 2"><div class="para">
+ <span class="emphasis"><em>Change the current time.</em></span> Use the following command, where <em class="replaceable"><code>HH</code></em> stands for an hour, <em class="replaceable"><code>MM</code></em> is a minute, and <em class="replaceable"><code>SS</code></em> is a second, all typed in a two-digit form:
+ </div><pre class="screen">~]# <code class="command">date +%T -s <em class="replaceable"><code>HH:MM:SS</code></em></code></pre><div class="para">
+ If your system clock is set to use <acronym class="acronym">UTC</acronym> (Coordinated Universal Time), add the following option:
+ </div><pre class="screen">~]# <code class="command">date +%T -s <em class="replaceable"><code>HH:MM:SS</code></em> -u</code></pre><div class="para">
+ For instance, to set the system clock to 11:26 PM using the <acronym class="acronym">UTC</acronym>, type:
+ </div><pre class="screen">~]# <code class="command">date +%T -s 23:26:00 -u</code></pre></li></ol></div><div class="para">
+ You can check your current settings by typing <code class="command">date</code> without any additional argument:
+ </div><div class="example" title="Example 13.1. Displaying the current date and time" id="ex-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time"><h6>Example 13.1. Displaying the current date and time</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">date</code>
+Wed Jun 2 11:58:48 CEST 2010</pre></div></div><br class="example-break" /></div><div class="section" title="13.2.2. Network Time Protocol Setup" id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">13.2.2. Network Time Protocol Setup</h3></div></div></div><a id="id579230" class="indexterm"></a><a id="id579243" class="indexterm"></a><a id="id579256" class="indexterm"></a><a id="id768903" class="indexterm"></a><div class="para">
+ As opposed to the manual setup described above, you can also synchronize the system clock with a remote server over the Network Time Protocol (<acronym class="acronym">NTP</acronym>). For the one-time synchronization only, use the <span class="application"><strong>ntpdate</strong></span> command:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Firstly, check whether the selected NTP server is accessible:
+ </div><pre class="screen">~]# <code class="command">ntpdate -q <em class="replaceable"><code>server_address</code></em></code></pre><div class="para">
+ For example:
+ </div><pre class="screen">~]# <code class="command">ntpdate -q 0.rhel.pool.ntp.org</code></pre></li><li class="step" title="Step 2"><div class="para">
+ When you find a satisfactory server, run the <span class="application"><strong>ntpdate</strong></span> command followed with on or more server addresses:
+ </div><pre class="screen">~]# <code class="command">ntpdate <em class="replaceable"><code>server_address...</code></em></code></pre><div class="para">
+ For instance:
+ </div><pre class="screen">~]# <code class="command">ntpdate 0.rhel.pool.ntp.org 1.rhel.pool.ntp.org</code></pre><div class="para">
+ Unless an error message is displayed, the system time should now be set. You can check the current by setting typing <code class="command">date</code> without any additional arguments as shown in <a class="xref" href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time" title="13.2.1. Date and Time Setup">Section 13.2.1, “Date and Time Setup”</a>.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ In most cases, these steps are sufficient. Only if you really need one or more system services to always use the correct time, enable running the <span class="application"><strong>ntpdate</strong></span> at boot time:
+ </div><pre class="screen">~]# <code class="command">chkconfig ntpdate on</code></pre><div class="para">
+ For more information about system services and their setup, see <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If the synchronization with the time server at boot time keeps failing, i.e., you find a relevant error message in the <code class="filename">/var/log/boot.log</code> system log, try to add the following line to <code class="filename">/etc/sysconfig/network</code>:
+ </div><pre class="screen">NETWORKWAIT=1</pre></div></div></li></ol></div><a id="id533740" class="indexterm"></a><a id="id713392" class="indexterm"></a><a id="id713410" class="indexterm"></a><div class="para">
+ However, the more convenient way is to set the <span class="application"><strong>ntpd</strong></span> daemon to synchronize the time at boot time automatically:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Open the NTP configuration file <code class="filename">/etc/ntp.conf</code> in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, or create a new one if it does not already exist:
+ </div><pre class="screen">~]# <code class="command">nano /etc/ntp.conf</code></pre></li><li class="step" title="Step 2"><div class="para">
+ Now add or edit the list of public NTP servers. If you are using Fedora 14, the file should already contain the following lines, but feel free to change or expand these according to your needs:
+ </div><pre class="screen">server 0.rhel.pool.ntp.org
+server 1.rhel.pool.ntp.org
+server 2.rhel.pool.ntp.org</pre><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ To speed the initial synchronization up, add the <code class="command">iburst</code> directive at the end of each server line:
+ </div><pre class="screen">server 0.rhel.pool.ntp.org iburst
+server 1.rhel.pool.ntp.org iburst
+server 2.rhel.pool.ntp.org iburst</pre></div></div></li><li class="step" title="Step 3"><div class="para">
+ Once you have the list of servers complete, in the same file, set the proper permissions, giving the unrestricted access to localhost only:
+ </div><pre class="screen">restrict default kod nomodify notrap nopeer noquery
+restrict -6 default kod nomodify notrap nopeer noquery
+restrict 127.0.0.1
+restrict -6 ::1</pre></li><li class="step" title="Step 4"><div class="para">
+ Save all changes, exit the editor, and restart the NTP daemon:
+ </div><pre class="screen">~]# <code class="command">service ntpd restart</code></pre></li><li class="step" title="Step 5"><div class="para">
+ Make sure that <code class="command">ntpd</code> daemon is started at boot time:
+ </div><pre class="screen">~]# <code class="command">chkconfig ntpd on</code></pre></li></ol></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 14. Keyboard Configuration" id="ch-Keyboard_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 14. Keyboard Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-keyboard-layout">14.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="#s1-keyboard-indicator">14.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="#s1-keyboard-break">14.3. Setting Up a Typing Break</a></span></dt></dl></div><a id="id663292" class="indexterm"></a><div class="para">
+ This chapter describes how to change the keyboard layout, as well as how to add the <span class="application"><strong>Keyboard Indicator</strong></span> applet to the panel. It also covers the option to enforce a typing break, and explains both advantages and disadvantages of doing so.
+ </div><div class="section" title="14.1. Changing the Keyboard Layout" id="s1-keyboard-layout"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-keyboard-layout">14.1. Changing the Keyboard Layout</h2></div></div></div><a id="id1769045" class="indexterm"></a><a id="id449373" class="indexterm"></a><a id="id661547" class="indexterm"></a><div class="para">
+ The installation program allowed you to configure a keyboard layout for your system. However, the default settings may not always suit your current needs. To configure a different keyboard layout after the installation, use the <span class="application"><strong>Keyboard Preferences</strong></span> tool.
+ </div><div class="para">
+ To open <span class="application"><strong>Keyboard Layout Preferences</strong></span>, select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Keyboard</strong></span> from the panel, and click the <span class="guilabel"><strong>Layouts</strong></span> tab.
+ </div><div class="figure" title="Figure 14.1. Keybord Layout Preferences" id="fig-keyboard-layouts-layout"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-layouts.png" alt="Keybord Layout Preferences" /><div class="longdesc"><div class="para">
+ Keyboard Layout Preferences
+ </div></div></div></div><h6>Figure 14.1. Keybord Layout Preferences</h6></div><br class="figure-break" /><div class="para">
+ You will be presented with a list of available layouts. To add a new one, click the <span class="guibutton"><strong>Add...</strong></span> button below the list, and you will be prompted to chose which layout you want to add.
+ </div><div class="figure" title="Figure 14.2. Choosing a layout" id="fig-keyboard-layouts-layout-new"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-layouts-new.png" alt="Choosing a layout" /><div class="longdesc"><div class="para">
+ Choosing a layout
+ </div></div></div></div><h6>Figure 14.2. Choosing a layout</h6></div><br class="figure-break" /><div class="para">
+ Currently, there are two ways how to chose the keyboard layout: you can either find it by the country it is associated with (the <span class="guilabel"><strong>By country</strong></span> tab), or you can select it by the language (the <span class="guilabel"><strong>By language</strong></span> tab). In either case, first select the desired country or language from the <span class="guilabel"><strong>Country</strong></span> or <span class="guilabel"><strong>Language</strong></span> pulldown menu, then specify the variant from the <span class="guilabel"><strong>Variants</strong></span> menu. The preview of the layout changes immediately. To confirm the selection, click <span class="guibutton"><strong>Add</strong></span>.
+ </div><div class="figure" title="Figure 14.3. Selecting the default layout" id="fig-keyboard-layouts-default"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-layouts-default.png" alt="Selecting the default layout" /><div class="longdesc"><div class="para">
+ Selecting the default layout
+ </div></div></div></div><h6>Figure 14.3. Selecting the default layout</h6></div><br class="figure-break" /><div class="para">
+ The layout should appear in the list. To make it the default, select the radio button next to its name. The changes take effect immediately. Note that there is a text-entry field at the bottom of the window where you can safely test your settings. Once you are satisfied, click <span class="guibutton"><strong>Close</strong></span> to close the window.
+ </div><div class="figure" title="Figure 14.4. Testing the layout" id="fig-keyboard-layouts-layout-test"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-layouts-test.png" alt="Testing the layout" /><div class="longdesc"><div class="para">
+ Testing the layout
+ </div></div></div></div><h6>Figure 14.4. Testing the layout</h6></div><br class="figure-break" /><div class="note" title="Suggestion: Disable Separate Layout for Each Window"><div class="admonition_header"><h2>Suggestion: Disable Separate Layout for Each Window</h2></div><div class="admonition"><div class="para">
+ By default, changing the keyboard layout affects the active window only. This means that if you change the layout and switch to another window, this window will use the old one, which might be confusing. To turn this unfortunate behavior off, unselect the <span class="guilabel"><strong>Separate layout for each window</strong></span> check box.
+ </div><div class="mediaobject" align="center"><img src="images/keyboard-configuration-layouts-separate.png" align="middle" /><div class="longdesc"><div class="para">
+ Disabling separate layout for each window
+ </div></div></div><div class="para">
+ Doing this has its drawbacks though, as you will no longer be able to chose the default layout by selecting the radio button as shown in <a class="xref" href="#fig-keyboard-layouts-default" title="Figure 14.3. Selecting the default layout">Figure 14.3, “Selecting the default layout”</a>. To make the layout the default, simply drag it at the beginning of the list.
+ </div><div class="mediaobject" align="center"><img src="images/keyboard-configuration-layouts-prioritize.png" align="middle" /><div class="longdesc"><div class="para">
+ Changing the order of layouts
+ </div></div></div></div></div></div><div class="section" title="14.2. Adding the Keyboard Layout Indicator" id="s1-keyboard-indicator"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-keyboard-indicator">14.2. Adding the Keyboard Layout Indicator</h2></div></div></div><a id="id436922" class="indexterm"></a><a id="id884916" class="indexterm"></a><div class="para">
+ If you want to see what keyboard layout you are currently using, or you would like to switch between different layouts with a single mouse click, add the <span class="application"><strong>Keyboard Indicator</strong></span> applet to the panel. To do so, right-click the empty space on the main panel, and select the <span class="guimenuitem"><strong>Add to Panel...</strong></span> option from the pulldown menu.
+ </div><div class="figure" title="Figure 14.5. Adding a new applet" id="fig-keyboard-indicator-addition"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-applet-addition.png" alt="Adding a new applet" /><div class="longdesc"><div class="para">
+ Adding a New Applet
+ </div></div></div></div><h6>Figure 14.5. Adding a new applet</h6></div><br class="figure-break" /><div class="para">
+ You will be presented with a list of available applets. Scroll through the list (or start typing <span class="quote">“<span class="quote">keyboard</span>”</span> to the search field at the top of the window), select <span class="guimenuitem"><strong>Keyboard Indicator</strong></span>, and click the <span class="guibutton"><strong>Add</strong></span> button.
+ </div><div class="figure" title="Figure 14.6. Selecting the Keyboard Indicator" id="fig-keyboard-indicator-selection"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-applet-selection.png" alt="Selecting the Keyboard Indicator" /><div class="longdesc"><div class="para">
+ Selecting the <span class="application"><strong>Keyboard Indicator</strong></span>
+ </div></div></div></div><h6>Figure 14.6. Selecting the <span class="application">Keyboard Indicator</span></h6></div><br class="figure-break" /><div class="para">
+ The applet appears immediately, displaying the shortened name of the country the current layout is associated with. To display the actual variant, hover the pointer over the applet icon.
+ </div><div class="figure" title="Figure 14.7. The Keyboard Indicator applet" id="fig-keyboard-indicator-observation"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-applet-observation.png" alt="The Keyboard Indicator applet" /><div class="longdesc"><div class="para">
+ The <span class="application"><strong>Keyboard Indicator</strong></span> applet
+ </div></div></div></div><h6>Figure 14.7. The <span class="application">Keyboard Indicator</span> applet</h6></div><br class="figure-break" /></div><div class="section" title="14.3. Setting Up a Typing Break" id="s1-keyboard-break"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-keyboard-break">14.3. Setting Up a Typing Break</h2></div></div></div><a id="id755706" class="indexterm"></a><div class="para">
+ Typing for a long period of time can be not only tiresome, but it can also increase the risk of serious health problems, such as the carpal tunnel syndrome. One way of preventing this is to configure the system to enforce the typing break. Simply select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Keyboard</strong></span> from the panel, click the <span class="guilabel"><strong>Typing Break</strong></span> tab, and select the <span class="guilabel"><strong>Lock screen to enforce typing break</strong></span> check box.
+ </div><div class="figure" title="Figure 14.8. Typing Break Properties" id="fig-keyboard-break"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-break.png" alt="Typing Break Properties" /><div class="longdesc"><div class="para">
+ Typing Break Properties
+ </div></div></div></div><h6>Figure 14.8. Typing Break Properties</h6></div><br class="figure-break" /><div class="para">
+ To increase or decrease the amount of time you want to be allowed to type before the break is enforced, click the up or down button next to the <span class="guilabel"><strong>Work interval lasts</strong></span> label respectively. You can do the same with the <span class="guilabel"><strong>Break interval lasts</strong></span> setting to alter the length of the break itself. Finally, select the <span class="guilabel"><strong>Allow postponing of breaks</strong></span> check box if you want to be able to delay the break in case you need to finish the work. The changes take effect immediately.
+ </div><div class="figure" title="Figure 14.9. Taking a break" id="fig-keyboard-break-take"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-break-take.png" alt="Taking a break" /><div class="longdesc"><div class="para">
+ Taking a break
+ </div></div></div></div><h6>Figure 14.9. Taking a break</h6></div><br class="figure-break" /><div class="para">
+ Next time you reach the time limit, you will be presented with a screen advising you to take a break, and a clock displaying the remaining time. If you enabled it, the <span class="guibutton"><strong>Postpone Break</strong></span> button will be located at the bottom right corner of the screen.
+ </div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 15. Users and Groups" id="Users_and_Groups" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Users and Groups</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-users-configui">15.1. User and Group Configuration</a></span></dt><dt><span class="section"><a href="#s1-users-tools">15.2. User and Group Management Tools</a></span></dt><dt><span class="section"><a href="#s1-users-groups-standard-users">15.3. Standard Users</a></span></dt><dt><span class="section"><a href="#s1-users-groups-standard-groups">15.4. Standard Groups</a></span></dt><dt><span class="section"><a href="#s1-users-groups-private-groups">15.5. User Private Groups</a></span></dt><dt><span class="section"><a href="#s1-users-groups-shadow-utilities">15.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="#s1-users-groups-additional-resources">15.7. Additional Reso
urces</a></span></dt></dl></div><a id="id518298" class="indexterm"></a><a id="id758611" class="indexterm"></a><a id="id442980" class="indexterm"></a><a id="id689256" class="indexterm"></a><div class="para">
+ The control of <em class="firstterm">users</em> and <em class="firstterm">groups</em> is a core element of Fedora system administration.
+ </div><div class="para">
+ <em class="firstterm">Users</em> can be either people (meaning accounts tied to physical users) or accounts which exist for specific applications to use.
+ </div><div class="para">
+ <em class="firstterm">Groups</em> are logical expressions of organization, tying users together for a common purpose. Users within a group can read, write, or execute files owned by that group.
+ </div><div class="para">
+ Each user is associated with a unique numerical identification number called a <em class="firstterm">userid</em> (<em class="firstterm">UID</em>); likewise, each group is associated with a <em class="firstterm">groupid</em> (<em class="firstterm">GID</em>).
+ </div><div class="para">
+ A user who creates a file is also the owner and group owner of that file. The file is assigned separate read, write, and execute permissions for the owner, the group, and everyone else. The file owner can be changed only by the root user, and access permissions can be changed by both the root user and file owner.
+ </div><div class="para">
+ Fedora also supports <em class="firstterm">access control lists</em> (<em class="firstterm">ACLs</em>) for files and directories which allow permissions for specific users outside of the owner to be set.
+ </div><div class="section" title="15.1. User and Group Configuration" id="s1-users-configui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-configui">15.1. User and Group Configuration</h2></div></div></div><a id="id697963" class="indexterm"></a><a id="id824641" class="indexterm"></a><a id="id824655" class="indexterm"></a><a id="id553349" class="indexterm"></a><a id="id553362" class="indexterm"></a><a id="id790005" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>User Manager</strong></span> allows you to view, modify, add, and delete local users and groups.
+ </div><div class="figure" title="Figure 15.1. The GNOME User Manager" id="fig-Users_Groups-User_Manager"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Users_Groups-User_Manager.png" align="middle" alt="The GNOME User Manager" /><div class="longdesc"><div class="para">
+ the gnome user manager lets you manage users
+ </div></div></div></div><h6>Figure 15.1. The GNOME <span class="application">User Manager</span> </h6></div><br class="figure-break" /><div class="para">
+ You can start the <span class="application"><strong>User Manager</strong></span> by clicking <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Users and Groups</strong></span>. Alternatively, you can enter <code class="command">system-config-users</code> at the shell prompt to open the <span class="application"><strong>User Manager</strong></span>. Viewing and modifying user and group information requires superuser privileges. If you are not the superuser when you open the <span class="application"><strong>User Manager</strong></span>, it will prompt you for the superuser password.
+ </div><a id="id843102" class="indexterm"></a><a id="id843116" class="indexterm"></a><div class="para">
+ To view a list of local users on the system, click the <span class="guilabel"><strong>Users</strong></span> tab. To view a list of local groups on the system, click the <span class="guilabel"><strong>Groups</strong></span> tab.
+ </div><div class="para">
+ To find a specific user or group, type the first few letters of the name in the <span class="guilabel"><strong>Search filter</strong></span> field. Press <span class="keycap"><strong>Enter</strong></span> or click the <span class="guibutton"><strong>Apply filter</strong></span> button. The filtered list is displayed.
+ </div><div class="para">
+ To sort the users, click on the column User Name and for groups click on Group Name. The users or groups are sorted according to the value of that column.
+ </div><div class="para">
+ Fedora reserves user IDs below 500 for system users. By default, the <span class="application"><strong>User Manager</strong></span> does not display system users. To view all users, including the system users, go to <span class="guimenuitem"><strong>Edit</strong></span> > <span class="guimenuitem"><strong>Preferences</strong></span> and uncheck <span class="guimenuitem"><strong>Hide system users and groups</strong></span> from the dialog box.
+ </div><div class="section" title="15.1.1. Adding a New User" id="s2-redhat-config-users-user-new"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-redhat-config-users-user-new">15.1.1. Adding a New User</h3></div></div></div><a id="id429473" class="indexterm"></a><div class="para">
+ To add a new user, click the <span class="guibutton"><strong>Add User</strong></span> button. A window as shown in <a class="xref" href="#user-new-fig" title="Figure 15.2. Creating a new user">Figure 15.2, “Creating a new user”</a> appears. Type the username and full name for the new user in the appropriate fields. Type the user's password in the <span class="guilabel"><strong>Password</strong></span> and <span class="guilabel"><strong>Confirm Password</strong></span> fields. The password must be at least six characters.
+ </div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ It is advisable to use a much longer password, as this makes it more difficult for an intruder to guess it and access the account without permission. It is also recommended that the password not be based on a dictionary term; use a combination of letters, numbers and special characters.
+ </div></div></div><div class="para">
+ Select a login shell from the pulldown list. If you are not sure which shell to select, accept the default value of <code class="computeroutput">/bin/bash</code>. The default home directory is <code class="filename">/home/<em class="replaceable"><code><username></code></em>/</code>. You can change the home directory that is created for the user, or you can choose not to create the home directory by unselecting <span class="guilabel"><strong>Create home directory</strong></span>.
+ </div><div class="para">
+ If you select to create the home directory, default configuration files are copied from the <code class="filename">/etc/skel/</code> directory into the new home directory.
+ </div><div class="para">
+ Fedora uses a <em class="firstterm">user private group</em> (UPG) scheme. The UPG scheme does not add or change anything in the standard UNIX way of handling groups; it offers a new convention. Whenever you create a new user, by default, a unique group with the same name as the user is created. If you do not want to create this group, unselect <span class="guilabel"><strong>Create a private group for the user</strong></span>.
+ </div><div class="para">
+ To specify a user ID for the user, select <span class="guibutton"><strong>Specify user ID manually</strong></span>. If the option is not selected, the next available user ID above 500 is assigned to the new user. Because Fedora reserves user IDs below 500 for system users, it is not advisable to manually assign user IDs 1-499.
+ </div><div class="para">
+ Click <span class="guibutton"><strong>OK</strong></span> to create the user.
+ </div><div class="figure" title="Figure 15.2. Creating a new user" id="user-new-fig"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Users_Groups-Create_New_User.png" align="middle" alt="Creating a new user" /><div class="longdesc"><div class="para">
+ creating a new user with the create new user dialog
+ </div></div></div></div><h6>Figure 15.2. Creating a new user</h6></div><br class="figure-break" /><div class="para">
+ To configure more advanced user properties, such as password expiration, modify the user's properties after adding the user.
+ </div><h4 id="id682629">Modifying User Properties</h4><a id="id682633" class="indexterm"></a><a id="id682647" class="indexterm"></a><div class="para">
+ To view the properties of an existing user, click on the <span class="guilabel"><strong>Users</strong></span> tab, select the user from the user list, and click <span class="guibutton"><strong>Properties</strong></span> from the menu (or choose <span class="guimenu"><strong>File</strong></span> > <span class="guimenuitem"><strong>Properties</strong></span> from the pulldown menu). A window similar to <a class="xref" href="#user-properties-fig" title="Figure 15.3. User Properties">Figure 15.3, “User Properties”</a> appears.
+ </div><div class="figure" title="Figure 15.3. User Properties" id="user-properties-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/user-properties.png" alt="User Properties" /><div class="longdesc"><div class="para">
+ Modifying user properties
+ </div></div></div></div><h6>Figure 15.3. User Properties</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>User Properties</strong></span> window is divided into multiple tabbed pages:
+ </div><a id="id580261" class="indexterm"></a><a id="id580275" class="indexterm"></a><a id="id580288" class="indexterm"></a><a id="id580302" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>User Data</strong></span> — Shows the basic user information configured when you added the user. Use this tab to change the user's full name, password, home directory, or login shell.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Account Info</strong></span> — Select <span class="guibutton"><strong>Enable account expiration</strong></span> if you want the account to expire on a certain date. Enter the date in the provided fields. Select <span class="guilabel"><strong>Local password is locked</strong></span> to lock the user account and prevent the user from logging into the system.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Password Info</strong></span> — Displays the date that the user's password last changed. To force the user to change passwords after a certain number of days, select <span class="guilabel"><strong>Enable password expiration</strong></span> and enter a desired value in the <span class="guilabel"><strong>Days before change required:</strong></span> field. The number of days before the user's password expires, the number of days before the user is warned to change passwords, and days before the account becomes inactive can also be changed.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Groups</strong></span> — Allows you to view and configure the Primary Group of the user, as well as other groups that you want the user to be a member of.
+ </div></li></ul></div></div><div class="section" title="15.1.2. Adding a New Group" id="s2-redhat-config-users-group-new"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-redhat-config-users-group-new">15.1.2. Adding a New Group</h3></div></div></div><a id="id600550" class="indexterm"></a><div class="para">
+ To add a new user group, select <span class="guibutton"><strong>Add Group</strong></span> from the toolbar. A window similar to <a class="xref" href="#group-new-fig" title="Figure 15.4. New Group">Figure 15.4, “New Group”</a> appears. Type the name of the new group. To specify a group ID for the new group, select <span class="guibutton"><strong>Specify group ID manually</strong></span> and select the GID. Note that Fedora also reserves group IDs lower than 500 for system groups.
+ </div><div class="figure" title="Figure 15.4. New Group" id="group-new-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/group-new.png" alt="New Group" /><div class="longdesc"><div class="para">
+ Creating a new group
+ </div></div></div></div><h6>Figure 15.4. New Group</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>OK</strong></span> to create the group. The new group appears in the group list.
+ </div></div><div class="section" title="15.1.3. Modifying Group Properties" id="s2-redhat-config-users-group-properties"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-redhat-config-users-group-properties">15.1.3. Modifying Group Properties</h3></div></div></div><a id="id496851" class="indexterm"></a><div class="para">
+ To view the properties of an existing group, select the group from the group list and click <span class="guibutton"><strong>Properties</strong></span> from the menu (or choose <span class="guimenu"><strong>File</strong></span> > <span class="guimenuitem"><strong>Properties</strong></span> from the pulldown menu). A window similar to <a class="xref" href="#group-properties-fig" title="Figure 15.5. Group Properties">Figure 15.5, “Group Properties”</a> appears.
+ </div><div class="figure" title="Figure 15.5. Group Properties" id="group-properties-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/group-properties.png" alt="Group Properties" /><div class="longdesc"><div class="para">
+ Modifying group properties
+ </div></div></div></div><h6>Figure 15.5. Group Properties</h6></div><br class="figure-break" /><a id="id626695" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Group Users</strong></span> tab displays which users are members of the group. Use this tab to add or remove users from the group. Click <span class="guibutton"><strong>OK</strong></span> to save your changes.
+ </div></div></div><div class="section" title="15.2. User and Group Management Tools" id="s1-users-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-tools">15.2. User and Group Management Tools</h2></div></div></div><a id="id619090" class="indexterm"></a><a id="id619111" class="indexterm"></a><a id="id443207" class="indexterm"></a><a id="id443229" class="indexterm"></a><div class="para">
+ Managing users and groups can be tiresome; this is why Fedora provides tools and conventions to make this task easier to manage.
+ </div><div class="para">
+ The easiest way to manage users and groups is through the graphical application, <span class="application"><strong>User Manager</strong></span> (<code class="command">system-config-users</code>). For more information on <span class="application"><strong>User Manager</strong></span>, refer to <a class="xref" href="#s1-users-configui" title="15.1. User and Group Configuration">Section 15.1, “User and Group Configuration”</a>.
+ </div><div class="para">
+ The following command line tools can also be used to manage users and groups:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">useradd</code>, <code class="command">usermod</code>, and <code class="command">userdel</code> — Industry-standard methods of adding, deleting and modifying user accounts
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">groupadd</code>, <code class="command">groupmod</code>, and <code class="command">groupdel</code> — Industry-standard methods of adding, deleting, and modifying user groups
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">gpasswd</code> — Industry-standard method of administering the <code class="filename">/etc/group</code> file
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pwck</code>, <code class="command">grpck</code> — Tools used for the verification of the password, group, and associated shadow files
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pwconv</code>, <code class="command">pwunconv</code> — Tools used for the conversion of passwords to shadow passwords and back to standard passwords
+ </div></li></ul></div><div class="section" title="15.2.1. Command Line Configuration" id="s2-users-cmd-line"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-users-cmd-line">15.2.1. Command Line Configuration</h3></div></div></div><a id="id628391" class="indexterm"></a><a id="id628405" class="indexterm"></a><a id="id628422" class="indexterm"></a><div class="para">
+ If you prefer command line tools or do not have the X Window System installed, use following to configure users and groups.
+ </div><h4 id="id628441">Adding a User</h4><div class="para">
+ To add a user to the system:
+ </div><a id="id763132" class="indexterm"></a><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Issue the <code class="command">useradd</code> command to create a locked user account:
+ </div><pre class="screen">
+<code class="command">useradd <em class="replaceable"><code><username></code></em> </code>
+</pre></li><li class="listitem"><div class="para">
+ <a id="id763191" class="indexterm"></a>
+ Unlock the account by issuing the <code class="command">passwd</code> command to assign a password and set password aging guidelines:
+ </div><pre class="screen">
+<code class="command">passwd <em class="replaceable"><code><username></code></em> </code>
+</pre></li></ol></div><div class="para">
+ Command line options for <code class="command">useradd</code> are detailed in <a class="xref" href="#table-useradd-options" title="Table 15.1. useradd Command Line Options">Table 15.1, “ <code class="command">useradd</code> Command Line Options”</a>.
+ </div><div class="table" title="Table 15.1. useradd Command Line Options" id="table-useradd-options"><h6>Table 15.1. <code class="command">useradd</code> Command Line Options</h6><div class="table-contents"><table summary=" useradd Command Line Options" border="1"><colgroup><col width="29%" /><col width="71%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-c</code> '<em class="replaceable"><code><comment></code></em>'
+ </td><td>
+ <em class="replaceable"><code><comment></code></em> can be replaced with any string. This option is generally used to specify the full name of a user.
+ </td></tr><tr><td>
+ <code class="option">-d</code> <em class="replaceable"><code><home-dir></code></em>
+ </td><td>
+ Home directory to be used instead of default <code class="filename">/home/<em class="replaceable"><code><username></code></em>/</code>
+ </td></tr><tr><td>
+ <code class="option">-e</code> <em class="replaceable"><code><date></code></em>
+ </td><td>
+ Date for the account to be disabled in the format YYYY-MM-DD
+ </td></tr><tr><td>
+ <code class="option">-f</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Number of days after the password expires until the account is disabled. If <strong class="userinput"><code>0</code></strong> is specified, the account is disabled immediately after the password expires. If <strong class="userinput"><code>-1</code></strong> is specified, the account is not be disabled after the password expires.
+ </td></tr><tr><td>
+ <code class="option">-g</code> <em class="replaceable"><code><group-name></code></em>
+ </td><td>
+ Group name or group number for the user's default group. The group must exist prior to being specified here.
+ </td></tr><tr><td>
+ <code class="option">-G</code> <em class="replaceable"><code><group-list></code></em>
+ </td><td>
+ List of additional (other than default) group names or group numbers, separated by commas, of which the user is a member. The groups must exist prior to being specified here.
+ </td></tr><tr><td>
+ <code class="option">-m</code>
+ </td><td>
+ Create the home directory if it does not exist.
+ </td></tr><tr><td>
+ <code class="option">-M</code>
+ </td><td>
+ Do not create the home directory.
+ </td></tr><tr><td>
+ <code class="option">-N</code>
+ </td><td>
+ Do not create a user private group for the user.
+ </td></tr><tr><td>
+ <code class="option">-p</code> <em class="replaceable"><code><password></code></em>
+ </td><td>
+ The password encrypted with <code class="command">crypt</code>
+ </td></tr><tr><td>
+ <code class="option">-r</code>
+ </td><td>
+ Create a system account with a UID less than 500 and without a home directory
+ </td></tr><tr><td>
+ <code class="option">-s</code>
+ </td><td>
+ User's login shell, which defaults to <code class="filename">/bin/bash</code>
+ </td></tr><tr><td>
+ <code class="option">-u</code> <em class="replaceable"><code><uid></code></em>
+ </td><td>
+ User ID for the user, which must be unique and greater than 499
+ </td></tr></tbody></table></div></div><br class="table-break" /><h4 id="id1045419">Adding a Group</h4><a id="id1045423" class="indexterm"></a><a id="id1045444" class="indexterm"></a><div class="para">
+ To add a group to the system, use the command <code class="command">groupadd</code>:
+ </div><pre class="screen">
+<code class="command">groupadd <em class="replaceable"><code><group-name></code></em> </code>
+</pre><div class="para">
+ Command line options for <code class="command">groupadd</code> are detailed in <a class="xref" href="#table-groupadd-options" title="Table 15.2. groupadd Command Line Options">Table 15.2, “ <code class="command">groupadd</code> Command Line Options”</a>.
+ </div><div class="table" title="Table 15.2. groupadd Command Line Options" id="table-groupadd-options"><h6>Table 15.2. <code class="command">groupadd</code> Command Line Options</h6><div class="table-contents"><table summary=" groupadd Command Line Options" border="1"><colgroup><col width="29%" /><col width="71%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ -f, --force
+ </td><td>
+ When used with <code class="option">-g</code> <em class="replaceable"><code><gid></code></em> and <em class="replaceable"><code><gid></code></em> already exists, <code class="command">groupadd</code> will choose another unique <em class="replaceable"><code><gid></code></em> for the group.
+ </td></tr><tr><td>
+ <code class="option">-g</code> <em class="replaceable"><code><gid></code></em>
+ </td><td>
+ Group ID for the group, which must be unique and greater than 499
+ </td></tr><tr><td>
+ <code class="option">-K, --key KEY=VALUE</code>
+ </td><td>
+ override <code class="code">/etc/login.defs</code> defaults
+ </td></tr><tr><td>
+ <code class="option">-o</code>, <code class="option">--non-unique</code>
+ </td><td>
+ allow to create groups with duplicate
+ </td></tr><tr><td>
+ <code class="option">-p</code>, <code class="option">--password</code> <code class="option">PASSWORD</code>
+ </td><td>
+ use this encrypted password for the new group
+ </td></tr><tr><td>
+ <code class="option">-r</code>
+ </td><td>
+ Create a system group with a GID less than 500
+ </td></tr></tbody></table></div></div><br class="table-break" /><h4 id="id447641">Password Aging</h4><a id="id447645" class="indexterm"></a><a id="id443959" class="indexterm"></a><a id="id443974" class="indexterm"></a><a id="id443984" class="indexterm"></a><a id="id444005" class="indexterm"></a><div class="para">
+ For security reasons, it is advisable to require users to change their passwords periodically. This can be done when adding or editing a user on the <span class="guilabel"><strong>Password Info</strong></span> tab of the <span class="application"><strong>User Manager</strong></span>.
+ </div><div class="para">
+ To configure password expiration for a user from a shell prompt, use the <code class="command">chage</code> command with an option from <a class="xref" href="#table-chage-options" title="Table 15.3. chage Command Line Options">Table 15.3, “ <code class="command">chage</code> Command Line Options”</a>, followed by the username.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Shadow passwords must be enabled to use the <code class="command">chage</code> command. For more information, see <a class="xref" href="#s1-users-groups-shadow-utilities" title="15.6. Shadow Passwords">Section 15.6, “Shadow Passwords”</a>.
+ </div></div></div><div class="table" title="Table 15.3. chage Command Line Options" id="table-chage-options"><h6>Table 15.3. <code class="command">chage</code> Command Line Options</h6><div class="table-contents"><table summary=" chage Command Line Options" border="1"><colgroup><col width="29%" /><col width="71%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-d</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Specifies the number of days since January 1, 1970 the password was changed
+ </td></tr><tr><td>
+ <code class="option">-E</code> <em class="replaceable"><code><date></code></em>
+ </td><td>
+ Specifies the date on which the account is locked, in the format YYYY-MM-DD. Instead of the date, the number of days since January 1, 1970 can also be used.
+ </td></tr><tr><td>
+ <code class="option">-I</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Specifies the number of inactive days after the password expiration before locking the account. If the value is 0, the account is not locked after the password expires.
+ </td></tr><tr><td>
+ <code class="option">-l</code>
+ </td><td>
+ Lists current account aging settings.
+ </td></tr><tr><td>
+ <code class="option">-m</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Specify the minimum number of days after which the user must change passwords. If the value is 0, the password does not expire.
+ </td></tr><tr><td>
+ <code class="option">-M</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Specify the maximum number of days for which the password is valid. When the number of days specified by this option plus the number of days specified with the <code class="option">-d</code> option is less than the current day, the user must change passwords before using the account.
+ </td></tr><tr><td>
+ <code class="option">-W</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Specifies the number of days before the password expiration date to warn the user.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ If the <code class="command">chage</code> command is followed directly by a username (with no options), it displays the current password aging values and allows them to be changed interactively.
+ </div></div></div><div class="para">
+ You can configure a password to expire the first time a user logs in. This forces users to change passwords immediately.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Set up an initial password</em></span> — There are two common approaches to this step. The administrator can assign a default password or assign a null password.
+ </div><div class="para">
+ To assign a default password, use the following steps:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Start the command line Python interpreter with the <code class="command">python</code> command. It displays the following:
+ </div><pre class="screen">
+Python 2.4.3 (#1, Jul 21 2006, 08:46:09)
+[GCC 4.1.1 20060718 (Application Stack 4.1.1-9)] on linux2
+Type "help", "copyright", "credits" or "license" for more information.
+>>></pre></li><li class="listitem"><div class="para">
+ At the prompt, type the following commands. Replace <em class="replaceable"><code><password></code></em> with the password to encrypt and <em class="replaceable"><code><salt></code></em> with a random combination of at least 2 of the following: any alphanumeric character, the slash (/) character or a dot (.):
+ </div><pre class="screen">
+<code class="command">import crypt; print crypt.crypt("<em class="replaceable"><code><password></code></em>","<em class="replaceable"><code><salt></code></em>")</code>
+</pre><div class="para">
+ The output is the encrypted password, similar to <code class="computeroutput">'12CsGd8FRcMSM'</code>.
+ </div></li><li class="listitem"><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>-<span class="keycap"><strong>D</strong></span> to exit the Python interpreter.
+ </div></li><li class="listitem"><div class="para">
+ At the shell, enter the following command (replacing <em class="replaceable"><code><encrypted-password></code></em> with the encrypted output of the Python interpreter):
+ </div><pre class="screen">usermod -p "<em class="replaceable"><code><encrypted-password></code></em>" <em class="replaceable"><code><username></code></em>
+</pre></li></ul></div><div class="para">
+ Alternatively, you can assign a null password instead of an initial password. To do this, use the following command:
+ </div><pre class="screen">usermod -p "" <em class="replaceable"><code>username</code></em>
+</pre><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Using a null password, while convenient, is a highly unsecure practice, as any third party can log in first and access the system using the unsecure username. Always make sure that the user is ready to log in before unlocking an account with a null password.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Force immediate password expiration</em></span> — Type the following command:
+ </div><pre class="screen">chage -d 0 <em class="replaceable"><code>username</code></em>
+</pre><div class="para">
+ This command sets the value for the date the password was last changed to the epoch (January 1, 1970). This value forces immediate password expiration no matter what password aging policy, if any, is in place.
+ </div></li></ol></div><div class="para">
+ Upon the initial log in, the user is now prompted for a new password.
+ </div></div><div class="section" title="15.2.2. Explaining the Process" id="s2-redhat-config-users-process"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-redhat-config-users-process">15.2.2. Explaining the Process</h3></div></div></div><div class="para">
+ The following steps illustrate what happens if the command <code class="command">useradd juan</code> is issued on a system that has shadow passwords enabled:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ A new line for <code class="computeroutput">juan</code> is created in <code class="filename">/etc/passwd</code>.
+<pre class="screen"><code class="code">juan:x:501:501::/home/juan:/bin/bash</code>
+</pre>
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ It begins with the username <code class="computeroutput">juan</code>.
+ </div></li><li class="listitem"><div class="para">
+ There is an <code class="computeroutput">x</code> for the password field indicating that the system is using shadow passwords.
+ </div></li><li class="listitem"><div class="para">
+ A UID greater than 499 is created. Under Fedora. UIDs and GIDs below 500 are reserved for system use. These should not be assigned to users.
+ </div></li><li class="listitem"><div class="para">
+ A GID greater than 499 is created.
+ </div></li><li class="listitem"><div class="para">
+ The optional GECOS information is left blank.
+ </div></li><li class="listitem"><div class="para">
+ The home directory for <code class="computeroutput">juan</code> is set to <code class="filename">/home/juan/</code>.
+ </div></li><li class="listitem"><div class="para">
+ The default shell is set to <code class="command">/bin/bash</code>.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ A new line for <code class="computeroutput">juan</code> is created in <code class="filename">/etc/shadow</code>.
+<pre class="screen"><code class="code">juan:!!:14798:0:99999:7:::</code>
+</pre>
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ It begins with the username <code class="computeroutput">juan</code>.
+ </div></li><li class="listitem"><div class="para">
+ Two exclamation points (<code class="computeroutput">!!</code>) appear in the password field of the <code class="filename">/etc/shadow</code> file, which locks the account.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If an encrypted password is passed using the <code class="option">-p</code> flag, it is placed in the <code class="filename">/etc/shadow</code> file on the new line for the user.
+ </div></div></div></li><li class="listitem"><div class="para">
+ The password is set to never expire.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ A new line for a group named <code class="computeroutput">juan</code> is created in <code class="filename">/etc/group</code>.
+<pre class="screen"><code class="code">juan:x:501:</code>
+</pre>
+ A group with the same name as a user is called a <em class="firstterm">user private group</em>. For more information on user private groups, refer to <a class="xref" href="#s2-redhat-config-users-user-new" title="15.1.1. Adding a New User">Section 15.1.1, “Adding a New User”</a>.
+ </div><div class="para">
+ The line created in <code class="filename">/etc/group</code> has the following characteristics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ It begins with the group name <code class="computeroutput">juan</code>.
+ </div></li><li class="listitem"><div class="para">
+ An <code class="computeroutput">x</code> appears in the password field indicating that the system is using shadow group passwords.
+ </div></li><li class="listitem"><div class="para">
+ The GID matches the one listed for user <code class="computeroutput">juan</code> in <code class="filename">/etc/passwd</code>.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ A new line for a group named <code class="computeroutput">juan</code> is created in <code class="filename">/etc/gshadow</code>.
+<pre class="screen"><code class="code">juan:!::</code>
+</pre>
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ It begins with the group name <code class="computeroutput">juan</code>.
+ </div></li><li class="listitem"><div class="para">
+ An exclamation point (<code class="computeroutput">!</code>) appears in the password field of the <code class="filename">/etc/gshadow</code> file, which locks the group.
+ </div></li><li class="listitem"><div class="para">
+ All other fields are blank.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ A directory for user <code class="computeroutput">juan</code> is created in the <code class="filename">/home/</code> directory.
+<pre class="screen"><code class="code">ls -l /home</code>
+ <code class="code">drwx------. 4 juan juan 4096 Jul 9 14:55 juan</code>
+</pre>
+ This directory is owned by user <code class="computeroutput">juan</code> and group <code class="computeroutput">juan</code>. It has <span class="emphasis"><em>read</em></span>, <span class="emphasis"><em>write</em></span>, and <span class="emphasis"><em>execute</em></span> privileges <span class="emphasis"><em>only</em></span> for the user <code class="computeroutput">juan</code>. All other permissions are denied.
+ </div></li><li class="listitem"><div class="para">
+ The files within the <code class="filename">/etc/skel/</code> directory (which contain default user settings) are copied into the new <code class="filename">/home/juan/</code> directory.
+<pre class="screen"><code class="code"></code>
+</pre>
+
+ </div></li></ol></div><div class="para">
+ At this point, a locked account called <code class="computeroutput">juan</code> exists on the system. To activate it, the administrator must next assign a password to the account using the <code class="command">passwd</code> command and, optionally, set password aging guidelines.
+ </div></div></div><div class="section" title="15.3. Standard Users" id="s1-users-groups-standard-users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-groups-standard-users">15.3. Standard Users</h2></div></div></div><a id="id749386" class="indexterm"></a><a id="id749400" class="indexterm"></a><div class="para">
+ <a class="xref" href="#tb-users-groups-group-use" title="Table 15.4. Standard Users">Table 15.4, “Standard Users”</a> lists the standard users configured in the <code class="filename">/etc/passwd</code> file by an <span class="guilabel"><strong>Everything</strong></span> installation. The groupid (GID) in this table is the <span class="emphasis"><em>primary group</em></span> for the user. See <a class="xref" href="#s1-users-groups-standard-groups" title="15.4. Standard Groups">Section 15.4, “Standard Groups”</a> for a listing of standard groups.
+ </div><div class="table" title="Table 15.4. Standard Users" id="tb-users-groups-group-use"><h6>Table 15.4. Standard Users</h6><div class="table-contents"><table summary="Standard Users" border="1"><colgroup><col align="left" width="17%" /><col align="left" width="17%" /><col align="left" width="17%" /><col align="left" width="17%" /><col align="left" width="17%" /><col align="left" width="17%" /></colgroup><thead><tr><th align="left">
+ User
+ </th><th align="left">
+ UID
+ </th><th align="left">
+ GID
+ </th><th align="left">
+ Home Directory
+ </th><th align="left">
+ Shell
+ </th><th align="left">
+ Packages
+ </th></tr></thead><tbody><tr><td align="left">
+ root
+ </td><td align="left">
+ 0
+ </td><td align="left">
+ 0
+ </td><td align="left">
+ /root
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ bin
+ </td><td align="left">
+ 1
+ </td><td align="left">
+ 1
+ </td><td align="left">
+ /bin
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ daemon
+ </td><td align="left">
+ 2
+ </td><td align="left">
+ 2
+ </td><td align="left">
+ /sbin
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ sys
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 3
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ adm
+ </td><td align="left">
+ 3
+ </td><td align="left">
+ 4
+ </td><td align="left">
+ /var/adm
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ tty
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 5
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ disk
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 6
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ lp
+ </td><td align="left">
+ 4
+ </td><td align="left">
+ 7
+ </td><td align="left">
+ /var/spool/lpd
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ mem
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 8
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ kmem
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 9
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ wheel
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 10
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ cdrom
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 11
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">udev,MAKEDEV</code>
+ </td></tr><tr><td align="left">
+ sync
+ </td><td align="left">
+ 5
+ </td><td align="left">
+ (0)
+ </td><td align="left">
+ /sbin
+ </td><td align="left">
+ <code class="filename">/bin/sync</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ shutdown
+ </td><td align="left">
+ 6
+ </td><td align="left">
+ (0)
+ </td><td align="left">
+ /sbin
+ </td><td align="left">
+ <code class="filename">/sbin/shutdown</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ halt
+ </td><td align="left">
+ 7
+ </td><td align="left">
+ (0)
+ </td><td align="left">
+ /sbin
+ </td><td align="left">
+ <code class="filename">/sbin/halt</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ mail
+ </td><td align="left">
+ 8
+ </td><td align="left">
+ 12
+ </td><td align="left">
+ /var/spool/mail
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ news
+ </td><td align="left">
+ 9
+ </td><td align="left">
+ 13
+ </td><td align="left">
+ /var/spool/news
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ uucp
+ </td><td align="left">
+ 10
+ </td><td align="left">
+ 14
+ </td><td align="left">
+ /var/spool/uucp
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ operator
+ </td><td align="left">
+ 11
+ </td><td align="left">
+ (0)
+ </td><td align="left">
+ /root
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ games
+ </td><td align="left">
+ 12
+ </td><td align="left">
+ (100)
+ </td><td align="left">
+ /usr/games
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ gopher
+ </td><td align="left">
+ 13
+ </td><td align="left">
+ 30
+ </td><td align="left">
+ /usr/lib/gopher-data
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ ftp
+ </td><td align="left">
+ 14
+ </td><td align="left">
+ 50
+ </td><td align="left">
+ /var/ftp
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ man
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 15
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ oprofile
+ </td><td align="left">
+ 16
+ </td><td align="left">
+ 16
+ </td><td align="left">
+ /home/oprofile
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">oprofile</code>
+ </td></tr><tr><td align="left">
+ pkiuser
+ </td><td align="left">
+ 17
+ </td><td align="left">
+ 17
+ </td><td align="left">
+ /usr/share/pki
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">pki-ca,rhpki-ca</code>
+ </td></tr><tr><td align="left">
+ dialout
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 18
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">udev,MAKEDEV</code>
+ </td></tr><tr><td align="left">
+ floppy
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 19
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">dev,MAKEDEV</code>
+ </td></tr><tr><td align="left">
+ games
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 20
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ slocate
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 21
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">slocate</code>
+ </td></tr><tr><td align="left">
+ utmp
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 22
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">initscripts,libutempter</code>
+ </td></tr><tr><td align="left">
+ squid
+ </td><td align="left">
+ 23
+ </td><td align="left">
+ 23
+ </td><td align="left">
+ /var/spool/squid
+ </td><td align="left">
+ <code class="filename">/dev/null</code>
+ </td><td align="left">
+ <code class="command">squid</code>
+ </td></tr><tr><td align="left">
+ pvm
+ </td><td align="left">
+ 24
+ </td><td align="left">
+ 24
+ </td><td align="left">
+ /usr/share/pvm3
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">pvm</code>
+ </td></tr><tr><td align="left">
+ named
+ </td><td align="left">
+ 25
+ </td><td align="left">
+ 25
+ </td><td align="left">
+ /var/named
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">bind</code>
+ </td></tr><tr><td align="left">
+ postgres
+ </td><td align="left">
+ 26
+ </td><td align="left">
+ 26
+ </td><td align="left">
+ /var/lib/pgsql
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">postgresql-server</code>
+ </td></tr><tr><td align="left">
+ mysql
+ </td><td align="left">
+ 27
+ </td><td align="left">
+ 27
+ </td><td align="left">
+ /var/lib/mysql
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">mysql</code>
+ </td></tr><tr><td align="left">
+ nscd
+ </td><td align="left">
+ 28
+ </td><td align="left">
+ 28
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">nscd</code>
+ </td></tr><tr><td align="left">
+ rpcuser
+ </td><td align="left">
+ 29
+ </td><td align="left">
+ 29
+ </td><td align="left">
+ /var/lib/nfs
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">nfs-utils</code>
+ </td></tr><tr><td align="left">
+ console
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 31
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">dev</code>
+ </td></tr><tr><td align="left">
+ rpc
+ </td><td align="left">
+ 32
+ </td><td align="left">
+ 32
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">portmap</code>
+ </td></tr><tr><td align="left">
+ amanda
+ </td><td align="left">
+ 33
+ </td><td align="left">
+ (6)
+ </td><td align="left">
+ /var/lib/amanda
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">amanda</code>
+ </td></tr><tr><td align="left">
+ tape
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 33
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">udev,MAKEDEV</code>
+ </td></tr><tr><td align="left">
+ netdump
+ </td><td align="left">
+ 34
+ </td><td align="left">
+ 34
+ </td><td align="left">
+ /var/crash
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">netdump-client, netdump-server</code>
+ </td></tr><tr><td align="left">
+ utempter
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 35
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">libutempter</code>
+ </td></tr><tr><td align="left">
+ vdsm
+ </td><td align="left">
+ 36
+ </td><td align="left">
+ -
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">kvm, vdsm</code>
+ </td></tr><tr><td align="left">
+ kvm
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 36
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">kvm, vdsm, libvirt</code>
+ </td></tr><tr><td align="left">
+ rpm
+ </td><td align="left">
+ 37
+ </td><td align="left">
+ 37
+ </td><td align="left">
+ /var/lib/rpm
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">rpm</code>
+ </td></tr><tr><td align="left">
+ ntp
+ </td><td align="left">
+ 38
+ </td><td align="left">
+ 38
+ </td><td align="left">
+ /etc/ntp
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">ntp</code>
+ </td></tr><tr><td align="left">
+ video
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 39
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ dip
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 40
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ mailman
+ </td><td align="left">
+ 41
+ </td><td align="left">
+ 41
+ </td><td align="left">
+ /var/mailman
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">mailman</code>
+ </td></tr><tr><td align="left">
+ gdm
+ </td><td align="left">
+ 42
+ </td><td align="left">
+ 42
+ </td><td align="left">
+ /var/gdm
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">gdm</code>
+ </td></tr><tr><td align="left">
+ xfs
+ </td><td align="left">
+ 43
+ </td><td align="left">
+ 43
+ </td><td align="left">
+ /etc/X11/fs
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">XFree86-xfs</code>
+ </td></tr><tr><td align="left">
+ pppusers
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 44
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">linuxconf</code>
+ </td></tr><tr><td align="left">
+ popusers
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 45
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">linuxconf</code>
+ </td></tr><tr><td align="left">
+ slipusers
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 46
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">linuxconf</code>
+ </td></tr><tr><td align="left">
+ mailnull
+ </td><td align="left">
+ 47
+ </td><td align="left">
+ 47
+ </td><td align="left">
+ /var/spool/mqueue
+ </td><td align="left">
+ <code class="filename">/dev/null</code>
+ </td><td align="left">
+ <code class="command">sendmail</code>
+ </td></tr><tr><td align="left">
+ apache
+ </td><td align="left">
+ 48
+ </td><td align="left">
+ 48
+ </td><td align="left">
+ /var/www
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">apache</code>
+ </td></tr><tr><td align="left">
+ wnn
+ </td><td align="left">
+ 49
+ </td><td align="left">
+ 49
+ </td><td align="left">
+ /home/wnn
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">FreeWnn</code>
+ </td></tr><tr><td align="left">
+ smmsp
+ </td><td align="left">
+ 51
+ </td><td align="left">
+ 51
+ </td><td align="left">
+ /var/spool/mqueue
+ </td><td align="left">
+ <code class="filename">/dev/null</code>
+ </td><td align="left">
+ <code class="command">sendmail</code>
+ </td></tr><tr><td align="left">
+ puppet
+ </td><td align="left">
+ 52
+ </td><td align="left">
+ 52
+ </td><td align="left">
+ /var/lib/puppet
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">puppet</code>
+ </td></tr><tr><td align="left">
+ tomcat
+ </td><td align="left">
+ 53
+ </td><td align="left">
+ 53
+ </td><td align="left">
+ /var/lib/tomcat
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">tomcat</code>
+ </td></tr><tr><td align="left">
+ lock
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 54
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">lockdev</code>
+ </td></tr><tr><td align="left">
+ ldap
+ </td><td align="left">
+ 55
+ </td><td align="left">
+ 55
+ </td><td align="left">
+ /var/lib/ldap
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">openldap-servers</code>
+ </td></tr><tr><td align="left">
+ frontpage
+ </td><td align="left">
+ 56
+ </td><td align="left">
+ 56
+ </td><td align="left">
+ /var/www
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">mod_frontpage</code>
+ </td></tr><tr><td align="left">
+ nut
+ </td><td align="left">
+ 57
+ </td><td align="left">
+ 57
+ </td><td align="left">
+ /var/lib/ups
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">nut</code>
+ </td></tr><tr><td align="left">
+ beagleindex
+ </td><td align="left">
+ 58
+ </td><td align="left">
+ 58
+ </td><td align="left">
+ /var/cache/beagle
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">beagle</code>
+ </td></tr><tr><td align="left">
+ tss
+ </td><td align="left">
+ 59
+ </td><td align="left">
+ 59
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">trousers</code>
+ </td></tr><tr><td align="left">
+ piranha
+ </td><td align="left">
+ 60
+ </td><td align="left">
+ 60
+ </td><td align="left">
+ /etc/sysconfig/ha
+ </td><td align="left">
+ <code class="filename">/dev/null</code>
+ </td><td align="left">
+ <code class="command">piranha</code>
+ </td></tr><tr><td align="left">
+ prelude-manager
+ </td><td align="left">
+ 61
+ </td><td align="left">
+ 61
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">prelude-manager</code>
+ </td></tr><tr><td align="left">
+ snortd
+ </td><td align="left">
+ 62
+ </td><td align="left">
+ 62
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">snortd</code>
+ </td></tr><tr><td align="left">
+ audio
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 63
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ condor
+ </td><td align="left">
+ 64
+ </td><td align="left">
+ 64
+ </td><td align="left">
+ /var/lib/condor
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">condord</code>
+ </td></tr><tr><td align="left">
+ nslcd
+ </td><td align="left">
+ 65
+ </td><td align="left">
+ (55)
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">nslcd</code>
+ </td></tr><tr><td align="left">
+ wine
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 66
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">wine</code>
+ </td></tr><tr><td align="left">
+ pegasus
+ </td><td align="left">
+ 66
+ </td><td align="left">
+ 65
+ </td><td align="left">
+ /var/lib/Pegasus
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">tog-pegasus</code>
+ </td></tr><tr><td align="left">
+ webalizer
+ </td><td align="left">
+ 67
+ </td><td align="left">
+ 67
+ </td><td align="left">
+ /var/www/html/usage
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">webalizer</code>
+ </td></tr><tr><td align="left">
+ haldaemon
+ </td><td align="left">
+ 68
+ </td><td align="left">
+ 68
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">hal</code>
+ </td></tr><tr><td align="left">
+ vcsa
+ </td><td align="left">
+ 69
+ </td><td align="left">
+ 69
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">dev,MAKEDEV</code>
+ </td></tr><tr><td align="left">
+ avahi
+ </td><td align="left">
+ 70
+ </td><td align="left">
+ 70
+ </td><td align="left">
+ /var/run/avahi-daemon
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">avahi</code>
+ </td></tr><tr><td align="left">
+ realtime
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 71
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">-</code>
+ </td></tr><tr><td align="left">
+ tcpdump
+ </td><td align="left">
+ 72
+ </td><td align="left">
+ 72
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">tcpdump</code>
+ </td></tr><tr><td align="left">
+ privoxy
+ </td><td align="left">
+ 73
+ </td><td align="left">
+ 73
+ </td><td align="left">
+ /etc/privoxy
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">privoxy</code>
+ </td></tr><tr><td align="left">
+ sshd
+ </td><td align="left">
+ 74
+ </td><td align="left">
+ 74
+ </td><td align="left">
+ /var/empty/sshd
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">openssh-server</code>
+ </td></tr><tr><td align="left">
+ radvd
+ </td><td align="left">
+ 75
+ </td><td align="left">
+ 75
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">radvd</code>
+ </td></tr><tr><td align="left">
+ cyrus
+ </td><td align="left">
+ 76
+ </td><td align="left">
+ (12)
+ </td><td align="left">
+ /var/imap
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">cyrus-imapd</code>
+ </td></tr><tr><td align="left">
+ saslauth
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 76
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">cyrus-imapd</code>
+ </td></tr><tr><td align="left">
+ arpwatch
+ </td><td align="left">
+ 77
+ </td><td align="left">
+ 77
+ </td><td align="left">
+ /var/lib/arpwatch
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">arpwatch</code>
+ </td></tr><tr><td align="left">
+ fax
+ </td><td align="left">
+ 78
+ </td><td align="left">
+ 78
+ </td><td align="left">
+ /var/spool/fax
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">mgetty</code>
+ </td></tr><tr><td align="left">
+ nocpulse
+ </td><td align="left">
+ 79
+ </td><td align="left">
+ 79
+ </td><td align="left">
+ /etc/sysconfig/nocpulse
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">nocpulse</code>
+ </td></tr><tr><td align="left">
+ desktop
+ </td><td align="left">
+ 80
+ </td><td align="left">
+ 80
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">desktop-file-utils</code>
+ </td></tr><tr><td align="left">
+ dbus
+ </td><td align="left">
+ 81
+ </td><td align="left">
+ 81
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">dbus</code>
+ </td></tr><tr><td align="left">
+ jonas
+ </td><td align="left">
+ 82
+ </td><td align="left">
+ 82
+ </td><td align="left">
+ /var/lib/jonas
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">jonas</code>
+ </td></tr><tr><td align="left">
+ clamav
+ </td><td align="left">
+ 83
+ </td><td align="left">
+ 83
+ </td><td align="left">
+ /tmp
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">clamav</code>
+ </td></tr><tr><td align="left">
+ screen
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 84
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">screen</code>
+ </td></tr><tr><td align="left">
+ quaggavt
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 85
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">quagga</code>
+ </td></tr><tr><td align="left">
+ sabayon
+ </td><td align="left">
+ 86
+ </td><td align="left">
+ 86
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">sabayon</code>
+ </td></tr><tr><td align="left">
+ polkituser
+ </td><td align="left">
+ 87
+ </td><td align="left">
+ 87
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">PolicyKit</code>
+ </td></tr><tr><td align="left">
+ wbpriv
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 88
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">samba-common</code>
+ </td></tr><tr><td align="left">
+ postfix
+ </td><td align="left">
+ 89
+ </td><td align="left">
+ 89
+ </td><td align="left">
+ /var/spool/postfix
+ </td><td align="left">
+ <code class="filename">/bin/true</code>
+ </td><td align="left">
+ <code class="command">postfix</code>
+ </td></tr><tr><td align="left">
+ postdrop
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 90
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">postfix</code>
+ </td></tr><tr><td align="left">
+ majordomo
+ </td><td align="left">
+ 91
+ </td><td align="left">
+ 91
+ </td><td align="left">
+ /usr/lib/majordomo
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">majordomo</code>
+ </td></tr><tr><td align="left">
+ quagga
+ </td><td align="left">
+ 92
+ </td><td align="left">
+ 92
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">quagga</code>
+ </td></tr><tr><td align="left">
+ exim
+ </td><td align="left">
+ 93
+ </td><td align="left">
+ 93
+ </td><td align="left">
+ /var/spool/exim
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">exim</code>
+ </td></tr><tr><td align="left">
+ distcache
+ </td><td align="left">
+ 94
+ </td><td align="left">
+ 94
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">distcache</code>
+ </td></tr><tr><td align="left">
+ radiusd
+ </td><td align="left">
+ 95
+ </td><td align="left">
+ 95
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">freeradius</code>
+ </td></tr><tr><td align="left">
+ hsqldb
+ </td><td align="left">
+ 96
+ </td><td align="left">
+ 96
+ </td><td align="left">
+ /var/lib/hsqldb
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">hsqldb</code>
+ </td></tr><tr><td align="left">
+ dovecot
+ </td><td align="left">
+ 97
+ </td><td align="left">
+ 97
+ </td><td align="left">
+ /usr/libexec/dovecot
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">dovecot</code>
+ </td></tr><tr><td align="left">
+ ident
+ </td><td align="left">
+ 98
+ </td><td align="left">
+ 98
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">ident</code>
+ </td></tr><tr><td align="left">
+ nobody
+ </td><td align="left">
+ 99
+ </td><td align="left">
+ 99
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ users
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 100
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ qemu
+ </td><td align="left">
+ 107
+ </td><td align="left">
+ 107
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">libvirt</code>
+ </td></tr><tr><td align="left">
+ ovirt
+ </td><td align="left">
+ 108
+ </td><td align="left">
+ 108
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">libvirt</code>
+ </td></tr><tr><td align="left">
+ saned
+ </td><td align="left">
+ 111
+ </td><td align="left">
+ 111
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">sane-backends</code>
+ </td></tr><tr><td align="left">
+ vhostmd
+ </td><td align="left">
+ 112
+ </td><td align="left">
+ 112
+ </td><td align="left">
+ /usr/share/vhostmd
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">vhostmd</code>
+ </td></tr><tr><td align="left">
+ usbmuxd
+ </td><td align="left">
+ 113
+ </td><td align="left">
+ 113
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">usbmuxd</code>
+ </td></tr><tr><td align="left">
+ bacula
+ </td><td align="left">
+ 133
+ </td><td align="left">
+ 133
+ </td><td align="left">
+ /var/spool/bacula
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">bacula</code>
+ </td></tr><tr><td align="left">
+ ricci
+ </td><td align="left">
+ 140
+ </td><td align="left">
+ 140
+ </td><td align="left">
+ /var/lib/ricci
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">ricci</code>
+ </td></tr><tr><td align="left">
+ luci
+ </td><td align="left">
+ 141
+ </td><td align="left">
+ 141
+ </td><td align="left">
+ /var/lib/luci
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">luci</code>
+ </td></tr><tr><td align="left">
+ stap-server
+ </td><td align="left">
+ 155
+ </td><td align="left">
+ 155
+ </td><td align="left">
+ /var/lib/stap-server
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">systemtap</code>
+ </td></tr><tr><td align="left">
+ avahi-autoipd
+ </td><td align="left">
+ 170
+ </td><td align="left">
+ 170
+ </td><td align="left">
+ /var/lib/avahi-autoipd
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">avahi</code>
+ </td></tr><tr><td align="left">
+ pulse
+ </td><td align="left">
+ 171
+ </td><td align="left">
+ 171
+ </td><td align="left">
+ /var/run/pulse
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">pulseaudio</code>
+ </td></tr><tr><td align="left">
+ rtkit
+ </td><td align="left">
+ 172
+ </td><td align="left">
+ 172
+ </td><td align="left">
+ /proc
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">rtkit</code>
+ </td></tr><tr><td align="left">
+ nfsnobody
+ </td><td align="left">
+ 65534<sup>[<a id="id553982" href="#ftn.id553982" class="footnote">a</a>]</sup>
+ </td><td align="left">
+ 65534
+ </td><td align="left">
+ /var/lib/nfs
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">nfs-utils</code>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="6"><div class="footnote"><p><sup>[<a id="ftn.id553982" href="#id553982" class="para">a</a>] </sup>
+ nfsnobdy is 4294967294 on 64-bit platforms
+ </p></div></td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" title="15.4. Standard Groups" id="s1-users-groups-standard-groups"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-groups-standard-groups">15.4. Standard Groups</h2></div></div></div><a id="id485828" class="indexterm"></a><div class="para">
+ <a class="xref" href="#tb-users-groups-group-etc" title="Table 15.5. Standard Groups">Table 15.5, “Standard Groups”</a> lists the standard groups configured by an <span class="guilabel"><strong>Everything</strong></span> installation. Groups are stored in the <code class="filename">/etc/group</code> file.
+ </div><div class="table" title="Table 15.5. Standard Groups" id="tb-users-groups-group-etc"><h6>Table 15.5. Standard Groups</h6><div class="table-contents"><table summary="Standard Groups" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th>
+ Group
+ </th><th>
+ GID
+ </th><th>
+ Members
+ </th></tr></thead><tbody><tr><td>
+ root
+ </td><td>
+ 0
+ </td><td>
+ root
+ </td></tr><tr><td>
+ bin
+ </td><td>
+ 1
+ </td><td>
+ root, bin, daemon
+ </td></tr><tr><td>
+ daemon
+ </td><td>
+ 2
+ </td><td>
+ root, bin, daemon
+ </td></tr><tr><td>
+ sys
+ </td><td>
+ 3
+ </td><td>
+ root, bin, adm
+ </td></tr><tr><td>
+ adm
+ </td><td>
+ 4
+ </td><td>
+ root, adm, daemon
+ </td></tr><tr><td>
+ tty
+ </td><td>
+ 5
+ </td><td>
+ </td></tr><tr><td>
+ disk
+ </td><td>
+ 6
+ </td><td>
+ root
+ </td></tr><tr><td>
+ lp
+ </td><td>
+ 7
+ </td><td>
+ daemon, lp
+ </td></tr><tr><td>
+ mem
+ </td><td>
+ 8
+ </td><td>
+ </td></tr><tr><td>
+ kmem
+ </td><td>
+ 9
+ </td><td>
+ </td></tr><tr><td>
+ wheel
+ </td><td>
+ 10
+ </td><td>
+ root
+ </td></tr><tr><td>
+ mail
+ </td><td>
+ 12
+ </td><td>
+ mail, postfix
+ </td></tr><tr><td>
+ uucp
+ </td><td>
+ 14
+ </td><td>
+ uucp
+ </td></tr><tr><td>
+ man
+ </td><td>
+ 15
+ </td><td>
+ </td></tr><tr><td>
+ games
+ </td><td>
+ 20
+ </td><td>
+ </td></tr><tr><td>
+ gopher
+ </td><td>
+ 30
+ </td><td>
+ </td></tr><tr><td>
+ video
+ </td><td>
+ 39
+ </td><td>
+ </td></tr><tr><td>
+ dip
+ </td><td>
+ 40
+ </td><td>
+ </td></tr><tr><td>
+ ftp
+ </td><td>
+ 50
+ </td><td>
+ </td></tr><tr><td>
+ lock
+ </td><td>
+ 54
+ </td><td>
+ </td></tr><tr><td>
+ audio
+ </td><td>
+ 63
+ </td><td>
+ </td></tr><tr><td>
+ nobody
+ </td><td>
+ 99
+ </td><td>
+ </td></tr><tr><td>
+ users
+ </td><td>
+ 100
+ </td><td>
+ </td></tr><tr><td>
+ dbus
+ </td><td>
+ 81
+ </td><td>
+ </td></tr><tr><td>
+ usbmuxd
+ </td><td>
+ 113
+ </td><td>
+ </td></tr><tr><td>
+ utmp
+ </td><td>
+ 22
+ </td><td>
+ </td></tr><tr><td>
+ utempter
+ </td><td>
+ 35
+ </td><td>
+ </td></tr><tr><td>
+ avahi-autoipd
+ </td><td>
+ 170
+ </td><td>
+ </td></tr><tr><td>
+ floppy
+ </td><td>
+ 19
+ </td><td>
+ </td></tr><tr><td>
+ vcsa
+ </td><td>
+ 69
+ </td><td>
+ </td></tr><tr><td>
+ rpc
+ </td><td>
+ 32
+ </td><td>
+ </td></tr><tr><td>
+ rtkit
+ </td><td>
+ 499
+ </td><td>
+ </td></tr><tr><td>
+ abrt
+ </td><td>
+ 498
+ </td><td>
+ </td></tr><tr><td>
+ nscd
+ </td><td>
+ 28
+ </td><td>
+ </td></tr><tr><td>
+ desktop_admin_r
+ </td><td>
+ 497
+ </td><td>
+ </td></tr><tr><td>
+ desktop_user_r
+ </td><td>
+ 496
+ </td><td>
+ </td></tr><tr><td>
+ cdrom
+ </td><td>
+ 11
+ </td><td>
+ </td></tr><tr><td>
+ tape
+ </td><td>
+ 33
+ </td><td>
+ </td></tr><tr><td>
+ dialout
+ </td><td>
+ 18
+ </td><td>
+ </td></tr><tr><td>
+ haldaemon
+ </td><td>
+ 68
+ </td><td>
+ haldaemon
+ </td></tr><tr><td>
+ apache
+ </td><td>
+ 48
+ </td><td>
+ </td></tr><tr><td>
+ ldap
+ </td><td>
+ 55
+ </td><td>
+ </td></tr><tr><td>
+ saslauth
+ </td><td>
+ 495
+ </td><td>
+ </td></tr><tr><td>
+ postdrop
+ </td><td>
+ 90
+ </td><td>
+ </td></tr><tr><td>
+ postfix
+ </td><td>
+ 89
+ </td><td>
+ </td></tr><tr><td>
+ avahi
+ </td><td>
+ 70
+ </td><td>
+ </td></tr><tr><td>
+ ntp
+ </td><td>
+ 38
+ </td><td>
+ </td></tr><tr><td>
+ rpcuser
+ </td><td>
+ 29
+ </td><td>
+ </td></tr><tr><td>
+ nfsnobody
+ </td><td>
+ 4294967294
+ </td><td>
+ </td></tr><tr><td>
+ pulse
+ </td><td>
+ 494
+ </td><td>
+ </td></tr><tr><td>
+ pulse-access
+ </td><td>
+ 493
+ </td><td>
+ </td></tr><tr><td>
+ fuse
+ </td><td>
+ 492
+ </td><td>
+ </td></tr><tr><td>
+ gdm
+ </td><td>
+ 42
+ </td><td>
+ </td></tr><tr><td>
+ stapdev
+ </td><td>
+ 491
+ </td><td>
+ </td></tr><tr><td>
+ stapusr
+ </td><td>
+ 490
+ </td><td>
+ </td></tr><tr><td>
+ sshd
+ </td><td>
+ 74
+ </td><td>
+ </td></tr><tr><td>
+ tcpdump
+ </td><td>
+ 72
+ </td><td>
+ </td></tr><tr><td>
+ slocate
+ </td><td>
+ 21
+ </td><td>
+ </td></tr><tr><td>
+ dovecot
+ </td><td>
+ 97
+ </td><td>
+ </td></tr><tr><td>
+ dovenull
+ </td><td>
+ 489
+ </td><td>
+ </td></tr><tr><td>
+ mailnull
+ </td><td>
+ 47
+ </td><td>
+ </td></tr><tr><td>
+ smmsp
+ </td><td>
+ 51
+ </td><td>
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" title="15.5. User Private Groups" id="s1-users-groups-private-groups"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-groups-private-groups">15.5. User Private Groups</h2></div></div></div><a id="id585311" class="indexterm"></a><a id="id474870" class="indexterm"></a><a id="id474884" class="indexterm"></a><a id="id474906" class="indexterm"></a><div class="para">
+ Fedora uses a <em class="firstterm">user private group</em> (<em class="firstterm">UPG</em>) scheme, which makes UNIX groups easier to manage.
+ </div><div class="para">
+ A UPG is created whenever a new user is added to the system. A UPG has the same name as the user for which it was created and that user is the only member of the UPG.
+ </div><div class="para">
+ UPGs make it safe to set default permissions for a newly created file or directory, allowing both the user and <span class="emphasis"><em>the group of that user</em></span> to make modifications to the file or directory.
+ </div><div class="para">
+ The setting which determines what permissions are applied to a newly created file or directory is called a <em class="firstterm">umask</em> and is configured in the <code class="filename">/etc/bashrc</code> file. Traditionally on UNIX systems, the <code class="command">umask</code> is set to <code class="command">022</code>, which allows only the user who created the file or directory to make modifications. Under this scheme, all other users, <span class="emphasis"><em>including members of the creator's group</em></span>, are not allowed to make any modifications. However, under the UPG scheme, this "group protection" is not necessary since every user has their own private group.
+ </div><div class="section" title="15.5.1. Group Directories" id="s2-users-groups-rationale"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-users-groups-rationale">15.5.1. Group Directories</h3></div></div></div><a id="id863352" class="indexterm"></a><a id="id863366" class="indexterm"></a><div class="para">
+ System administrators usually like to create a group for each major project and assign people to the group when they need to access that project's files. With this traditional scheme, file managing is difficult; when someone creates a file, it is associated with the primary group to which they belong. When a single person works on multiple projects, it becomes difficult to associate the right files with the right group. However, with the UPG scheme, groups are automatically assigned to files created within a directory with the <em class="firstterm">setgid</em> bit set. The setgid bit makes managing group projects that share a common directory very simple because any files a user creates within the directory are owned by the group which owns the directory.
+ </div><div class="para">
+ For example, a group of people need to work on files in the <code class="filename">/usr/share/emacs/site-lisp/</code> directory. Some people are trusted to modify the directory, but not everyone. First create an <code class="computeroutput">emacs</code> group, as in the following command:
+ </div><pre class="screen">
+<code class="command">/usr/sbin/groupadd emacs</code>
+</pre><div class="para">
+ To associate the contents of the directory with the <code class="computeroutput">emacs</code> group, type:
+ </div><pre class="screen">
+<code class="command">chown -R root.emacs <code class="filename">/usr/share/emacs/site-lisp</code> </code>
+</pre><div class="para">
+ Now, it is possible to add the right users to the group with the <code class="command">gpasswd</code> command:
+ </div><pre class="screen">
+<code class="command">/usr/bin/gpasswd -a <em class="replaceable"><code><username></code></em> emacs</code>
+</pre><div class="para">
+ To allow users to create files within the directory, use the following command:
+ </div><pre class="screen">
+<code class="command">chmod 775 <code class="filename">/usr/share/emacs/site-lisp</code> </code>
+</pre><div class="para">
+ When a user creates a new file, it is assigned the group of the user's default private group. Next, set the setgid bit, which assigns everything created in the directory the same group permission as the directory itself (<code class="computeroutput">emacs</code>). Use the following command:
+ </div><pre class="screen">
+<code class="command">chmod 2775 /usr/share/emacs/site-lisp</code>
+</pre><div class="para">
+ At this point, because the default umask of each user is 002, all members of the <code class="computeroutput">emacs</code> group can create and edit files in the <code class="filename">/usr/share/emacs/site-lisp/</code> directory without the administrator having to change file permissions every time users write new files.
+ </div><div class="para">
+ The command <code class="command">ls -l /usr/share/emacs/</code> displays the current settings:
+ </div><pre class="screen">
+ <code class="code">total 4</code>
+<code class="code">drwxrwsr-x. 2 root emacs 4096 May 18 15:41 site-lisp</code>
+</pre></div></div><div class="section" title="15.6. Shadow Passwords" id="s1-users-groups-shadow-utilities"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-groups-shadow-utilities">15.6. Shadow Passwords</h2></div></div></div><a id="id649964" class="indexterm"></a><a id="id649978" class="indexterm"></a><div class="para">
+ In multiuser environments it is very important to use <em class="firstterm">shadow passwords</em> (provided by the <code class="filename">shadow-utils</code> package). Doing so enhances the security of system authentication files. For this reason, the installation program enables shadow passwords by default.
+ </div><div class="para">
+ The following list shows the advantages shadow passwords have over the traditional way of storing passwords on UNIX-based systems:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Improves system security by moving encrypted password hashes from the world-readable <code class="filename">/etc/passwd</code> file to <code class="filename">/etc/shadow</code>, which is readable only by the root user.
+ </div></li><li class="listitem"><div class="para">
+ Stores information about password aging.
+ </div></li><li class="listitem"><div class="para">
+ Allows the <code class="filename">/etc/login.defs</code> file to enforce security policies.
+ </div></li></ul></div><div class="para">
+ Most utilities provided by the <code class="filename">shadow-utils</code> package work properly whether or not shadow passwords are enabled. However, since password aging information is stored exclusively in the <code class="filename">/etc/shadow</code> file, any commands which create or modify password aging information do not work.
+ </div><div class="para">
+ The following is a list of commands which do not work without first enabling shadow passwords:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">chage</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">gpasswd</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">/usr/sbin/usermod</code> <code class="option">-e</code> or <code class="option">-f</code> options
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">/usr/sbin/useradd</code> <code class="option">-e</code> or <code class="option">-f</code> options
+ </div></li></ul></div></div><div class="section" title="15.7. Additional Resources" id="s1-users-groups-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-groups-additional-resources">15.7. Additional Resources</h2></div></div></div><a id="id461336" class="indexterm"></a><a id="id461350" class="indexterm"></a><div class="para">
+ For more information about users and groups, and tools to manage them, refer to the following resources.
+ </div><div class="section" title="15.7.1. Installed Documentation" id="s2-users-groups-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-users-groups-documentation">15.7.1. Installed Documentation</h3></div></div></div><a id="id844122" class="indexterm"></a><a id="id844141" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Related man pages — There are a number of man pages for the various applications and configuration files involved with managing users and groups. Some of the more important man pages have been listed here:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">User and Group Administrative Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man chage</code> — A command to modify password aging policies and account expiration.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man gpasswd</code> — A command to administer the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man groupadd</code> — A command to add groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man grpck</code> — A command to verify the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man groupdel</code> — A command to remove groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man groupmod</code> — A command to modify group membership.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man pwck</code> — A command to verify the <code class="filename">/etc/passwd</code> and <code class="filename">/etc/shadow</code> files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man pwconv</code> — A tool to convert standard passwords to shadow passwords.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man pwunconv</code> — A tool to convert shadow passwords to standard passwords.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man useradd</code> — A command to add users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man userdel</code> — A command to remove users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man usermod</code> — A command to modify users.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man 5 group</code> — The file containing group information for the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man 5 passwd</code> — The file containing user information for the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man 5 shadow</code> — The file containing passwords and account expiration information for the system.
+ </div></li></ul></div></dd></dl></div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 16. Automated Tasks" id="ch-Automated_Tasks" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 16. Automated Tasks</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-autotasks-cron-anacron">16.1. Cron and Anacron</a></span></dt><dt><span class="section"><a href="#s1-autotasks-at-batch">16.2. At and Batch</a></span></dt><dt><span class="section"><a href="#s1-autotasks-additional-resources">16.3. Additional Resources</a></span></dt></dl></div><a id="id499963" class="indexterm"></a><div class="para">
+ In Linux, tasks, which are also known as <em class="firstterm">jobs</em>, can be configured to run automatically within a specified period of time, on a specified date, or when the system load average is below a specified number. Fedora is pre-configured to run important system tasks to keep the system updated. For example, the slocate database used by the <code class="command">locate</code> command is updated daily. A system administrator can use automated tasks to perform periodic backups, monitor the system, run custom scripts, and more.
+ </div><div class="para">
+ Fedora comes with several automated tasks utilities: <code class="command">cron</code>, <code class="command">at</code>, and <code class="command">batch</code>.
+ </div><a id="id504095" class="indexterm"></a><div class="section" title="16.1. Cron and Anacron" id="s1-autotasks-cron-anacron"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-autotasks-cron-anacron">16.1. Cron and Anacron</h2></div></div></div><a id="id423072" class="indexterm"></a><a id="id638392" class="indexterm"></a><div class="para">
+ Both, Cron and Anacron, are daemons that can be used to schedule the execution of recurring tasks according to a combination of the time, day of the month, month, day of the week, and week.
+ </div><div class="para">
+ Cron assumes that the system is on continuously. If the system is not on when a job is scheduled, it is not executed. Cron allows jobs to be run as often as every minute. Anacron does not assume the system is always on, remembers every scheduled job, and executes it the next time the system is up. However, Anacron can only run a job once a day. To schedule reccurring jobs, refer to <a class="xref" href="#s2-configuring-anacron-jobs" title="16.1.2. Configuring Anacron Jobs">Section 16.1.2, “Configuring Anacron Jobs”</a> or <a class="xref" href="#s2-configuring-cron-jobs" title="16.1.3. Configuring Cron Jobs">Section 16.1.3, “Configuring Cron Jobs”</a>. To schedule one-time jobs, refer to <a class="xref" href="#s1-autotasks-at-batch" title="16.2. At and Batch">Section 16.2, “At and Batch”</a>.
+ </div><div class="para">
+ To use the cron service, the <code class="filename">cronie</code> RPM package must be installed and the <code class="command">crond</code> service must be running. <code class="filename">anacron</code> is a sub-package of <code class="filename">cronie</code>. To determine if these packages are installed, use the <code class="command">rpm -q cronie cronie-anacron</code> command.
+ </div><div class="section" title="16.1.1. Starting and Stopping the Service" id="s2-autotasks-cron-service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-cron-service">16.1.1. Starting and Stopping the Service</h3></div></div></div><div class="para">
+ To determine if the service is running, use the command <code class="command">/sbin/service crond status</code>. To start the cron service, use the command <code class="command">/sbin/service crond start</code>. To stop the service, use the command <code class="command">/sbin/service crond stop</code>. It is recommended that you start the service at boot time. Refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for details on starting the cron service automatically at boot time.
+ </div></div><div class="section" title="16.1.2. Configuring Anacron Jobs" id="s2-configuring-anacron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-configuring-anacron-jobs">16.1.2. Configuring Anacron Jobs</h3></div></div></div><a id="id447693" class="indexterm"></a><a id="id447706" class="indexterm"></a><a id="id447720" class="indexterm"></a><a id="id690087" class="indexterm"></a><div class="para">
+ The main configuration file to schedule jobs is <code class="filename">/etc/anacrontab</code> (only root is allowed to modify this file), which contains the following lines:
+ </div><pre class="screen">
+SHELL=/bin/sh
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+# the maximal random delay added to the base delay of the jobs
+RANDOM_DELAY=45
+# the jobs will be started during the following hours only
+START_HOURS_RANGE=3-22
+
+#period in days delay in minutes job-identifier command
+1 5 cron.daily nice run-parts /etc/cron.daily
+7 25 cron.weekly nice run-parts /etc/cron.weekly
+ at monthly 45 cron.monthly nice run-parts /etc/cron.monthly
+</pre><div class="para">
+ The first three lines are variables used to configure the environment in which the anacron tasks are run. The <code class="computeroutput">SHELL</code> variable tells the system which shell environment to use (in this example the bash shell). The <code class="computeroutput">PATH</code> variable defines the path used to execute commands. The output of the anacron jobs are emailed to the username defined with the <code class="computeroutput">MAILTO</code> variable. If the <code class="computeroutput">MAILTO</code> variable is not defined, (i.e. is empty, <code class="computeroutput">MAILTO=</code>), email is not sent.
+ </div><div class="para">
+ The next two lines are variables that modify the time for each scheduled job. The <code class="computeroutput">RANDOM_DELAY</code> variable denotes the maximum number of minutes that will be added to the <code class="filename">delay in minutes</code> variable which is specified for each job. The minimum delay value is set, by default, to 6 minutes. A <code class="computeroutput">RANDOM_DELAY</code> set to 12 would therefore add, randomly, between 6 and 12 minutes to the <code class="filename">delay in minutes</code> for each job in that particular anacrontab. <code class="computeroutput">RANDOM_DELAY</code> can also be set to a value below 6, or even 0. When set to 0, no random delay is added. This proves to be useful when, for example, more computers that share one network connection need to download the same data every day. The <code class="computeroutput">START_HOURS_RANGE</code> variable defines an interval (in hours) when scheduled jobs can be run. In case this time
interval is missed, for example, due to a power down, then scheduled jobs are not executed that day.
+ </div><div class="para">
+ The rest of the lines in the <code class="filename">/etc/anacrontab</code> file represent scheduled jobs and have the following format:
+ </div><pre class="screen">
+period in days delay in minutes job-identifier command
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">period in days</code> — specifies the frequency of execution of a job in days. This variable can be represented by an integer or a macro (<code class="computeroutput">@daily</code>, <code class="computeroutput">@weekly</code>, <code class="computeroutput">@monthly</code>), where <code class="computeroutput">@daily</code> denotes the same value as the integer 1, <code class="computeroutput">@weekly</code> the same as 7, and <code class="computeroutput">@monthly</code> specifies that the job is run once a month, independent on the length of the month.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">delay in minutes</code> — specifies the number of minutes anacron waits, if necessary, before executing a job. This variable is represented by an integer where 0 means no delay.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">job-identifier</code> — specifies a unique name of a job which is used in the log files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">command</code> — specifies the command to execute. The command can either be a command such as <code class="computeroutput">ls /proc >> /tmp/proc</code> or a command to execute a custom script.
+ </div></li></ul></div><div class="para">
+ Any lines that begin with a hash sign (#) are comments and are not processed.
+ </div><div class="section" title="16.1.2.1. Examples of Anacron Jobs" id="s3-anacron-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-anacron-examples">16.1.2.1. Examples of Anacron Jobs </h4></div></div></div><div class="para">
+ The following example shows a simple <code class="filename">/etc/anacrontab</code> file:
+ </div><pre class="screen">
+SHELL=/bin/sh
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+
+# the maximal random delay added to the base delay of the jobs
+RANDOM_DELAY=30
+# the jobs will be started during the following hours only
+START_HOURS_RANGE=16-20
+
+#period in days delay in minutes job-identifier command
+1 20 dailyjob nice run-parts /etc/cron.daily
+7 25 weeklyjob /etc/weeklyjob.bash
+ at monthly 45 monthlyjob ls /proc >> /tmp/proc
+</pre><div class="para">
+ All jobs defined in this <code class="filename">anacrontab</code> file are randomly delayed by 6-30 minutes and can be executed between 16:00 and 20:00. Thus, the first defined job will run anywhere between 16:26 and 16:50 every day. The command specified for this job will execute all present programs in the <code class="filename">/etc/cron.daily</code> directory (using the <code class="command">run-parts</code> script which takes a directory as a command-line argument and sequentially executes every program within that directory). The second specified job will be executed once a week and will execute the <code class="filename">weeklyjob.bash</code> script in the <code class="filename">/etc</code> directory. The third job is executed once a month and runs a command to write the contents of the <code class="filename">/proc</code> to the <code class="filename">/tmp/proc</code> file (e.g. <code class="computeroutput">ls /proc >> /tmp/proc</code>).
+ </div><div class="section" title="16.1.2.1.1. Disabling Anacron" id="s3-disabling-anacron"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-disabling-anacron">16.1.2.1.1. Disabling Anacron</h5></div></div></div><div class="para">
+ In case your system is continuously on and you do not require anacron to run your scheduled jobs, you may uninstall the <code class="filename">cronie-anacron</code> package. Thus, you will be able to define jobs using crontabs only.
+ </div></div></div></div><div class="section" title="16.1.3. Configuring Cron Jobs" id="s2-configuring-cron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-configuring-cron-jobs">16.1.3. Configuring Cron Jobs</h3></div></div></div><a id="id545890" class="indexterm"></a><a id="id444452" class="indexterm"></a><a id="id444465" class="indexterm"></a><a id="id444479" class="indexterm"></a><div class="para">
+ The configuration file to configure cron jobs, <code class="filename">/etc/crontab</code> (only root is allowed to modify this file), contains the following lines:
+ </div><pre class="screen">
+SHELL=/bin/bash
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+HOME=/
+# For details see man 4 crontabs
+# Example of job definition:
+# .---------------- minute (0 - 59)
+# | .------------- hour (0 - 23)
+# | | .---------- day of month (1 - 31)
+# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
+# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
+# | | | | |
+# * * * * * user command to be executed
+</pre><div class="para">
+ The first three lines contain the same variables as an <code class="filename">anacrontab</code> file, <code class="computeroutput">SHELL</code>, <code class="computeroutput">PATH</code> and <code class="computeroutput">MAILTO</code>. For more information about these variables, refer to <a class="xref" href="#s2-configuring-anacron-jobs" title="16.1.2. Configuring Anacron Jobs">Section 16.1.2, “Configuring Anacron Jobs”</a>. The fourth line contains the <code class="computeroutput">HOME</code> variable. The <code class="computeroutput">HOME</code> variable can be used to set the home directory to use when executing commands or scripts.
+ </div><div class="para">
+ The rest of the lines in the <code class="filename">/etc/crontab</code> file represent scheduled jobs and have the following format:
+ </div><pre class="screen">
+minute hour day month day of week user command
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">minute</code> — any integer from 0 to 59
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">hour</code> — any integer from 0 to 23
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">day</code> — any integer from 1 to 31 (must be a valid day if a month is specified)
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">month</code> — any integer from 1 to 12 (or the short name of the month such as jan or feb)
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">day of week</code> — any integer from 0 to 7, where 0 or 7 represents Sunday (or the short name of the week such as sun or mon)
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">user</code> — specifies the user under which the jobs are run
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">command</code> — the command to execute (the command can either be a command such as <code class="command">ls /proc >> /tmp/proc</code> or the command to execute a custom script)
+ </div></li></ul></div><div class="para">
+ For any of the above values, an asterisk (*) can be used to specify all valid values. For example, an asterisk for the month value means execute the command every month within the constraints of the other values.
+ </div><div class="para">
+ A hyphen (-) between integers specifies a range of integers. For example, <strong class="userinput"><code>1-4</code></strong> means the integers 1, 2, 3, and 4.
+ </div><div class="para">
+ A list of values separated by commas (,) specifies a list. For example, <strong class="userinput"><code>3, 4, 6, 8</code></strong> indicates those four specific integers.
+ </div><div class="para">
+ The forward slash (/) can be used to specify step values. The value of an integer can be skipped within a range by following the range with <strong class="userinput"><code>/<<em class="replaceable"><code>integer</code></em>></code></strong>. For example, <strong class="userinput"><code>0-59/2</code></strong> can be used to define every other minute in the minute field. Step values can also be used with an asterisk. For instance, the value <strong class="userinput"><code>*/3</code></strong> can be used in the month field to run the task every third month.
+ </div><div class="para">
+ Any lines that begin with a hash sign (#) are comments and are not processed.
+ </div><div class="para">
+ Users other than root can configure cron tasks by using the <code class="command">crontab</code> utility. All user-defined crontabs are stored in the <code class="filename">/var/spool/cron/</code> directory and are executed using the usernames of the users that created them. To create a crontab as a user, login as that user and type the command <code class="command">crontab -e</code> to edit the user's crontab using the editor specified by the <code class="computeroutput">VISUAL</code> or <code class="computeroutput">EDITOR</code> environment variable. The file uses the same format as <code class="filename">/etc/crontab</code>. When the changes to the crontab are saved, the crontab is stored according to username and written to the file <code class="filename">/var/spool/cron/<em class="replaceable"><code>username</code></em> </code>. To list the contents of your own personal crontab file, use the <code class="command">crontab -l</code> command.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When using the <code class="command">crontab</code> utility, there is no need to specify a user when defining a job.
+ </div></div></div><div class="para">
+ The <code class="filename">/etc/cron.d/</code> directory contains files that have the same syntax as the <code class="filename">/etc/crontab</code> file. Only root is allowed to create and modify files in this directory.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The cron daemon checks the <code class="filename">/etc/anacrontab</code> file, the <code class="filename">/etc/crontab</code> file, the <code class="filename">/etc/cron.d/</code> directory, and the <code class="filename">/var/spool/cron/</code> directory every minute for any changes. If any changes are found, they are loaded into memory. Thus, the daemon does not need to be restarted if an anacrontab or a crontab file is changed.
+ </div></div></div></div><div class="section" title="16.1.4. Controlling Access to Cron" id="s2-autotasks-cron-access"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-cron-access">16.1.4. Controlling Access to Cron</h3></div></div></div><div class="para">
+ The <code class="filename">/etc/cron.allow</code> and <code class="filename">/etc/cron.deny</code> files are used to restrict access to cron. The format of both access control files is one username on each line. Whitespace is not permitted in either file. The cron daemon (<code class="command">crond</code>) does not have to be restarted if the access control files are modified. The access control files are checked each time a user tries to add or delete a cron job.
+ </div><div class="para">
+ The root user can always use cron, regardless of the usernames listed in the access control files.
+ </div><div class="para">
+ If the file <code class="filename">cron.allow</code> exists, only users listed in it are allowed to use cron, and the <code class="filename">cron.deny</code> file is ignored.
+ </div><div class="para">
+ If <code class="filename">cron.allow</code> does not exist, users listed in <code class="filename">cron.deny</code> are not allowed to use cron.
+ </div><div class="para">
+ Access can also be controlled through Pluggable Authentication Modules (PAM). These settings are stored in <code class="filename">/etc/security/access.conf</code>. For example, adding the following line in this file forbids creating crontabs for all users except the root user:
+ </div><pre class="screen">
+-:ALL EXCEPT root :cron
+</pre><div class="para">
+ The forbidden jobs are logged in an appropriate log file or, when using “crontab -e”, returned to the standard output. For more information, refer to <code class="filename">access.conf.5</code> (i.e. <code class="command">man 5 access.conf</code>).
+ </div></div><div class="section" title="16.1.5. Black/White Listing of Cron Jobs" id="s2-black-white-listing-of-cron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-black-white-listing-of-cron-jobs">16.1.5. Black/White Listing of Cron Jobs</h3></div></div></div><div class="para">
+ Black/White listing of jobs is used to omit parts of the defined jobs that do not need to be executed. When calling the <code class="command">run-parts</code> script on a cron folder, such as <code class="filename">/etc/cron.daily</code>, we can define which of the programs in this folder will not be executed by <code class="command">run-parts</code>.
+ </div><div class="para">
+ To define a black list, create a <code class="filename">jobs.deny</code> file in the folder that <code class="command">run-parts</code> will be executing from. For example, if we need to omit a particular program from /etc/cron.daily, then, a file <code class="filename">/etc/cron.daily/jobs.deny</code> has to be created. In this file, specify the names of the omitted programs from the same directory. These will not be executed when a command, such as <code class="computeroutput">run-parts /etc/cron.daily</code>, is executed by a specific job.
+ </div><div class="para">
+ To define a white list, create a <code class="filename">jobs.allow</code> file.
+ </div><div class="para">
+ The principles of <code class="filename">jobs.deny</code> and <code class="filename">jobs.allow</code> are the same as those of <code class="filename">cron.deny</code> and <code class="filename">cron.allow</code> described in section <a class="xref" href="#s2-autotasks-cron-access" title="16.1.4. Controlling Access to Cron">Section 16.1.4, “Controlling Access to Cron”</a>.
+ </div></div></div><div class="section" title="16.2. At and Batch" id="s1-autotasks-at-batch"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-autotasks-at-batch">16.2. At and Batch</h2></div></div></div><a id="id857277" class="indexterm"></a><a id="id774028" class="indexterm"></a><div class="para">
+ While cron is used to schedule recurring tasks, the <code class="command">at</code> command is used to schedule a one-time task at a specific time and the <code class="command">batch</code> command is used to schedule a one-time task to be executed when the systems load average drops below 0.8.
+ </div><div class="para">
+ To use <code class="command">at</code> or <code class="command">batch</code>, the <code class="filename">at</code> RPM package must be installed, and the <code class="command">atd</code> service must be running. To determine if the package is installed, use the <code class="command">rpm -q at</code> command. To determine if the service is running, use the command <code class="command">/sbin/service atd status</code>.
+ </div><div class="section" title="16.2.1. Configuring At Jobs" id="s2-autotasks-at-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-at-configuring">16.2.1. Configuring At Jobs</h3></div></div></div><div class="para">
+ To schedule a one-time job at a specific time, type the command <code class="command">at <em class="replaceable"><code>time</code></em> </code>, where <code class="command"><em class="replaceable"><code>time</code></em> </code> is the time to execute the command.
+ </div><div class="para">
+ The argument <em class="replaceable"><code>time</code></em> can be one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ HH:MM format — For example, 04:00 specifies 4:00 a.m. If the time is already past, it is executed at the specified time the next day.
+ </div></li><li class="listitem"><div class="para">
+ midnight — Specifies 12:00 a.m.
+ </div></li><li class="listitem"><div class="para">
+ noon — Specifies 12:00 p.m.
+ </div></li><li class="listitem"><div class="para">
+ teatime — Specifies 4:00 p.m.
+ </div></li><li class="listitem"><div class="para">
+ month-name day year format — For example, January 15 2002 specifies the 15th day of January in the year 2002. The year is optional.
+ </div></li><li class="listitem"><div class="para">
+ MMDDYY, MM/DD/YY, or MM.DD.YY formats — For example, 011502 for the 15th day of January in the year 2002.
+ </div></li><li class="listitem"><div class="para">
+ now + time — time is in minutes, hours, days, or weeks. For example, now + 5 days specifies that the command should be executed at the same time five days from now.
+ </div></li></ul></div><div class="para">
+ The time must be specified first, followed by the optional date. For more information about the time format, read the <code class="filename">/usr/share/doc/at-<em class="replaceable"><code><version></code></em>/timespec</code> text file.
+ </div><div class="para">
+ After typing the <code class="command">at</code> command with the time argument, the <code class="prompt">at></code> prompt is displayed. Type the command to execute, press <span class="keycap"><strong>Enter</strong></span>, and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Multiple commands can be specified by typing each command followed by the <span class="keycap"><strong>Enter</strong></span> key. After typing all the commands, press <span class="keycap"><strong>Enter</strong></span> to go to a blank line and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Alternatively, a shell script can be entered at the prompt, pressing <span class="keycap"><strong>Enter</strong></span> after each line in the script, and pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> on a blank line to exit. If a script i
s entered, the shell used is the shell set in the user's <code class="envar">SHELL</code> environment, the user's login shell, or <code class="command">/bin/sh</code> (whichever is found first).
+ </div><div class="para">
+ If the set of commands or script tries to display information to standard output, the output is emailed to the user.
+ </div><div class="para">
+ Use the command <code class="command">atq</code> to view pending jobs. Refer to <a class="xref" href="#s2-autotasks-at-batch-viewing" title="16.2.3. Viewing Pending Jobs">Section 16.2.3, “Viewing Pending Jobs”</a> for more information.
+ </div><div class="para">
+ Usage of the <code class="command">at</code> command can be restricted. For more information, refer to <a class="xref" href="#s2-autotasks-at-batch-controlling-access" title="16.2.5. Controlling Access to At and Batch">Section 16.2.5, “Controlling Access to At and Batch”</a> for details.
+ </div></div><div class="section" title="16.2.2. Configuring Batch Jobs" id="s2-autotasks-batch-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-batch-configuring">16.2.2. Configuring Batch Jobs</h3></div></div></div><div class="para">
+ To execute a one-time task when the load average is below 0.8, use the <code class="command">batch</code> command.
+ </div><div class="para">
+ After typing the <code class="command">batch</code> command, the <code class="prompt">at></code> prompt is displayed. Type the command to execute, press <span class="keycap"><strong>Enter</strong></span>, and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Multiple commands can be specified by typing each command followed by the <span class="keycap"><strong>Enter</strong></span> key. After typing all the commands, press <span class="keycap"><strong>Enter</strong></span> to go to a blank line and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Alternatively, a shell script can be entered at the prompt, pressing <span class="keycap"><strong>Enter</strong></span> after each line in the script, and pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> on a blank line to exit. If a script is entered, the shell
used is the shell set in the user's <code class="envar">SHELL</code> environment, the user's login shell, or <code class="command">/bin/sh</code> (whichever is found first). As soon as the load average is below 0.8, the set of commands or script is executed.
+ </div><div class="para">
+ If the set of commands or script tries to display information to standard out, the output is emailed to the user.
+ </div><div class="para">
+ Use the command <code class="command">atq</code> to view pending jobs. Refer to <a class="xref" href="#s2-autotasks-at-batch-viewing" title="16.2.3. Viewing Pending Jobs">Section 16.2.3, “Viewing Pending Jobs”</a> for more information.
+ </div><div class="para">
+ Usage of the <code class="command">batch</code> command can be restricted. For more information, refer to <a class="xref" href="#s2-autotasks-at-batch-controlling-access" title="16.2.5. Controlling Access to At and Batch">Section 16.2.5, “Controlling Access to At and Batch”</a> for details.
+ </div></div><div class="section" title="16.2.3. Viewing Pending Jobs" id="s2-autotasks-at-batch-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-at-batch-viewing">16.2.3. Viewing Pending Jobs</h3></div></div></div><div class="para">
+ To view pending <code class="command">at</code> and <code class="command">batch</code> jobs, use the <code class="command">atq</code> command. The <code class="command">atq</code> command displays a list of pending jobs, with each job on a line. Each line follows the job number, date, hour, job class, and username format. Users can only view their own jobs. If the root user executes the <code class="command">atq</code> command, all jobs for all users are displayed.
+ </div></div><div class="section" title="16.2.4. Additional Command Line Options" id="s2-autotasks-commandline-options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-commandline-options">16.2.4. Additional Command Line Options</h3></div></div></div><div class="para">
+ Additional command line options for <code class="command">at</code> and <code class="command">batch</code> include:
+ </div><div class="table" title="Table 16.1. at and batch Command Line Options" id="tb-at-command-line-options"><h6>Table 16.1. <code class="command">at</code> and <code class="command">batch</code> Command Line Options</h6><div class="table-contents"><table summary=" at and batch Command Line Options" border="1"><colgroup><col width="29%" /><col width="71%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-f</code>
+ </td><td>
+ Read the commands or shell script from a file instead of specifying them at the prompt.
+ </td></tr><tr><td>
+ <code class="option">-m</code>
+ </td><td>
+ Send email to the user when the job has been completed.
+ </td></tr><tr><td>
+ <code class="option">-v</code>
+ </td><td>
+ Display the time that the job is executed.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" title="16.2.5. Controlling Access to At and Batch" id="s2-autotasks-at-batch-controlling-access"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-at-batch-controlling-access">16.2.5. Controlling Access to At and Batch</h3></div></div></div><div class="para">
+ The <code class="filename">/etc/at.allow</code> and <code class="filename">/etc/at.deny</code> files can be used to restrict access to the <code class="command">at</code> and <code class="command">batch</code> commands. The format of both access control files is one username on each line. Whitespace is not permitted in either file. The <code class="command">at</code> daemon (<code class="command">atd</code>) does not have to be restarted if the access control files are modified. The access control files are read each time a user tries to execute the <code class="command">at</code> or <code class="command">batch</code> commands.
+ </div><div class="para">
+ The root user can always execute <code class="command">at</code> and <code class="command">batch</code> commands, regardless of the access control files.
+ </div><div class="para">
+ If the file <code class="filename">at.allow</code> exists, only users listed in it are allowed to use <code class="command">at</code> or <code class="command">batch</code>, and the <code class="filename">at.deny</code> file is ignored.
+ </div><div class="para">
+ If <code class="filename">at.allow</code> does not exist, users listed in <code class="filename">at.deny</code> are not allowed to use <code class="command">at</code> or <code class="command">batch</code>.
+ </div></div><div class="section" title="16.2.6. Starting and Stopping the Service" id="s2-autotasks-at-batch-service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-at-batch-service">16.2.6. Starting and Stopping the Service</h3></div></div></div><div class="para">
+ To start the <code class="command">at</code> service, use the command <code class="command">/sbin/service atd start</code>. To stop the service, use the command <code class="command">/sbin/service atd stop</code>. It is recommended that you start the service at boot time. Refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for details on starting the cron service automatically at boot time.
+ </div></div></div><div class="section" title="16.3. Additional Resources" id="s1-autotasks-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-autotasks-additional-resources">16.3. Additional Resources</h2></div></div></div><a id="id863342" class="indexterm"></a><a id="id1377210" class="indexterm"></a><a id="id1377223" class="indexterm"></a><div class="para">
+ To learn more about configuring automated tasks, refer to the following resources.
+ </div><div class="section" title="16.3.1. Installed Documentation" id="s2-autotasks-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-installed-docs">16.3.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">cron</code> man page — contains an overview of cron.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">crontab</code> man pages in sections 1 and 5 — The man page in section 1 contains an overview of the <code class="filename">crontab</code> file. The man page in section 5 contains the format for the file and some example entries.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">anacron</code> man page — contains an overview of anacron.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">anacrontab</code> man page — contains an overview of the <code class="filename">anacrontab</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/at-<em class="replaceable"><code><version></code></em>/timespec</code> contains more detailed information about the times that can be specified for cron jobs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">at</code> man page — description of <code class="command">at</code> and <code class="command">batch</code> and their command line options.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 17. Log Files" id="ch-Log_Files" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 17. Log Files</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-configuring-rsyslog">17.1. Configuring <code class="command">rsyslog</code> </a></span></dt><dt><span class="section"><a href="#s1-rsyslog-performance">17.2. <code class="command">rsyslog</code> Performance</a></span></dt><dt><span class="section"><a href="#s1-logfiles-locating">17.3. Locating Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-viewing">17.4. Viewing Log Files</a></span></dt><dt><span class="section"><a href="#s1-logfiles-adding">17.5. Adding a Log File</a></span></dt><dt><span class="section"><a href="#s1-logfiles-examining">17.6. Monitoring Log Files</a></span></dt><dt><span class="section"><a href="#s1-log-files-additional-resources">17.
7. Additional Resources</a></span></dt></dl></div><a id="id1376533" class="indexterm"></a><a id="id794207" class="indexterm"></a><div class="para">
+ <em class="firstterm">Log files</em> are files that contain messages about the system, including the kernel, services, and applications running on it. There are different log files for different information. For example, there is a default system log file, a log file just for security messages, and a log file for cron tasks.
+ </div><div class="para">
+ Log files can be very useful when trying to troubleshoot a problem with the system such as trying to load a kernel driver or when looking for unauthorized log in attempts to the system. This chapter discusses where to find log files, how to view log files, and what to look for in log files.
+ </div><a id="id644516" class="indexterm"></a><a id="id844206" class="indexterm"></a><div class="para">
+ Some log files are controlled by a daemon called <code class="systemitem">rsyslogd</code>. A list of log messages maintained by <code class="systemitem">rsyslogd</code> can be found in the <code class="filename">/etc/rsyslog.conf</code> configuration file.
+ </div><div class="para">
+ <code class="command">rsyslog</code> replaced <code class="command">syslogd</code> as the default program for forwarding syslog messages over the network. <code class="command">rsyslog</code> uses the basic <code class="command">syslog</code> protocol and extends its functionality with enhanced filtering, encryption protected relaying of messages, various configuration options, or support for transportation via the <code class="systemitem">TCP</code> or <code class="systemitem">UDP</code> protocols.
+ </div><div class="section" title="17.1. Configuring rsyslog" id="s1-configuring-rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-configuring-rsyslog">17.1. Configuring <code class="command">rsyslog</code> </h2></div></div></div><div class="para">
+ The main configuration file for <code class="command">rsyslog</code> is <code class="filename">/etc/rsyslog.conf</code>. It is essentially divided in the following parts:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Modules
+ </div></li><li class="listitem"><div class="para">
+ Global directives
+ </div></li><li class="listitem"><div class="para">
+ Rules
+ </div></li><li class="listitem"><div class="para">
+ Templates
+ </div></li><li class="listitem"><div class="para">
+ Filter conditions
+ </div></li><li class="listitem"><div class="para">
+ Output channels
+ </div></li></ul></div><div class="para">
+ Each of these segments of the <code class="filename">/etc/rsyslog.conf</code> configuration file is described in the sections below.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ In your <code class="filename">/etc/rsyslog.conf</code> configuration file, any empty lines or any text following a hash sign (#) are comments and are not processed.
+ </div></div></div><div class="section" title="17.1.1. Modules" id="s2-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-modules">17.1.1. Modules</h3></div></div></div><div class="para">
+ Due to its modular design, <code class="command">rsyslog</code> offers a variety of <em class="firstterm">modules</em> which provide dynamic functionality. Note that modules can be written by third parties. Essentially, modules are comprised of various configuration directives that become available when a module is loaded. To load a module, use the following syntax:
+ </div><pre class="screen">
+$ModLoad <em class="replaceable"><code><MODULE></code></em>
+</pre><div class="para">
+ where <em class="replaceable"><code><MODULE></code></em> represents your desired module. For example, if you want to load the <code class="literal">Text File Input Module</code> (<code class="command">imfile</code> — enables <code class="command">rsyslog</code> to convert any standard text files into a syslog messages), specify the following line in your <code class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad imfile
+</pre><div class="para">
+ <code class="command">rsyslog</code> offers a number of modules which are split into these main categories:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Input Modules — Input modules gather messages from various sources. The name of an input module always starts with the <code class="literal">im</code> prefix, such as <code class="command">imfile</code>, <code class="command">imrelp</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Output Modules — Output modules process messages into different formats or perform various actions on them. The name of an output module always starts with the <code class="literal">om</code> prefix, such as <code class="command">omsnmp</code>, <code class="command">omrelp</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Filter Modules — Filter modules provide the ability to filter messages according to specified rules. The name of a filter module always starts with the <code class="literal">fm</code> prefix.
+ </div></li><li class="listitem"><div class="para">
+ Parser Modules — Parser modules use the message parsers to parse message content of any received messages. The name of a parser module always starts with the <code class="literal">pm</code> prefix, such as <code class="command">pmrfc5424</code>, <code class="command">pmrfc3164</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Message Modification Modules — Message modification modules change the content of asyslog message. The message modification modules only differ in their implementation from the output and filter modules but share the same interface.
+ </div></li><li class="listitem"><div class="para">
+ String Generator Modules — String generator modules generate strings based on the message content and strongly cooperate with the template feature provided by <code class="command">rsyslog</code>. For more information on templates, refer to . The name of a string generator module always starts with the <code class="literal">sm</code> prefix, such as <code class="command">smfile</code>, <code class="command">smtradfile</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Library Modules — Library modules provide the ability to load and handle other loadable modules. These modules are loaded automatically by <code class="command">rsyslog</code> when needed and cannot be configured by the user.
+ </div></li></ul></div><div class="para">
+ A comprehensive list of all available modules and their detailed description can be found at <a href="http://www.rsyslog.com/doc/rsyslog_conf_modules.html/">http://www.rsyslog.com/doc/rsyslog_conf_modules.html</a>
+ </div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Note that when <code class="command">rsyslog</code> loads any modules, it provides them with access to some of its functions and data. This poses a possible security threat. To minimize security risks, use trustworthy modules only.
+ </div></div></div></div><div class="section" title="17.1.2. Global Directives" id="s2-global-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-global-directives">17.1.2. Global Directives</h3></div></div></div><div class="para">
+ <em class="firstterm">Global directives</em> specify configuration options that apply to the <code class="systemitem">rsyslogd</code> daemon. All of the global directives must start with a dollar sign (<code class="literal">$</code>). Only one directive can be specified per line. The following is an example of a global directive that specifies the maximum size of the syslog message queue:
+ </div><pre class="screen">
+$MainMsgQueueSize
+</pre><div class="para">
+ The default size defined for this directive (<code class="constant">10,000</code> messages) can be overridden by specifying a different value.
+ </div><div class="para">
+ A comprehensive list of all available configuration directives and their detailed description can be found in <code class="filename">/usr/share/doc/rsyslog-4.4.2/rsyslog_conf_global.html</code> or online at <a href="http://www.rsyslog.com/doc/rsyslog_conf_global.html">http://www.rsyslog.com/doc/rsyslog_conf_global.html</a>.
+ </div></div><div class="section" title="17.1.3. Rules" id="s2-rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rules">17.1.3. Rules</h3></div></div></div><div class="para">
+ A rule specifies the cooperation of a <em class="firstterm">selector</em> with an <em class="firstterm">action</em>. To define a rule in your <code class="filename">/etc/rsyslog.conf</code> configuration file, define both, a selector and an action, on one line and separate them with one or more spaces or tabs. For more information on selectors, refer to <a class="xref" href="#s3-selectors" title="17.1.3.1. Selectors">Section 17.1.3.1, “Selectors”</a> and for information on actions, refer to <a class="xref" href="#s3-actions" title="17.1.3.2. Actions">Section 17.1.3.2, “Actions”</a>.
+ </div><div class="section" title="17.1.3.1. Selectors" id="s3-selectors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-selectors">17.1.3.1. Selectors</h4></div></div></div><div class="para">
+ Selectors filter syslog messages based on two conditions: <em class="firstterm">facility</em> and <em class="firstterm">priority</em>. The following is an example of a selector:
+ </div><pre class="screen">
+<em class="replaceable"><code><FACILITY></code></em>.<em class="replaceable"><code><PRIORITY></code></em>
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="replaceable"><code><FACILITY></code></em> specifies the subsystem that produces a specific syslog message. For example, the <code class="command">mail</code> subsystem handles all mail related syslog messages. <em class="replaceable"><code><FACILITY></code></em> can be represented by one of these keywords: <code class="command">auth</code>, <code class="command">authpriv</code>, <code class="command">cron</code>, <code class="command">daemon</code>, <code class="command">kern</code>, <code class="command">lpr</code>, <code class="command">mail</code>, <code class="command">news</code>, <code class="command">syslog</code>, <code class="command">user</code>, <code class="command">uucp</code>, and <code class="command">local0</code> through <code class="command">local7</code>.
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code><PRIORITY></code></em> specifies a priority of a syslog message. <em class="replaceable"><code><PRIORITY></code></em> can be represented by one of these keywords: <code class="command">debug</code>, <code class="command">info</code>, <code class="command">notice</code>, <code class="command">warning</code>, <code class="command">err</code>, <code class="command">crit</code>, <code class="command">alert</code>, and <code class="command">emerg</code>.
+ </div><div class="para">
+ By preceding any priority with an equal sign (<code class="literal">=</code>), you specify that only syslog messages with that priority will be selected. All other priorities will be ignored. Conversely, preceding a priority with an exclamation mark (<code class="literal">!</code>) selects all syslog messages but those with the defined priority. By not using either of these two extensions, you specify a selection of syslog messages with the defined priority and higher.
+ </div></li></ul></div><div class="para">
+ In addition to the keywords specified above, you may also use an asterisk (<code class="literal">*</code>) to define all facilities or priorities (depending on where you place the asterisk, before or after the dot). Specifying the keyword <code class="literal">none</code> serves for facilities with no given priorities.
+ </div><div class="para">
+ To define multiple facilities and priorities, simply separate them with a comma (<code class="literal">,</code>). To define multiple selectors on one line, separate them with a semi-colon (<code class="literal">;</code>).
+ </div><div class="para">
+ The following are a few examples of simple selectors:
+ </div><pre class="screen">
+kern.* # Selects all kernel syslog messages with any priority
+</pre><pre class="screen">
+mail.crit # Selects all mail syslog messages with priority <code class="command">crit</code> and higher.
+</pre><pre class="screen">
+cron.!info,!debug # Selects all cron syslog messages except those with the <code class="command">info</code> or <code class="command">debug</code> priority.
+</pre></div><div class="section" title="17.1.3.2. Actions" id="s3-actions"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-actions">17.1.3.2. Actions</h4></div></div></div><div class="para">
+ Actions specify what is to be done with the messages filtered out by the defined selector. The following are some of the actions you can define in your rule:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Syslog message placement</span></dt><dd><div class="para">
+ The majority of actions specify to which log file a syslog message is saved. This is done by specifying a file path after your already defined selector. The following is a rule comprised of a selector that selects all <span class="application"><strong>cron</strong></span> syslog messages and an action that saves them into the <code class="filename">/var/log/cron</code> log file:
+ </div><pre class="screen">cron.* /var/log/cron
+</pre><div class="para">
+ Use a dash mark (<code class="literal">-</code>) as a prefix of the file path you specified if you want to omit syncing the desired log file after every syslog message is generated.
+ </div><div class="para">
+ Your specified file path can be either static or dynamic. Static files are represented by a simple file path as was shown in the example above. Dynamic files are represented by a template and a question mark (<code class="literal">?</code>) prefix. For more information on templates, refer to <a class="xref" href="#s2-templates" title="17.1.4. Templates">Section 17.1.4, “Templates”</a>.
+ </div></dd><dt class="varlistentry"><span class="term">Sending syslog messages over the network</span></dt><dd><div class="para">
+ <code class="command">rsyslog</code> allows you to send and receive syslog messages over the network. This feature allows to administer syslog messages of multiple hosts on one machine. To forward syslog messages to a remote machine, use the following syntax:
+ </div><pre class="screen">@[<span class="optional">(<em class="replaceable"><code><OPTION></code></em>,<em class="replaceable"><code><MORE OPTIONS></code></em>)</span>]<em class="replaceable"><code><HOST></code></em>:[<span class="optional"><em class="replaceable"><code><PORT></code></em></span>]
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The at sign (<code class="literal">@</code>) indicates that the syslog messages are forwarded to a host using the <code class="systemitem">UDP</code> protocol. To use the <code class="systemitem">TCP</code> protocol, use two at signs with no space between them (<code class="literal">@@</code>).
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code><OPTION></code></em> and <em class="replaceable"><code><MORE OPTIONS></code></em> attributes can be replaced with an option such as <code class="command">z<em class="replaceable"><code><NUMBER></code></em></code>. This option enables <span class="application"><strong>zlib</strong></span> compression for syslog messages; the <em class="replaceable"><code><NUMBER></code></em> attribute specifies the level of compression.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code><HOST></code></em> attribute specifies the host which receives the selected syslog messages.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code><PORT></code></em> attribute specifies the host machine's port.
+ </div></li></ul></div><div class="para">
+ When specifying an <code class="systemitem">IPv6</code> address as the hoset, enclose the address in square brackets (<code class="literal">[</code>, <code class="literal">]</code>).
+ </div><div class="para">
+ The following are some examples of actions that forward syslog messages over the network (note that all actions are preceded with a selector that selects all messages with any priority):
+ </div><pre class="screen">*.* @192.168.0.1 # Forwards messages to 192.168.0.1 via the <code class="systemitem">UDP</code> protocol</pre><pre class="screen">*.* @@example.com:18 # Forwards messages to "example.com" using port 18 and the <code class="systemitem">TCP</code> protocol</pre><pre class="screen">
+*.* @(z9)[2001::1] # Compresses messages with <span class="application"><strong>zlib</strong></span> (level 9 compression)
+ # and forwards them to 2001::1 using the <code class="systemitem">UDP</code> protocol</pre></dd><dt class="varlistentry"><span class="term">Sending syslog messages to specific users</span></dt><dd><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> can send syslog messages to specific users by simply specifying a username of the user you wish to send the messages to. To specify more than one user, separate each username with a comma (<code class="literal">,</code>). To send messages to every user that is currently logged on, use an asterisk (<code class="literal">*</code>).
+ </div></dd><dt class="varlistentry"><span class="term">Discarding syslog messages</span></dt><dd><div class="para">
+ To discard your selected messages, use the tilde character (<code class="literal">~</code>). The following rule discards any cron syslog messages:
+ </div><pre class="screen">cron.* ~</pre></dd></dl></div><div class="para">
+
+ </div><div class="para">
+ Note that any action can be followed by a template that formats the message. To specify a template, suffix an action with a semicolon (<code class="literal">;</code>) and specify the name of the template.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ A template must be defined before it is used in an action.
+ </div></div></div><div class="para">
+ For more information on templates, refer to <a class="xref" href="#s2-templates" title="17.1.4. Templates">Section 17.1.4, “Templates”</a>.
+ </div><div class="para">
+ For more information on various <span class="application"><strong>rsyslog</strong></span> actions, refer to <code class="filename">/usr/share/doc/rsyslog-4.4.2/rsyslog_conf_actions.html</code>.
+ </div></div></div><div class="section" title="17.1.4. Templates" id="s2-templates"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-templates">17.1.4. Templates</h3></div></div></div><div class="para">
+
+ </div></div><div class="section" title="17.1.5. Filter Conditions" id="s2-filter-conditions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-filter-conditions">17.1.5. Filter Conditions</h3></div></div></div><div class="para">
+
+ </div></div><div class="section" title="17.1.6. Output Channels" id="s2-output-channels"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-output-channels">17.1.6. Output Channels</h3></div></div></div><div class="para">
+
+ </div></div></div><div class="section" title="17.2. rsyslog Performance" id="s1-rsyslog-performance"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-rsyslog-performance">17.2. <code class="command">rsyslog</code> Performance</h2></div></div></div><div class="para">
+
+ </div></div><div class="section" title="17.3. Locating Log Files" id="s1-logfiles-locating"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-locating">17.3. Locating Log Files</h2></div></div></div><a id="id803196" class="indexterm"></a><div class="para">
+ Most log files are located in the <code class="filename">/var/log/</code> directory. Some applications such as <code class="command">httpd</code> and <code class="command">samba</code> have a directory within <code class="filename">/var/log/</code> for their log files.
+ </div><a id="id803229" class="indexterm"></a><a id="id496890" class="indexterm"></a><div class="para">
+ You may notice multiple files in the <code class="filename">/var/log/</code> directory with numbers after them (e.g.: <code class="filename">cron-20100906</code>). These numbers represent a timestamp that has been added to a rotated log file. Log files are rotated so their file sizes do not become too large. The <code class="filename">logrotate</code> package contains a cron task that automatically rotates log files according to the <code class="filename">/etc/logrotate.conf</code> configuration file and the configuration files in the <code class="filename">/etc/logrotate.d/</code> directory.
+ </div><div class="section" title="17.3.1. Configuring logrotate" id="configuring-logrotate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="configuring-logrotate">17.3.1. Configuring <span class="package">logrotate</span> </h3></div></div></div><div class="para">
+ The following is a sample <code class="filename">/etc/logrotate.conf</code> configuration file:
+ </div><pre class="screen">
+# rotate log files weekly
+weekly
+# keep 4 weeks worth of backlogs
+rotate 4
+# uncomment this if you want your log files compressed
+compress
+</pre><div class="para">
+ All of the lines in the sample configuration file define global options that apply to every log file. In our example, log files are rotated weekly, rotated log files are kept for the duration of 4 weeks, and all rotated log files are compressed by <span class="application"><strong>gzip</strong></span> into the <code class="literal">.gz</code> format. Any lines that begin with a hash sign (#) are comments and are not processed
+ </div><div class="para">
+ You may define configuration options for a specific log file and place it under the global options. However, it is advisable to create a separate configuration file for any specific log file in the <code class="filename">/etc/logrotate.d/</code> directory and define any configuration options there.
+ </div><div class="para">
+ The following is an example of a configuration file placed in the <code class="filename">/etc/logrotate.d/</code> directory:
+ </div><pre class="screen">
+/var/log/messages {
+ rotate 5
+ weekly
+ postrotate
+ /usr/bin/killall -HUP syslogd
+ endscript
+}
+</pre><div class="para">
+ The configuration options in this file are specific for the <code class="filename">/var/log/messages</code> log file only. The settings specified here override the global settings where possible. Thus the rotated <code class="filename">/var/log/messages</code> log file will be kept for five weeks instead of four weeks as was defined in the global options.
+ </div><div class="para">
+ The following is a list of some of the directives you can specify in your <span class="application"><strong>logrotate</strong></span> configuration file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>weekly</code></em> — Specifies the rotation of log files on a weekly basis. Similar directives include:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>daily</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>monthly</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>yearly</code></em>
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>compress</code></em> — Enables compression of rotated log files. Similar directives include:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>nocompress</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>compresscmd</code></em> — Specifies the command to be used for compressing.
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>uncompresscmd</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>compressext</code></em> — Specifies what extension is to be used for compressing.
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>compressoptions</code></em> — Lets you specify any options that may be passed to the used compression program.
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>delaycompress</code></em> — Postpones the compression of log files to the next rotation of log files.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>rotate <em class="replaceable"><code><INTEGER></code></em> </code></em> — Specifies the number of rotations a log file undergoes before it is removed or mailed to a specific address. If the value <code class="constant">0</code> is specified, old log files are removed instead of rotated.
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>mail <em class="replaceable"><code><ADDRESS></code></em> </code></em> — This option enables mailing of log files that have been rotated as many times as is defined by the <em class="parameter"><code>rotate</code></em> directive to the specified address. Similar directives include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>nomail</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>mailfirst</code></em> — Specifies that the just-rotated log files are to be mailed, instead of the about-to-expire log files.
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>maillast</code></em> — Specifies that the just-rotated log files are to be mailed, instead of the about-to-expire log files. This is the default option when <em class="parameter"><code>mail</code></em> is enabled.
+ </div></li></ul></div></li></ul></div><div class="para">
+ For the full list of directives and various configuration options, refer to the <code class="command">logrotate</code> man page (<code class="command">man logrotate</code>).
+ </div></div></div><div class="section" title="17.4. Viewing Log Files" id="s1-logfiles-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-viewing">17.4. Viewing Log Files</h2></div></div></div><a id="id1688182" class="indexterm"></a><div class="para">
+ Most log files are in plain text format. You can view them with any text editor such as <code class="command">Vi</code> or <span class="application"><strong>Emacs</strong></span>. Some log files are readable by all users on the system; however, root privileges are required to read most log files.
+ </div><a id="id839148" class="indexterm"></a><div class="para">
+ To view system log files in an interactive, real-time application, use the <span class="application"><strong>Log File Viewer</strong></span>.
+ </div><div class="note" title="Note: Installing the gnome-system-log package"><div class="admonition_header"><h2>Note: Installing the <span class="package">gnome-system-log</span> package</h2></div><div class="admonition"><div class="para">
+ In order to use the <span class="application"><strong>Log File Viewer</strong></span>, first ensure the <span class="package">gnome-system-log</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install gnome-system-log</code>
+</pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ After you have installed the <span class="package">gnome-system-log</span> package, you can open the <span class="application"><strong>Log File Viewer</strong></span> by clicking on <span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System</strong></span> → <span class="guimenuitem"><strong>Log File Viewer</strong></span>, or type the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">gnome-system-log</code>
+</pre><div class="para">
+ The application only displays log files that exist; thus, the list might differ from the one shown in <a class="xref" href="#fig-redhat-logviewer" title="Figure 17.1. Log File Viewer">Figure 17.1, “ <span class="application">Log File Viewer</span> ”</a>.
+ </div><a id="id965884" class="indexterm"></a><a id="id965902" class="indexterm"></a><div class="figure" title="Figure 17.1. Log File Viewer" id="fig-redhat-logviewer"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-logviewer.png" align="middle" alt="Log File Viewer" /><div class="longdesc"><div class="para">
+ Log File Viewer
+ </div></div></div></div><h6>Figure 17.1. <span class="application">Log File Viewer</span> </h6></div><br class="figure-break" /><a id="id2229964" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Log File Viewer</strong></span> application lets you filter any existing log file. Click on <span class="guimenuitem"><strong>Filters</strong></span> from the menu and select <span class="guimenuitem"><strong>Manage Filters</strong></span> to define or edit your desired filter.
+ </div><div class="figure" title="Figure 17.2. Log File Viewer - Filters" id="fig-redhat-filters"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-filters.png" align="middle" alt="Log File Viewer - Filters" /><div class="longdesc"><div class="para">
+ Log File Viewer - Filters
+ </div></div></div></div><h6>Figure 17.2. <span class="application">Log File Viewer - Filters</span> </h6></div><br class="figure-break" /><div class="para">
+ Adding or editing a filter lets you define its parameters as is shown in <a class="xref" href="#fig-redhat-filter-sample" title="Figure 17.3. Log File Viewer - Defining a Filter">Figure 17.3, “ <span class="application">Log File Viewer - Defining a Filter</span> ”</a>.
+ </div><div class="figure" title="Figure 17.3. Log File Viewer - Defining a Filter" id="fig-redhat-filter-sample"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-filter-sample.png" align="middle" alt="Log File Viewer - Defining a Filter" /><div class="longdesc"><div class="para">
+ Log File Viewer - Defining a Filter
+ </div></div></div></div><h6>Figure 17.3. <span class="application">Log File Viewer - Defining a Filter</span> </h6></div><br class="figure-break" /><div class="para">
+ When defining a filter, you can edit the following parameters:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Name</strong></span> — Specifies the name of the filter.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Regular Expression</strong></span> — Specifies the regular expression that will be applied to the log file and will attempt to match any possible strings of text in it.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Effect</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Highlight</strong></span> — If checked, the found results will be highlighted with the selected color. You may select whether to highlight the background or the foreground of the text.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hide</strong></span> — If checked, the found results will be hidden from the log file you are viewing.
+ </div></li></ul></div></li></ul></div><div class="para">
+ When you have at least one filter defined, you may select it from the <span class="guilabel"><strong>Filters</strong></span> menu and it will automatically search for the strings you have defined in the filter and highlight/hide every successful match in the log file you are currently viewing.
+ </div><div class="figure" title="Figure 17.4. Log File Viewer - Enabling a Filter" id="fig-redhat-filter-enable"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-filter-enable.png" align="middle" alt="Log File Viewer - Enabling a Filter" /><div class="longdesc"><div class="para">
+ Log File Viewer - Enabling a Filter
+ </div></div></div></div><h6>Figure 17.4. <span class="application">Log File Viewer - Enabling a Filter</span> </h6></div><br class="figure-break" /><div class="para">
+ When you check the <span class="guilabel"><strong>Show matches only</strong></span> option, only the matched strings will be shown in the log file you are currently viewing.
+ </div></div><div class="section" title="17.5. Adding a Log File" id="s1-logfiles-adding"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-adding">17.5. Adding a Log File</h2></div></div></div><div class="para">
+ To add a log file you wish to view in the list, select <span class="guimenu"><strong>File</strong></span> → <span class="guimenuitem"><strong>Open</strong></span>. This will display the <span class="guilabel"><strong>Open Log</strong></span> window where you can select the directory and filename of the log file you wish to view.<a class="xref" href="#fig-redhat-logviewer-add" title="Figure 17.5. Log File Viewer - Adding a Log File">Figure 17.5, “Log File Viewer - Adding a Log File”</a> illustrates the <span class="guimenu"><strong>Open Log</strong></span> window.
+ </div><div class="figure" title="Figure 17.5. Log File Viewer - Adding a Log File" id="fig-redhat-logviewer-add"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-logviewer-add.png" align="middle" alt="Log File Viewer - Adding a Log File" /><div class="longdesc"><div class="para">
+ Log File Viewer - Adding a Log File
+ </div></div></div></div><h6>Figure 17.5. Log File Viewer - Adding a Log File</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Open</strong></span> button to open the file. The file is immediately added to the viewing list where you can select it and view its contents.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <span class="application"><strong>Log File Viewer</strong></span> also allows you to open log files zipped in the <code class="literal">.gz</code> format.
+ </div></div></div></div><div class="section" title="17.6. Monitoring Log Files" id="s1-logfiles-examining"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-examining">17.6. Monitoring Log Files</h2></div></div></div><a id="id834768" class="indexterm"></a><a id="id834782" class="indexterm"></a><div class="para">
+ <span class="application"><strong>Log File Viewer</strong></span> monitors all opened logs by default. If a new line is added to a monitored log file, the log name appears in bold in the log list. If the log file is selected or displayed, the new lines appear in bold at the bottom of the log file. <a class="xref" href="#fig-redhat-logviewer-monitoring" title="Figure 17.6. Log File Viewer - New Log Alert">Figure 17.6, “Log File Viewer - New Log Alert”</a> illustrates a new alert in the <span class="guilabel"><strong>cron</strong></span> log file and in the <span class="guilabel"><strong>messages</strong></span> log file. Clicking on the <span class="guimenuitem"><strong>cron</strong></span> log file displays the logs in the file with the new lines in bold.
+ </div><div class="figure" title="Figure 17.6. Log File Viewer - New Log Alert" id="fig-redhat-logviewer-monitoring"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-logviewer-monitoring.png" align="middle" alt="Log File Viewer - New Log Alert" /><div class="longdesc"><div class="para">
+ Log File Viewer - New Log Alert
+ </div></div></div></div><h6>Figure 17.6. Log File Viewer - New Log Alert</h6></div><br class="figure-break" /></div><div class="section" title="17.7. Additional Resources" id="s1-log-files-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-log-files-additional-resources">17.7. Additional Resources</h2></div></div></div><div class="para">
+ To learn more about <span class="application"><strong>rsyslog</strong></span>, <span class="application"><strong>logrotate</strong></span>, and log files in general, refer to the following resources.
+ </div><div class="section" title="17.7.1. Installed Documentation" id="s2-log-files-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-log-files-installed-docs">17.7.1. Installed Documentation</h3></div></div></div><a id="id797482" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">rsyslogd</code> manual page — Type <code class="command">man rsyslogd</code> to learn more about <code class="command">rsyslogd</code> and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">rsyslog.conf</code> manual page — Type <code class="command">man rsyslog.conf</code> to learn more about the <code class="command">/etc/rsyslog.conf</code> configuration file and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em> </code> — After installing the <span class="package">rsyslog</span> package, this directory contains extensive documentation in the <code class="systemitem">html</code> format.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">logrotate</code> manual page — Type <code class="command">man logrotate</code> to learn more about <code class="command">logrotate</code> and its many options.
+ </div></li></ul></div></div><div class="section" title="17.7.2. Useful Websites" id="s2-log-files-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-log-files-useful-websites">17.7.2. Useful Websites</h3></div></div></div><a id="id458560" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.rsyslog.com/">http://www.rsyslog.com/</a> — Offers a thorough technical breakdown of <span class="package">rsyslog</span> features, documentation, configuration examples, and video tutorials.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://wiki.rsyslog.com/index.php/Main_Page">http://wiki.rsyslog.com/index.php/Main_Page</a> — Contains useful <code class="filename">/etc/rsyslog.conf</code> configuration examples.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 18. The sysconfig Directory" id="ch-The_sysconfig_Directory" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 18. The sysconfig Directory</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-sysconfig-files">18.1. Files in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="#s1-sysconfig-etcsysconf-dir">18.2. Directories in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="#s1-sysconfig-additional-resources">18.3. Additional Resources</a></span></dt></dl></div><a id="id701708" class="indexterm"></a><a id="id660263" class="indexterm"></a><div class="para">
+ This chapter outlines some of the files and directories found in the <code class="filename">/etc/sysconfig/</code> directory, their function, and their contents. The information in this chapter is not intended to be complete, as many of these files have a variety of options that are only used in very specific or rare circumstances.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The actual content of your <code class="filename">/etc/sysconfig/</code> directory depends on the programs you have installed on your machine. To find the name of the package the configuration file belongs to, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">yum provides /etc/sysconfig/<em class="replaceable"><code>filename</code></em> </code>
+</pre><div class="para">
+ Refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><div class="section" title="18.1. Files in the /etc/sysconfig/ Directory" id="s1-sysconfig-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysconfig-files">18.1. Files in the <code class="filename">/etc/sysconfig/</code> Directory</h2></div></div></div><a id="id854420" class="indexterm"></a><div class="para">
+ The following sections offer descriptions of files normally found in the <code class="filename">/etc/sysconfig/</code> directory.
+ </div><div class="section" title="18.1.1. /etc/sysconfig/arpwatch" id="s2-sysconfig-arpwatch"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-arpwatch">18.1.1. <code class="filename">/etc/sysconfig/arpwatch</code> </h3></div></div></div><a id="id679300" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/arpwatch</code> file is used to pass arguments to the <code class="command">arpwatch</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">arpwatch</code> daemon. For example:
+ </div><pre class="screen">OPTIONS="-u arpwatch -e root -s 'root (Arpwatch)'"</pre></dd></dl></div></div><div class="section" title="18.1.2. /etc/sysconfig/authconfig" id="s2-sysconfig-authconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-authconfig">18.1.2. <code class="filename">/etc/sysconfig/authconfig</code> </h3></div></div></div><a id="id617759" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/authconfig</code> file sets the authorization to be used on the host. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">USEMKHOMEDIR=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) creating a home directory for a user on the first login. For example:
+ </div><pre class="screen">USEMKHOMEDIR=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEPAMACCESS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the PAM authentication. For example:
+ </div><pre class="screen">USEPAMACCESS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESSSDAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the SSSD authentication. For example:
+ </div><pre class="screen">USESSSDAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESHADOW=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) shadow passwords. For example:
+ </div><pre class="screen">USESHADOW=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEWINBIND=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using Winbind for user account configuration. For example:
+ </div><pre class="screen">USEWINBIND=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEDB=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the FAS authentication. For example:
+ </div><pre class="screen">USEDB=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEFPRINTD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the fingerprint authentication. For example:
+ </div><pre class="screen">USEFPRINTD=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">FORCESMARTCARD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) enforcing the smart card authentication. For example:
+ </div><pre class="screen">FORCESMARTCARD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PASSWDALGORITHM=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The password algorithm. The <em class="replaceable"><code>value</code></em> can be <code class="option">bigcrypt</code>, <code class="option">descrypt</code>, <code class="option">md5</code>, <code class="option">sha256</code>, or <code class="option">sha512</code>. For example:
+ </div><pre class="screen">PASSWDALGORITHM=sha512</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELDAPAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the LDAP authentication. For example:
+ </div><pre class="screen">USELDAPAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELOCAUTHORIZE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the local authorization for local users. For example:
+ </div><pre class="screen">USELOCAUTHORIZE=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USECRACKLIB=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the CrackLib. For example:
+ </div><pre class="screen">USECRACKLIB=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEWINBINDAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the Winbind authentication. For example:
+ </div><pre class="screen">USEWINBINDAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESMARTCARD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the smart card authentication. For example:
+ </div><pre class="screen">USESMARTCARD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELDAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using LDAP for user account configuration. For example:
+ </div><pre class="screen">USELDAP=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USENIS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using NIS for user account configuration. For example:
+ </div><pre class="screen">USENIS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEKERBEROS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the Kerberos authentication. For example:
+ </div><pre class="screen">USEKERBEROS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESYSNETAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) authenticating system accounts with network services. For example:
+ </div><pre class="screen">USESYSNETAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESMBAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the SMB authentication. For example:
+ </div><pre class="screen">USESMBAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESSSD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using SSSD for obtaining user information. For example:
+ </div><pre class="screen">USESSSD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEHESIOD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the Hesoid name service. For example:
+ </div><pre class="screen">USEHESIOD=no</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#ch-Authentication_Configuration" title="Chapter 8. Authentication Configuration">Chapter 8, <i>Authentication Configuration</i></a> for more information on this topic.
+ </div></div><div class="section" title="18.1.3. /etc/sysconfig/autofs" id="s2-sysconfig-autofs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-autofs">18.1.3. <code class="filename">/etc/sysconfig/autofs</code> </h3></div></div></div><a id="id510221" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/autofs</code> file defines custom options for the automatic mounting of devices. This file controls the operation of the automount daemons, which automatically mount file systems when you use them and unmount them after a period of inactivity. File systems can include network file systems, CD-ROM drives, diskettes, and other media.
+ </div><div class="para">
+ By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">MASTER_MAP_NAME=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default name for the master map. For example:
+ </div><pre class="screen">MASTER_MAP_NAME="auto.master"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default mount timeout. For example:
+ </div><pre class="screen">TIMEOUT=300</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">NEGATIVE_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default negative timeout for unsuccessful mount attempts. For example:
+ </div><pre class="screen">NEGATIVE_TIMEOUT=60</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOUNT_WAIT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for a response from <code class="command">mount</code>. For example:
+ </div><pre class="screen">MOUNT_WAIT=-1</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">UMOUNT_WAIT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for a response from <code class="command">umount</code>. For example:
+ </div><pre class="screen">UMOUNT_WAIT=12</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">BROWSE_MODE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) browsing the maps. For example:
+ </div><pre class="screen">BROWSE_MODE="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOUNT_NFS_DEFAULT_PROTOCOL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default protocol to be used by <code class="command">mount.nfs</code>. For example:
+ </div><pre class="screen">MOUNT_NFS_DEFAULT_PROTOCOL=4</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">APPEND_OPTIONS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) appending the global options instead of replacing them. For example:
+ </div><pre class="screen">APPEND_OPTIONS="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LOGGING=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default logging level. The <em class="replaceable"><code>value</code></em> has to be either <code class="option">none</code>, <code class="option">verbose</code>, or <code class="option">debug</code>. For example:
+ </div><pre class="screen">LOGGING="none"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_URI=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of server URIs in the form of <code class="systemitem"><em class="replaceable"><code>protocol</code></em>://<em class="replaceable"><code>server</code></em> </code>. For example:
+ </div><pre class="screen">LDAP_URI="ldaps://ldap.example.com/"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The synchronous API calls timeout. For example:
+ </div><pre class="screen">LDAP_TIMEOUT=-1</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_NETWORK_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The network response timeout. For example:
+ </div><pre class="screen">LDAP_NETWORK_TIMEOUT=8</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SEARCH_BASE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The base Distinguished Name (DN) for the map search. For example:
+ </div><pre class="screen">SEARCH_BASE=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">AUTH_CONF_FILE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default location of the SASL authentication configuration file. For example:
+ </div><pre class="screen">AUTH_CONF_FILE="/etc/autofs_ldap_auth.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MAP_HASH_TABLE_SIZE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The hash table size for the map cache. For example:
+ </div><pre class="screen">MAP_HASH_TABLE_SIZE=1024</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USE_MISC_DEVICE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the autofs miscellaneous device. For example:
+ </div><pre class="screen">USE_MISC_DEVICE="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the LDAP daemon. For example:
+ </div><pre class="screen">OPTIONS=""</pre></dd></dl></div></div><div class="section" title="18.1.4. /etc/sysconfig/clock" id="s2-sysconfig-clock"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-clock">18.1.4. <code class="filename">/etc/sysconfig/clock</code> </h3></div></div></div><a id="id726543" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/clock</code> file controls the interpretation of values read from the system hardware clock. It is used by the <span class="application"><strong>Date/Time Properties</strong></span> tool, and should not be edited by hand. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">ZONE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time zone file under <code class="filename">/usr/share/zoneinfo</code> that <code class="filename">/etc/localtime</code> is a copy of. For example:
+ </div><pre class="screen">ZONE="Europe/Prague"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool" title="13.1. Date/Time Properties Tool">Section 13.1, “Date/Time Properties Tool”</a> for more information on the <span class="application"><strong>Date/Time Properties</strong></span> tool and its usage.
+ </div></div><div class="section" title="18.1.5. /etc/sysconfig/dhcpd" id="s2-sysconfig-dhcpd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-dhcpd">18.1.5. <code class="filename">/etc/sysconfig/dhcpd</code> </h3></div></div></div><a id="id619449" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/dhcpd</code> file is used to pass arguments to the <code class="command">dhcpd</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">DHCPDARGS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">dhcpd</code> daemon. For example:
+ </div><pre class="screen">DHCPDARGS=</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#ch-Dynamic_Host_Configuration_Protocol_DHCP" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)">Chapter 6, <i>Dynamic Host Configuration Protocol (DHCP)</i></a> for more information on DHCP and its usage.
+ </div></div><div class="section" title="18.1.6. /etc/sysconfig/firstboot" id="s2-sysconfig-firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-firewall">18.1.6. <code class="filename">/etc/sysconfig/firstboot</code> </h3></div></div></div><a id="id540857" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/firstboot</code> file defines whether to run the <code class="command">firstboot</code> utility. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">RUN_FIRSTBOOT=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">YES</code>) or disable (<code class="option">NO</code>) running the <code class="command">firstboot</code> program. For example:
+ </div><pre class="screen">RUN_FIRSTBOOT=NO</pre></dd></dl></div><div class="para">
+ The first time the system boots, the <code class="command">init</code> program calls the <code class="filename">/etc/rc.d/init.d/firstboot</code> script, which looks for the <code class="filename">/etc/sysconfig/firstboot</code> file. If this file does not contain the <code class="option">RUN_FIRSTBOOT=NO</code> option, the <code class="command">firstboot</code> program is run, guiding a user through the initial configuration of the system.
+ </div><div class="note" title="Tip: You Can Run the firstboot Program Again"><div class="admonition_header"><h2>Tip: You Can Run the <code class="command">firstboot</code> Program Again</h2></div><div class="admonition"><div class="para">
+ To start the <code class="command">firstboot</code> program the next time the system boots, change the value of <code class="command">RUN_FIRSTBOOT</code> option to <code class="option">YES</code>, and type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">chkconfig firstboot on</code>
+</pre></div></div></div><div class="section" title="18.1.7. /etc/sysconfig/i18n" id="s2-sysconfig-i18n"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-i18n">18.1.7. <code class="filename">/etc/sysconfig/i18n</code> </h3></div></div></div><div class="para">
+ The <code class="filename">/etc/sysconfig/i18n</code> configuration file defines the default language, any supported languages, and the default system font. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">LANG=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default language. For example:
+ </div><pre class="screen">LANG="en_US.UTF-8"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SUPPORTED=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A colon-separated list of supported languages. For example:
+ </div><pre class="screen">SUPPORTED="en_US.UTF-8:en_US:en"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SYSFONT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default system font. For example:
+ </div><pre class="screen">SYSFONT="latarcyrheb-sun16"</pre></dd></dl></div></div><div class="section" title="18.1.8. /etc/sysconfig/init" id="s2-sysconfig-init"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-init">18.1.8. <code class="filename">/etc/sysconfig/init</code> </h3></div></div></div><a id="id669758" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/init</code> file controls how the system appears and functions during the boot process. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">BOOTUP=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The bootup style. The value has to be either <code class="option">color</code> (the standard color boot display), <code class="option">verbose</code> (an old style display which provides more information), or anything else for the new style display, but without ANSI formatting. For example:
+ </div><pre class="screen">BOOTUP=color</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RES_COL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The number of the column in which the status labels start. For example:
+ </div><pre class="screen">RES_COL=60</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOVE_TO_COL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to move the cursor to the column specified in <code class="option">RES_COL</code> (see above). For example:
+ </div><pre class="screen">MOVE_TO_COL="echo -en \\033[${RES_COL}G"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_SUCCESS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the success color. For example:
+ </div><pre class="screen">SETCOLOR_SUCCESS="echo -en \\033[0;32m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_FAILURE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the failure color. For example:
+ </div><pre class="screen">SETCOLOR_FAILURE="echo -en \\033[0;31m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_WARNING=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the warning color. For example:
+ </div><pre class="screen">SETCOLOR_WARNING="echo -en \\033[0;33m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_NORMAL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the default color. For example:
+ </div><pre class="screen">SETCOLOR_NORMAL="echo -en \\033[0;39m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LOGLEVEL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The initial console logging level. The <em class="replaceable"><code>value</code></em> has to be in the range from <code class="option">1</code> (kernel panics only) to <code class="option">8</code> (everything, including the debugging information). For example:
+ </div><pre class="screen">LOGLEVEL=3</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PROMPT=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the hotkey interactive startup. For example:
+ </div><pre class="screen">PROMPT=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">AUTOSWAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) probing for devices with swap signatures. For example:
+ </div><pre class="screen">AUTOSWAP=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ACTIVE_CONSOLES=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The list of active consoles. For example:
+ </div><pre class="screen">ACTIVE_CONSOLES=/dev/tty[1-6]</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SINGLE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The single-user mode type. The <em class="replaceable"><code>value</code></em> has to be either <code class="option">/sbin/sulogin</code> (a user will be prompted for a password to log in), or <code class="option">/sbin/sushell</code> (the user will be logged in directly). For example:
+ </div><pre class="screen">SINGLE=/sbin/sushell</pre></dd></dl></div></div><div class="section" title="18.1.9. /etc/sysconfig/ip6tables-config" id="s2-sysconfig-ip6tables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-ip6tables">18.1.9. <code class="filename">/etc/sysconfig/ip6tables-config</code> </h3></div></div></div><a id="id568595" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ip6tables-config</code> file stores information used by the kernel to set up IPv6 packet filtering at boot time or whenever the <code class="command">ip6tables</code> service is started. Note that you should not modify it unless you are familiar with <code class="command">ip6tables</code> rules. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_MODULES=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of helpers to be loaded after the firewall rules are applied. For example:
+ </div><pre class="screen">IP6TABLES_MODULES="ip_nat_ftp ip_nat_irc"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_MODULES_UNLOAD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) module unloading when the firewall is stopped or restarted. For example:
+ </div><pre class="screen">IP6TABLES_MODULES_UNLOAD="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_ON_STOP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the current firewall rules when the firewall is stopped. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_ON_STOP="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_ON_RESTART=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the current firewall rules when the firewall is restarted. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_ON_RESTART="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_COUNTER=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the rule and chain counters. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_COUNTER="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_NUMERIC=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing IP addresses and port numbers in a numeric format in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_NUMERIC="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_VERBOSE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing information about the number of packets and bytes in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_VERBOSE="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_LINENUMBERS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing line numbers in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_LINENUMBERS="yes"</pre></dd></dl></div><div class="para">
+ </div><div class="note" title="Tip: Use the ip6tables Command to Create the Rules"><div class="admonition_header"><h2>Tip: Use the <code class="command">ip6tables</code> Command to Create the Rules</h2></div><div class="admonition"><div class="para">
+ You can create the rules manually using the <code class="command">ip6tables</code> command. Once created, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service ip6tables save</code>
+</pre><div class="para">
+ This will add the rules to <code class="filename">/etc/sysconfig/ip6tables</code>. Once this file exists, any firewall rules saved in it persist through a system reboot or a service restart.
+ </div></div></div></div><div class="section" title="18.1.10. /etc/sysconfig/keyboard" id="s2-sysconfig-kybd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-kybd">18.1.10. <code class="filename">/etc/sysconfig/keyboard</code> </h3></div></div></div><a id="id779018" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/keyboard</code> file controls the behavior of the keyboard. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">KEYTABLE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The name of a keytable file. The files that can be used as keytables start in the <code class="filename">/lib/kbd/keymaps/i386/</code> directory, and branch into different keyboard layouts from there, all labeled <code class="filename"><em class="replaceable"><code>value</code></em>.kmap.gz</code>. The first filename that matches the <code class="option">KEYTABLE</code> setting is used. For example:
+ </div><pre class="screen">KEYTABLE="us"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MODEL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard model. For example:
+ </div><pre class="screen">MODEL="pc105+inet"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LAYOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard layout. For example:
+ </div><pre class="screen">LAYOUT="us"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">KEYBOARDTYPE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard type. Allowed values are <code class="option">pc</code> (a PS/2 keyboard), or <code class="option">sun</code> (a Sun keyboard). For example:
+ </div><pre class="screen">KEYBOARDTYPE="pc"</pre></dd></dl></div></div><div class="section" title="18.1.11. /etc/sysconfig/ldap" id="s2-sysconfig-ldap"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-ldap">18.1.11. <code class="filename">/etc/sysconfig/ldap</code> </h3></div></div></div><a id="id544314" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ldap</code> file holds the basic configuration for the LDAP server. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">slapd</code> daemon. For example:
+ </div><pre class="screen">SLAPD_OPTIONS="-4"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLURPD_OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">slurpd</code> daemon. For example:
+ </div><pre class="screen">SLURPD_OPTIONS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over TCP (that is, <code class="systemitem">ldap:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAP="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAPI=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over IPC (that is, <code class="systemitem">ldapi:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAPI="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAPS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over TLS (that is, <code class="systemitem">ldaps:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAPS="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_URLS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of URLs. For example:
+ </div><pre class="screen">SLAPD_URLS="ldapi:///var/lib/ldap_root/ldapi ldapi:/// ldaps:///"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_SHUTDOWN_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for <code class="command">slapd</code> to shut down. For example:
+ </div><pre class="screen">SLAPD_SHUTDOWN_TIMEOUT=3</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_ULIMIT_SETTINGS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The parameters to be passed to <code class="command">ulimit</code> before the <code class="command">slapd</code> daemon is started. For example:
+ </div><pre class="screen">SLAPD_ULIMIT_SETTINGS=""</pre></dd></dl></div></div><div class="section" title="18.1.12. /etc/sysconfig/named" id="s2-sysconfig-named"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-named">18.1.12. <code class="filename">/etc/sysconfig/named</code> </h3></div></div></div><a id="id693480" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/named</code> file is used to pass arguments to the <code class="command">named</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">ROOTDIR=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The chroot environment under which the <code class="command">named</code> daemon runs. The <em class="replaceable"><code>value</code></em> has to be a full directory path. For example:
+ </div><pre class="screen">ROOTDIR="/var/named/chroot"</pre><div class="para">
+ Note that the chroot environment has to be configured first (type <code class="command">info chroot</code> at a shell prompt for more information).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">named</code>. For example:
+ </div><pre class="screen">OPTIONS="-6"</pre><div class="para">
+ Note that you should not use the <code class="option">-t</code> option. Instead, use <code class="option">ROOTDIR</code> as described above.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">KEYTAB_FILE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keytab filename. For example:
+ </div><pre class="screen">KEYTAB_FILE="/etc/named.keytab"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#ch-The_BIND_DNS_Server" title="Chapter 10. The BIND DNS Server">Chapter 10, <i>The BIND DNS Server</i></a> for more information on the BIND DNS server and its configuration.
+ </div></div><div class="section" title="18.1.13. /etc/sysconfig/network" id="s2-sysconfig-network"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-network">18.1.13. <code class="filename">/etc/sysconfig/network</code> </h3></div></div></div><a id="id970424" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/network</code> file is used to specify information about the desired network configuration. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">NETWORKING=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the networking. For example:
+ </div><pre class="screen">NETWORKING=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">HOSTNAME=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The hostname of the machine. For example:
+ </div><pre class="screen">HOSTNAME=penguin.example.com</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">GATEWAY=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The IP address of the network's gateway. For example:
+ </div><pre class="screen">GATEWAY=192.168.1.0</pre></dd></dl></div><div class="warning" title="Warning: Avoid Using Custom Init Scripts"><div class="admonition_header"><h2>Warning: Avoid Using Custom Init Scripts</h2></div><div class="admonition"><div class="para">
+ Do not use custom init scripts to configure network settings. When performing a post-boot network service restart, custom init scripts configuring network settings that are run outside of the network init script lead to unpredictable results.
+ </div></div></div></div><div class="section" title="18.1.14. /etc/sysconfig/ntpd" id="s2-sysconfig-ntpd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-ntpd">18.1.14. <code class="filename">/etc/sysconfig/ntpd</code> </h3></div></div></div><a id="id687840" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ntpd</code> file is used to pass arguments to the <code class="command">ntpd</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">ntpd</code>. For example:
+ </div><pre class="screen">OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid -g"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#sect-Date_and_Time_Configuration-Network_Time_Protocol" title="13.1.2. Network Time Protocol Properties">Section 13.1.2, “Network Time Protocol Properties”</a> or <a class="xref" href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol" title="13.2.2. Network Time Protocol Setup">Section 13.2.2, “Network Time Protocol Setup”</a> for more information on how to configure the <code class="command">ntpd</code> daemon.
+ </div></div><div class="section" title="18.1.15. /etc/sysconfig/quagga" id="s2-sysconfig-quagga"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-quagga">18.1.15. <code class="filename">/etc/sysconfig/quagga</code> </h3></div></div></div><a id="id483114" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/quagga</code> file holds the basic configuration for Quagga daemons. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">QCONFDIR=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The directory with the configuration files for Quagga daemons. For example:
+ </div><pre class="screen">QCONFDIR="/etc/quagga"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">BGPD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">bgpd</code> daemon. For example:
+ </div><pre class="screen">BGPD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/bgpd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OSPF6D_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ospf6d</code> daemon. For example:
+ </div><pre class="screen">OSPF6D_OPTS="-A ::1 -f ${QCONFDIR}/ospf6d.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OSPFD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ospfd</code> daemon. For example:
+ </div><pre class="screen">OSPFD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/ospfd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RIPD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ripd</code> daemon. For example:
+ </div><pre class="screen">RIPD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/ripd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RIPNGD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ripngd</code> daemon. For example:
+ </div><pre class="screen">RIPNGD_OPTS="-A ::1 -f ${QCONFDIR}/ripngd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ZEBRA_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">zebra</code> daemon. For example:
+ </div><pre class="screen">ZEBRA_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/zebra.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ISISD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">isisd</code> daemon. For example:
+ </div><pre class="screen">ISISD_OPTS="-A ::1 -f ${QCONFDIR}/isisd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WATCH_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">watchquagga</code> daemon. For example:
+ </div><pre class="screen">WATCH_OPTS="-Az -b_ -r/sbin/service_%s_restart -s/sbin/service_%s_start -k/sbin/service_%s_stop"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WATCH_DAEMONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space separated list of monitored daemons. For example:
+ </div><pre class="screen">WATCH_DAEMONS="zebra bgpd ospfd ospf6d ripd ripngd"</pre></dd></dl></div></div><div class="section" title="18.1.16. /etc/sysconfig/radvd" id="s2-sysconfig-radvd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-radvd">18.1.16. <code class="filename">/etc/sysconfig/radvd</code> </h3></div></div></div><a id="id765182" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/radvd</code> file is used to pass arguments to the <code class="command">radvd</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">radvd</code> daemon. For example:
+ </div><pre class="screen">OPTIONS="-u radvd"</pre></dd></dl></div></div><div class="section" title="18.1.17. /etc/sysconfig/samba" id="s2-sysconfig-samba"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-samba">18.1.17. <code class="filename">/etc/sysconfig/samba</code> </h3></div></div></div><a id="id739426" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/samba</code> file is used to pass arguments to the Samba daemons at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">SMBDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">smbd</code>. For example:
+ </div><pre class="screen">SMBDOPTIONS="-D"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">NMBDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">nmbd</code>. For example:
+ </div><pre class="screen">NMBDOPTIONS="-D"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WINBINDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">winbindd</code>. For example:
+ </div><pre class="screen">WINBINDOPTIONS=""</pre></dd></dl></div></div><div class="section" title="18.1.18. /etc/sysconfig/selinux" id="s2-sysconfig-selinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-selinux">18.1.18. <code class="filename">/etc/sysconfig/selinux</code> </h3></div></div></div><a id="id801660" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/selinux</code> file contains the basic configuration options for SELinux. It is a symbolic link to <code class="filename">/etc/selinux/config</code>, and by default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">SELINUX=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The security policy. The <em class="replaceable"><code>value </code></em> can be either <code class="option">enforcing</code> (the security policy is always enforced), <code class="option">permissive</code> (instead of enforcing the policy, appropriate warnings are displayed), or <code class="option">disabled</code> (no policy is used). For example:
+ </div><pre class="screen">SELINUX=enforcing</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SELINUXTYPE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The protection type. The <em class="replaceable"><code>value</code></em> can be either <code class="option">targeted</code> (the targeted processes are protected), or <code class="option">mls</code> (the Multi Level Security protection). For example:
+ </div><pre class="screen">SELINUXTYPE=targeted</pre></dd></dl></div></div><div class="section" title="18.1.19. /etc/sysconfig/sendmail" id="s2-sysconfig-sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-sendmail">18.1.19. <code class="filename">/etc/sysconfig/sendmail</code> </h3></div></div></div><a id="id744553" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/sendmail</code> is used to set the default values for the <span class="application"><strong>Sendmail</strong></span> application. By default, it contains the following values:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">DAEMON=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) running <code class="command">sendmail</code> as a daemon. For example:
+ </div><pre class="screen">DAEMON=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">QUEUE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The interval at which the messages are to be processed. For example:
+ </div><pre class="screen">QUEUE=1h</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#s2-email-mta-sendmail" title="12.3.2. Sendmail">Section 12.3.2, “Sendmail”</a> for more information on Sendmail and its configuration.
+ </div></div><div class="section" title="18.1.20. /etc/sysconfig/spamassassin" id="s2-sysconfig-spamd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-spamd">18.1.20. <code class="filename">/etc/sysconfig/spamassassin</code> </h3></div></div></div><a id="id515050" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/spamassassin</code> file is used to pass arguments to the <code class="command">spamd</code> daemon (a daemonized version of <span class="application"><strong>Spamassassin</strong></span>) at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">SPAMDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">spamd</code> daemon. For example:
+ </div><pre class="screen">SPAMDOPTIONS="-d -c -m5 -H"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#s3-email-mda-spam" title="12.4.2.6. Spam Filters">Section 12.4.2.6, “Spam Filters”</a> for more information on Spamassassin and its configuration.
+ </div></div><div class="section" title="18.1.21. /etc/sysconfig/squid" id="s2-sysconfig-squid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-squid">18.1.21. <code class="filename">/etc/sysconfig/squid</code> </h3></div></div></div><a id="id867080" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/squid</code> file is used to pass arguments to the <code class="command">squid</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">SQUID_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">squid</code> daemon. For example:
+ </div><pre class="screen">SQUID_OPTS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SQUID_SHUTDOWN_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for <code class="command">squid</code> daemon to shut down. For example:
+ </div><pre class="screen">SQUID_SHUTDOWN_TIMEOUT=100</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SQUID_CONF=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default configuration file. For example:
+ </div><pre class="screen">SQUID_CONF="/etc/squid/squid.conf"</pre></dd></dl></div></div><div class="section" title="18.1.22. /etc/sysconfig/system-config-users" id="s2-sysconfig-rcu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-rcu">18.1.22. <code class="filename">/etc/sysconfig/system-config-users</code> </h3></div></div></div><a id="id967662" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/system-config-users</code> file is the configuration file for the <span class="application"><strong>User Manager</strong></span> utility, and should not be edited by hand. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">FILTER=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) filtering of system users. For example:
+ </div><pre class="screen">FILTER=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ASSIGN_HIGHEST_UID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) assigning the highest available UID to newly added users. For example:
+ </div><pre class="screen">ASSIGN_HIGHEST_UID=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ASSIGN_HIGHEST_GID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) assigning the highest available GID to newly added groups. For example:
+ </div><pre class="screen">ASSIGN_HIGHEST_GID=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PREFER_SAME_UID_GID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) using the same UID and GID for newly added users when possible. For example:
+ </div><pre class="screen">PREFER_SAME_UID_GID=true</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#s1-users-configui" title="15.1. User and Group Configuration">Section 15.1, “User and Group Configuration”</a> for more information on <span class="application"><strong>User Manager</strong></span> and its usage.
+ </div></div><div class="section" title="18.1.23. /etc/sysconfig/vncservers" id="s2-sysconfig-vncservers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-vncservers">18.1.23. <code class="filename">/etc/sysconfig/vncservers</code> </h3></div></div></div><a id="id500383" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/vncservers</code> file configures the way the <em class="firstterm">Virtual Network Computing</em> (<em class="firstterm">VNC</em>) server starts up. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">VNCSERVERS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A list of space separated <code class="option"><em class="replaceable"><code>display</code></em>:<em class="replaceable"><code>username</code></em> </code> pairs. For example:
+ </div><pre class="screen">VNCSERVERS="2:myusername"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">VNCSERVERARGS[<em class="replaceable"><code>display</code></em>]=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional arguments to be passed to the VNC server running on the specified <em class="replaceable"><code>display</code></em>. For example:
+ </div><pre class="screen">VNCSERVERARGS[2]="-geometry 800x600 -nolisten tcp -localhost"</pre></dd></dl></div></div><div class="section" title="18.1.24. /etc/sysconfig/xinetd" id="s2-sysconfig-xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-xinetd">18.1.24. <code class="filename">/etc/sysconfig/xinetd</code> </h3></div></div></div><a id="id651500" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/xinetd</code> file is used to pass arguments to the <code class="command">xinetd</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">EXTRAOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">xinetd</code>. For example:
+ </div><pre class="screen">EXTRAOPTIONS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">XINETD_LANG=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The locale information to be passed to every service started by <code class="command">xinetd</code>. Note that to remove locale information from the <code class="command">xinetd</code> environment, you can use an empty string (<code class="option">""</code>) or <code class="option">none</code>. For example:
+ </div><pre class="screen">XINETD_LANG="en_US"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for more information on how to configure the <code class="command">xinetd</code> services.
+ </div></div></div><div class="section" title="18.2. Directories in the /etc/sysconfig/ Directory" id="s1-sysconfig-etcsysconf-dir"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysconfig-etcsysconf-dir">18.2. Directories in the <code class="filename">/etc/sysconfig/</code> Directory</h2></div></div></div><a id="id768399" class="indexterm"></a><div class="para">
+ The following directories are normally found in <code class="filename">/etc/sysconfig/</code>.
+ </div><a id="id768425" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/cbq/</code> </span></dt><dd><div class="para">
+ <a id="id781069" class="indexterm"></a>
+ This directory contains the configuration files needed to do <em class="firstterm">Class Based Queuing</em> for bandwidth management on network interfaces. CBQ divides user traffic into a hierarchy of classes based on any combination of IP addresses, protocols, and application types.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/networking/</code> </span></dt><dd><div class="para">
+ <a id="id781119" class="indexterm"></a>
+ This directory is used by the <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>), and its contents should not be edited manually. For more information about configuring network interfaces using the <span class="application"><strong>Network Administration Tool</strong></span>, refer to <a class="xref" href="#ch-Network_Configuration" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/network-scripts/</code> </span></dt><dd><div class="para">
+ <a id="id1566590" class="indexterm"></a>
+ This directory contains the following network-related configuration files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Network configuration files for each configured network interface, such as <code class="filename">ifcfg-eth0</code> for the <code class="systemitem">eth0</code> Ethernet interface.
+ </div></li><li class="listitem"><div class="para">
+ Scripts used to bring network interfaces up and down, such as <code class="command">ifup</code> and <code class="command">ifdown</code>.
+ </div></li><li class="listitem"><div class="para">
+ Scripts used to bring ISDN interfaces up and down, such as <code class="command">ifup-isdn</code> and <code class="command">ifdown-isdn</code>.
+ </div></li><li class="listitem"><div class="para">
+ Various shared network function scripts which should not be edited directly.
+ </div></li></ul></div><div class="para">
+ For more information on the <code class="filename">/etc/sysconfig/network-scripts/</code> directory, refer to <a class="xref" href="#ch-Network_Interfaces" title="Chapter 4. Network Interfaces">Chapter 4, <i>Network Interfaces</i></a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/rhn/</code> </span></dt><dd><div class="para">
+ <a id="id638340" class="indexterm"></a>
+ This directory contains the configuration files and GPG keys for Red Hat Network. No files in this directory should be edited by hand. For more information on Red Hat Network, refer to the Red Hat Network website online at <a href="https://rhn.redhat.com/">https://rhn.redhat.com/</a>.
+ </div></dd></dl></div></div><div class="section" title="18.3. Additional Resources" id="s1-sysconfig-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysconfig-additional-resources">18.3. Additional Resources</h2></div></div></div><a id="id468763" class="indexterm"></a><div class="para">
+ This chapter is only intended as an introduction to the files in the <code class="filename">/etc/sysconfig/</code> directory. The following source contains more comprehensive information.
+ </div><div class="section" title="18.3.1. Installed Documentation" id="s2-sysconfig-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-installed-documentation">18.3.1. Installed Documentation</h3></div></div></div><a id="id468800" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code>version</code></em>/sysconfig.txt</code> </span></dt><dd><div class="para">
+ A more authoritative listing of the files found in the <code class="filename">/etc/sysconfig/</code> directory and the configuration options available for them.
+ </div></dd></dl></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 19. The proc File System" id="ch-proc" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. The <code class="filename">proc</code> File System</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-proc-virtual">19.1. A Virtual File System</a></span></dt><dt><span class="section"><a href="#s1-proc-topfiles">19.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dt><span class="section"><a href="#s1-proc-directories">19.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dt><span class="section"><a href="#s1-proc-sysctl">19.4. Using the <code class="command">sysctl</code> Command</a></span></dt><dt><span class="section"><a href="#s1-proc-additional-resources">19.5. References</a></span></dt></dl></div><a id="id693738" class="indexterm"></a><a id="id415711" class
="indexterm"></a><div class="para">
+ The Linux kernel has two primary functions: to control access to physical devices on the computer and to schedule when and how processes interact with these devices. The <code class="filename">/proc/</code> directory (also called the <code class="filename">proc</code> file system) contains a hierarchy of special files which represent the current state of the kernel, allowing applications and users to peer into the kernel's view of the system.
+ </div><div class="para">
+ The <code class="filename">/proc/</code> directory contains a wealth of information detailing system hardware and any running processes. In addition, some of the files within <code class="filename">/proc/</code> can be manipulated by users and applications to communicate configuration changes to the kernel.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Later versions of the 2.6 kernel have made the <code class="filename">/proc/ide/</code> and <code class="filename">/proc/pci/</code> directories obsolete. The <code class="command">/proc/ide/</code> file system is now superseded by files in <code class="command">sysfs</code>; to retrieve information on PCI devices, use <code class="command">lspci</code> instead. For more information on <code class="command">sysfs</code> or <code class="command">lspci</code>, refer to their respective <code class="command">man</code> pages.
+ </div></div></div><div class="section" title="19.1. A Virtual File System" id="s1-proc-virtual"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-proc-virtual">19.1. A Virtual File System</h2></div></div></div><a id="id2338472" class="indexterm"></a><a id="id616774" class="indexterm"></a><a id="id610850" class="indexterm"></a><div class="para">
+ Linux systems store all data as <span class="emphasis"><em>files</em></span>. Most users are familiar with the two primary types of files: text and binary. But the <code class="filename">/proc/</code> directory contains another type of file called a <em class="firstterm">virtual file</em>. As such, <code class="filename">/proc/</code> is often referred to as a <em class="firstterm">virtual file system</em>.
+ </div><div class="para">
+ Virtual files have unique qualities. Most of them are listed as zero bytes in size, but can still contain a large amount of information when viewed. In addition, most of the time and date stamps on virtual files reflect the current time and date, indicative of the fact they are constantly updated.
+ </div><div class="para">
+ Virtual files such as <code class="filename">/proc/interrupts</code>, <code class="filename">/proc/meminfo</code>, <code class="filename">/proc/mounts</code>, and <code class="filename">/proc/partitions</code> provide an up-to-the-moment glimpse of the system's hardware. Others, like the <code class="filename">/proc/filesystems</code> file and the <code class="filename">/proc/sys/</code> directory provide system configuration information and interfaces.
+ </div><div class="para">
+ For organizational purposes, files containing information on a similar topic are grouped into virtual directories and sub-directories. Process directories contain information about each running process on the system.
+ </div><div class="section" title="19.1.1. Viewing Virtual Files" id="s2-proc-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-viewing">19.1.1. Viewing Virtual Files</h3></div></div></div><a id="id481033" class="indexterm"></a><a id="id481046" class="indexterm"></a><div class="para">
+ Most files within <code class="filename">/proc/</code> files operate similarly to text files, storing useful system and hardware data in human-readable text format. As such, you can use <code class="command">cat</code>, <code class="command">more</code>, or <code class="command">less</code> to view them. For example, to display information about the system's CPU, run <code class="command">cat /proc/cpuinfo</code>. This will return output similar to the following:
+ </div><pre class="screen">
+processor : 0
+vendor_id : AuthenticAMD
+cpu family : 5
+model : 9
+model name : AMD-K6(tm) 3D+
+Processor stepping : 1 cpu
+MHz : 400.919
+cache size : 256 KB
+fdiv_bug : no
+hlt_bug : no
+f00f_bug : no
+coma_bug : no
+fpu : yes
+fpu_exception : yes
+cpuid level : 1
+wp : yes
+flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr
+bogomips : 799.53
+</pre><div class="para">
+ Some files in <code class="command">/proc/</code> contain information that is not human-readable. To retrieve information from such files, use tools such as <code class="command">lspci</code>, <code class="command">apm</code>, <code class="command">free</code>, and <code class="command">top</code>.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Some of the virtual files in the <code class="filename">/proc/</code> directory are readable only by the root user.
+ </div></div></div></div><div class="section" title="19.1.2. Changing Virtual Files" id="s2-proc-change"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-change">19.1.2. Changing Virtual Files</h3></div></div></div><a id="id822628" class="indexterm"></a><a id="id822642" class="indexterm"></a><div class="para">
+ As a general rule, most virtual files within the <code class="filename">/proc/</code> directory are read-only. However, some can be used to adjust settings in the kernel. This is especially true for files in the <code class="filename">/proc/sys/</code> subdirectory.
+ </div><div class="para">
+ To change the value of a virtual file, use the following command:
+ </div><div class="para">
+ <code class="command">echo <em class="replaceable"><code>value</code></em> > /proc/<em class="replaceable"><code>file</code></em> </code>
+ </div><div class="para">
+ For example, to change the hostname on the fly, run:
+ </div><div class="para">
+ <code class="command">echo <em class="replaceable"><code>www.example.com</code></em> > /proc/sys/kernel/hostname </code>
+ </div><div class="para">
+ Other files act as binary or Boolean switches. Typing <code class="command">cat /proc/sys/net/ipv4/ip_forward</code> returns either a <code class="computeroutput">0</code> (off or false) or a <code class="computeroutput">1</code> (on or true). A <code class="computeroutput">0</code> indicates that the kernel is not forwarding network packets. To turn packet forwarding on, run <code class="command">echo 1 > /proc/sys/net/ipv4/ip_forward</code>.
+ </div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ Another command used to alter settings in the <code class="filename">/proc/sys/</code> subdirectory is <code class="command">/sbin/sysctl</code>. For more information on this command, refer to <a class="xref" href="#s1-proc-sysctl" title="19.4. Using the sysctl Command">Section 19.4, “Using the <code class="command">sysctl</code> Command”</a>
+ </div></div></div><div class="para">
+ For a listing of some of the kernel configuration files available in the <code class="filename">/proc/sys/</code> subdirectory, refer to <a class="xref" href="#s2-proc-dir-sys" title="19.3.9. /proc/sys/">Section 19.3.9, “ <code class="filename">/proc/sys/</code> ”</a>.
+ </div></div></div><div class="section" title="19.2. Top-level Files within the proc File System" id="s1-proc-topfiles"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-proc-topfiles">19.2. Top-level Files within the <code class="filename">proc</code> File System</h2></div></div></div><a id="id735419" class="indexterm"></a><div class="para">
+ Below is a list of some of the more useful virtual files in the top-level of the <code class="filename">/proc/</code> directory.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ In most cases, the content of the files listed in this section are not the same as those installed on your machine. This is because much of the information is specific to the hardware on which Fedora is running for this documentation effort.
+ </div></div></div><div class="section" title="19.2.1. /proc/buddyinfo" id="s2-proc-buddyinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-buddyinfo">19.2.1. <code class="filename">/proc/buddyinfo</code> </h3></div></div></div><a id="id697785" class="indexterm"></a><div class="para">
+ This file is used primarily for diagnosing memory fragmentation issues. Using the buddy algorithm, each column represents the number of pages of a certain order (a certain size) that are available at any given time. For example, for zone <em class="firstterm">direct memory access</em> (DMA), there are 90 of 2<sup>(0*PAGE_SIZE)</sup> chunks of memory. Similarly, there are 6 of 2<sup>(1*PAGE_SIZE)</sup> chunks, and 2 of 2<sup>(2*PAGE_SIZE)</sup> chunks of memory available.
+ </div><div class="para">
+ The <code class="computeroutput">DMA</code> row references the first 16 MB on a system, the <code class="computeroutput">HighMem</code> row references all memory greater than 4 GB on a system, and the <code class="computeroutput">Normal</code> row references all memory in between.
+ </div><div class="para">
+ The following is an example of the output typical of <code class="filename">/proc/buddyinfo</code>:
+ </div><pre class="screen">
+Node 0, zone DMA 90 6 2 1 1 ...
+Node 0, zone Normal 1650 310 5 0 0 ...
+Node 0, zone HighMem 2 0 0 1 1 ...
+</pre></div><div class="section" title="19.2.2. /proc/cmdline" id="s2-proc-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-cmdline">19.2.2. <code class="filename">/proc/cmdline</code> </h3></div></div></div><a id="id621939" class="indexterm"></a><div class="para">
+ This file shows the parameters passed to the kernel at the time it is started. A sample <code class="filename">/proc/cmdline</code> file looks like the following:
+ </div><pre class="screen">
+ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3
+</pre><div class="para">
+ This tells us that the kernel is mounted read-only (signified by <code class="computeroutput">(ro)</code>), located on the first logical volume (<code class="computeroutput">LogVol00</code>) of the first volume group (<code class="computeroutput">/dev/VolGroup00</code>). <code class="computeroutput">LogVol00</code> is the equivalent of a disk partition in a non-LVM system (Logical Volume Management), just as <code class="computeroutput">/dev/VolGroup00</code> is similar in concept to <code class="filename">/dev/hda1</code>, but much more extensible.
+ </div><div class="para">
+ For more information on LVM used in Fedora, refer to <a href="http://www.tldp.org/HOWTO/LVM-HOWTO/index.html">http://www.tldp.org/HOWTO/LVM-HOWTO/index.html</a>.
+ </div><div class="para">
+ Next, <code class="computeroutput">rhgb</code> signals that the <code class="filename">rhgb</code> package has been installed, and graphical booting is supported, assuming <code class="filename">/etc/inittab</code> shows a default runlevel set to <code class="command">id:5:initdefault:</code>.
+ </div><div class="para">
+ Finally, <code class="computeroutput">quiet</code> indicates all verbose kernel messages are suppressed at boot time.
+ </div></div><div class="section" title="19.2.3. /proc/cpuinfo" id="s2-proc-cpuinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-cpuinfo">19.2.3. <code class="filename">/proc/cpuinfo</code> </h3></div></div></div><a id="id598179" class="indexterm"></a><div class="para">
+ This virtual file identifies the type of processor used by your system. The following is an example of the output typical of <code class="filename">/proc/cpuinfo</code>:
+ </div><pre class="screen">
+processor : 0
+vendor_id : GenuineIntel
+cpu family : 15
+model : 2
+model name : Intel(R) Xeon(TM) CPU 2.40GHz
+stepping : 7 cpu
+MHz : 2392.371
+cache size : 512 KB
+physical id : 0
+siblings : 2
+runqueue : 0
+fdiv_bug : no
+hlt_bug : no
+f00f_bug : no
+coma_bug : no
+fpu : yes
+fpu_exception : yes
+cpuid level : 2
+wp : yes
+flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
+bogomips : 4771.02
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">processor</code> — Provides each processor with an identifying number. On systems that have one processor, only a <code class="computeroutput">0</code> is present.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu family</code> — Authoritatively identifies the type of processor in the system. For an Intel-based system, place the number in front of "86" to determine the value. This is particularly helpful for those attempting to identify the architecture of an older system such as a 586, 486, or 386. Because some RPM packages are compiled for each of these particular architectures, this value also helps users determine which packages to install.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">model name</code> — Displays the common name of the processor, including its project name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu MHz</code> — Shows the precise speed in megahertz for the processor to the thousandths decimal place.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cache size</code> — Displays the amount of level 2 memory cache available to the processor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">siblings</code> — Displays the number of sibling CPUs on the same physical CPU for architectures which use hyper-threading.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">flags</code> — Defines a number of different qualities about the processor, such as the presence of a floating point unit (FPU) and the ability to process MMX instructions.
+ </div></li></ul></div></div><div class="section" title="19.2.4. /proc/crypto" id="s2-proc-crypto"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-crypto">19.2.4. <code class="filename">/proc/crypto</code> </h3></div></div></div><a id="id1038217" class="indexterm"></a><div class="para">
+ This file lists all installed cryptographic ciphers used by the Linux kernel, including additional details for each. A sample <code class="filename">/proc/crypto</code> file looks like the following:
+ </div><pre class="screen">
+name : sha1
+module : kernel
+type : digest
+blocksize : 64
+digestsize : 20
+name : md5
+module : md5
+type : digest
+blocksize : 64
+digestsize : 16
+</pre></div><div class="section" title="19.2.5. /proc/devices" id="s2-proc-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-devices">19.2.5. <code class="filename">/proc/devices</code> </h3></div></div></div><a id="id528746" class="indexterm"></a><a id="id528772" class="indexterm"></a><a id="id486656" class="indexterm"></a><a id="id486669" class="indexterm"></a><a id="id486687" class="indexterm"></a><a id="id486705" class="indexterm"></a><div class="para">
+ This file displays the various character and block devices currently configured (not including devices whose modules are not loaded). Below is a sample output from this file:
+ </div><pre class="screen">
+Character devices:
+ 1 mem
+ 4 /dev/vc/0
+ 4 tty
+ 4 ttyS
+ 5 /dev/tty
+ 5 /dev/console
+ 5 /dev/ptmx
+ 7 vcs
+ 10 misc
+ 13 input
+ 29 fb
+ 36 netlink
+ 128 ptm
+ 136 pts
+ 180 usb
+
+Block devices:
+ 1 ramdisk
+ 3 ide0
+ 9 md
+ 22 ide1
+ 253 device-mapper
+ 254 mdp
+</pre><div class="para">
+ The output from <code class="filename">/proc/devices</code> includes the major number and name of the device, and is broken into two major sections: <code class="computeroutput">Character devices</code> and <code class="computeroutput">Block devices</code>.
+ </div><div class="para">
+ <em class="firstterm">Character devices</em> are similar to <em class="firstterm">block devices</em>, except for two basic differences:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Character devices do not require buffering. Block devices have a buffer available, allowing them to order requests before addressing them. This is important for devices designed to store information — such as hard drives — because the ability to order the information before writing it to the device allows it to be placed in a more efficient order.
+ </div></li><li class="listitem"><div class="para">
+ Character devices send data with no preconfigured size. Block devices can send and receive information in blocks of a size configured per device.
+ </div></li></ol></div><div class="para">
+ For more information about devices refer to the following installed documentation:
+ </div><pre class="screen">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/devices.txt</pre></div><div class="section" title="19.2.6. /proc/dma" id="s2-proc-dma"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dma">19.2.6. <code class="filename">/proc/dma</code> </h3></div></div></div><a id="id754648" class="indexterm"></a><div class="para">
+ This file contains a list of the registered ISA DMA channels in use. A sample <code class="filename">/proc/dma</code> files looks like the following:
+ </div><pre class="screen">
+4: cascade
+</pre></div><div class="section" title="19.2.7. /proc/execdomains" id="s2-proc-execdomains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-execdomains">19.2.7. <code class="filename">/proc/execdomains</code> </h3></div></div></div><a id="id754696" class="indexterm"></a><a id="id457937" class="indexterm"></a><a id="id457955" class="indexterm"></a><div class="para">
+ This file lists the <em class="firstterm">execution domains</em> currently supported by the Linux kernel, along with the range of personalities they support.
+ </div><pre class="screen">
+0-0 Linux [kernel]
+</pre><div class="para">
+ Think of execution domains as the "personality" for an operating system. Because other binary formats, such as Solaris, UnixWare, and FreeBSD, can be used with Linux, programmers can change the way the operating system treats system calls from these binaries by changing the personality of the task. Except for the <code class="computeroutput">PER_LINUX</code> execution domain, different personalities can be implemented as dynamically loadable modules.
+ </div></div><div class="section" title="19.2.8. /proc/fb" id="s2-proc-fb"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-fb">19.2.8. <code class="filename">/proc/fb</code> </h3></div></div></div><a id="id458004" class="indexterm"></a><a id="id639774" class="indexterm"></a><div class="para">
+ This file contains a list of frame buffer devices, with the frame buffer device number and the driver that controls it. Typical output of <code class="filename">/proc/fb</code> for systems which contain frame buffer devices looks similar to the following:
+ </div><pre class="screen">
+0 VESA VGA
+</pre></div><div class="section" title="19.2.9. /proc/filesystems" id="s2-proc-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-filesystems">19.2.9. <code class="filename">/proc/filesystems</code> </h3></div></div></div><a id="id639819" class="indexterm"></a><div class="para">
+ This file displays a list of the file system types currently supported by the kernel. Sample output from a generic <code class="filename">/proc/filesystems</code> file looks similar to the following:
+ </div><pre class="screen">
+nodev sysfs
+nodev rootfs
+nodev bdev
+nodev proc
+nodev sockfs
+nodev binfmt_misc
+nodev usbfs
+nodev usbdevfs
+nodev futexfs
+nodev tmpfs
+nodev pipefs
+nodev eventpollfs
+nodev devpts
+ ext2
+nodev ramfs
+nodev hugetlbfs
+ iso9660
+nodev mqueue
+ ext3
+nodev rpc_pipefs
+nodev autofs
+</pre><div class="para">
+ The first column signifies whether the file system is mounted on a block device. Those beginning with <code class="computeroutput">nodev</code> are not mounted on a device. The second column lists the names of the file systems supported.
+ </div><div class="para">
+ The <code class="command">mount</code> command cycles through the file systems listed here when one is not specified as an argument.
+ </div></div><div class="section" title="19.2.10. /proc/interrupts" id="s2-proc-interrupts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-interrupts">19.2.10. <code class="filename">/proc/interrupts</code> </h3></div></div></div><a id="id649108" class="indexterm"></a><div class="para">
+ This file records the number of interrupts per IRQ on the x86 architecture. A standard <code class="filename">/proc/interrupts</code> looks similar to the following:
+ </div><pre class="screen">
+ CPU0
+ 0: 80448940 XT-PIC timer
+ 1: 174412 XT-PIC keyboard
+ 2: 0 XT-PIC cascade
+ 8: 1 XT-PIC rtc
+ 10: 410964 XT-PIC eth0
+ 12: 60330 XT-PIC PS/2 Mouse
+ 14: 1314121 XT-PIC ide0
+ 15: 5195422 XT-PIC ide1
+NMI: 0
+ERR: 0
+</pre><div class="para">
+ For a multi-processor machine, this file may look slightly different:
+ </div><pre class="screen">
+ CPU0 CPU1
+ 0: 1366814704 0 XT-PIC timer
+ 1: 128 340 IO-APIC-edge keyboard
+ 2: 0 0 XT-PIC cascade
+ 8: 0 1 IO-APIC-edge rtc
+ 12: 5323 5793 IO-APIC-edge PS/2 Mouse
+ 13: 1 0 XT-PIC fpu
+ 16: 11184294 15940594 IO-APIC-level Intel EtherExpress Pro 10/100 Ethernet
+ 20: 8450043 11120093 IO-APIC-level megaraid
+ 30: 10432 10722 IO-APIC-level aic7xxx
+ 31: 23 22 IO-APIC-level aic7xxx
+NMI: 0
+ERR: 0
+</pre><div class="para">
+ The first column refers to the IRQ number. Each CPU in the system has its own column and its own number of interrupts per IRQ. The next column reports the type of interrupt, and the last column contains the name of the device that is located at that IRQ.
+ </div><div class="para">
+ Each of the types of interrupts seen in this file, which are architecture-specific, mean something different. For x86 machines, the following values are common:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">XT-PIC</code> — This is the old AT computer interrupts.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">IO-APIC-edge</code> — The voltage signal on this interrupt transitions from low to high, creating an <span class="emphasis"><em>edge</em></span>, where the interrupt occurs and is only signaled once. This kind of interrupt, as well as the <code class="computeroutput">IO-APIC-level</code> interrupt, are only seen on systems with processors from the 586 family and higher.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">IO-APIC-level</code> — Generates interrupts when its voltage signal is high until the signal is low again.
+ </div></li></ul></div></div><div class="section" title="19.2.11. /proc/iomem" id="s2-proc-iomem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-iomem">19.2.11. <code class="filename">/proc/iomem</code> </h3></div></div></div><a id="id600468" class="indexterm"></a><div class="para">
+ This file shows you the current map of the system's memory for each physical device:
+ </div><pre class="screen">
+00000000-0009fbff : System RAM
+0009fc00-0009ffff : reserved
+000a0000-000bffff : Video RAM area
+000c0000-000c7fff : Video ROM
+000f0000-000fffff : System ROM
+00100000-07ffffff : System RAM
+00100000-00291ba8 : Kernel code
+00291ba9-002e09cb : Kernel data
+e0000000-e3ffffff : VIA Technologies, Inc. VT82C597 [Apollo VP3] e4000000-e7ffffff : PCI Bus #01
+e4000000-e4003fff : Matrox Graphics, Inc. MGA G200 AGP
+e5000000-e57fffff : Matrox Graphics, Inc. MGA G200 AGP
+e8000000-e8ffffff : PCI Bus #01
+e8000000-e8ffffff : Matrox Graphics, Inc. MGA G200 AGP
+ea000000-ea00007f : Digital Equipment Corporation DECchip 21140 [FasterNet]
+ea000000-ea00007f : tulip ffff0000-ffffffff : reserved
+</pre><div class="para">
+ The first column displays the memory registers used by each of the different types of memory. The second column lists the kind of memory located within those registers and displays which memory registers are used by the kernel within the system RAM or, if the network interface card has multiple Ethernet ports, the memory registers assigned for each port.
+ </div></div><div class="section" title="19.2.12. /proc/ioports" id="s2-proc-ioports"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-ioports">19.2.12. <code class="filename">/proc/ioports</code> </h3></div></div></div><a id="id569715" class="indexterm"></a><div class="para">
+ The output of <code class="filename">/proc/ioports</code> provides a list of currently registered port regions used for input or output communication with a device. This file can be quite long. The following is a partial listing:
+ </div><pre class="screen">
+0000-001f : dma1
+0020-003f : pic1
+0040-005f : timer
+0060-006f : keyboard
+0070-007f : rtc
+0080-008f : dma page reg
+00a0-00bf : pic2
+00c0-00df : dma2
+00f0-00ff : fpu
+0170-0177 : ide1
+01f0-01f7 : ide0
+02f8-02ff : serial(auto)
+0376-0376 : ide1
+03c0-03df : vga+
+03f6-03f6 : ide0
+03f8-03ff : serial(auto)
+0cf8-0cff : PCI conf1
+d000-dfff : PCI Bus #01
+e000-e00f : VIA Technologies, Inc. Bus Master IDE
+e000-e007 : ide0
+e008-e00f : ide1
+e800-e87f : Digital Equipment Corporation DECchip 21140 [FasterNet]
+e800-e87f : tulip
+</pre><div class="para">
+ The first column gives the I/O port address range reserved for the device listed in the second column.
+ </div></div><div class="section" title="19.2.13. /proc/kcore" id="s2-proc-kcore"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-kcore">19.2.13. <code class="filename">/proc/kcore</code> </h3></div></div></div><a id="id569775" class="indexterm"></a><div class="para">
+ This file represents the physical memory of the system and is stored in the core file format. Unlike most <code class="filename">/proc/</code> files, <code class="filename">kcore</code> displays a size. This value is given in bytes and is equal to the size of the physical memory (RAM) used plus 4 KB.
+ </div><div class="para">
+ The contents of this file are designed to be examined by a debugger, such as <code class="command">gdb</code>, and is not human readable.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Do not view the <code class="filename">/proc/kcore</code> virtual file. The contents of the file scramble text output on the terminal. If this file is accidentally viewed, press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>C</strong></span> to stop the process and then type <code class="command">reset</code> to bring back the command line prompt.
+ </div></div></div></div><div class="section" title="19.2.14. /proc/kmsg" id="s2-proc-kmsg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-kmsg">19.2.14. <code class="filename">/proc/kmsg</code> </h3></div></div></div><a id="id776076" class="indexterm"></a><div class="para">
+ This file is used to hold messages generated by the kernel. These messages are then picked up by other programs, such as <code class="command">/sbin/klogd</code> or <code class="command">/bin/dmesg</code>.
+ </div></div><div class="section" title="19.2.15. /proc/loadavg" id="s2-proc-loadavg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-loadavg">19.2.15. <code class="filename">/proc/loadavg</code> </h3></div></div></div><a id="id776126" class="indexterm"></a><div class="para">
+ This file provides a look at the load average in regard to both the CPU and IO over time, as well as additional data used by <code class="command">uptime</code> and other commands. A sample <code class="filename">/proc/loadavg</code> file looks similar to the following:
+ </div><pre class="screen">
+0.20 0.18 0.12 1/80 11206
+</pre><div class="para">
+ The first three columns measure CPU and IO utilization of the last one, five, and 15 minute periods. The fourth column shows the number of currently running processes and the total number of processes. The last column displays the last process ID used.
+ </div><div class="para">
+ In addition, load average also refers to the number of processes ready to run (i.e. in the run queue, waiting for a CPU share.
+ </div></div><div class="section" title="19.2.16. /proc/locks" id="s2-proc-locks"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-locks">19.2.16. <code class="filename">/proc/locks</code> </h3></div></div></div><a id="id508419" class="indexterm"></a><div class="para">
+ This file displays the files currently locked by the kernel. The contents of this file contain internal kernel debugging data and can vary tremendously, depending on the use of the system. A sample <code class="filename">/proc/locks</code> file for a lightly loaded system looks similar to the following:
+ </div><pre class="screen">
+1: POSIX ADVISORY WRITE 3568 fd:00:2531452 0 EOF
+2: FLOCK ADVISORY WRITE 3517 fd:00:2531448 0 EOF
+3: POSIX ADVISORY WRITE 3452 fd:00:2531442 0 EOF
+4: POSIX ADVISORY WRITE 3443 fd:00:2531440 0 EOF
+5: POSIX ADVISORY WRITE 3326 fd:00:2531430 0 EOF
+6: POSIX ADVISORY WRITE 3175 fd:00:2531425 0 EOF
+7: POSIX ADVISORY WRITE 3056 fd:00:2548663 0 EOF
+</pre><div class="para">
+ Each lock has its own line which starts with a unique number. The second column refers to the class of lock used, with <code class="computeroutput">FLOCK</code> signifying the older-style UNIX file locks from a <code class="command">flock</code> system call and <code class="computeroutput">POSIX</code> representing the newer POSIX locks from the <code class="command">lockf</code> system call.
+ </div><div class="para">
+ The third column can have two values: <code class="computeroutput">ADVISORY</code> or <code class="computeroutput">MANDATORY</code>. <code class="computeroutput">ADVISORY</code> means that the lock does not prevent other people from accessing the data; it only prevents other attempts to lock it. <code class="computeroutput">MANDATORY</code> means that no other access to the data is permitted while the lock is held. The fourth column reveals whether the lock is allowing the holder <code class="computeroutput">READ</code> or <code class="computeroutput">WRITE</code> access to the file. The fifth column shows the ID of the process holding the lock. The sixth column shows the ID of the file being locked, in the format of <code class="computeroutput"><em class="replaceable"><code>MAJOR-DEVICE</code></em>:<em class="replaceable"><code>MINOR-DEVICE</code></em>:<em class="replaceable"><code>INODE-NUMBER</code></em> </code>. The seventh and eighth column shows the start and end o
f the file's locked region.
+ </div></div><div class="section" title="19.2.17. /proc/mdstat" id="s2-proc-mdstat"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-mdstat">19.2.17. <code class="filename">/proc/mdstat</code> </h3></div></div></div><a id="id744118" class="indexterm"></a><div class="para">
+ This file contains the current information for multiple-disk, RAID configurations. If the system does not contain such a configuration, then <code class="filename">/proc/mdstat</code> looks similar to the following:
+ </div><pre class="screen">
+Personalities : read_ahead not set unused devices: <none>
+</pre><div class="para">
+ This file remains in the same state as seen above unless a software RAID or <code class="filename">md</code> device is present. In that case, view <code class="filename">/proc/mdstat</code> to find the current status of <code class="filename">md<em class="replaceable"><code>X</code></em> </code> RAID devices.
+ </div><div class="para">
+ The <code class="filename">/proc/mdstat</code> file below shows a system with its <code class="filename">md0</code> configured as a RAID 1 device, while it is currently re-syncing the disks:
+ </div><pre class="screen">
+Personalities : [linear] [raid1] read_ahead 1024 sectors
+md0: active raid1 sda2[1] sdb2[0] 9940 blocks [2/2] [UU] resync=1% finish=12.3min algorithm 2 [3/3] [UUU]
+unused devices: <none>
+</pre></div><div class="section" title="19.2.18. /proc/meminfo" id="s2-proc-meminfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-meminfo">19.2.18. <code class="filename">/proc/meminfo</code> </h3></div></div></div><a id="id744683" class="indexterm"></a><div class="para">
+ This is one of the more commonly used files in the <code class="filename">/proc/</code> directory, as it reports a large amount of valuable information about the systems RAM usage.
+ </div><div class="para">
+ The following sample <code class="filename">/proc/meminfo</code> virtual file is from a system with 256 MB of RAM and 512 MB of swap space:
+ </div><pre class="screen">
+MemTotal: 255908 kB
+MemFree: 69936 kB
+Buffers: 15812 kB
+Cached: 115124 kB
+SwapCached: 0 kB
+Active: 92700 kB
+Inactive: 63792 kB
+HighTotal: 0 kB
+HighFree: 0 kB
+LowTotal: 255908 kB
+LowFree: 69936 kB
+SwapTotal: 524280 kB
+SwapFree: 524280 kB
+Dirty: 4 kB
+Writeback: 0 kB
+Mapped: 42236 kB
+Slab: 25912 kB
+Committed_AS: 118680 kB
+PageTables: 1236 kB
+VmallocTotal: 3874808 kB
+VmallocUsed: 1416 kB
+VmallocChunk: 3872908 kB
+HugePages_Total: 0
+HugePages_Free: 0
+Hugepagesize: 4096 kB
+</pre><div class="para">
+ Much of the information here is used by the <code class="command">free</code>, <code class="command">top</code>, and <code class="command">ps</code> commands. In fact, the output of the <code class="command">free</code> command is similar in appearance to the contents and structure of <code class="filename">/proc/meminfo</code>. But by looking directly at <code class="filename">/proc/meminfo</code>, more details are revealed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">MemTotal</code> — Total amount of physical RAM, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">MemFree</code> — The amount of physical RAM, in kilobytes, left unused by the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Buffers</code> — The amount of physical RAM, in kilobytes, used for file buffers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Cached</code> — The amount of physical RAM, in kilobytes, used as cache memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapCached</code> — The amount of swap, in kilobytes, used as cache memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Active</code> — The total amount of buffer or page cache memory, in kilobytes, that is in active use. This is memory that has been recently used and is usually not reclaimed for other purposes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Inactive</code> — The total amount of buffer or page cache memory, in kilobytes, that are free and available. This is memory that has not been recently used and can be reclaimed for other purposes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HighTotal</code> and <code class="computeroutput">HighFree</code> — The total and free amount of memory, in kilobytes, that is not directly mapped into kernel space. The <code class="computeroutput">HighTotal</code> value can vary based on the type of kernel used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">LowTotal</code> and <code class="computeroutput">LowFree</code> — The total and free amount of memory, in kilobytes, that is directly mapped into kernel space. The <code class="computeroutput">LowTotal</code> value can vary based on the type of kernel used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapTotal</code> — The total amount of swap available, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapFree</code> — The total amount of swap free, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Dirty</code> — The total amount of memory, in kilobytes, waiting to be written back to the disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Writeback</code> — The total amount of memory, in kilobytes, actively being written back to the disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Mapped</code> — The total amount of memory, in kilobytes, which have been used to map devices, files, or libraries using the <code class="command">mmap</code> command.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Slab</code> — The total amount of memory, in kilobytes, used by the kernel to cache data structures for its own use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Committed_AS</code> — The total amount of memory, in kilobytes, estimated to complete the workload. This value represents the worst case scenario value, and also includes swap memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">PageTables</code> — The total amount of memory, in kilobytes, dedicated to the lowest page table level.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocTotal</code> — The total amount of memory, in kilobytes, of total allocated virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocUsed</code> — The total amount of memory, in kilobytes, of used virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocChunk</code> — The largest contiguous block of memory, in kilobytes, of available virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HugePages_Total</code> — The total number of hugepages for the system. The number is derived by dividing <code class="computeroutput">Hugepagesize</code> by the megabytes set aside for hugepages specified in <code class="filename">/proc/sys/vm/hugetlb_pool</code>. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HugePages_Free</code> — The total number of hugepages available for the system. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Hugepagesize</code> — The size for each hugepages unit in kilobytes. By default, the value is 4096 KB on uniprocessor kernels for 32 bit architectures. For SMP, hugemem kernels, and AMD64, the default is 2048 KB. For Itanium architectures, the default is 262144 KB. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li></ul></div></div><div class="section" title="19.2.19. /proc/misc" id="s2-proc-misc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-misc">19.2.19. <code class="filename">/proc/misc</code> </h3></div></div></div><a id="id686543" class="indexterm"></a><div class="para">
+ This file lists miscellaneous drivers registered on the miscellaneous major device, which is device number 10:
+ </div><pre class="screen">
+63 device-mapper 175 agpgart 135 rtc 134 apm_bios
+</pre><div class="para">
+ The first column is the minor number of each device, while the second column shows the driver in use.
+ </div></div><div class="section" title="19.2.20. /proc/modules" id="s2-proc-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-modules">19.2.20. <code class="filename">/proc/modules</code> </h3></div></div></div><a id="id692437" class="indexterm"></a><div class="para">
+ This file displays a list of all modules loaded into the kernel. Its contents vary based on the configuration and use of your system, but it should be organized in a similar manner to this sample <code class="filename">/proc/modules</code> file output:
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This example has been reformatted into a readable format. Most of this information can also be viewed via the <code class="command">/sbin/lsmod</code> command.
+ </div></div></div><pre class="screen">
+nfs 170109 0 - Live 0x129b0000
+lockd 51593 1 nfs, Live 0x128b0000
+nls_utf8 1729 0 - Live 0x12830000
+vfat 12097 0 - Live 0x12823000
+fat 38881 1 vfat, Live 0x1287b000
+autofs4 20293 2 - Live 0x1284f000
+sunrpc 140453 3 nfs,lockd, Live 0x12954000
+3c59x 33257 0 - Live 0x12871000
+uhci_hcd 28377 0 - Live 0x12869000
+md5 3777 1 - Live 0x1282c000
+ipv6 211845 16 - Live 0x128de000
+ext3 92585 2 - Live 0x12886000
+jbd 65625 1 ext3, Live 0x12857000
+dm_mod 46677 3 - Live 0x12833000
+</pre><div class="para">
+ The first column contains the name of the module.
+ </div><div class="para">
+ The second column refers to the memory size of the module, in bytes.
+ </div><div class="para">
+ The third column lists how many instances of the module are currently loaded. A value of zero represents an unloaded module.
+ </div><div class="para">
+ The fourth column states if the module depends upon another module to be present in order to function, and lists those other modules.
+ </div><div class="para">
+ The fifth column lists what load state the module is in: <code class="command">Live</code>, <code class="command">Loading</code>, or <code class="command">Unloading</code> are the only possible values.
+ </div><div class="para">
+ The sixth column lists the current kernel memory offset for the loaded module. This information can be useful for debugging purposes, or for profiling tools such as <code class="filename">oprofile</code>.
+ </div></div><div class="section" title="19.2.21. /proc/mounts" id="s2-proc-mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-mounts">19.2.21. <code class="filename">/proc/mounts</code> </h3></div></div></div><a id="id762863" class="indexterm"></a><div class="para">
+ This file provides a list of all mounts in use by the system:
+ </div><pre class="screen">
+rootfs / rootfs rw 0 0
+/proc /proc proc rw,nodiratime 0 0 none
+/dev ramfs rw 0 0
+/dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0
+none /dev ramfs rw 0 0
+/proc /proc proc rw,nodiratime 0 0
+/sys /sys sysfs rw 0 0
+none /dev/pts devpts rw 0 0
+usbdevfs /proc/bus/usb usbdevfs rw 0 0
+/dev/hda1 /boot ext3 rw 0 0
+none /dev/shm tmpfs rw 0 0
+none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
+sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
+</pre><div class="para">
+ The output found here is similar to the contents of <code class="filename">/etc/mtab</code>, except that <code class="filename">/proc/mounts</code> is more up-to-date.
+ </div><div class="para">
+ The first column specifies the device that is mounted, the second column reveals the mount point, and the third column tells the file system type, and the fourth column tells you if it is mounted read-only (<code class="computeroutput">ro</code>) or read-write (<code class="computeroutput">rw</code>). The fifth and sixth columns are dummy values designed to match the format used in <code class="filename">/etc/mtab</code>.
+ </div></div><div class="section" title="19.2.22. /proc/mtrr" id="s2-proc-mtrr"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-mtrr">19.2.22. <code class="filename">/proc/mtrr</code> </h3></div></div></div><a id="id774391" class="indexterm"></a><div class="para">
+ This file refers to the current Memory Type Range Registers (MTRRs) in use with the system. If the system architecture supports MTRRs, then the <code class="filename">/proc/mtrr</code> file may look similar to the following:
+ </div><pre class="screen">
+reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
+reg01: base=0xe8000000 (3712MB), size= 32MB: write-combining, count=1
+</pre><div class="para">
+ MTRRs are used with the Intel P6 family of processors (Pentium II and higher) and control processor access to memory ranges. When using a video card on a PCI or AGP bus, a properly configured <code class="filename">/proc/mtrr</code> file can increase performance more than 150%.
+ </div><div class="para">
+ Most of the time, this value is properly configured by default. More information on manually configuring this file can be found locally at the following location:
+ </div><pre class="screen">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/<em class="replaceable"><code><arch></code></em>/mtrr.txt</pre></div><div class="section" title="19.2.23. /proc/partitions" id="s2-proc-partitions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-partitions">19.2.23. <code class="filename">/proc/partitions</code> </h3></div></div></div><a id="id569507" class="indexterm"></a><div class="para">
+ This file contains partition block allocation information. A sampling of this file from a basic system looks similar to the following:
+ </div><pre class="screen">
+major minor #blocks name
+ 3 0 19531250 hda
+ 3 1 104391 hda1
+ 3 2 19422585 hda2
+253 0 22708224 dm-0
+253 1 524288 dm-1
+</pre><div class="para">
+ Most of the information here is of little importance to the user, except for the following columns:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">major</code> — The major number of the device with this partition. The major number in the <code class="filename">/proc/partitions</code>, (<code class="computeroutput">3</code>), corresponds with the block device <code class="computeroutput">ide0</code>, in <code class="filename">/proc/devices</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">minor</code> — The minor number of the device with this partition. This serves to separate the partitions into different physical devices and relates to the number at the end of the name of the partition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">#blocks</code> — Lists the number of physical disk blocks contained in a particular partition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">name</code> — The name of the partition.
+ </div></li></ul></div></div><div class="section" title="19.2.24. /proc/slabinfo" id="s2-proc-slabinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-slabinfo">19.2.24. <code class="filename">/proc/slabinfo</code> </h3></div></div></div><a id="id1521259" class="indexterm"></a><a id="id721266" class="indexterm"></a><div class="para">
+ This file gives full information about memory usage on the <em class="firstterm">slab</em> level. Linux kernels greater than version 2.2 use <em class="firstterm">slab pools</em> to manage memory above the page level. Commonly used objects have their own slab pools.
+ </div><div class="para">
+ Instead of parsing the highly verbose <code class="filename">/proc/slabinfo</code> file manually, the <code class="filename">/usr/bin/slabtop</code> program displays kernel slab cache information in real time. This program allows for custom configurations, including column sorting and screen refreshing.
+ </div><div class="para">
+ A sample screen shot of <code class="filename">/usr/bin/slabtop</code> usually looks like the following example:
+ </div><pre class="screen">
+Active / Total Objects (% used) : 133629 / 147300 (90.7%)
+Active / Total Slabs (% used) : 11492 / 11493 (100.0%)
+Active / Total Caches (% used) : 77 / 121 (63.6%)
+Active / Total Size (% used) : 41739.83K / 44081.89K (94.7%)
+Minimum / Average / Maximum Object : 0.01K / 0.30K / 128.00K
+OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
+44814 43159 96% 0.62K 7469 6 29876K ext3_inode_cache
+36900 34614 93% 0.05K 492 75 1968K buffer_head
+35213 33124 94% 0.16K 1531 23 6124K dentry_cache
+7364 6463 87% 0.27K 526 14 2104K radix_tree_node
+2585 1781 68% 0.08K 55 47 220K vm_area_struct
+2263 2116 93% 0.12K 73 31 292K size-128
+1904 1125 59% 0.03K 16 119 64K size-32
+1666 768 46% 0.03K 14 119 56K anon_vma
+1512 1482 98% 0.44K 168 9 672K inode_cache
+1464 1040 71% 0.06K 24 61 96K size-64
+1320 820 62% 0.19K 66 20 264K filp
+678 587 86% 0.02K 3 226 12K dm_io
+678 587 86% 0.02K 3 226 12K dm_tio
+576 574 99% 0.47K 72 8 288K proc_inode_cache
+528 514 97% 0.50K 66 8 264K size-512
+492 372 75% 0.09K 12 41 48K bio
+465 314 67% 0.25K 31 15 124K size-256
+452 331 73% 0.02K 2 226 8K biovec-1
+420 420 100% 0.19K 21 20 84K skbuff_head_cache
+305 256 83% 0.06K 5 61 20K biovec-4
+290 4 1% 0.01K 1 290 4K revoke_table
+264 264 100% 4.00K 264 1 1056K size-4096
+260 256 98% 0.19K 13 20 52K biovec-16
+260 256 98% 0.75K 52 5 208K biovec-64
+</pre><div class="para">
+ Some of the more commonly used statistics in <code class="filename">/proc/slabinfo</code> that are included into <code class="filename">/usr/bin/slabtop</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJS</code> — The total number of objects (memory blocks), including those in use (allocated), and some spares not in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">ACTIVE</code> — The number of objects (memory blocks) that are in use (allocated).
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">USE</code> — Percentage of total objects that are active. ((ACTIVE/OBJS)(100))
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJ SIZE</code> — The size of the objects.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SLABS</code> — The total number of slabs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJ/SLAB</code> — The number of objects that fit into a slab.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">CACHE SIZE</code> — The cache size of the slab.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">NAME</code> — The name of the slab.
+ </div></li></ul></div><div class="para">
+ For more information on the <code class="filename">/usr/bin/slabtop</code> program, refer to the <code class="filename">slabtop</code> man page.
+ </div></div><div class="section" title="19.2.25. /proc/stat" id="s2-proc-stat"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-stat">19.2.25. <code class="filename">/proc/stat</code> </h3></div></div></div><a id="id446207" class="indexterm"></a><a id="id494382" class="indexterm"></a><a id="id494397" class="indexterm"></a><div class="para">
+ This file keeps track of a variety of different statistics about the system since it was last restarted. The contents of <code class="filename">/proc/stat</code>, which can be quite long, usually begins like the following example:
+ </div><pre class="screen">
+cpu 259246 7001 60190 34250993 137517 772 0
+cpu0 259246 7001 60190 34250993 137517 772 0
+intr 354133732 347209999 2272 0 4 4 0 0 3 1 1249247 0 0 80143 0 422626 5169433
+ctxt 12547729
+btime 1093631447
+processes 130523
+procs_running 1
+procs_blocked 0
+preempt 5651840
+cpu 209841 1554 21720 118519346 72939 154 27168
+cpu0 42536 798 4841 14790880 14778 124 3117
+cpu1 24184 569 3875 14794524 30209 29 3130
+cpu2 28616 11 2182 14818198 4020 1 3493
+cpu3 35350 6 2942 14811519 3045 0 3659
+cpu4 18209 135 2263 14820076 12465 0 3373
+cpu5 20795 35 1866 14825701 4508 0 3615
+cpu6 21607 0 2201 14827053 2325 0 3334
+cpu7 18544 0 1550 14831395 1589 0 3447
+intr 15239682 14857833 6 0 6 6 0 5 0 1 0 0 0 29 0 2 0 0 0 0 0 0 0 94982 0 286812
+ctxt 4209609
+btime 1078711415
+processes 21905
+procs_running 1
+procs_blocked 0
+</pre><div class="para">
+ Some of the more commonly used statistics include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu</code> — Measures the number of <em class="firstterm">jiffies</em> (1/100 of a second for x86 systems) that the system has been in user mode, user mode with low priority (nice), system mode, idle task, I/O wait, IRQ (hardirq), and softirq respectively. The IRQ (hardirq) is the direct response to a hardware event. The IRQ takes minimal work for queuing the "heavy" work up for the softirq to execute. The softirq runs at a lower priority than the IRQ and therefore may be interrupted more frequently. The total for all CPUs is given at the top, while each individual CPU is listed below with its own statistics. The following example is a 4-way Intel Pentium Xeon configuration with multi-threading enabled, therefore showing four physical processors and four virtual processors totaling eight processors.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">page</code> — The number of memory pages the system has written in and out to disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">swap</code> — The number of swap pages the system has brought in and out.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">intr</code> — The number of interrupts the system has experienced.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">btime</code> — The boot time, measured in the number of seconds since January 1, 1970, otherwise known as the <em class="firstterm">epoch</em>.
+ </div></li></ul></div></div><div class="section" title="19.2.26. /proc/swaps" id="s2-proc-swaps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-swaps">19.2.26. <code class="filename">/proc/swaps</code> </h3></div></div></div><a id="id777733" class="indexterm"></a><div class="para">
+ This file measures swap space and its utilization. For a system with only one swap partition, the output of <code class="filename">/proc/swaps</code> may look similar to the following:
+ </div><pre class="screen">
+Filename Type Size Used Priority
+/dev/mapper/VolGroup00-LogVol01 partition 524280 0 -1
+</pre><div class="para">
+ While some of this information can be found in other files in the <code class="filename">/proc/</code> directory, <code class="filename">/proc/swap</code> provides a snapshot of every swap file name, the type of swap space, the total size, and the amount of space in use (in kilobytes). The priority column is useful when multiple swap files are in use. The lower the priority, the more likely the swap file is to be used.
+ </div></div><div class="section" title="19.2.27. /proc/sysrq-trigger" id="s2-proc-sysrq-trigger"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-sysrq-trigger">19.2.27. <code class="filename">/proc/sysrq-trigger</code> </h3></div></div></div><a id="id777798" class="indexterm"></a><div class="para">
+ Using the <code class="command">echo</code> command to write to this file, a remote root user can execute most System Request Key commands remotely as if at the local terminal. To <code class="command">echo</code> values to this file, the <code class="filename">/proc/sys/kernel/sysrq</code> must be set to a value other than <code class="computeroutput">0</code>. For more information about the System Request Key, refer to <a class="xref" href="#s3-proc-sys-kernel" title="19.3.9.3. /proc/sys/kernel/">Section 19.3.9.3, “ <code class="filename">/proc/sys/kernel/</code> ”</a>.
+ </div><div class="para">
+ Although it is possible to write to this file, it cannot be read, even by the root user.
+ </div></div><div class="section" title="19.2.28. /proc/uptime" id="s2-proc-uptime"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-uptime">19.2.28. <code class="filename">/proc/uptime</code> </h3></div></div></div><a id="id853779" class="indexterm"></a><div class="para">
+ This file contains information detailing how long the system has been on since its last restart. The output of <code class="filename">/proc/uptime</code> is quite minimal:
+ </div><pre class="screen">
+350735.47 234388.90
+</pre><div class="para">
+ The first number is the total number of seconds the system has been up. The second number is how much of that time the machine has spent idle, in seconds.
+ </div></div><div class="section" title="19.2.29. /proc/version" id="s2-proc-version"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-version">19.2.29. <code class="filename">/proc/version</code> </h3></div></div></div><a id="id1320291" class="indexterm"></a><div class="para">
+ This file specifies the version of the Linux kernel, the version of <code class="command">gcc</code> used to compile the kernel, and the time of kernel compilation. It also contains the kernel compiler's user name (in parentheses).
+ </div><pre class="screen">
+Linux version 2.6.8-1.523 (user at foo.redhat.com) (gcc version 3.4.1 20040714 \ (Red Hat Enterprise Linux 3.4.1-7)) #1 Mon Aug 16 13:27:03 EDT 2004
+</pre><div class="para">
+ This information is used for a variety of purposes, including the version data presented when a user logs in.
+ </div></div></div><div class="section" title="19.3. Directories within /proc/" id="s1-proc-directories"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-proc-directories">19.3. Directories within <code class="filename">/proc/</code> </h2></div></div></div><a id="id665333" class="indexterm"></a><div class="para">
+ Common groups of information concerning the kernel are grouped into directories and subdirectories within the <code class="filename">/proc/</code> directory.
+ </div><div class="section" title="19.3.1. Process Directories" id="s2-proc-processdirs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-processdirs">19.3.1. Process Directories</h3></div></div></div><a id="id665370" class="indexterm"></a><div class="para">
+ Every <code class="filename">/proc/</code> directory contains a number of directories with numerical names. A listing of them may be similar to the following:
+ </div><pre class="screen">
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 1
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 1010
+dr-xr-xr-x 3 xfs xfs 0 Feb 13 01:28 1087
+dr-xr-xr-x 3 daemon daemon 0 Feb 13 01:28 1123
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 11307
+dr-xr-xr-x 3 apache apache 0 Feb 13 01:28 13660
+dr-xr-xr-x 3 rpc rpc 0 Feb 13 01:28 637
+dr-xr-xr-x 3 rpcuser rpcuser 0 Feb 13 01:28 666
+</pre><div class="para">
+ These directories are called <em class="firstterm">process directories</em>, as they are named after a program's process ID and contain information specific to that process. The owner and group of each process directory is set to the user running the process. When the process is terminated, its <code class="filename">/proc/</code> process directory vanishes.
+ </div><div class="para">
+ Each process directory contains the following files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">cmdline</code> — Contains the command issued when starting the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cwd</code> — A symbolic link to the current working directory for the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">environ</code> — A list of the environment variables for the process. The environment variable is given in all upper-case characters, and the value is in lower-case characters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">exe</code> — A symbolic link to the executable of this process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">fd</code> — A directory containing all of the file descriptors for a particular process. These are given in numbered links:
+ </div><pre class="screen">
+total 0
+lrwx------ 1 root root 64 May 8 11:31 0 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 1 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 2 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 3 -> /dev/ptmx
+lrwx------ 1 root root 64 May 8 11:31 4 -> socket:[7774817]
+lrwx------ 1 root root 64 May 8 11:31 5 -> /dev/ptmx
+lrwx------ 1 root root 64 May 8 11:31 6 -> socket:[7774829]
+lrwx------ 1 root root 64 May 8 11:31 7 -> /dev/ptmx
+</pre></li><li class="listitem"><div class="para">
+ <code class="computeroutput">maps</code> — A list of memory maps to the various executables and library files associated with this process. This file can be rather long, depending upon the complexity of the process, but sample output from the <code class="command">sshd</code> process begins like the following:
+ </div><pre class="screen">
+08048000-08086000 r-xp 00000000 03:03 391479 /usr/sbin/sshd
+08086000-08088000 rw-p 0003e000 03:03 391479 /usr/sbin/sshd
+08088000-08095000 rwxp 00000000 00:00 0
+40000000-40013000 r-xp 0000000 03:03 293205 /lib/ld-2.2.5.so
+40013000-40014000 rw-p 00013000 03:03 293205 /lib/ld-2.2.5.so
+40031000-40038000 r-xp 00000000 03:03 293282 /lib/libpam.so.0.75
+40038000-40039000 rw-p 00006000 03:03 293282 /lib/libpam.so.0.75
+40039000-4003a000 rw-p 00000000 00:00 0
+4003a000-4003c000 r-xp 00000000 03:03 293218 /lib/libdl-2.2.5.so
+4003c000-4003d000 rw-p 00001000 03:03 293218 /lib/libdl-2.2.5.so
+</pre></li><li class="listitem"><div class="para">
+ <code class="computeroutput">mem</code> — The memory held by the process. This file cannot be read by the user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">root</code> — A link to the root directory of the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">stat</code> — The status of the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">statm</code> — The status of the memory in use by the process. Below is a sample <code class="filename">/proc/statm</code> file:
+ </div><pre class="screen">
+263 210 210 5 0 205 0
+</pre><div class="para">
+ The seven columns relate to different memory statistics for the process. From left to right, they report the following aspects of the memory used:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Total program size, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ Size of memory portions, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages that are shared.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages that are code.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages of data/stack.
+ </div></li><li class="listitem"><div class="para">
+ Number of library pages.
+ </div></li><li class="listitem"><div class="para">
+ Number of dirty pages.
+ </div></li></ol></div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">status</code> — The status of the process in a more readable form than <code class="filename">stat</code> or <code class="filename">statm</code>. Sample output for <code class="command">sshd</code> looks similar to the following:
+ </div><pre class="screen">
+Name: sshd
+State: S (sleeping)
+Tgid: 797
+Pid: 797
+PPid: 1
+TracerPid: 0
+Uid: 0 0 0 0
+Gid: 0 0 0 0
+FDSize: 32
+Groups:
+VmSize: 3072 kB
+VmLck: 0 kB
+VmRSS: 840 kB
+VmData: 104 kB
+VmStk: 12 kB
+VmExe: 300 kB
+VmLib: 2528 kB
+SigPnd: 0000000000000000
+SigBlk: 0000000000000000
+SigIgn: 8000000000001000
+SigCgt: 0000000000014005
+CapInh: 0000000000000000
+CapPrm: 00000000fffffeff
+CapEff: 00000000fffffeff
+</pre><div class="para">
+ The information in this output includes the process name and ID, the state (such as <code class="computeroutput">S (sleeping)</code> or <code class="computeroutput">R (running)</code>), user/group ID running the process, and detailed data regarding memory usage.
+ </div></li></ul></div><div class="section" title="19.3.1.1. /proc/self/" id="s3-proc-self"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-self">19.3.1.1. <code class="filename">/proc/self/</code> </h4></div></div></div><a id="id733003" class="indexterm"></a><div class="para">
+ The <code class="filename">/proc/self/</code> directory is a link to the currently running process. This allows a process to look at itself without having to know its process ID.
+ </div><div class="para">
+ Within a shell environment, a listing of the <code class="filename">/proc/self/</code> directory produces the same contents as listing the process directory for that process.
+ </div></div></div><div class="section" title="19.3.2. /proc/bus/" id="s2-proc-dir-bus"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-bus">19.3.2. <code class="filename">/proc/bus/</code> </h3></div></div></div><a id="id733059" class="indexterm"></a><div class="para">
+ This directory contains information specific to the various buses available on the system. For example, on a standard system containing PCI and USB buses, current data on each of these buses is available within a subdirectory within <code class="filename">/proc/bus/</code> by the same name, such as <code class="filename">/proc/bus/pci/</code>.
+ </div><div class="para">
+ The subdirectories and files available within <code class="filename">/proc/bus/</code> vary depending on the devices connected to the system. However, each bus type has at least one directory. Within these bus directories are normally at least one subdirectory with a numerical name, such as <code class="filename">001</code>, which contain binary files.
+ </div><div class="para">
+ For example, the <code class="filename">/proc/bus/usb/</code> subdirectory contains files that track the various devices on any USB buses, as well as the drivers required for them. The following is a sample listing of a <code class="filename">/proc/bus/usb/</code> directory:
+ </div><pre class="screen">
+total 0 dr-xr-xr-x 1 root root 0 May 3 16:25 001
+-r--r--r-- 1 root root 0 May 3 16:25 devices
+-r--r--r-- 1 root root 0 May 3 16:25 drivers
+</pre><div class="para">
+ The <code class="filename">/proc/bus/usb/001/</code> directory contains all devices on the first USB bus and the <code class="filename">devices</code> file identifies the USB root hub on the motherboard.
+ </div><div class="para">
+ The following is a example of a <code class="filename">/proc/bus/usb/devices</code> file:
+ </div><pre class="screen">
+T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
+B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
+D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
+P: Vendor=0000 ProdID=0000 Rev= 0.00
+S: Product=USB UHCI Root Hub
+S: SerialNumber=d400
+C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
+I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
+E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
+</pre></div><div class="section" title="19.3.3. /proc/bus/pci" id="s2-proc-pci"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-pci">19.3.3. <code class="filename">/proc/bus/pci</code> </h3></div></div></div><a id="id709851" class="indexterm"></a><a id="id709881" class="indexterm"></a><div class="para">
+ Later versions of the 2.6 Linux kernel have obsoleted the <code class="filename">/proc/pci</code> directory in favor of the <code class="filename">/proc/bus/pci</code> directory. Although you can get a list of all PCI devices present on the system using the command <code class="command">cat /proc/bus/pci/devices</code>, the output is difficult to read and interpret.
+ </div><div class="para">
+ For a human-readable list of PCI devices, run the following command:
+ </div><pre class="screen">~]# <code class="command">/sbin/lspci -vb</code>
+00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controller
+ Subsystem: Hewlett-Packard Company Device 1308
+ Flags: bus master, fast devsel, latency 0
+ Capabilities: [e0] Vendor Specific Information <?>
+ Kernel driver in use: x38_edac
+ Kernel modules: x38_edac
+
+00:01.0 PCI bridge: Intel Corporation 82X38/X48 Express Host-Primary PCI Express Bridge (prog-if 00 [Normal decode])
+ Flags: bus master, fast devsel, latency 0
+ Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
+ I/O behind bridge: 00001000-00001fff
+ Memory behind bridge: f0000000-f2ffffff
+ Capabilities: [88] Subsystem: Hewlett-Packard Company Device 1308
+ Capabilities: [80] Power Management version 3
+ Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
+ Capabilities: [a0] Express Root Port (Slot+), MSI 00
+ Capabilities: [100] Virtual Channel <?>
+ Capabilities: [140] Root Complex Link <?>
+ Kernel driver in use: pcieport
+ Kernel modules: shpchp
+
+00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
+ Subsystem: Hewlett-Packard Company Device 1308
+ Flags: bus master, medium devsel, latency 0, IRQ 5
+ I/O ports at 2100
+ Capabilities: [50] PCI Advanced Features
+ Kernel driver in use: uhci_hcd
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em>
+</pre><div class="para">
+ The output is a sorted list of all IRQ numbers and addresses as seen by the cards on the PCI bus instead of as seen by the kernel. Beyond providing the name and version of the device, this list also gives detailed IRQ information so an administrator can quickly look for conflicts.
+ </div></div><div class="section" title="19.3.4. /proc/driver/" id="s2-proc-dir-driver"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-driver">19.3.4. <code class="filename">/proc/driver/</code> </h3></div></div></div><a id="id862361" class="indexterm"></a><div class="para">
+ This directory contains information for specific drivers in use by the kernel.
+ </div><div class="para">
+ A common file found here is <code class="filename">rtc</code> which provides output from the driver for the system's <em class="firstterm">Real Time Clock (RTC)</em>, the device that keeps the time while the system is switched off. Sample output from <code class="filename">/proc/driver/rtc</code> looks like the following:
+ </div><pre class="screen">
+rtc_time : 16:21:00
+rtc_date : 2004-08-31
+rtc_epoch : 1900
+alarm : 21:16:27
+DST_enable : no
+BCD : yes
+24hr : yes
+square_wave : no
+alarm_IRQ : no
+update_IRQ : no
+periodic_IRQ : no
+periodic_freq : 1024
+batt_status : okay
+</pre><div class="para">
+ For more information about the RTC, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/rtc.txt</code>.
+ </div></div><div class="section" title="19.3.5. /proc/fs" id="s2-proc-dir-fs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-fs">19.3.5. <code class="filename">/proc/fs</code> </h3></div></div></div><a id="id414963" class="indexterm"></a><div class="para">
+ This directory shows which file systems are exported. If running an NFS server, typing <code class="command">cat /proc/fs/nfsd/exports</code> displays the file systems being shared and the permissions granted for those file systems. For more on file system sharing with NFS, refer to the <em class="citetitle">Network File System (NFS)</em> chapter of the <em class="citetitle">Storage Administration Guide</em>.
+ </div></div><div class="section" title="19.3.6. /proc/irq/" id="s2-proc-dir-irq"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-irq">19.3.6. <code class="filename">/proc/irq/</code> </h3></div></div></div><a id="id415020" class="indexterm"></a><div class="para">
+ This directory is used to set IRQ to CPU affinity, which allows the system to connect a particular IRQ to only one CPU. Alternatively, it can exclude a CPU from handling any IRQs.
+ </div><div class="para">
+ Each IRQ has its own directory, allowing for the individual configuration of each IRQ. The <code class="filename">/proc/irq/prof_cpu_mask</code> file is a bitmask that contains the default values for the <code class="filename">smp_affinity</code> file in the IRQ directory. The values in <code class="filename">smp_affinity</code> specify which CPUs handle that particular IRQ.
+ </div><div class="para">
+ For more information about the <code class="filename">/proc/irq/</code> directory, refer to the following installed documentation:
+ </div><pre class="screen">
+/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><div class="section" title="19.3.7. /proc/net/" id="s2-proc-dir-net"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-net">19.3.7. <code class="filename">/proc/net/</code> </h3></div></div></div><a id="id2227540" class="indexterm"></a><div class="para">
+ This directory provides a comprehensive look at various networking parameters and statistics. Each directory and virtual file within this directory describes aspects of the system's network configuration. Below is a partial list of the <code class="filename">/proc/net/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">arp</code> — Lists the kernel's ARP table. This file is particularly useful for connecting a hardware address to an IP address on a system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">atm/</code> directory — The files within this directory contain <em class="firstterm">Asynchronous Transfer Mode (ATM)</em> settings and statistics. This directory is primarily used with ATM networking and ADSL cards.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dev</code> — Lists the various network devices configured on the system, complete with transmit and receive statistics. This file displays the number of bytes each interface has sent and received, the number of packets inbound and outbound, the number of errors seen, the number of packets dropped, and more.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dev_mcast</code> — Lists Layer2 multicast groups on which each device is listening.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">igmp</code> — Lists the IP multicast addresses which this system joined.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_conntrack</code> — Lists tracked network connections for machines that are forwarding IP connections.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_tables_names</code> — Lists the types of <code class="command">iptables</code> in use. This file is only present if <code class="command">iptables</code> is active on the system and contains one or more of the following values: <code class="filename">filter</code>, <code class="filename">mangle</code>, or <code class="filename">nat</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_mr_cache</code> — Lists the multicast routing cache.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_mr_vif</code> — Lists multicast virtual interfaces.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">netstat</code> — Contains a broad yet detailed collection of networking statistics, including TCP timeouts, SYN cookies sent and received, and much more.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">psched</code> — Lists global packet scheduler parameters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">raw</code> — Lists raw device statistics.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">route</code> — Lists the kernel's routing table.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rt_cache</code> — Contains the current routing cache.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">snmp</code> — List of Simple Network Management Protocol (SNMP) data for various networking protocols in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sockstat</code> — Provides socket statistics.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp</code> — Contains detailed TCP socket information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tr_rif</code> — Lists the token ring RIF routing table.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">udp</code> — Contains detailed UDP socket information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">unix</code> — Lists UNIX domain sockets currently in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wireless</code> — Lists wireless interface data.
+ </div></li></ul></div></div><div class="section" title="19.3.8. /proc/scsi/" id="s2-proc-dir-scsi"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-scsi">19.3.8. <code class="filename">/proc/scsi/</code> </h3></div></div></div><a id="id841231" class="indexterm"></a><div class="para">
+ The primary file in this directory is <code class="filename">/proc/scsi/scsi</code>, which contains a list of every recognized SCSI device. From this listing, the type of device, as well as the model name, vendor, SCSI channel and ID data is available.
+ </div><div class="para">
+ For example, if a system contains a SCSI CD-ROM, a tape drive, a hard drive, and a RAID controller, this file looks similar to the following:
+ </div><pre class="screen">
+Attached devices:
+Host: scsi1
+Channel: 00
+Id: 05
+Lun: 00
+Vendor: NEC
+Model: CD-ROM DRIVE:466
+Rev: 1.06
+Type: CD-ROM
+ANSI SCSI revision: 02
+Host: scsi1
+Channel: 00
+Id: 06
+Lun: 00
+Vendor: ARCHIVE
+Model: Python 04106-XXX
+Rev: 7350
+Type: Sequential-Access
+ANSI SCSI revision: 02
+Host: scsi2
+Channel: 00
+Id: 06
+Lun: 00
+Vendor: DELL
+Model: 1x6 U2W SCSI BP
+Rev: 5.35
+Type: Processor
+ANSI SCSI revision: 02
+Host: scsi2
+Channel: 02
+Id: 00
+Lun: 00
+Vendor: MegaRAID
+Model: LD0 RAID5 34556R
+Rev: 1.01
+Type: Direct-Access
+ANSI SCSI revision: 02
+</pre><div class="para">
+ Each SCSI driver used by the system has its own directory within <code class="filename">/proc/scsi/</code>, which contains files specific to each SCSI controller using that driver. From the previous example, <code class="filename">aic7xxx/</code> and <code class="filename">megaraid/</code> directories are present, since two drivers are in use. The files in each of the directories typically contain an I/O address range, IRQ information, and statistics for the SCSI controller using that driver. Each controller can report a different type and amount of information. The Adaptec AIC-7880 Ultra SCSI host adapter's file in this example system produces the following output:
+ </div><pre class="screen">
+Adaptec AIC7xxx driver version: 5.1.20/3.2.4
+Compile Options:
+TCQ Enabled By Default : Disabled
+AIC7XXX_PROC_STATS : Enabled
+AIC7XXX_RESET_DELAY : 5
+Adapter Configuration:
+SCSI Adapter: Adaptec AIC-7880 Ultra SCSI host adapter
+Ultra Narrow Controller PCI MMAPed
+I/O Base: 0xfcffe000
+Adapter SEEPROM Config: SEEPROM found and used.
+Adaptec SCSI BIOS: Enabled
+IRQ: 30
+SCBs: Active 0, Max Active 1, Allocated 15, HW 16, Page 255
+Interrupts: 33726
+BIOS Control Word: 0x18a6
+Adapter Control Word: 0x1c5f
+Extended Translation: Enabled
+Disconnect Enable Flags: 0x00ff
+Ultra Enable Flags: 0x0020
+Tag Queue Enable Flags: 0x0000
+Ordered Queue Tag Flags: 0x0000
+Default Tag Queue Depth: 8
+Tagged Queue By Device array for aic7xxx
+host instance 1: {255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255}
+Actual queue depth per device for aic7xxx host instance 1: {1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}
+Statistics:
+
+(scsi1:0:5:0) Device using Narrow/Sync transfers at 20.0 MByte/sec, offset 15
+Transinfo settings: current(12/15/0/0), goal(12/15/0/0), user(12/15/0/0)
+Total transfers 0 (0 reads and 0 writes)
+ < 2K 2K+ 4K+ 8K+ 16K+ 32K+ 64K+ 128K+
+Reads: 0 0 0 0 0 0 0 0
+Writes: 0 0 0 0 0 0 0 0
+
+(scsi1:0:6:0) Device using Narrow/Sync transfers at 10.0 MByte/sec, offset 15
+Transinfo settings: current(25/15/0/0), goal(12/15/0/0), user(12/15/0/0)
+Total transfers 132 (0 reads and 132 writes)
+ < 2K 2K+ 4K+ 8K+ 16K+ 32K+ 64K+ 128K+
+Reads: 0 0 0 0 0 0 0 0
+Writes: 0 0 0 1 131 0 0 0
+</pre><div class="para">
+ This output reveals the transfer speed to the SCSI devices connected to the controller based on channel ID, as well as detailed statistics concerning the amount and sizes of files read or written by that device. For example, this controller is communicating with the CD-ROM at 20 megabytes per second, while the tape drive is only communicating at 10 megabytes per second.
+ </div></div><div class="section" title="19.3.9. /proc/sys/" id="s2-proc-dir-sys"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-sys">19.3.9. <code class="filename">/proc/sys/</code> </h3></div></div></div><a id="id548260" class="indexterm"></a><a id="id548283" class="indexterm"></a><a id="id548297" class="indexterm"></a><a id="id786539" class="indexterm"></a><a id="id786558" class="indexterm"></a><a id="id786572" class="indexterm"></a><div class="para">
+ The <code class="filename">/proc/sys/</code> directory is different from others in <code class="filename">/proc/</code> because it not only provides information about the system but also allows the system administrator to immediately enable and disable kernel features.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Use caution when changing settings on a production system using the various files in the <code class="filename">/proc/sys/</code> directory. Changing the wrong setting may render the kernel unstable, requiring a system reboot.
+ </div><div class="para">
+ For this reason, be sure the options are valid for that file before attempting to change any value in <code class="filename">/proc/sys/</code>.
+ </div></div></div><div class="para">
+ A good way to determine if a particular file can be configured, or if it is only designed to provide information, is to list it with the <code class="option">-l</code> option at the shell prompt. If the file is writable, it may be used to configure the kernel. For example, a partial listing of <code class="filename">/proc/sys/fs</code> looks like the following:
+ </div><pre class="screen">
+-r--r--r-- 1 root root 0 May 10 16:14 dentry-state
+-rw-r--r-- 1 root root 0 May 10 16:14 dir-notify-enable
+-rw-r--r-- 1 root root 0 May 10 16:14 file-max
+-r--r--r-- 1 root root 0 May 10 16:14 file-nr
+</pre><div class="para">
+ In this listing, the files <code class="filename">dir-notify-enable</code> and <code class="filename">file-max</code> can be written to and, therefore, can be used to configure the kernel. The other files only provide feedback on current settings.
+ </div><div class="para">
+ Changing a value within a <code class="filename">/proc/sys/</code> file is done by echoing the new value into the file. For example, to enable the System Request Key on a running kernel, type the command:
+ </div><pre class="screen">
+echo 1 > /proc/sys/kernel/sysrq
+</pre><div class="para">
+ This changes the value for <code class="filename">sysrq</code> from <code class="computeroutput">0</code> (off) to <code class="computeroutput">1</code> (on).
+ </div><div class="para">
+ A few <code class="filename">/proc/sys/</code> configuration files contain more than one value. To correctly send new values to them, place a space character between each value passed with the <code class="command">echo</code> command, such as is done in this example:
+ </div><pre class="screen">
+echo 4 2 45 > /proc/sys/kernel/acct
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Any configuration changes made using the <code class="command">echo</code> command disappear when the system is restarted. To make configuration changes take effect after the system is rebooted, refer to <a class="xref" href="#s1-proc-sysctl" title="19.4. Using the sysctl Command">Section 19.4, “Using the <code class="command">sysctl</code> Command”</a>.
+ </div></div></div><div class="para">
+ The <code class="filename">/proc/sys/</code> directory contains several subdirectories controlling different aspects of a running kernel.
+ </div><div class="section" title="19.3.9.1. /proc/sys/dev/" id="s3-proc-sys-dev"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-sys-dev">19.3.9.1. <code class="filename">/proc/sys/dev/</code> </h4></div></div></div><a id="id1686142" class="indexterm"></a><div class="para">
+ This directory provides parameters for particular devices on the system. Most systems have at least two directories, <code class="filename">cdrom/</code> and <code class="filename">raid/</code>. Customized kernels can have other directories, such as <code class="filename">parport/</code>, which provides the ability to share one parallel port between multiple device drivers.
+ </div><div class="para">
+ The <code class="filename">cdrom/</code> directory contains a file called <code class="filename">info</code>, which reveals a number of important CD-ROM parameters:
+ </div><pre class="screen">
+CD-ROM information, Id: cdrom.c 3.20 2003/12/17
+drive name: hdc
+drive speed: 48
+drive # of slots: 1
+Can close tray: 1
+Can open tray: 1
+Can lock tray: 1
+Can change speed: 1
+Can select disk: 0
+Can read multisession: 1
+Can read MCN: 1
+Reports media changed: 1
+Can play audio: 1
+Can write CD-R: 0
+Can write CD-RW: 0
+Can read DVD: 0
+Can write DVD-R: 0
+Can write DVD-RAM: 0
+Can read MRW: 0
+Can write MRW: 0
+Can write RAM: 0
+</pre><div class="para">
+ This file can be quickly scanned to discover the qualities of an unknown CD-ROM. If multiple CD-ROMs are available on a system, each device is given its own column of information.
+ </div><div class="para">
+ Various files in <code class="filename">/proc/sys/dev/cdrom</code>, such as <code class="filename">autoclose</code> and <code class="filename">checkmedia</code>, can be used to control the system's CD-ROM. Use the <code class="command">echo</code> command to enable or disable these features.
+ </div><div class="para">
+ If RAID support is compiled into the kernel, a <code class="filename">/proc/sys/dev/raid/</code> directory becomes available with at least two files in it: <code class="filename">speed_limit_min</code> and <code class="filename">speed_limit_max</code>. These settings determine the acceleration of RAID devices for I/O intensive tasks, such as resyncing the disks.
+ </div></div><div class="section" title="19.3.9.2. /proc/sys/fs/" id="s3-proc-sys-fs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-sys-fs">19.3.9.2. <code class="filename">/proc/sys/fs/</code> </h4></div></div></div><a id="id789014" class="indexterm"></a><div class="para">
+ This directory contains an array of options and information concerning various aspects of the file system, including quota, file handle, inode, and dentry information.
+ </div><div class="para">
+ The <code class="filename">binfmt_misc/</code> directory is used to provide kernel support for miscellaneous binary formats.
+ </div><div class="para">
+ The important files in <code class="filename">/proc/sys/fs/</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">dentry-state</code> — Provides the status of the directory cache. The file looks similar to the following:
+ </div><pre class="screen">
+57411 52939 45 0 0 0
+</pre><div class="para">
+ The first number reveals the total number of directory cache entries, while the second number displays the number of unused entries. The third number tells the number of seconds between when a directory has been freed and when it can be reclaimed, and the fourth measures the pages currently requested by the system. The last two numbers are not used and display only zeros.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">file-max</code> — Lists the maximum number of file handles that the kernel allocates. Raising the value in this file can resolve errors caused by a lack of available file handles.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">file-nr</code> — Lists the number of allocated file handles, used file handles, and the maximum number of file handles.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overflowgid</code> and <code class="filename">overflowuid</code> — Defines the fixed group ID and user ID, respectively, for use with file systems that only support 16-bit group and user IDs.
+ </div></li></ul></div></div><div class="section" title="19.3.9.3. /proc/sys/kernel/" id="s3-proc-sys-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-sys-kernel">19.3.9.3. <code class="filename">/proc/sys/kernel/</code> </h4></div></div></div><a id="id750618" class="indexterm"></a><a id="id750648" class="indexterm"></a><a id="id582948" class="indexterm"></a><a id="id582966" class="indexterm"></a><a id="id582984" class="indexterm"></a><div class="para">
+ This directory contains a variety of different configuration files that directly affect the operation of the kernel. Some of the most important files include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">acct</code> — Controls the suspension of process accounting based on the percentage of free space available on the file system containing the log. By default, the file looks like the following:
+ </div><pre class="screen">
+4 2 30
+</pre><div class="para">
+ The first value dictates the percentage of free space required for logging to resume, while the second value sets the threshold percentage of free space when logging is suspended. The third value sets the interval, in seconds, that the kernel polls the file system to see if logging should be suspended or resumed.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ctrl-alt-del</code> — Controls whether <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Delete</strong></span> gracefully restarts the computer using <code class="command">init</code> (<code class="computeroutput">0</code>) or forces an immediate reboot without syncing the dirty buffers to disk (<code class="computeroutput">1</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">domainname</code> — Configures the system domain name, such as <code class="computeroutput">example.com</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">exec-shield</code> — Configures the Exec Shield feature of the kernel. Exec Shield provides protection against certain types of buffer overflow attacks.
+ </div><div class="para">
+ There are two possible values for this virtual file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">0</code> — Disables Exec Shield.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">1</code> — Enables Exec Shield. This is the default value.
+ </div></li></ul></div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If a system is running security-sensitive applications that were started while Exec Shield was disabled, these applications must be restarted when Exec Shield is enabled in order for Exec Shield to take effect.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="filename">hostname</code> — Configures the system hostname, such as <code class="computeroutput">www.example.com</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">hotplug</code> — Configures the utility to be used when a configuration change is detected by the system. This is primarily used with USB and Cardbus PCI. The default value of <code class="computeroutput">/sbin/hotplug</code> should not be changed unless testing a new program to fulfill this role.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">modprobe</code> — Sets the location of the program used to load kernel modules. The default value is <code class="computeroutput">/sbin/modprobe</code> which means <code class="command">kmod</code> calls it to load the module when a kernel thread calls <code class="command">kmod</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmax</code> — Sets the maximum size of any message sent from one process to another and is set to <code class="computeroutput">8192</code> bytes by default. Be careful when raising this value, as queued messages between processes are stored in non-swappable kernel memory. Any increase in <code class="filename">msgmax</code> would increase RAM requirements for the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmnb</code> — Sets the maximum number of bytes in a single message queue. The default is <code class="computeroutput">16384</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmni</code> — Sets the maximum number of message queue identifiers. The default is <code class="computeroutput">4008</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">osrelease</code> — Lists the Linux kernel release number. This file can only be altered by changing the kernel source and recompiling.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ostype</code> — Displays the type of operating system. By default, this file is set to <code class="computeroutput">Linux</code>, and this value can only be changed by changing the kernel source and recompiling.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overflowgid</code> and <code class="filename">overflowuid</code> — Defines the fixed group ID and user ID, respectively, for use with system calls on architectures that only support 16-bit group and user IDs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">panic</code> — Defines the number of seconds the kernel postpones rebooting when the system experiences a kernel panic. By default, the value is set to <code class="computeroutput">0</code>, which disables automatic rebooting after a panic.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">printk</code> — This file controls a variety of settings related to printing or logging error messages. Each error message reported by the kernel has a <em class="firstterm">loglevel</em> associated with it that defines the importance of the message. The loglevel values break down in this order:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">0</code> — Kernel emergency. The system is unusable.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">1</code> — Kernel alert. Action must be taken immediately.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">2</code> — Condition of the kernel is considered critical.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">3</code> — General kernel error condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">4</code> — General kernel warning condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">5</code> — Kernel notice of a normal but significant condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">6</code> — Kernel informational message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">7</code> — Kernel debug-level messages.
+ </div></li></ul></div><div class="para">
+ Four values are found in the <code class="filename">printk</code> file:
+ </div><pre class="screen">
+6 4 1 7
+</pre><div class="para">
+ Each of these values defines a different rule for dealing with error messages. The first value, called the <em class="firstterm">console loglevel</em>, defines the lowest priority of messages printed to the console. (Note that, the lower the priority, the higher the loglevel number.) The second value sets the default loglevel for messages without an explicit loglevel attached to them. The third value sets the lowest possible loglevel configuration for the console loglevel. The last value sets the default value for the console loglevel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">random/</code> directory — Lists a number of values related to generating random numbers for the kernel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sem</code> — Configures <em class="firstterm">semaphore</em> settings within the kernel. A semaphore is a System V IPC object that is used to control utilization of a particular process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmall</code> — Sets the total amount of shared memory that can be used at one time on the system, in bytes. By default, this value is <code class="computeroutput">2097152</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmmax</code> — Sets the largest shared memory segment size allowed by the kernel, in bytes. By default, this value is <code class="computeroutput">33554432</code>. However, the kernel supports much larger values than this.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmmni</code> — Sets the maximum number of shared memory segments for the whole system, in bytes. By default, this value is <code class="computeroutput">4096</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sysrq</code> — Activates the System Request Key, if this value is set to anything other than zero (<code class="computeroutput">0</code>), the default.
+ </div><div class="para">
+ The System Request Key allows immediate input to the kernel through simple key combinations. For example, the System Request Key can be used to immediately shut down or restart a system, sync all mounted file systems, or dump important information to the console. To initiate a System Request Key, type <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>SysRq</strong></span>+<span class="keycap"><strong> <em class="replaceable"><code>system request code</code></em> </strong></span> . Replace <em class="replaceable"><code>system request code</code></em> with one of the following system request codes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">r</code> — Disables raw mode for the keyboard and sets it to XLATE (a limited keyboard mode which does not recognize modifiers such as <span class="keycap"><strong>Alt</strong></span>, <span class="keycap"><strong>Ctrl</strong></span>, or <span class="keycap"><strong>Shift</strong></span> for all keys).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">k</code> — Kills all processes active in a virtual console. Also called <em class="firstterm">Secure Access Key</em> (<em class="firstterm">SAK</em>), it is often used to verify that the login prompt is spawned from <code class="command">init</code> and not a trojan copy designed to capture usernames and passwords.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">b</code> — Reboots the kernel without first unmounting file systems or syncing disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">c</code> — Crashes the system without first unmounting file systems or syncing disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">o</code> — Shuts off the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">s</code> — Attempts to sync disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">u</code> — Attempts to unmount and remount all file systems as read-only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">p</code> — Outputs all flags and registers to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">t</code> — Outputs a list of processes to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">m</code> — Outputs memory statistics to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">0</code> through <code class="command">9</code> — Sets the log level for the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">e</code> — Kills all processes except <code class="command">init</code> using SIGTERM.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">i</code> — Kills all processes except <code class="command">init</code> using SIGKILL.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">l</code> — Kills all processes using SIGKILL (including <code class="command">init</code>). <span class="emphasis"><em>The system is unusable after issuing this System Request Key code.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">h</code> — Displays help text.
+ </div></li></ul></div><div class="para">
+ This feature is most beneficial when using a development kernel or when experiencing system freezes.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ The System Request Key feature is considered a security risk because an unattended console provides an attacker with access to the system. For this reason, it is turned off by default.
+ </div></div></div><div class="para">
+ Refer to <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysrq.txt</code> for more information about the System Request Key.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tainted</code> — Indicates whether a non-GPL module is loaded.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">0</code> — No non-GPL modules are loaded.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">1</code> — At least one module without a GPL license (including modules with no license) is loaded.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">2</code> — At least one module was force-loaded with the command <code class="command">insmod -f</code>.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="filename">threads-max</code> — Sets the maximum number of threads to be used by the kernel, with a default value of <code class="computeroutput">2048</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">version</code> — Displays the date and time the kernel was last compiled. The first field in this file, such as <code class="computeroutput">#3</code>, relates to the number of times a kernel was built from the source base.
+ </div></li></ul></div></div><div class="section" title="19.3.9.4. /proc/sys/net/" id="s3-proc-sys-net"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-sys-net">19.3.9.4. <code class="filename">/proc/sys/net/</code> </h4></div></div></div><a id="id2328561" class="indexterm"></a><a id="id790258" class="indexterm"></a><a id="id790272" class="indexterm"></a><a id="id790287" class="indexterm"></a><div class="para">
+ This directory contains subdirectories concerning various networking topics. Various configurations at the time of kernel compilation make different directories available here, such as <code class="filename">ethernet/</code>, <code class="filename">ipv4/</code>, <code class="filename">ipx/</code>, and <code class="filename">ipv6/</code>. By altering the files within these directories, system administrators are able to adjust the network configuration on a running system.
+ </div><div class="para">
+ Given the wide variety of possible networking options available with Linux, only the most common <code class="filename">/proc/sys/net/</code> directories are discussed.
+ </div><div class="para">
+ The <code class="filename">/proc/sys/net/core/</code> directory contains a variety of settings that control the interaction between the kernel and networking layers. The most important of these files are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">message_burst</code> — Sets the amount of time in tenths of a second required to write a new warning message. This setting is used to mitigate <em class="firstterm">Denial of Service</em> (<em class="firstterm">DoS</em>) attacks. The default setting is <code class="computeroutput">10</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">message_cost</code> — Sets a cost on every warning message. The higher the value of this file (default of <code class="computeroutput">5</code>), the more likely the warning message is ignored. This setting is used to mitigate DoS attacks.
+ </div><div class="para">
+ The idea of a DoS attack is to bombard the targeted system with requests that generate errors and fill up disk partitions with log files or require all of the system's resources to handle the error logging. The settings in <code class="filename">message_burst</code> and <code class="filename">message_cost</code> are designed to be modified based on the system's acceptable risk versus the need for comprehensive logging.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">netdev_max_backlog</code> — Sets the maximum number of packets allowed to queue when a particular interface receives packets faster than the kernel can process them. The default value for this file is <code class="computeroutput">1000</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">optmem_max</code> — Configures the maximum ancillary buffer size allowed per socket.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rmem_default</code> — Sets the receive socket buffer default size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rmem_max</code> — Sets the receive socket buffer maximum size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wmem_default</code> — Sets the send socket buffer default size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wmem_max</code> — Sets the send socket buffer maximum size in bytes.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">/proc/sys/net/ipv4/</code> directory contains additional networking settings. Many of these settings, used in conjunction with one another, are useful in preventing attacks on the system or when using the system to act as a router.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ An erroneous change to these files may affect remote connectivity to the system.
+ </div></div></div><div class="para">
+ The following is a list of some of the more important files within the <code class="filename">/proc/sys/net/ipv4/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">icmp_echo_ignore_all</code> and <code class="filename">icmp_echo_ignore_broadcasts</code> — Allows the kernel to ignore ICMP ECHO packets from every host or only those originating from broadcast and multicast addresses, respectively. A value of <code class="computeroutput">0</code> allows the kernel to respond, while a value of <code class="computeroutput">1</code> ignores the packets.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_default_ttl</code> — Sets the default <em class="firstterm">Time To Live (TTL)</em>, which limits the number of hops a packet may make before reaching its destination. Increasing this value can diminish system performance.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_forward</code> — Permits interfaces on the system to forward packets to one other. By default, this file is set to <code class="computeroutput">0</code>. Setting this file to <code class="computeroutput">1</code> enables network packet forwarding.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_local_port_range</code> — Specifies the range of ports to be used by TCP or UDP when a local port is needed. The first number is the lowest port to be used and the second number specifies the highest port. Any systems that expect to require more ports than the default 1024 to 4999 should use a range from 32768 to 61000.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_syn_retries</code> — Provides a limit on the number of times the system re-transmits a SYN packet when attempting to make a connection.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_retries1</code> — Sets the number of permitted re-transmissions attempting to answer an incoming connection. Default of <code class="computeroutput">3</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_retries2</code> — Sets the number of permitted re-transmissions of TCP packets. Default of <code class="computeroutput">15</code>.
+ </div></li></ul></div><div class="para">
+ The file called
+ </div><pre class="screen">
+<code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/networking/ip-sysctl.txt</code>
+</pre><div class="para">
+ contains a complete list of files and options available in the <code class="filename">/proc/sys/net/ipv4/</code> directory.
+ </div><div class="para">
+ A number of other directories exist within the <code class="filename">/proc/sys/net/ipv4/</code> directory and each covers a different aspect of the network stack. The <code class="filename">/proc/sys/net/ipv4/conf/</code> directory allows each system interface to be configured in different ways, including the use of default settings for unconfigured devices (in the <code class="filename">/proc/sys/net/ipv4/conf/default/</code> subdirectory) and settings that override all special configurations (in the <code class="filename">/proc/sys/net/ipv4/conf/all/</code> subdirectory).
+ </div><div class="para">
+ The <code class="filename">/proc/sys/net/ipv4/neigh/</code> directory contains settings for communicating with a host directly connected to the system (called a network neighbor) and also contains different settings for systems more than one hop away.
+ </div><div class="para">
+ Routing over IPV4 also has its own directory, <code class="filename">/proc/sys/net/ipv4/route/</code>. Unlike <code class="filename">conf/</code> and <code class="filename">neigh/</code>, the <code class="filename">/proc/sys/net/ipv4/route/</code> directory contains specifications that apply to routing with any interfaces on the system. Many of these settings, such as <code class="filename">max_size</code>, <code class="filename">max_delay</code>, and <code class="filename">min_delay</code>, relate to controlling the size of the routing cache. To clear the routing cache, write any value to the <code class="filename">flush</code> file.
+ </div><div class="para">
+ Additional information about these directories and the possible values for their configuration files can be found in:
+ </div><pre class="screen">
+/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><div class="section" title="19.3.9.5. /proc/sys/vm/" id="s3-proc-sys-vm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-sys-vm">19.3.9.5. <code class="filename">/proc/sys/vm/</code> </h4></div></div></div><a id="id790123" class="indexterm"></a><a id="id821394" class="indexterm"></a><a id="id821409" class="indexterm"></a><div class="para">
+ This directory facilitates the configuration of the Linux kernel's virtual memory (VM) subsystem. The kernel makes extensive and intelligent use of virtual memory, which is commonly referred to as swap space.
+ </div><div class="para">
+ The following files are commonly found in the <code class="filename">/proc/sys/vm/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">block_dump</code> — Configures block I/O debugging when enabled. All read/write and block dirtying operations done to files are logged accordingly. This can be useful if diagnosing disk spin up and spin downs for laptop battery conservation. All output when <code class="filename">block_dump</code> is enabled can be retrieved via <code class="command">dmesg</code>. The default value is <code class="computeroutput">0</code>.
+ </div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ If <code class="filename">block_dump</code> is enabled at the same time as kernel debugging, it is prudent to stop the <code class="command">klogd</code> daemon, as it generates erroneous disk activity caused by <code class="filename">block_dump</code>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_background_ratio</code> — Starts background writeback of dirty data at this percentage of total memory, via a pdflush daemon. The default value is <code class="command">10</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_expire_centisecs</code> — Defines when dirty in-memory data is old enough to be eligible for writeout. Data which has been dirty in-memory for longer than this interval is written out next time a pdflush daemon wakes up. The default value is <code class="command">3000</code>, expressed in hundredths of a second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_ratio</code> — Starts active writeback of dirty data at this percentage of total memory for the generator of dirty data, via pdflush. The default value is <code class="command">20</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_writeback_centisecs</code> — Defines the interval between pdflush daemon wakeups, which periodically writes dirty in-memory data out to disk. The default value is <code class="command">500</code>, expressed in hundredths of a second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">laptop_mode</code> — Minimizes the number of times that a hard disk needs to spin up by keeping the disk spun down for as long as possible, therefore conserving battery power on laptops. This increases efficiency by combining all future I/O processes together, reducing the frequency of spin ups. The default value is <code class="computeroutput">0</code>, but is automatically enabled in case a battery on a laptop is used.
+ </div><div class="para">
+ This value is controlled automatically by the acpid daemon once a user is notified battery power is enabled. No user modifications or interactions are necessary if the laptop supports the ACPI (Advanced Configuration and Power Interface) specification.
+ </div><div class="para">
+ For more information, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/laptop-mode.txt</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">max_map_count</code> — Configures the maximum number of memory map areas a process may have. In most cases, the default value of <code class="computeroutput">65536</code> is appropriate.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">min_free_kbytes</code> — Forces the Linux VM (virtual memory manager) to keep a minimum number of kilobytes free. The VM uses this number to compute a <code class="filename">pages_min</code> value for each <code class="filename">lowmem</code> zone in the system. The default value is in respect to the total memory on the machine.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nr_hugepages</code> — Indicates the current number of configured <code class="filename">hugetlb</code> pages in the kernel.
+ </div><div class="para">
+ For more information, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/vm/hugetlbpage.txt</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nr_pdflush_threads</code> — Indicates the number of pdflush daemons that are currently running. This file is read-only, and should not be changed by the user. Under heavy I/O loads, the default value of two is increased by the kernel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overcommit_memory</code> — Configures the conditions under which a large memory request is accepted or denied. The following three modes are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">0</code> — The kernel performs heuristic memory over commit handling by estimating the amount of memory available and failing requests that are blatantly invalid. Unfortunately, since memory is allocated using a heuristic rather than a precise algorithm, this setting can sometimes allow available memory on the system to be overloaded. This is the default setting.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">1</code> — The kernel performs no memory over commit handling. Under this setting, the potential for memory overload is increased, but so is performance for memory intensive tasks (such as those executed by some scientific software).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">2</code> — The kernel fails requests for memory that add up to all of swap plus the percent of physical RAM specified in <code class="filename">/proc/sys/vm/overcommit_ratio</code>. This setting is best for those who desire less risk of memory overcommitment.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This setting is only recommended for systems with swap areas larger than physical memory.
+ </div></div></div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="filename">overcommit_ratio</code> — Specifies the percentage of physical RAM considered when <code class="filename">/proc/sys/vm/overcommit_memory</code> is set to <code class="command">2</code>. The default value is <code class="command">50</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">page-cluster</code> — Sets the number of pages read in a single attempt. The default value of <code class="computeroutput">3</code>, which actually relates to 16 pages, is appropriate for most systems.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">swappiness</code> — Determines how much a machine should swap. The higher the value, the more swapping occurs. The default value, as a percentage, is set to <code class="computeroutput">60</code>.
+ </div></li></ul></div><div class="para">
+ All kernel-based documentation can be found in the following locally installed location:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/</code>, which contains additional information.
+ </div></div></div><div class="section" title="19.3.10. /proc/sysvipc/" id="s2-proc-dir-sysvipc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-sysvipc">19.3.10. <code class="filename">/proc/sysvipc/</code> </h3></div></div></div><a id="id1338627" class="indexterm"></a><div class="para">
+ This directory contains information about System V IPC resources. The files in this directory relate to System V IPC calls for messages (<code class="filename">msg</code>), semaphores (<code class="filename">sem</code>), and shared memory (<code class="filename">shm</code>).
+ </div></div><div class="section" title="19.3.11. /proc/tty/" id="s2-proc-tty"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-tty">19.3.11. <code class="filename">/proc/tty/</code> </h3></div></div></div><a id="id1338681" class="indexterm"></a><div class="para">
+ This directory contains information about the available and currently used <em class="firstterm">tty devices</em> on the system. Originally called <em class="firstterm">teletype devices</em>, any character-based data terminals are called tty devices.
+ </div><div class="para">
+ In Linux, there are three different kinds of tty devices. <em class="firstterm">Serial devices</em> are used with serial connections, such as over a modem or using a serial cable. <em class="firstterm">Virtual terminals</em> create the common console connection, such as the virtual consoles available when pressing <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong><F-key></strong></span> at the system console. <em class="firstterm">Pseudo terminals</em> create a two-way communication that is used by some higher level applications, such as XFree86. The <code class="filename">drivers</code> file is a list of the current tty devices in use, as in the following example:
+ </div><pre class="screen">
+serial /dev/cua 5 64-127 serial:callout
+serial /dev/ttyS 4 64-127 serial
+pty_slave /dev/pts 136 0-255 pty:slave
+pty_master /dev/ptm 128 0-255 pty:master
+pty_slave /dev/ttyp 3 0-255 pty:slave
+pty_master /dev/pty 2 0-255 pty:master
+/dev/vc/0 /dev/vc/0 4 0 system:vtmaster
+/dev/ptmx /dev/ptmx 5 2 system
+/dev/console /dev/console 5 1 system:console
+/dev/tty /dev/tty 5 0 system:/dev/tty
+unknown /dev/vc/%d 4 1-63 console
+</pre><div class="para">
+ The <code class="filename">/proc/tty/driver/serial</code> file lists the usage statistics and status of each of the serial tty lines.
+ </div><div class="para">
+ In order for tty devices to be used as network devices, the Linux kernel enforces <em class="firstterm">line discipline</em> on the device. This allows the driver to place a specific type of header with every block of data transmitted over the device, making it possible for the remote end of the connection to a block of data as just one in a stream of data blocks. SLIP and PPP are common line disciplines, and each are commonly used to connect systems to one other over a serial link.
+ </div></div><div class="section" title="19.3.12. /proc/PID/" id="s2-proc-pid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-pid">19.3.12. <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> </h3></div></div></div><a id="id476674" class="indexterm"></a><div class="para">
+ Out of Memory (OOM) refers to a computing state where all available memory, including swap space, has been allocated. When this situation occurs, it will cause the system to panic and stop functioning as expected. There is a switch that controls OOM behavior in <code class="filename">/proc/sys/vm/panic_on_oom</code>. When set to <code class="filename">1</code> the kernel will panic on OOM. A setting of <code class="filename">0</code> instructs the kernel to call a function named <code class="filename">oom_killer</code> on an OOM. Usually, <code class="filename">oom_killer</code> can kill rogue processes and the system will survive.
+ </div><div class="para">
+ The easiest way to change this is to echo the new value to <code class="filename">/proc/sys/vm/panic_on_oom</code>.
+ </div><pre class="screen">
+# cat /proc/sys/vm/panic_on_oom
+1
+
+# echo 0 > /proc/sys/vm/panic_on_oom
+
+# cat /proc/sys/vm/panic_on_oom
+0
+</pre><div class="para">
+ It is also possible to prioritize which processes get killed by adjusting the <code class="filename">oom_killer</code> score. In <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> there are two tools labelled <code class="filename">oom_adj</code> and <code class="filename">oom_score</code>. Valid scores for <code class="filename">oom_adj</code> are in the range -16 to +15. To see the current <code class="filename">oom_killer</code> score, view the <code class="filename">oom_score</code> for the process. <code class="filename">oom_killer</code> will kill processes with the highest scores first.
+ </div><div class="para">
+ This example adjusts the oom_score of a process with a <em class="replaceable"><code>PID</code></em> of 12465 to make it less likely that <code class="filename">oom_killer</code> will kill it.
+ </div><pre class="screen">
+# cat /proc/12465/oom_score
+79872
+
+# echo -5 > /proc/12465/oom_adj
+
+# cat /proc/12465/oom_score
+78
+</pre><div class="para">
+ There is also a special value of -17, which disables <code class="filename">oom_killer</code> for that process. In the example below, <code class="filename">oom_score</code> returns a value of 0, indicating that this process would not be killed.
+ </div><pre class="screen">
+# cat /proc/12465/oom_score
+78
+
+# echo -17 > /proc/12465/oom_adj
+
+# cat /proc/12465/oom_score
+0
+</pre><div class="para">
+ A function called <code class="filename">badness()</code> is used to determine the actual score for each process. This is done by adding up 'points' for each examined process. The process scoring is done in the following way:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ The basis of each process's score is its memory size.
+ </div></li><li class="listitem"><div class="para">
+ The memory size of any of the process's children (not including a kernel thread) is also added to the score
+ </div></li><li class="listitem"><div class="para">
+ The process's score is increased for 'niced' processes and decreased for long running processes.
+ </div></li><li class="listitem"><div class="para">
+ Processes with the <code class="filename">CAP_SYS_ADMIN</code> and <code class="filename">CAP_SYS_RAWIO</code> capabilities have their scores reduced.
+ </div></li><li class="listitem"><div class="para">
+ The final score is then bitshifted by the value saved in the <code class="filename">oom_adj</code> file.
+ </div></li></ol></div><div class="para">
+ Thus, a process with the highest <code class="filename">oom_score</code> value will most probably be a non-priviliged, recently started process that, along with its children, uses a large amount of memory, has been 'niced', and handles no raw I/O.
+ </div></div></div><div class="section" title="19.4. Using the sysctl Command" id="s1-proc-sysctl"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-proc-sysctl">19.4. Using the <code class="command">sysctl</code> Command</h2></div></div></div><a id="id549040" class="indexterm"></a><a id="id549054" class="indexterm"></a><a id="id549069" class="indexterm"></a><a id="id549091" class="indexterm"></a><a id="id466994" class="indexterm"></a><a id="id467012" class="indexterm"></a><div class="para">
+ The <code class="command">/sbin/sysctl</code> command is used to view, set, and automate kernel settings in the <code class="filename">/proc/sys/</code> directory.
+ </div><div class="para">
+ For a quick overview of all settings configurable in the <code class="filename">/proc/sys/</code> directory, type the <code class="command">/sbin/sysctl -a</code> command as root. This creates a large, comprehensive list, a small portion of which looks something like the following:
+ </div><pre class="screen">
+net.ipv4.route.min_delay = 2 kernel.sysrq = 0 kernel.sem = 250 32000 32 128
+</pre><div class="para">
+ This is the same information seen if each of the files were viewed individually. The only difference is the file location. For example, the <code class="filename">/proc/sys/net/ipv4/route/min_delay</code> file is listed as <code class="computeroutput">net.ipv4.route.min_delay</code>, with the directory slashes replaced by dots and the <code class="computeroutput">proc.sys</code> portion assumed.
+ </div><div class="para">
+ The <code class="command">sysctl</code> command can be used in place of <code class="command">echo</code> to assign values to writable files in the <code class="filename">/proc/sys/</code> directory. For example, instead of using the command
+ </div><pre class="screen">
+echo 1 > /proc/sys/kernel/sysrq
+</pre><div class="para">
+ use the equivalent <code class="command">sysctl</code> command as follows:
+ </div><pre class="screen">
+sysctl -w kernel.sysrq="1"
+kernel.sysrq = 1
+</pre><div class="para">
+ While quickly setting single values like this in <code class="filename">/proc/sys/</code> is helpful during testing, this method does not work as well on a production system as special settings within <code class="filename">/proc/sys/</code> are lost when the machine is rebooted. To preserve custom settings, add them to the <code class="filename">/etc/sysctl.conf</code> file.
+ </div><div class="para">
+ Each time the system boots, the <code class="command">init</code> program runs the <code class="filename">/etc/rc.d/rc.sysinit</code> script. This script contains a command to execute <code class="command">sysctl</code> using <code class="filename">/etc/sysctl.conf</code> to determine the values passed to the kernel. Any values added to <code class="filename">/etc/sysctl.conf</code> therefore take effect each time the system boots.
+ </div></div><div class="section" title="19.5. References" id="s1-proc-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-proc-additional-resources">19.5. References</h2></div></div></div><a id="id761173" class="indexterm"></a><div class="para">
+ Below are additional sources of information about <code class="filename">proc</code> file system.
+ </div><div class="simplesect" title="Installed Documentation" id="s2-proc-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h1 class="title">Installed Documentation</h1></div></div></div><a id="id761209" class="indexterm"></a><div class="para">
+ Some of the best documentation about the <code class="filename">proc</code> file system is installed on the system by default.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt</code> — Contains assorted, but limited, information about all aspects of the <code class="filename">/proc/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysrq.txt</code> — An overview of System Request Key options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysctl/</code> — A directory containing a variety of <code class="command">sysctl</code> tips, including modifying values that concern the kernel (<code class="filename">kernel.txt</code>), accessing file systems (<code class="filename">fs.txt</code>), and virtual memory use (<code class="filename">vm.txt</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/networking/ip-sysctl.txt</code> — A detailed overview of IP networking options.
+ </div></li></ul></div></div><div class="simplesect" title="Useful Websites" id="s2-proc-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h1 class="title">Useful Websites</h1></div></div></div><a id="id2227729" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.linuxhq.com/">http://www.linuxhq.com/</a> — This website maintains a complete database of source, patches, and documentation for various versions of the Linux kernel.
+ </div></li></ul></div></div></div></div></div><div class="part" title="Part IV. System Monitoring" id="pt-system-monitoring"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part IV. System Monitoring</h1></div></div></div><div class="partintro" title="System Monitoring" id="id485894"><div></div><div class="para">
+ System administrators also monitor system performance. Fedora contains tools to assist administrators with these tasks.
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#ch-Gathering_System_Information">20. Gathering System Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-sysinfo-system-processes">20.1. System Processes</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-memory-usage">20.2. Memory Usage</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-filesystems">20.3. File Systems</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-hardware">20.4. Hardware</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-additional-resources">20.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-abrt">21. ABRT</a></span></dt><dd><dl><dt><span class="section"><a href="#id525678">21.1. Overview</a></span></dt><dt><span class="section"><a href="#id741804">21.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="#abrt-plugins">21.3.
<span class="application"><strong>ABRT</strong></span> Plugins</a></span></dt><dt><span class="section"><a href="#generating-backtrace">21.4. Generating Backtraces</a></span></dt><dt><span class="section"><a href="#id944926">21.5. Using the Command Line Interface</a></span></dt><dt><span class="section"><a href="#configuring">21.6. Configuring ABRT</a></span></dt><dt><span class="section"><a href="#configuring-centralized-crash-collection">21.7. Configuring Centralized Crash Collection</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" title="Chapter 20. Gathering System Information" id="ch-Gathering_System_Information" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. Gathering System Information</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-sysinfo-system-processes">20.1. System Processes</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-memory-usage">20.2. Memory U
sage</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-filesystems">20.3. File Systems</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-hardware">20.4. Hardware</a></span></dt><dt><span class="section"><a href="#s1-sysinfo-additional-resources">20.5. Additional Resources</a></span></dt></dl></div><a id="id758954" class="indexterm"></a><a id="id840899" class="indexterm"></a><div class="para">
+ Before you learn how to configure your system, you should learn how to gather essential system information. For example, you should know how to find the amount of free memory, the amount of available hard drive space, how your hard drive is partitioned, and what processes are running. This chapter discusses how to retrieve this type of information from your Fedora system using simple commands and a few simple programs.
+ </div><div class="section" title="20.1. System Processes" id="s1-sysinfo-system-processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-system-processes">20.1. System Processes</h2></div></div></div><a id="id548995" class="indexterm"></a><a id="id1369712" class="indexterm"></a><a id="id799222" class="indexterm"></a><div class="para">
+ The <code class="command">ps ax</code> command displays a list of current system processes, including processes owned by other users. To display the owner alongside each process, use the <code class="command">ps aux</code> command. This list is a static list; in other words, it is a snapshot of what was running when you invoked the command. If you want a constantly updated list of running processes, use <code class="command">top</code> as described below.
+ </div><div class="para">
+ The <code class="command">ps</code> output can be long. To prevent it from scrolling off the screen, you can pipe it through less:
+ </div><pre class="screen">
+<code class="command">ps aux | less</code>
+</pre><div class="para">
+ You can use the <code class="command">ps</code> command in combination with the <code class="command">grep</code> command to see if a process is running. For example, to determine if <span class="application"><strong>Emacs</strong></span> is running, use the following command:
+ </div><pre class="screen">
+<code class="command">ps ax | grep emacs</code>
+</pre><a id="id724508" class="indexterm"></a><a id="id764068" class="indexterm"></a><div class="para">
+ The <code class="command">top</code> command displays currently running processes and important information about them including their memory and CPU usage. The list is both real-time and interactive. An example of output from the <code class="command">top</code> command is provided as follows:
+ </div><pre class="screen">top - 18:11:48 up 1 min, 1 user, load average: 0.68, 0.30, 0.11
+Tasks: 122 total, 1 running, 121 sleeping, 0 stopped, 0 zombie
+Cpu(s): 0.0%us, 0.5%sy, 0.0%ni, 93.4%id, 5.7%wa, 0.2%hi, 0.2%si, 0.0
+Mem: 501924k total, 376496k used, 125428k free, 29664k buffers
+Swap: 1015800k total, 0k used, 1015800k free, 189008k cached
+
+ PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
+ 1601 root 40 0 20172 1084 920 S 0.3 0.2 0:00.08 hald-addon-sto
+ 1998 silas 40 0 14984 1160 880 R 0.3 0.2 0:00.13 top
+ 1 root 40 0 19160 1412 1156 S 0.0 0.3 0:00.96 init
+ 2 root 40 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
+ 3 root RT 0 0 0 0 S 0.0 0.0 0:00.05 migration/0
+ 4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
+ 5 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
+ 6 root RT 0 0 0 0 S 0.0 0.0 0:00.04 migration/1
+ 7 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/1
+ 8 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/1
+ 9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events/0
+ 10 root 20 0 0 0 0 S 0.0 0.0 0:00.01 events/1
+ 11 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuset
+ 12 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre><div class="para">
+ To exit <code class="command">top</code>, press the <span class="keycap"><strong>q</strong></span> key.
+ </div><div class="para">
+ <a class="xref" href="#interactive-top-command" title="Table 20.1. Interactive top commands">Table 20.1, “Interactive <code class="command">top</code> commands”</a> contains useful interactive commands that you can use with <code class="command">top</code>. For more information, refer to the <code class="command">top</code>(1) manual page.
+ </div><div class="table" title="Table 20.1. Interactive top commands" id="interactive-top-command"><h6>Table 20.1. Interactive <code class="command">top</code> commands</h6><div class="table-contents"><table summary="Interactive top commands" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span class="keycap"><strong>Space</strong></span>
+ </td><td>
+ Immediately refresh the display
+ </td></tr><tr><td>
+ <span class="keycap"><strong>h</strong></span>
+ </td><td>
+ Display a help screen
+ </td></tr><tr><td>
+ <span class="keycap"><strong>k</strong></span>
+ </td><td>
+ Kill a process. You are prompted for the process ID and the signal to send to it.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>n</strong></span>
+ </td><td>
+ Change the number of processes displayed. You are prompted to enter the number.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>u</strong></span>
+ </td><td>
+ Sort by user.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>M</strong></span>
+ </td><td>
+ Sort by memory usage.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>P</strong></span>
+ </td><td>
+ Sort by CPU usage.
+ </td></tr></tbody></table></div></div><br class="table-break" /><a id="id834349" class="indexterm"></a><a id="id834362" class="indexterm"></a><div class="para">
+ If you prefer a graphical interface for <code class="command">top</code>, you can use the <span class="application"><strong>GNOME System Monitor</strong></span>. To start it from the desktop, select <span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> or execute <code class="command">gnome-system-monitor</code> at a shell prompt. Select the <span class="guilabel"><strong>Processes</strong></span> tab.
+ </div><div class="para">
+ The <span class="application"><strong>GNOME System Monitor</strong></span> allows you to search for a process in the list of running processes. Using the <span class="application"><strong>GNOME System Monitor</strong></span>, you can also view all processes, your processes, or active processes.
+ </div><div class="para">
+ The <span class="guimenuitem"><strong>Edit</strong></span> menu item allows you to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Stop a process.
+ </div></li><li class="listitem"><div class="para">
+ Continue or start a process.
+ </div></li><li class="listitem"><div class="para">
+ End a processes.
+ </div></li><li class="listitem"><div class="para">
+ Kill a process.
+ </div></li><li class="listitem"><div class="para">
+ Change the priority of a selected process.
+ </div></li><li class="listitem"><div class="para">
+ Edit the System Monitor preferences. These include changing the interval seconds to refresh the list and selecting process fields to display in the System Monitor window.
+ </div></li></ul></div><div class="para">
+ The <span class="guimenuitem"><strong>View</strong></span> menu item allows you to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ View only active processes.
+ </div></li><li class="listitem"><div class="para">
+ View all processes.
+ </div></li><li class="listitem"><div class="para">
+ View my processes.
+ </div></li><li class="listitem"><div class="para">
+ View process dependencies.
+ </div></li><li class="listitem"><div class="para">
+ View a memory map of a selected process.
+ </div></li><li class="listitem"><div class="para">
+ View the files opened by the selected process.
+ </div></li><li class="listitem"><div class="para">
+ Refresh the list of processes.
+ </div></li></ul></div><div class="para">
+ To stop a process, select it and click <span class="guibutton"><strong>End Process</strong></span>. Alternatively you can also stop a process by selecting it, clicking <span class="guimenuitem"><strong>Edit</strong></span> on your menu and selecting <span class="guimenuitem"><strong>Stop Process</strong></span>.
+ </div><div class="para">
+ To sort the information by a specific column, click on the name of the column. This sorts the information by the selected column in ascending order. Click on the name of the column again to toggle the sort between ascending and descending order.
+ </div><div class="figure" title="Figure 20.1. GNOME System Monitor - Processes tab" id="fig-sysinfo-processes"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/gnome-system-monitor-processes.png" align="middle" alt="GNOME System Monitor - Processes tab" /><div class="longdesc"><div class="para">
+ Processes tab of the gnome-system-monitor
+ </div></div></div></div><h6>Figure 20.1. <span class="application">GNOME System Monitor - Processes tab</span> </h6></div><br class="figure-break" /></div><div class="section" title="20.2. Memory Usage" id="s1-sysinfo-memory-usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-memory-usage">20.2. Memory Usage</h2></div></div></div><a id="id469258" class="indexterm"></a><a id="id469272" class="indexterm"></a><a id="id469282" class="indexterm"></a><a id="id469291" class="indexterm"></a><div class="para">
+ The <code class="command">free</code> command displays the total amount of physical memory and swap space for the system as well as the amount of memory that is used, free, shared, in kernel buffers, and cached.
+ </div><pre class="screen">
+ total used free shared buffers cached
+Mem: 4017660 1619044 2398616 0 59864 637968
+-/+ buffers/cache: 921212 3096448
+Swap: 3071996 0 3071996
+</pre><div class="para">
+ The command <code class="command">free -m</code> shows the same information in megabytes, which are easier to read.
+ </div><pre class="screen">
+ total used free shared buffers cached
+Mem: 3923 1569 2353 0 58 626
+-/+ buffers/cache: 884 3038
+Swap: 2999 0 2999
+</pre><div class="para">
+ If you prefer a graphical interface for <code class="command">free</code>, you can use the <span class="application"><strong>GNOME System Monitor</strong></span>. To start it from the desktop, select <span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> or execute <code class="command">gnome-system-monitor</code> at a shell prompt. Click on the <span class="guilabel"><strong>Resources</strong></span> tab.
+ </div><div class="figure" title="Figure 20.2. GNOME System Monitor - Resources tab" id="fig-sysinfo-memory"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/gnome-system-monitor-memory.png" align="middle" alt="GNOME System Monitor - Resources tab" /><div class="longdesc"><div class="para">
+ Resources tab of the gnome-system-monitor
+ </div></div></div></div><h6>Figure 20.2. <span class="application">GNOME System Monitor - Resources tab</span> </h6></div><br class="figure-break" /></div><div class="section" title="20.3. File Systems" id="s1-sysinfo-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-filesystems">20.3. File Systems</h2></div></div></div><a id="id511678" class="indexterm"></a><a id="id672413" class="indexterm"></a><a id="id672422" class="indexterm"></a><div class="para">
+ The <code class="command">df</code> command reports the system's disk space usage. If you Execute the command <code class="command">df</code> at a shell prompt, the output looks similar to the following:
+ </div><pre class="screen">
+Filesystem 1K-blocks Used Available Use% Mounted on
+/dev/mapper/volgrp1-lvroot
+ 14127024 6868092 6541316 52% /
+tmpfs 2008828 592 2008236 1% /dev/shm
+/dev/sda1 495844 65047 405197 14% /boot
+/dev/mapper/luks-b20f8f7a-7f0f-4497-8de4-81bfa3e541cf
+ 122046576 12111420 103735552 11% /home
+</pre><div class="para">
+ By default, this utility shows the partition size in 1 kilobyte blocks and the amount of used and available disk space in kilobytes. To view the information in megabytes and gigabytes, use the command <code class="command">df -h</code>. The <code class="command">-h</code> argument stands for human-readable format. The output looks similar to the following:
+ </div><pre class="screen">
+Filesystem Size Used Avail Use% Mounted on
+/dev/mapper/volgrp1-lvroot
+ 14G 6.6G 6.3G 52% /
+tmpfs 2.0G 592K 2.0G 1% /dev/shm
+/dev/sda1 485M 64M 396M 14% /boot
+/dev/mapper/luks-b20f8f7a-7f0f-4497-8de4-81bfa3e541cf
+ 117G 12G 99G 11% /home
+</pre><a id="id2230531" class="indexterm"></a><a id="id2230553" class="indexterm"></a><div class="para">
+ In the list of mounted partitions, there is an entry for <code class="filename">/dev/shm</code>. This entry represents the system's virtual memory file system.
+ </div><a id="id2230574" class="indexterm"></a><div class="para">
+ The <code class="command">du</code> command displays the estimated amount of space being used by files in a directory. If you execute <code class="command">du</code> at a shell prompt, the disk usage for each of the subdirectories is displayed in a list. The grand total for the current directory and subdirectories are also shown as the last line in the list. If you do not want to see the totals for all the subdirectories, use the command <code class="command">du -hs</code> to see only the grand total for the directory in human-readable format. Use the <code class="command">du --help</code> command to see more options.
+ </div><div class="para">
+ To view the system's partitions and disk space usage in a graphical format, use the <span class="guilabel"><strong>Gnome System Monitor</strong></span> by clicking on <span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> or executing the <code class="command">gnome-system-monitor</code> command at a shell prompt. Select the File Systems tab to view the system's partitions. The figure below illustrates the File Systems tab.
+ </div><div class="figure" title="Figure 20.3. GNOME System Monitor - File Systems tab" id="fig-sysinfo-filesystems"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/gnome-system-monitor-filesystems.png" align="middle" alt="GNOME System Monitor - File Systems tab" /><div class="longdesc"><div class="para">
+ File systems tab of the gnome-system-monitor
+ </div></div></div></div><h6>Figure 20.3. <span class="application">GNOME System Monitor - File Systems tab</span> </h6></div><br class="figure-break" /></div><div class="section" title="20.4. Hardware" id="s1-sysinfo-hardware"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-hardware">20.4. Hardware</h2></div></div></div><a id="id458473" class="indexterm"></a><a id="id458486" class="indexterm"></a><a id="id503706" class="indexterm"></a><a id="id503719" class="indexterm"></a><div class="para">
+ If you are having trouble configuring your hardware or just want to know what hardware is in your system, you can use the <span class="application"><strong>Hardware Browser</strong></span> application to display the hardware that can be probed. To start the program from the desktop, select <span class="guimenu"><strong>System</strong></span> (the main menu on the panel) > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>Hardware</strong></span> or type <code class="command">hwbrowser</code> at a shell prompt. As shown in <a class="xref" href="#sysinfo-hwbrowser-fig" title="Figure 20.4. Hardware Browser">Figure 20.4, “ <span class="application">Hardware Browser</span> ”</a>, it displays your CD-ROM devices, diskette drives, hard drives and their partitions, network devices, pointing devices, system devices, and video cards. Click on the category name in the left menu, and the information is displayed.
+ </div><div class="figure" title="Figure 20.4. Hardware Browser" id="sysinfo-hwbrowser-fig"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/hwbrowser.png" align="middle" width="444" alt="Hardware Browser" /><div class="longdesc"><div class="para">
+ hwbrowser
+ </div></div></div></div><h6>Figure 20.4. <span class="application">Hardware Browser</span> </h6></div><br class="figure-break" /><a id="id1521538" class="indexterm"></a><a id="id457269" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Device Manager</strong></span> application can also be used to display your system hardware. This application can be started by selecting <span class="guimenu"><strong>System</strong></span> (the main menu on the panel) > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>Hardware</strong></span> like the <span class="application"><strong>Hardware Browser</strong></span>. To start the application from a terminal, type <code class="command">hal-device-manager</code>. Depending on your installation preferences, the graphical menu above may start this application or the <span class="application"><strong>Hardware Browser</strong></span> when clicked. The figure below illustrates the <span class="application"><strong>Device Manager</strong></span> window.
+ </div><div class="figure" title="Figure 20.5. Device Manager" id="sysinfo-devicemngr-fig"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/devicemngr.png" align="middle" width="444" alt="Device Manager" /><div class="longdesc"><div class="para">
+ Device Manager
+ </div></div></div></div><h6>Figure 20.5. <span class="application">Device Manager</span> </h6></div><br class="figure-break" /><div class="para">
+ You can also use the <code class="command">lspci</code> command to list all PCI devices. Use the command <code class="command">lspci -v</code> for more verbose information or <code class="command">lspci -vv</code> for very verbose output.
+ </div><div class="para">
+ For example, <code class="command">lspci</code> can be used to determine the manufacturer, model, and memory size of a system's video card:
+ </div><pre class="screen">
+00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
+ Subsystem: Lenovo Device 20e4
+ Flags: bus master, fast devsel, latency 0
+ Memory at f4200000 (64-bit, non-prefetchable) [size=1M]
+ Capabilities: [d0] Power Management version 3</pre><div class="para">
+ The <code class="command">lspci</code> is also useful to determine the network card in your system if you do not know the manufacturer or model number.
+ </div></div><div class="section" title="20.5. Additional Resources" id="s1-sysinfo-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-additional-resources">20.5. Additional Resources</h2></div></div></div><div class="para">
+ To learn more about gathering system information, refer to the following resources.
+ </div><div class="section" title="20.5.1. Installed Documentation" id="s2-sysinfo-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysinfo-installed-docs">20.5.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">ps --help</code> — Displays a list of options that can be used with <code class="command">ps</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">top</code> manual page — Execute <code class="command">man top</code> to learn more about <code class="command">top</code> and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">free</code> manual page — Execute <code class="command">man free</code> to learn more about <code class="command">free</code> and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">df</code> manual page — Execute <code class="command">man df</code> to learn more about the <code class="command">df</code> command and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">du</code> manual page — Execute <code class="command">man du</code> to learn more about the <code class="command">du</code> command and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">lspci</code> manual page — Execute <code class="command">man lspci</code> to learn more about the <code class="command">lspci</code> command and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id620272" class="indexterm"></a>
+ <code class="filename">/proc/</code> directory — The contents of the <code class="filename">/proc/</code> directory can also be used to gather more detailed system information.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 21. ABRT" id="ch-abrt" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. ABRT</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#id525678">21.1. Overview</a></span></dt><dt><span class="section"><a href="#id741804">21.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="#abrt-plugins">21.3. <span class="application"><strong>ABRT</strong></span> Plugins</a></span></dt><dt><span class="section"><a href="#generating-backtrace">21.4. Generating Backtraces</a></span></dt><dt><span class="section"><a href="#id944926">21.5. Using the Command Line Interface</a></span></dt><dt><span class="section"><a href="#configuring">21.6. Configuring ABRT</a></span></dt><dt><span class="section"><a href="#configuring-centralized-crash-collection">21.7. Configuring Centralized Crash Collection</a></span></dt></dl><
/div><div class="section" title="21.1. Overview"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id525678">21.1. Overview</h2></div></div></div><div class="para">
+ <span class="application"><strong>ABRT</strong></span> is the <span class="application"><strong>Automatic Bug-Reporting Tool</strong></span>. <span class="application"><strong>ABRT</strong></span> consists of a daemon that runs silently in the background most of the time. It springs into action when an application crashes. It then collects the relevant crash data such as a core file if there is one, the crashing application's command line parameters, and other contextual puzzle pieces of forensic utility. Finally, <span class="application"><strong>ABRT</strong></span> is capable of reporting crash data to a relevant issue tracker, such as RHTSupport. Reporting crash data to a relevant issue tracker can be configured to happen automatically at every detected crash, or crash dumps can be stored locally, reviewed, reported, and deleted manually by a user. <span class="application"><strong>ABRT</strong></span>'s various plugins analyze crash data from applications written in
the C, C++ and Python language, as well as report crashes to relevant issue trackers.
+ </div><div class="para">
+ The <span class="application"><strong>ABRT</strong></span> package consists of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">abrtd</code>, the system service
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>abrt-applet</strong></span>, which runs in the user's Notification Area
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>abrt-gui</strong></span>, the GUI application that shows collected crash dumps and allows you to edit, report, and delete them
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>abrt-cli</strong></span>, the command line interface with functionality similar to <span class="application"><strong>abrt-gui</strong></span>.
+ </div></li></ul></div><div class="para">
+ You can open the <span class="application"><strong>ABRT</strong></span> GUI application by clicking <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Automatic Bug Reporting Tool</strong></span>.
+ </div><div class="mediaobject" align="center"><img src="images/ABRT-Main_Window.png" align="middle" /><div class="caption"><div class="para">
+ Automatic Bug Reporting Tool Main Window
+ </div></div></div><div class="para">
+ A number of additional packages can be installed to provide <span class="application"><strong>ABRT</strong></span> plugins and addons. To view all the available <span class="application"><strong>ABRT</strong></span> packages, type the following command:
+<pre class="screen">
+<code class="command">~]$ yum list all | grep abrt</code>
+</pre>
+
+ </div></div><div class="section" title="21.2. Installing and Running ABRT"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id741804">21.2. Installing and Running ABRT</h2></div></div></div><div class="para">
+ By default, <span class="application"><strong>ABRT</strong></span> should be installed on your system, the <code class="systemitem">abrtd</code> daemon configured to run at boot time, and <span class="application"><strong>abrt-applet</strong></span> to run in the Notification Area of your desktop session.
+ </div><div class="note" title="Note: Installing the ABRT packages"><div class="admonition_header"><h2>Note: Installing the <span class="application"><strong>ABRT</strong></span> packages</h2></div><div class="admonition"><div class="para">
+ In order to use <span class="application"><strong>ABRT</strong></span>, first ensure the <code class="command">abrt-desktop</code> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install abrt-desktop</code>
+</pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ <span class="application"><strong>ABRT</strong></span> is typically configured to start up at boot time. You can check that the <code class="systemitem">abrtd</code> daemon is running by running the following command, as root:
+ </div><pre class="screen">~]# <code class="command">service abrtd status</code>
+abrt (pid 1559) is running...</pre><div class="para">
+ If you receive <code class="computeroutput">abrt is stopped</code>, you can start the <code class="systemitem">abrtd</code> service by running, as root:
+ </div><pre class="screen">~]# <code class="command">service abrtd start</code>
+Starting abrt daemon: [ OK ]</pre><div class="para">
+ You can ensure that the <code class="systemitem">abrtd</code> service initializes at startup time by running the following command, as root:
+ </div><pre class="screen">~]# <code class="command">chkconfig abrtd on</code>
+</pre><div class="para">
+ <span class="application"><strong>ABRT</strong></span>'s applet can be started by hand by running the <code class="command">abrt-applet</code> program as a normal user when logged into your desktop session, or by arranging for it to be started when the GUI session is initialized. For example, on the GNOME desktop, this can be configured in <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Startup Applications</strong></span>.
+ </div><div class="mediaobject" align="center"><img src="images/ABRT-Notification_Area_alarm_icon.png" align="middle" width="29" /><div class="caption"><div class="para">
+ The ABRT alarm icon
+ </div></div></div><div class="para">
+ When a crash is detected and saved, a broadcast <code class="systemitem">D-Bus</code> message is sent about this crash. If <code class="command">abrt-applet</code> is running, it receives this message and displays a red alarm icon in the Notification Area. You can open the GUI application by clicking on this icon.
+ </div><div class="para">
+ Alternatively, you can open the <span class="application"><strong>ABRT</strong></span> GUI application by clicking <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Automatic Bug Reporting Tool</strong></span>.
+ </div></div><div class="section" title="21.3. ABRT Plugins" id="abrt-plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="abrt-plugins">21.3. <span class="application"><strong>ABRT</strong></span> Plugins</h2></div></div></div><div class="para">
+ <span class="application"><strong>ABRT</strong></span> offers a variety of analyzer plugins and reporter plugins. These plugins are described in the following two sections. Not all of the plugins mentioned in the following sections are installed by default. To view all available plugins, run the following command:
+<pre class="screen">
+<code class="command">]$ yum list all | grep abrt-plugin-*</code>
+</pre>
+
+ </div><div class="section" title="21.3.1. Analyzer Plugins" id="analyzer-plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="analyzer-plugins">21.3.1. Analyzer Plugins</h3></div></div></div><div class="para">
+ These plugins serve as analyzers and crash information collectors for specific types of crashes. For example, the <span class="application"><strong>Kerneloops</strong></span> analyzer plugin checks for crashes in the kernel only. These plugins can be enabled/disabled from loading at start-up in their corresponding configuration files placed in the <code class="filename">/etc/abrt/plugins/</code> directory. The following is a list of all analyzer plugins.
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Kerneloops</span></dt><dd><div class="para">
+ — Checks for crashes in the kernel and consequently collects kernel crash information. It can be enabled/disabled from loading at start-up in the <code class="filename">/etc/abrt/plugins/Kerneloops.conf</code> file.
+ </div></dd><dt class="varlistentry"><span class="term">Python</span></dt><dd><div class="para">
+ — Checks for crashes in Python programs and consequently collects the crash information. It can be enabled/disabled from loading at start-up in the <code class="filename">/etc/abrt/plugins/Python.conf</code> file.
+ </div></dd><dt class="varlistentry"><span class="term">CCpp</span></dt><dd><div class="para">
+ — Checks for crashes in C and C++ programs and consequently collects the crash information. It can be enabled/disabled from loading at start-up in the <code class="filename">/etc/abrt/plugins/CCpp.conf</code> file.
+ </div></dd></dl></div></div><div class="section" title="21.3.2. Reporter Plugins" id="reporter-plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="reporter-plugins">21.3.2. Reporter Plugins</h3></div></div></div><div class="para">
+ These plugins gather the crash data acquired by the analyzer plugins, combine the data with any user input (such as comments about the crash, reproducibility, etc.), and provide a specific output. Each of these plugins is configurable in its corresponding configuration file placed in the <code class="filename">/etc/abrt/plugins/</code> directory or in the <span class="application"><strong>ABRT</strong></span> GUI application (for more information on reporter plugin configuration in the <span class="application"><strong>ABRT</strong></span> GUI application, refer to <a class="xref" href="#configuring-plugins-in-the-gui" title="21.3.3. Plugin Configuration in the GUI">Section 21.3.3, “Plugin Configuration in the GUI”</a>).
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">RHTSupport</span></dt><dd><div class="para">
+ — Reports crashes into the Red Hat Technical Support system. Intended for users of Fedora.
+ </div></dd><dt class="varlistentry"><span class="term">MailX</span></dt><dd><div class="para">
+ — Sends a crash report via the <span class="application"><strong>mailx</strong></span> utility to a specified email address.
+ </div></dd><dt class="varlistentry"><span class="term">Report Uploader</span></dt><dd><div class="para">
+ — Uploads a tarball with crash data into a <code class="systemitem">FTP</code>/<code class="systemitem">SCP</code> server
+ </div></dd><dt class="varlistentry"><span class="term">Bugzilla</span></dt><dd><div class="para">
+ — Reports crashes into Bugzilla in the form of Bugzilla database entries.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The use of the Bugzilla plugin to report crashes into Bugzilla in the form of Bugzilla database entries is strongly discouraged. Please use the RHTSupport plugin to report crashes into the Red Hat Ticketing System instead.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Logger</span></dt><dd><div class="para">
+ — Creates a crash report and saves it to a specified local file.
+ </div></dd></dl></div></div><div class="section" title="21.3.3. Plugin Configuration in the GUI" id="configuring-plugins-in-the-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="configuring-plugins-in-the-gui">21.3.3. Plugin Configuration in the GUI</h3></div></div></div><div class="para">
+ You can override the system-wide plugin configuration in the <code class="filename">/etc/abrt/plugins/*.conf</code> configuration files on a per-user basis. Each of the plugins specified in section <a class="xref" href="#reporter-plugins" title="21.3.2. Reporter Plugins">Section 21.3.2, “Reporter Plugins”</a> can be configured in the <span class="application"><strong>ABRT</strong></span> GUI application. Open the plugins window by clicking <span class="guimenu"><strong>Edit</strong></span> → <span class="guisubmenu"><strong>Plugins</strong></span>. This window shows a list of all installed plugins. You can also view each of the plugins' details by selecting one and expanding <span class="guimenu"><strong>Plugin Details</strong></span>. When you select one of the configurable plugins, you can click the <span class="guibutton"><strong>Configure plugin</strong></span> button and you will be able to configure your desired plugin. If you change any of the plugins' par
ameters, they are saved in the Gnome keyring and will be used in the future GUI sessions.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ All of the <code class="filename">/etc/abrt/plugins/*.conf</code> configuration files are world readable and are meant to be used as global settings. Thus, it is not advisable to store usernames, passwords or any other sensitive data in them. The per-user settings (set in the GUI application and readable by the owner of $HOME only) are stored in the Gnome keyring or can be stored in a text file in <code class="filename">$HOME/.abrt/*.conf</code> for use in <code class="command">abrt-cli</code>.
+ </div></div></div><div class="mediaobject" align="center"><img src="images/ABRT-plugins.png" align="middle" width="444" /><div class="caption"><div class="para">
+ ABRT Plugins
+ </div></div></div><div class="para">
+ The following is a list of all configuration options available for each configurable plugin in the <span class="application"><strong>ABRT</strong></span> GUI application.
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">RHTSupport</span></dt><dd><div class="para">
+ In the <span class="guilabel"><strong>RHTSupport plugin configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>RHTSupport URL</strong></span> — Specifies the RHTSupport URL where crash dumps are sent (by default, set to <a href="https://api.access.redhat.com/rs">https://api.access.redhat.com/rs</a>).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Login</strong></span> — User login which is used to log into RHTSupport and create a RHTSupport database entry for a reported crash.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Password</strong></span> — Password used to log into RHTSupport.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>SSL verify</strong></span> option is checked, the <code class="systemitem">SSL</code> protocol is used when sending the data over the network.
+ </div></dd><dt class="varlistentry"><span class="term">MailX</span></dt><dd><div class="para">
+ In the <span class="guilabel"><strong>MailX plugin configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Subject</strong></span> — A string that appears in the <code class="literal">Subject</code> field of a crash report email sent by <span class="application"><strong>mailx</strong></span> (by default, set to <code class="literal">"[abrt] crash report"</code>).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Your Email</strong></span> — A string that appears in the <code class="literal">From</code> field of a crash report email.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Recipient's Email</strong></span> — Email address of the recipient of a crash report email.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Send Binary Data</strong></span> option is checked, the crash report email will also contain all binary files associated with the crash in an attachment. The core dump file is also sent as an attachment.
+ </div></dd><dt class="varlistentry"><span class="term">ReportUploader</span></dt><dd><div class="para">
+ In the <span class="guilabel"><strong>ReportUploader plugin configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Customer</strong></span> — Specifies customer's identification.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Ticket</strong></span> — Specifies the Ticket ID number in a specific issue tracker that collects crash reports.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>URL</strong></span> — Specifies the URL of the issue tracker used to collect crash reports.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Retry count</strong></span> — Specifies the number of retries should an upload fail.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Retry delay</strong></span> — Specifies the number or seconds between two retries.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Use encryption</strong></span> option is checked, the crash report sent to the issue tracker is encrypted.
+ </div><div class="para">
+ When the <span class="guilabel"><strong>Upload</strong></span> option is checked, all crash reports are uploaded to the specified issue tracker. If the option is unchecked, all crash reports are saved locally.
+ </div></dd><dt class="varlistentry"><span class="term">Bugzilla</span></dt><dd><div class="para">
+ In the <span class="guilabel"><strong>Bugzilla plugin configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Bugzilla URL</strong></span> — Specifies the Bugzilla URL where crash dumps are sent (by default, set to <a href="https://bugzilla.redhat.com">https://bugzilla.redhat.com</a>).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Login (email)</strong></span> — User login which is used to log into Bugzilla and create a Bugzilla database entry for a reported crash.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Password</strong></span> — Password used to log into Bugzilla.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>SSL verify</strong></span> option is checked, the <code class="systemitem">SSL</code> protocol is used when sending the data over the network.
+ </div></dd><dt class="varlistentry"><span class="term">Logger</span></dt><dd><div class="para">
+ In the <span class="guilabel"><strong>Logger plugin configuration</strong></span>, you can configure the following parameter:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Logger file</strong></span> — Specifies a file into which the crash reports are saved (by default, set to <code class="filename">/var/log/abrt.log</code>).
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Append new logs</strong></span> option is checked, the Logger plugin will append new crash reports to the log file specified in the <span class="guilabel"><strong>Logger file</strong></span> option. When unchecked, the new crash report always replaces the previous one.
+ </div></dd></dl></div></div></div><div class="section" title="21.4. Generating Backtraces" id="generating-backtrace"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="generating-backtrace">21.4. Generating Backtraces</h2></div></div></div><div class="para">
+ In order to analyze a reported crash, developers need as much detail about the crash as possible. A <em class="firstterm">stack backtrace</em> is an important source of information when a crash in a binary program (caught by the <code class="command">CCpp</code> analyzer plugin) occurs.
+ </div><div class="para">
+ <span class="application"><strong>ABRT</strong></span> is configured to generate a backtrace whenever a crash is reported through the <span class="application"><strong>ABRT</strong></span> GUI application or the <span class="application"><strong>ABRT</strong></span> command line interface.
+ </div><div class="para">
+ <span class="application"><strong>ABRT</strong></span> completes the following steps to generate a backtrace:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ It examines the core dump (which consists of the recorded contents of the memory of an application at a specific time), which is saved in the crash dump directory. From this file, <span class="application"><strong>ABRT</strong></span> extracts the information about the crashed binary program and information about every loaded dynamic library.
+ </div></li><li class="listitem"><div class="para">
+ It queries <span class="application"><strong>Yum</strong></span> to determine which <span class="package">debuginfo</span> packages correspond to all the files extracted from the crash dump. This is the first potentially slow operation. <span class="application"><strong>Yum</strong></span> may need to refresh the <em class="parameter"><code>filelists</code></em> of various repositories in order to find the correct package names. This process may take a few minutes.
+ </div></li><li class="listitem"><div class="para">
+ It downloads the needed <span class="package">debuginfo</span> packages, and extracts and saves the <code class="command">debuginfo</code> files. In order to speed up future backtrace generation, <code class="command">debuginfo</code> files are cached in the <code class="filename">/var/cache/abrt-di</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ It generates a backtrace using <span class="application"><strong>GDB</strong></span> (the GNU Debugger) and saves it into the crash dump directory.
+ </div></li></ul></div><div class="para">
+ You can change the following backtrace generation parameters in the <code class="filename">/etc/abrt/plugins/CCpp.conf</code> file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Backtrace = <em class="replaceable"><code><yes/no></code></em></code> — Enables/Disables backtrace generation.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">BacktraceRemotes = <em class="replaceable"><code><yes/no></code></em></code> — For more information about this parameter, refer to <a class="xref" href="#configuring-centralized-crash-collection" title="21.7. Configuring Centralized Crash Collection">Section 21.7, “Configuring Centralized Crash Collection”</a>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">InstallDebugInfo = <em class="replaceable"><code><yes/no></code></em></code> — Enables/Disables the installation of <span class="package">debuginfo</span> packages (useful if your network is not available or it is firewalled).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ReadonlyLocalDebugInfoDirs = /path1:/path2:...</code> — Specifies the paths of local repositories (available, for example, through a network mount) that contain pre-downloaded <span class="package">debuginfo</span> packages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">DebugInfoCacheMB = <code class="constant">4000</code></code> — Specifies the maximum size of the cached <span class="package">debuginfo</span> packages in the <code class="filename">/var/cache/abrt-di</code> directory.
+ </div></li></ul></div><div class="section" title="21.4.1. Troubleshooting Backtrace Generation" id="troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="troubleshooting">21.4.1. Troubleshooting Backtrace Generation</h3></div></div></div><div class="para">
+ In some cases, a long delay in the <span class="application"><strong>ABRT</strong></span> GUI application occurs after choosing a crash and pressing the <span class="guibutton"><strong>Report</strong></span> button. In this case, open the <span class="guibutton"><strong>Details</strong></span> in the <span class="guilabel"><strong>Generating backtrace</strong></span> window and examine the messages.
+ </div><div class="para">
+ The following is a typical output seen in the <span class="guilabel"><strong>Generating backtrace</strong></span> window:
+ </div><pre class="screen">
+Starting the debuginfo installation
+Getting list of build IDs
+12 missing debuginfos, getting package list from cache
+12 missing debuginfos, getting package list from repositories
+Downloading 7 packages
+Download 1/7: acl-debuginfo-2.2.49-6.fc13.x86_64
+Unpacking: acl-debuginfo-2.2.49-6.fc13.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/3d/e20df1db609bd9313b1dc440796004f95911fd.debug
+Download 2/7: firefox-debuginfo-3.6.7-1.fc13.x86_64
+Unpacking: firefox-debuginfo-3.6.7-1.fc13.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/3d/b29c9308cb276431ce8854a2d88cf83518afc6.debug
+Caching debuginfo:
+usr/lib/debug/.build-id/a3/86884285365c8288e4e761ec034fafaa1daee1.debug
+⋮
+Download 7/7: zlib-debuginfo-1.2.3-23.fc12.x86_64
+Unpacking: zlib-debuginfo-1.2.3-23.fc12.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/f7/933750da80f555321576e72b375caf7a3cc075.debug
+All needed debuginfos are present
+Generating backtrace
+</pre><div class="para">
+ This process is performed by the <span class="application"><strong>/usr/bin/abrt-debuginfo-install</strong></span> shell script. This script uses a temporary directory (e.g. <code class="filename">/var/run/abrt/tmp-29177-1283344373</code>) for its operations. Normally, this directory is removed when <span class="application"><strong>abrt-debuginfo-install</strong></span> exits.
+ </div><div class="para">
+ If the <span class="package">debuginfo</span> installation hangs, or is unable to download anything, you may debug the problem by editing the <span class="application"><strong>abrt-debuginfo-install</strong></span> script. Change the following parameters:
+ </div><pre class="screen">
+debug=false
+keep_tmp=false
+</pre><div class="para">
+ at the top of the script to:
+ </div><pre class="screen">
+debug=true
+keep_tmp=true
+</pre><div class="para">
+ The first parameter instructs <span class="application"><strong>abrt-debuginfo-install</strong></span> to be verbose, the second parameter instructs <span class="application"><strong>abrt-debuginfo-install</strong></span> to not delete the <code class="filename">/var/run/abrt/tmp-NNN-NNN</code> directory. You can examine the log files in this directory, they may contain useful error messages.
+ </div><div class="para">
+ <span class="application"><strong>abrt-debuginfo-install</strong></span> uses <span class="application"><strong>yum</strong></span> and <span class="application"><strong>yumdownloader</strong></span> to handle the <span class="package">debuginfo</span> packages. In order to quickly check that your <span class="application"><strong>yum</strong></span> configuration does not cause any problems which prevent <span class="application"><strong>abrt-debuginfo-install</strong></span> from working properly, change to the <code class="filename">/tmp</code> directory and run the following commands, as root:
+ </div><pre class="screen">
+tmp]# yum --enablerepo=*debuginfo* --quiet provides /usr/bin/true
+tmp]# yumdownloader --enablerepo=*debuginfo* --quiet coreutils
+</pre><div class="para">
+ Both of these commands should complete successfully, with no error messages. The second command should download the <code class="filename">coreutils-*.rpm</code> file. If any error messages appear, check your <span class="application"><strong>yum</strong></span> configuration files in the <code class="filename">/etc/yum.repos.d/*</code> directory and the <code class="filename">/etc/yum/*</code> directory. If any of these commands hang, check that you do not have another instance of <span class="application"><strong>yum</strong></span> running, and that your network connection is working properly.
+ </div></div></div><div class="section" title="21.5. Using the Command Line Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id944926">21.5. Using the Command Line Interface</h2></div></div></div><div class="para">
+ Crashes detected by <span class="application"><strong>ABRT</strong></span> can be viewed, reported, and deleted using the command line interface.
+ </div><div class="section" title="21.5.1. Viewing Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id524381">21.5.1. Viewing Crashes</h3></div></div></div><div class="para">
+ To get a list of all crashes, simply enter <code class="command">abrt-cli --list</code> or <code class="command">abrt-cli -l</code>:
+ </div><pre class="screen">
+~]$ <code class="command">abrt-cli --list</code>
+0.
+ UID : 500
+ UUID : 784b06666020e9f43718d99bf2649f19b4f251a9
+ Package : bash-4.1.2-3.el6
+ Executable : /bin/bash
+ Crash Time : Tue 20 Jul 2010 03:22:52 PM CEST
+ Crash Count: 2
+1.
+ UID : 500
+ UUID : 48007b98d65cca4530d99a564379e2609169239d
+ Package : coreutils-8.4-9.el6
+ Executable : /bin/sleep
+ Crash Time : Tue 20 Jul 2010 03:22:00 PM CEST
+ Crash Count: 1
+</pre><div class="para">
+ This output contains basic information for every crash. The <code class="computeroutput">UID:</code> field shows the ID of the user which ran the program that caused the crash. The <code class="computeroutput">Package</code> field shows the name and version of the Fedora package that contains the program, and the <code class="computeroutput">Executable</code> field shows the location of the binary or script that crashed. The <code class="computeroutput">Crash Count</code> field indicates how many times the same crash happened.
+ </div></div><div class="section" title="21.5.2. Reporting Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id524432">21.5.2. Reporting Crashes</h3></div></div></div><div class="para">
+ To report a certain crash, enter <code class="command">abrt-cli --report <em class="replaceable"><code><UUID></code></em></code> or <code class="command">abrt-cli --r <em class="replaceable"><code><UUID></code></em></code>, where <code class="varname">UUID</code> is a Universally Unique Identifier of a crash from the list of crashes; to view this list, execute the <code class="command">abrt-cli --list</code> command. You do not need to remember the exact <code class="varname">UUID</code>; either use a mouse to copy and paste it, or enter a unique prefix and press <span class="keycap"><strong><ENTER></strong></span>.
+ </div><pre class="screen">
+~]$ <code class="command">abrt-cli --report 480</code>
+ <span class="keycap"><strong><ENTER></strong></span>
+>> Starting report creation...
+</pre><div class="para">
+ <span class="application"><strong>ABRT</strong></span> analyzes the crash and creates a report about it. This might take a while. When the report is ready, <code class="command">abrt-cli</code> opens a text editor with the content of the report. You can see what is being reported, and you can fill in instructions on how to reproduce the crash and other comments. You should also check the backtrace, because the backtrace might be sent to a public server and viewed by anyone, depending on the plugin settings.
+ </div><div class="note" title="Preferred Text Editor"><div class="admonition_header"><h2>Preferred Text Editor</h2></div><div class="admonition"><div class="para">
+ You can choose which text editor is used to check the reports. <code class="command">abrt-cli</code> uses the editor defined in the <code class="envar">ABRT_EDITOR</code> environment variable. If the variable is not defined, it checks the <code class="envar">VISUAL</code> and <code class="envar">EDITOR</code> variables. If none of these variables is set, <code class="command">vi</code> is used. You can set the preferred editor in your <code class="filename">.bashrc</code> configuration file. For example, if you prefer GNU Emacs, add the following line to the file:
+ </div><pre class="screen">
+export <code class="varname">VISUAL</code>=<strong class="userinput"><code>emacs</code></strong></pre></div></div><div class="para">
+ When you are done with the report, save your changes and close the editor. You will be asked which of the enabled <span class="application"><strong>ABRT</strong></span> plugins you want to use to send the report. Respond <span class="keycap"><strong>Y</strong></span> to send the report using your desired plugin or <span class="keycap"><strong>N</strong></span> to skip a plugin you wish not to use.
+ </div></div><div class="section" title="21.5.3. Deleting Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id416358">21.5.3. Deleting Crashes</h3></div></div></div><div class="para">
+ If you know that you do not want to report a certain crash dump, you can delete it from the crash list. To delete a certain crash dump, enter the command: <code class="command">abrt-cli --delete <em class="replaceable"><code><UUID></code></em> </code>.
+ </div><div class="para">
+ Note that <span class="application"><strong>ABRT</strong></span> performs a detection of duplicate crashes by comparing new crashes with all locally saved crashes. For a repeating crash, <span class="application"><strong>ABRT</strong></span> requires you to act upon it only once. However, if you delete the crash dump of that crash, the next time this specific crash occurs, <span class="application"><strong>ABRT</strong></span> will treat it as a new crash: <span class="application"><strong>ABRT</strong></span> will alert you about it, prompt you to fill in a description, and report it. This can be redundant, therefore, deleting a crash is not advisable.
+ </div></div></div><div class="section" title="21.6. Configuring ABRT" id="configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="configuring">21.6. Configuring ABRT</h2></div></div></div><div class="para">
+ <span class="application"><strong>ABRT</strong></span>'s main configuration file is <code class="filename">/etc/abrt/abrt.conf</code>. <span class="application"><strong>ABRT</strong></span> plugins can be configured through their config files, located in the <code class="filename">/etc/abrt/plugins/</code> directory.
+ </div><div class="para">
+ After changing and saving the <code class="filename">abrt.conf</code> configuration file, you must restart the <code class="systemitem">abrtd</code> daemon—as root—for the new settings to take effect:
+ </div><pre class="screen">~]# <code class="command">service abrtd restart</code>
+</pre><div class="para">
+ The following configuration directives are currently supported in <code class="filename">/etc/abrt/abrt.conf</code>.
+ </div><div class="variablelist" title="[ Common ] Section Directives"><h6>[ Common ] Section Directives</h6><dl><dt class="varlistentry"><span class="term">OpenGPGCheck = <em class="replaceable"><code><yes/no></code></em> </span></dt><dd><div class="para">
+ Setting the <code class="computeroutput">OpenGPGCheck</code> directive to <strong class="userinput"><code>yes</code></strong> (the default setting) tells <span class="application"><strong>ABRT</strong></span> to <span class="emphasis"><em>only</em></span> analyze and handle crashes in applications provided by packages which are signed by the GPG keys whose locations are listed in the <code class="filename">/etc/abrt/gpg_keys</code> file. Setting <em class="parameter"><code>OpenGPGCheck</code></em> to <strong class="userinput"><code>no</code></strong> tells <span class="application"><strong>ABRT</strong></span> to catch crashes in all programs.
+ </div></dd><dt class="varlistentry"><span class="term">BlackList = nspluginwrapper, valgrind, strace, avant-window-navigator, [<span class="optional"><em class="replaceable"><code><additional_packages></code></em> </span>] </span></dt><dd><div class="para">
+ Crashes in packages and binaries listed after the <em class="parameter"><code>BlackList</code></em> directive will not be handled by <span class="application"><strong>ABRT</strong></span>. If you want <span class="application"><strong>ABRT</strong></span> to ignore other packages and binaries, list them here separated by commas.
+ </div></dd><dt class="varlistentry"><span class="term">ProcessUnpackaged = <em class="replaceable"><code><yes/no></code></em> </span></dt><dd><div class="para">
+ This directive tells <span class="application"><strong>ABRT</strong></span> whether to process crashes in executables that do not belong to any package.
+ </div></dd><dt class="varlistentry"><span class="term">BlackListedPaths = <code class="filename">/usr/share/doc/*</code>, <code class="filename">*/example*</code> </span></dt><dd><div class="para">
+ Crashes in executables in these paths will be ignored by <span class="application"><strong>ABRT</strong></span>.
+ </div></dd><dt class="varlistentry"><span class="term">Database = SQLite3</span></dt><dd><div class="para">
+ This directive instructs <span class="application"><strong>ABRT</strong></span> to store its crash data in the <span class="application"><strong>SQLite3</strong></span> database. Other databases are not currently supported. However, <span class="application"><strong>ABRT</strong></span>'s plugin architecture allows for future support for alternative databases.
+ </div></dd><dt class="varlistentry"><span class="term">#WatchCrashdumpArchiveDir = /var/spool/abrt-upload/</span></dt><dd><div class="para">
+ This directive is commented out by default. Enable (uncomment) it if you want <code class="systemitem">abrtd</code> to auto-unpack crashdump tarballs which appear in the specified directory — in this case <code class="filename">/var/spool/abrt-upload/</code> — (for example, uploaded via <code class="systemitem">ftp</code>, <code class="systemitem">scp</code>, etc.). You must ensure that whatever directory you specify in this directive exists and is writable for <code class="systemitem">abrtd</code>. <code class="systemitem">abrtd</code> will not create it automatically.
+ </div></dd><dt class="varlistentry"><span class="term">MaxCrashReportsSize = <em class="replaceable"><code><size_in_megabytes></code></em> </span></dt><dd><div class="para">
+ This option sets the amount of storage space, in megabytes, used by <span class="application"><strong>ABRT</strong></span> to store all crash information from all users. The default setting is <code class="constant">1000</code> MB. Once the quota specified here has been met, <span class="application"><strong>ABRT</strong></span> will continue catching crashes, and in order to make room for the new crash dumps, it will delete the oldest and largest ones.
+ </div></dd><dt class="varlistentry"><span class="term">ActionsAndReporters = SOSreport, [<span class="optional"><em class="replaceable"><code><additional_plugins></code></em> </span>] </span></dt><dd><div class="para">
+ This option tells <span class="application"><strong>ABRT</strong></span> to run the specified plugin(s) immediately after a crash is detected and saved. For example, the <strong class="userinput"><code>SOSreport</code></strong> plugin runs the <code class="systemitem">sosreport</code> tool which adds the data collected by it to the created crash dump. You can turn this behavior off by commenting out this line. For further fine-tuning, you can add <strong class="userinput"><code>SOSreport</code></strong> (or any other specified plugin) to either the <em class="parameter"><code>CCpp</code></em> or <em class="parameter"><code>Python</code></em> options to make <span class="application"><strong>ABRT</strong></span> run <code class="command">sosreport</code> (or any other specified plugin) after any C and C++ or Python applications crash, respectively. For more information on various Action and Reporter plugins, refer to <a class="xref" href="#abrt-plugins" title="21.3. A
BRT Plugins">Section 21.3, “ <span class="application"><strong>ABRT</strong></span> Plugins”</a>
+ </div></dd></dl></div><div class="variablelist" title="[ AnalyzerActionsAndReporters ] Section Directives"><h6>[ AnalyzerActionsAndReporters ] Section Directives</h6><div class="para">
+ This section allows you to associate certain analyzer actions and reporter actions to run when <span class="application"><strong>ABRT</strong></span> catches kernel oopses or crashes in C, C++ or Python programs. The actions and reporters specified in any of the directives below will run only if you run <code class="command">abrt-gui</code> or <code class="command">abrt-cli</code> and report the crash that occurred. If you do not specify any actions and reporters in these directives, you will not be able to report a crash via <code class="command">abrt-gui</code> or <code class="command">abrt-cli</code>. The order of actions and reporters is important. Commenting out a directive, will cause <span class="application"><strong>ABRT</strong></span> not to catch the crashes associated with that directive. For example, commenting out the Kerneloops line will cause <span class="application"><strong>ABRT</strong></span> not to catch kernel oopses.
+ </div><dl><dt class="varlistentry"><span class="term">Kerneloops = RHTSupport, Logger</span></dt><dd><div class="para">
+ This directive specifies that, for kernel oopses, both the RHTSupport and Logger reporters will be run.
+ </div></dd><dt class="varlistentry"><span class="term">CCpp = RHTSupport, Logger</span></dt><dd><div class="para">
+ This directive specifies that, when C or C++ program crashes occur, both the RHTSupport and Logger reporters will be run.
+ </div></dd><dt class="varlistentry"><span class="term">Python = RHTSupport, Logger</span></dt><dd><div class="para">
+ This directive specifies that, when Python program crashes occur, both the RHTSupport and Logger reporters will be run.
+ </div></dd></dl></div><div class="para">
+ Each of these destinations' details can be specified in the corresponding <code class="filename">plugins/*.conf</code> file. For example, <code class="filename">plugins/RHTSupport.conf</code> specifies which RHTSupport URL to use (set to <a href="https://api.access.redhat.com/rs">https://api.access.redhat.com/rs</a> by default), the user's login name, password for logging in to the RHTSupport site, etc. All these options can also be configured through the <code class="command">abrt-gui</code> application (for more information on plugin configuration refer to <a class="xref" href="#abrt-plugins" title="21.3. ABRT Plugins">Section 21.3, “ <span class="application"><strong>ABRT</strong></span> Plugins”</a>).
+ </div><div class="variablelist" title="[ Cron ] Section Directives"><h6>[ Cron ] Section Directives</h6><dl><dt class="varlistentry"><span class="term"> <em class="replaceable"><code><time></code></em> = <em class="replaceable"><code><action_to_run></code></em> </span></dt><dd><div class="para">
+ The <code class="computeroutput">[ Cron ]</code> section of <code class="filename">abrt.conf</code> allows you to specify the exact time, or elapsed amount of time between, when <span class="application"><strong>ABRT</strong></span> should run a certain action, such as scanning for kernel oopses or performing file transfers. You can list further actions to run by appending them to the end of this section.
+ </div><div class="example" title="Example 21.1. [ Cron ] section of /etc/abrt/abrt.conf" id="ex-_Cron__section_of__etc_abrt_abrt.conf"><h6>Example 21.1. [ Cron ] section of /etc/abrt/abrt.conf</h6><div class="example-contents"><pre class="screen"># Which Action plugins to run repeatedly
+[ Cron ]
+# h:m - at h:m
+# s - every s seconds
+120 = KerneloopsScanner
+#02:00 = FileTransfer</pre></div></div><br class="example-break" /><div class="para">
+ The format for an entry is either <strong class="userinput"><code><time_in_seconds> = <em class="replaceable"><code><action_to_run></code></em> </code></strong> or <strong class="userinput"><code><hh:mm> = <action_to_run> </code></strong>, where <strong class="userinput"><code>hh</code></strong> (hour) is in the range <code class="constant">00-23</code> (all hours less than 10 should be zero-filled, i.e. preceded by a <code class="constant">0</code>), and <strong class="userinput"><code>mm</code></strong> (minute) is <code class="constant">00-59</code>, zero-filled likewise.
+ </div></dd></dl></div></div><div class="section" title="21.7. Configuring Centralized Crash Collection" id="configuring-centralized-crash-collection"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="configuring-centralized-crash-collection">21.7. Configuring Centralized Crash Collection</h2></div></div></div><div class="para">
+ You can set up <span class="application"><strong>ABRT</strong></span> so that crash reports are collected from multiple systems and sent to a dedicated system for further processing. This is useful when an administrator does not want to log into hundreds of systems and manually check for crashes found by <span class="application"><strong>ABRT</strong></span>. In order to use this method, you need to install the <span class="application"><strong>abrt-plugin-reportuploader</strong></span> plugin (<code class="command">yum install abrt-plugin-reportuploader</code>).
+ </div><div class="para">
+ The steps to configure <span class="application"><strong>ABRT</strong></span>'s centralized crash collection are:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Complete the following steps on a dedicated system ("server system"):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Create a directory to which you want the crash reports to be uploaded to. Usually, <code class="filename">/var/spool/abrt-upload/</code> is used (the rest of the document assumes you are using <code class="filename">/var/spool/abrt-upload/</code>). Make sure this directory is writable by the <code class="systemitem">abrt</code> user.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When the <span class="package">abrt-desktop</span> package is installed, it creates a new system user and and a group, both named <code class="systemitem">abrt</code>. This user is used by the <code class="systemitem">abrtd</code> daemon for various things, for example, as the owner:group of <code class="filename">/var/spool/abrt/*</code> directories.
+ </div></div></div></li><li class="listitem"><div class="para">
+ In the <code class="filename">/etc/abrt/abrt.conf</code> configuration file, set the <code class="varname">WatchCrashdumpArchiveDir</code> directive to the following:
+<pre class="screen">
+WatchCrashdumpArchiveDir = /var/spool/abrt-upload/
+</pre>
+
+ </div></li><li class="listitem"><div class="para">
+ Determine your preferred upload mechanism; for example, <code class="systemitem">FTP</code> or <code class="systemitem">SCP</code>. For more information on how to configure <code class="systemitem">SCP</code>, refer to <a class="xref" href="#s2-ssh-clients-scp" title="9.3.2. Using the scp Utility">Section 9.3.2, “Using the <code class="command">scp</code> Utility”</a>.
+ </div><div class="para">
+ For security reasons, make sure that uploads can only be performed by a specific user and with a password. The rest of the document assumes that the username used for uploads is <code class="systemitem">USERNAME</code> and the password is <code class="literal">PASSWORD</code>. If you do not already have a suitable username which can be used to perform uploads under, you may use the <code class="systemitem">abrt</code> user which already exists on every system where <span class="application"><strong>ABRT</strong></span> is installed.
+ </div><div class="para">
+ It is advisable to check whether your upload method works. For more information, refer to <a class="xref" href="#testing-upload-method" title="21.7.2. Testing the Upload Method">Section 21.7.2, “Testing the Upload Method”</a>.
+ </div></li><li class="listitem"><div class="para">
+ It is advisable to check and modify the following parameters if needed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="parameter"><code>MaxCrashReportsSize</code></em> directive (in <code class="filename">/etc/abrt/abrt.conf</code>) needs to be set to a larger value if the expected volume of crash data is larger than the default <code class="constant">1000</code> MB.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="parameter"><code>ProcessUnpackaged</code></em> directive (in <code class="filename">/etc/abrt/abrt.conf</code>) needs to be set to <em class="replaceable"><code>yes</code></em> and the <em class="parameter"><code>BacktraceRemotes</code></em> (in <code class="filename">/etc/abrt/plugins/CCpp.conf</code>) needs to be set to <em class="replaceable"><code>no</code></em> if the client system and the server system have significantly different sets of installed packages.
+ </div></li></ul></div></li></ul></div></li><li class="listitem"><div class="para">
+ Complete the following steps on every client system which will use the central management method:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Modify the <code class="filename">/etc/abrt/plugins/ReportUploader.conf</code> configuration file so that the <span class="application"><strong>ReportUploader</strong></span> plugin knows where to copy the saved crash reports in the following way:
+<pre class="screen">
+Enabled = yes
+Upload = yes
+URL = ftp://USERNAME:PASSWORD@SERVERNAME/var/spool/abrt-upload/
+</pre>
+
+ </div></li><li class="listitem"><div class="para">
+ To automatically send the crash reports to the server system immediately after the crash occurs, is detected, and saved, set the <code class="varname">[ ActionsAndReporters ]</code> directive in the <code class="filename">/etc/abrt/abrt.conf</code> configuration file to the following:
+<pre class="screen">
+ActionsAndReporters = ReportUploader
+</pre>
+
+ </div></li><li class="listitem"><div class="para">
+ # Alternatively, if user interaction is required before the crash dump is sent to the server system, set the <em class="parameter"><code>ReportUploader</code></em> to be a reporter plugin for a specific crash type in the <code class="literal">[ AnalyzerActionsAndReporters ]</code> section of the <code class="filename">/etc/abrt/abrt.conf</code> configuration file. The user will be required to run <span class="application"><strong>abrt-cli</strong></span> or <span class="application"><strong>abrt-gui</strong></span> and instruct the <code class="systemitem">abrtd</code> daemon to report the crash and send it to the server system. For example, if you want all crash types to use this method, edit the <code class="literal">[ AnalyzerActionsAndReporters ]</code> section in your <code class="filename">/etc/abrt/abrt.conf</code> configuration file in the following way:
+ </div><pre class="screen">
+Kerneloops = ReportUploader
+CCpp = ReportUploader
+Python = ReportUploader
+</pre></li></ul></div></li></ol></div><div class="section" title="21.7.1. Testing ABRT's Crash Detection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id740993">21.7.1. Testing ABRT's Crash Detection</h3></div></div></div><div class="para">
+ After completing all the steps of the configuration process, the basic setup is finished. To test that this setup works properly use the <code class="command">kill -s SEGV <em class="replaceable"><code>PID</code></em> </code> command to terminate a process on a client system. For example, start a <code class="systemitem">sleep</code> process and terminate it with the <code class="command">kill</code> command in the following way:
+<pre class="screen">
+~]$ sleep 100 &
+[1] 2823
+~]$ kill -s SEGV 2823
+</pre>
+ <span class="application"><strong>ABRT</strong></span> should detect a crash shortly after executing the <code class="command">kill</code> command. Check that the crash was detected by <span class="application"><strong>ABRT</strong></span> on the client system (this can be checked by examining the appropriate syslog file, by running the <code class="command">abrt-cli --list --full</code> command, or by examining the crash dump created in the <code class="filename">/var/spool/abrt</code> directory), copied to the server system, unpacked on the server system and can be seen and acted upon using <code class="command">abrt-cli</code> or <code class="command">abrt-gui</code> on the server system.
+ </div></div><div class="section" title="21.7.2. Testing the Upload Method" id="testing-upload-method"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="testing-upload-method">21.7.2. Testing the Upload Method</h3></div></div></div><div class="para">
+ Test your upload method from a client system to ensure that it works. For example, upload a file using the interactive <code class="systemitem">FTP</code> client:
+ </div><pre class="screen">
+~]$ ftp
+ftp> open SERVERNAME
+Name: USERNAME
+Password: PASSWORD
+ftp> cd /var/spool/abrt-upload
+250 Operation successful
+ftp> put TESTFILE
+ftp> quit
+</pre><div class="para">
+ Check whether <code class="filename">TESTFILE</code> appeared in the correct directory on the server system.
+ </div></div></div></div></div><div class="part" title="Part V. Kernel, Module and Driver Configuration" id="pt-kernel-configuration"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part V. Kernel, Module and Driver Configuration</h1></div></div></div><div class="partintro" title="Kernel, Module and Driver Configuration" id="id709584"><div></div><div class="para">
+ System administrators can learn about and customize their kernels. Fedora contains kernel tools to assist administrators with their customizations.
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="#ch-Working_with_Kernel_Modules">22. Working with Kernel Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="#sec-Loading_a_Module">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="#sec-Unloading_a_Module">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="#sec-Setting_Module_Parameters">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="#sec-Persistent_Module_Loading">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#sec-Specific_Kernel_Module_Capabilities">22.7. Specific Kernel Module Capabilit
ies</a></span></dt><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">22.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Manually_Upgrading_the_Kernel">23. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kernel-packages">23.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">23.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">23.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">23.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image">23.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">23.6. Verifying the Boot Loader</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-kdum
p">24. The <code class="systemitem">kdump</code> Crash Recovery Service</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kdump-configuration">24.1. Configuring the <code class="systemitem">kdump</code> Service</a></span></dt><dt><span class="section"><a href="#s1-kdump-crash">24.2. Analyzing the Core Dump</a></span></dt><dt><span class="section"><a href="#s1-kdump-resources">24.3. Additional Resources</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" title="Chapter 22. Working with Kernel Modules" id="ch-Working_with_Kernel_Modules" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 22. Working with Kernel Modules</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</a></
span></dt><dt><span class="section"><a href="#sec-Loading_a_Module">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="#sec-Unloading_a_Module">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="#sec-Setting_Module_Parameters">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="#sec-Persistent_Module_Loading">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#sec-Specific_Kernel_Module_Capabilities">22.7. Specific Kernel Module Capabilities</a></span></dt><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">22.8. Additional Resources</a></span></dt></dl></div><a id="id795507" class="indexterm"></a><a id="id583370" class="indexterm"></a><a id="id1338763" class="indexterm"></a><div class="para">
+ The Linux kernel is modular, which means it can extend its capabilities through the use of dynamically-loaded <em class="firstterm">kernel modules</em>. A Kernel module can provide:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ a device driver which adds support for new hardware; or,
+ </div></li><li class="listitem"><div class="para">
+ support for a file system such as <code class="systemitem">btrfs</code> or<code class="systemitem">NFS</code>.
+ </div></li></ul></div><div class="para">
+ Like the kernel itself, modules can take parameters that customize their behavior, though the default parameters work well in most cases. User-space tools can list the modules currently loaded into a running kernel; query all available modules for available parameters and module-specific information; and load or unload (remove) modules dynamically into or from a running kernel. Many of these utilities, which are provided by the <span class="package">module-init-tools</span> package, take module dependencies into account when performing operations so that manual dependency-tracking is rarely necessary.
+ </div><div class="para">
+ On modern systems, kernel modules are automatically loaded by various mechanisms when the conditions call for it. However, there are occasions when it is necessary to load and/or unload modules manually, such as when a module provides optional functionality, one module should be preferred over another although either could provide basic functionality, or when a module is misbehaving, among other situations.
+ </div><div class="para">
+ This chapter explains how to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ use the user-space <span class="package">module-init-tools</span> package to display, query, load and unload kernel modules and their dependencies;
+ </div></li><li class="listitem"><div class="para">
+ set module parameters both dynamically on the command line and permanently so that you can customize the behavior of your kernel modules; and,
+ </div></li><li class="listitem"><div class="para">
+ load modules at boot time.
+ </div></li></ul></div><div class="note" title="Note: Installing the module-init-tools package"><div class="admonition_header"><h2>Note: Installing the module-init-tools package</h2></div><div class="admonition"><div class="para">
+ In order to use the kernel module utilities described in this chapter, first ensure the module-init-tools package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install module-init-tools</code>
+</pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="section" title="22.1. Listing Currently-Loaded Modules" id="sec-Listing_Currently-Loaded_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</h2></div></div></div><a id="id672224" class="indexterm"></a><a id="id1624249" class="indexterm"></a><a id="id1050773" class="indexterm"></a><div class="para">
+ You can list all kernel modules that are currently loaded into the kernel by running the <code class="command">lsmod</code> command:
+ </div><pre class="screen">
+~]$ <code class="command">lsmod</code>
+Module Size Used by
+xfs 803635 1
+exportfs 3424 1 xfs
+vfat 8216 1
+fat 43410 1 vfat
+tun 13014 2
+fuse 54749 2
+ip6table_filter 2743 0
+ip6_tables 16558 1 ip6table_filter
+ebtable_nat 1895 0
+ebtables 15186 1 ebtable_nat
+ipt_MASQUERADE 2208 6
+iptable_nat 5420 1
+nf_nat 19059 2 ipt_MASQUERADE,iptable_nat
+rfcomm 65122 4
+ipv6 267017 33
+sco 16204 2
+bridge 45753 0
+stp 1887 1 bridge
+llc 4557 2 bridge,stp
+bnep 15121 2
+l2cap 45185 16 rfcomm,bnep
+cpufreq_ondemand 8420 2
+acpi_cpufreq 7493 1
+freq_table 3851 2 cpufreq_ondemand,acpi_cpufreq
+usb_storage 44536 1
+sha256_generic 10023 2
+aes_x86_64 7654 5
+aes_generic 27012 1 aes_x86_64
+cbc 2793 1
+dm_crypt 10930 1
+kvm_intel 40311 0
+kvm 253162 1 kvm_intel
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em>
+</pre><div class="para">
+ Each row of <code class="command">lsmod</code> output specifies:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ the name of a kernel module currently loaded in memory;
+ </div></li><li class="listitem"><div class="para">
+ the amount of memory it uses; and,
+ </div></li><li class="listitem"><div class="para">
+ the sum total of processes that are using the module and other modules which depend on it, followed by a list of the names of those modules, if there are any. Using this list, you can first unload all the modules depending the module you want to unload. For more information, refer to <a class="xref" href="#sec-Unloading_a_Module" title="22.4. Unloading a Module">Section 22.4, “Unloading a Module”</a>.
+ </div></li></ul></div><a id="id639147" class="indexterm"></a><div class="para">
+ Finally, note that <code class="command">lsmod</code> output is less verbose and considerably easier to read than the content of the <code class="filename">/proc/modules</code> pseudo-file.
+ </div></div><div class="section" title="22.2. Displaying Information About a Module" id="sec-Displaying_Information_About_a_Module"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</h2></div></div></div><a id="id704234" class="indexterm"></a><a id="id704250" class="indexterm"></a><a id="id704270" class="indexterm"></a><div class="para">
+ You can display detailed information about a kernel module by running the <code class="command">modinfo <em class="replaceable"><code><module_name></code></em> </code> command.
+ </div><div class="note" title="Module names do not end in .ko" id="note-Module_names_do_not_end_in_.ko"><div class="admonition_header"><h2>Module names do not end in .ko</h2></div><div class="admonition"><div class="para">
+ When entering the name of a kernel module as an argument to one of the <span class="package">module-init-tools</span> utilities, do not append a <code class="filename">.ko</code> extension to the end of the name. Kernel module names do not have extensions: their corresponding files do.
+ </div></div></div><div class="para">
+ For example, to display information about the <code class="systemitem">e1000e</code> module, which is the Intel PRO/1000 network driver, run:
+ </div><div class="example" title="Example 22.1. Listing information about a kernel module with lsmod" id="ex-Listing_information_about_a_kernel_module_with_lsmod"><h6>Example 22.1. Listing information about a kernel module with lsmod</h6><div class="example-contents"><pre class="screen">~]# <code class="command">modinfo e1000e</code>
+filename: /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/net/e1000e/e1000e.ko
+version: 1.2.7-k2
+license: GPL
+description: Intel(R) PRO/1000 Network Driver
+author: Intel Corporation, <linux.nics at intel.com>
+srcversion: 93CB73D3995B501872B2982
+alias: pci:v00008086d00001503sv*sd*bc*sc*i*
+alias: pci:v00008086d00001502sv*sd*bc*sc*i*
+<em class="lineannotation"><span class="lineannotation">[some <code class="literal">alias</code> lines omitted]</span></em>
+alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
+depends:
+vermagic: 2.6.32-71.el6.x86_64 SMP mod_unload modversions
+parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
+parm: TxIntDelay:Transmit Interrupt Delay (array of int)
+parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
+parm: RxIntDelay:Receive Interrupt Delay (array of int)
+parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
+parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
+parm: IntMode:Interrupt Mode (array of int)
+parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
+parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
+parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to corrupted NVM] (array of int)
+parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)
+parm: EEE:Enable/disable on parts that support the feature (array of int)</pre></div></div><br class="example-break" /><div class="variablelist"><div class="para">
+ Here are descriptions of a few of the fields in <code class="command">modinfo</code> output:
+ </div><dl><dt class="varlistentry"><span class="term">filename</span></dt><dd><div class="para">
+ The absolute path to the <code class="filename">.ko</code> kernel object file. You can use <code class="command">modinfo -n</code> as a shorcut command for printing only the <code class="computeroutput">filename</code> field.
+ </div></dd><dt class="varlistentry"><span class="term">description</span></dt><dd><div class="para">
+ A short description of the module. You can use <code class="command">modinfo -d</code> as a shortcut command for printing only the description field.
+ </div></dd><dt class="varlistentry"><span class="term">alias</span></dt><dd><div class="para">
+ The <code class="computeroutput">alias</code> field appears as many times as there are aliases for a module, or is omitted entirely if there are none.
+ </div></dd><dt class="varlistentry"><span class="term">depends</span></dt><dd><div class="para">
+ This field contains a comma-separated list of all the modules this module depends on.
+ </div><div class="note" title="Note" id="note-Omitted_depends_field"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If a module has no dependencies, the <code class="computeroutput">depends</code> field may be omitted from the output.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">parm</span></dt><dd><div class="para">
+ Each <code class="computeroutput">parm</code> field presents one module parameter in the form <code class="computeroutput"><em class="replaceable"><code>parameter_name</code></em>:<em class="replaceable"><code>description</code></em></code>, where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="replaceable"><code>parameter_name</code></em> is the exact syntax you should use when using it as a module parameter on the command line, or in an option line in a <code class="filename">.conf</code> file in the <code class="filename">/etc/modprobe.d/</code> directory; and,
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>description</code></em> is a brief explanation of what the parameter does, along with an expectation for the type of value the parameter accepts (such as <span class="type">int</span>, <span class="type">unit</span> or <span class="type">array of int</span>) in parentheses.
+ </div></li></ul></div><div class="para">
+ You can list all parameters that the module supports by using the <code class="option">-p</code> option. However, because useful value type information is omitted from <code class="command">modinfo -p</code> output, it is more useful to run:
+ </div><pre class="screen">~]# <code class="command">modinfo e1000e |grep "^parm" |sort</code>
+parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
+parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)
+parm: EEE:Enable/disable on parts that support the feature (array of int)
+parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
+parm: IntMode:Interrupt Mode (array of int)
+parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
+parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
+parm: RxIntDelay:Receive Interrupt Delay (array of int)
+parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
+parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
+parm: TxIntDelay:Transmit Interrupt Delay (array of int)
+parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to corrupted NVM] (array of int)</pre></dd></dl></div></div><div class="section" title="22.3. Loading a Module" id="sec-Loading_a_Module"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Loading_a_Module">22.3. Loading a Module</h2></div></div></div><a id="id1748055" class="indexterm"></a><a id="id1748071" class="indexterm"></a><a id="id617826" class="indexterm"></a><div class="para">
+ To load a kernel module, run <code class="command">modprobe <em class="replaceable"><code><module_name></code></em> </code> as root. For example, to load the <code class="systemitem">wacom</code> module, run:
+ </div><pre class="screen">~]# <code class="command">modprobe wacom</code>
+</pre><a id="id617867" class="indexterm"></a><div class="para">
+ By default, <code class="command">modprobe</code> attempts to load the module from <code class="filename">/lib/modules/<em class="replaceable"><code><kernel_version></code></em>/kernel/drivers/</code>. In this directory, each type of module has its own subdirectory, such as <code class="filename">net/</code> and <code class="filename">scsi/</code>, for network and SCSI interface drivers respectively.
+ </div><div class="para">
+ Some modules have dependencies, which are other kernel modules that must be loaded before the module in question can be loaded. The <code class="command">modprobe</code> command always takes dependencies into account when performing operations. When you ask <code class="command">modprobe</code> to load a specific kernel module, it first examines the dependencies of that module, if there are any, and loads them if they are not already loaded into the kernel. <code class="command">modprobe</code> resolves dependencies recursively: it will load all dependencies of dependencies, and so on, if necessary, thus ensuring that all dependencies are always met.
+ </div><div class="para">
+ You can use the <code class="option">-v</code> (i.e. <code class="option">--verbose</code>) option to cause <code class="command">modprobe</code> to display detailed information about what it is doing, which may include loading module dependencies. Here's an example of loading the <code class="systemitem">Fibre Channel over Ethernet</code> module verbosely:
+ </div><div class="example" title="Example 22.2. modprobe -v shows module dependencies as they are loaded" id="ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded"><h6>Example 22.2. modprobe -v shows module dependencies as they are loaded</h6><div class="example-contents"><pre class="screen">~]# <code class="command">modprobe -v fcoe</code>
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_tgt.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/libfc/libfc.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</pre></div></div><br class="example-break" /><div class="para">
+ <a class="xref" href="#ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded" title="Example 22.2. modprobe -v shows module dependencies as they are loaded">Example 22.2, “modprobe -v shows module dependencies as they are loaded”</a> shows that <code class="command">modprobe</code> loaded the <code class="systemitem">scsi_tgt</code>, <code class="systemitem">scsi_transport_fc</code>, <code class="systemitem">libfc</code> and <code class="systemitem">libfcoe</code> modules as dependencies before finally loading <code class="systemitem">fcoe</code>. Also note that <code class="command">modprobe</code> used the more <span class="quote">“<span class="quote">primitive</span>”</span> <code class="command">insmod</code> command to insert the modules into the running kernel.
+ </div><a id="id805498" class="indexterm"></a><a id="id805518" class="indexterm"></a><div class="important" title="Always use modprobe instead of insmod!" id="important-Always_use_modprobe_instead_of_insmod"><div class="admonition_header"><h2>Always use modprobe instead of insmod!</h2></div><div class="admonition"><div class="para">
+ Although the <code class="command">insmod</code> command can also be used to load kernel modules, it does not resolve dependencies. Because of this, you should <span class="emphasis"><em>always</em></span> load modules using <code class="command">modprobe</code> instead.
+ </div></div></div></div><div class="section" title="22.4. Unloading a Module" id="sec-Unloading_a_Module"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Unloading_a_Module">22.4. Unloading a Module</h2></div></div></div><a id="id668696" class="indexterm"></a><a id="id668708" class="indexterm"></a><a id="id802374" class="indexterm"></a><div class="para">
+ You can unload a kernel module by running <code class="command">modprobe -r <em class="replaceable"><code><module_name></code></em> </code> as root. For example, assuming that the <code class="systemitem">wacom</code> module is already loaded into the kernel, you can unload it by running:
+ </div><pre class="screen">~]# <code class="command">modprobe -r wacom</code>
+</pre><div class="para">
+ However, this command will fail if a process is using:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ the <code class="systemitem">wacom</code> module,
+ </div></li><li class="listitem"><div class="para">
+ a module that <code class="systemitem">wacom</code> directly depends on, or,
+ </div></li><li class="listitem"><div class="para">
+ any module that <code class="systemitem">wacom</code>—through the dependency tree—depends on indirectly.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref" href="#sec-Listing_Currently-Loaded_Modules" title="22.1. Listing Currently-Loaded Modules">Section 22.1, “Listing Currently-Loaded Modules”</a> for more information about using <code class="command">lsmod</code> to obtain the names of the modules which are preventing you from unloading a certain module.
+ </div><div class="para">
+ For example, if you want to unload the <code class="systemitem">firewire_ohci</code> module because (because you believe there is a bug in it that is affecting system stability, for example), your terminal session might look similar to this:
+ </div><pre class="screen">~]# <code class="command">modinfo -F depends firewire_ohci</code>
+depends: firewire-core
+~]# <code class="command">modinfo -F depends firewire_core</code>
+depends: crc-itu-t
+~]# <code class="command">modinfo -F depends crc-itu-t</code>
+depends:</pre><div class="para">
+ You have figured out the dependency tree (which does not branch in this example) for the loaded Firewire modules: <code class="systemitem">firewire_ohci</code> depends on <code class="systemitem">firewire_core</code>, which itself depends on <code class="systemitem">crc-itu-t</code>.
+ </div><div class="para">
+ You can unload <code class="systemitem">firewire_ohci</code> using the <code class="command">modprobe -v -r <em class="replaceable"><code><module_name></code></em> </code> command, where <code class="option">-r</code> is short for <code class="option">--remove</code> and <code class="option">-v</code> for <code class="option">--verbose</code>:
+ </div><pre class="screen">~]# <code class="command">modprobe -r -v firewire_ohci</code>
+rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/firewire/firewire-ohci.ko
+rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/firewire/firewire-core.ko
+rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/lib/crc-itu-t.ko</pre><div class="para">
+ The output shows that modules are unloaded in the reverse order that they are loaded, given that no proceses depend on any of the modules being unloaded.
+ </div><a id="id1566650" class="indexterm"></a><a id="id1566670" class="indexterm"></a><div class="important" title="Do not use rmmod directly!" id="important-Do_not_use_rmmod_directly"><div class="admonition_header"><h2>Do not use rmmod directly!</h2></div><div class="admonition"><div class="para">
+ Although the <code class="command">rmmod</code> command can be used to unload kernel modules, it is recommended to use <code class="command">modprobe -r</code> instead.
+ </div></div></div></div><div class="section" title="22.5. Setting Module Parameters" id="sec-Setting_Module_Parameters"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Setting_Module_Parameters">22.5. Setting Module Parameters</h2></div></div></div><a id="id482656" class="indexterm"></a><a id="id482668" class="indexterm"></a><div class="para">
+ Like the kernel itself, modules can also take parameters that change their behavior. Most of the time, the default ones work well, but occasionally it is necessary or desirable to set custom parameters for a module. Because parameters cannot be dynamically set for a module that is already loaded into a running kernel, there are two different methods for setting them.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ You can unload all dependencies of the module you want to set parameters for, unload the module using <code class="command">modprobe -r</code>, and then load it with <code class="command">modprobe</code> along with a list of customized parameters. This method is often used when the module does not have many dependencies, or to test different combinations of parameters without making them persistent, and is the method covered in this section.
+ </div></li><li class="listitem"><div class="para">
+ Alternatively, you can list the new parameters in an existing or newly-created file in the <code class="filename">/etc/modprobe.d/</code> directory. This method makes the module parameters persistent by ensuring that they are set each time the module is loaded, such as after every reboot or <code class="command">modprobe</code> command. This method is covered in <a class="xref" href="#sec-Persistent_Module_Loading" title="22.6. Persistent Module Loading">Section 22.6, “Persistent Module Loading”</a>, though the following information is a prerequisite.
+ </div></li></ol></div><div class="para">
+ You can use <code class="command">modprobe</code> to load a kernel module with custom parameters using the following command line format:
+ </div><div class="example" title="Example 22.3. Supplying optional parameters when loading a kernel module" id="ex-Supplying_optional_parameters_when_loading_a_kernel_module"><h6>Example 22.3. Supplying optional parameters when loading a kernel module</h6><div class="example-contents"><pre class="screen">~]# <code class="command">modprobe <em class="replaceable"><code><module_name></code></em> [<span class="optional"><em class="replaceable"><code>parameter</code></em>=<em class="replaceable"><code>value</code></em></span>] </code>
+</pre></div></div><br class="example-break" /><div class="para">
+ Here are some things to be aware of when loading a module with custom parameters on the command line:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ You can enter multiple parameters and values by separating them with spaces.
+ </div></li><li class="listitem"><div class="para">
+ Some module parameters expect a list of comma-separated values as their argument. When entering the list of values, do <span class="emphasis"><em>not</em></span> insert a space after each comma, or <code class="command">modprobe</code> will incorrectly interpret the values following spaces as additional parameters.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">modprobe</code> command silently succeeds with an exit status of <code class="constant">0</code> if:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ it successfully loads the module, <span class="emphasis"><em>or</em></span>
+ </div></li><li class="listitem"><div class="para">
+ the module is <span class="emphasis"><em>already</em></span> loaded into the kernel.
+ </div></li></ul></div><div class="para">
+ Thus, you must ensure that the module is not already loaded before attempting to load it with custom parameters. The <code class="command">modprobe</code> command does not automatically reload the module, or alert you that it is already loaded.
+ </div></li></ul></div><div class="para">
+ Here are the recommended steps for setting custom parameters and then loading a kernel module. This procedure illustrates the steps using the <code class="systemitem">e1000e</code> module, which is the network driver for Intel PRO/1000 network adapters, as an example:
+ </div><div class="procedure" title="Procedure 22.1. Loading a Kernel Module with Custom Parameters" id="proc-Loading_a_Kernel_Module_with_Custom_Parameters"><h6>Procedure 22.1. Loading a Kernel Module with Custom Parameters</h6><ol class="1"><li class="step" title="Step 1" id="proc-step1-Loading_a_Kernel_Module_with_Custom_Parameters"><div class="para">
+ First, ensure the module is not already loaded into the kernel:
+ </div><pre class="screen">~]# <code class="command">lsmod |grep e1000e</code>
+~]# </pre><div class="para">
+ Output indicates that the module is already loaded into the kernel, in which case you must first unload it before proceeding. Refer to <a class="xref" href="#sec-Unloading_a_Module" title="22.4. Unloading a Module">Section 22.4, “Unloading a Module”</a> for instructions on safely unloading it.
+ </div></li><li class="step" title="Step 2" id="proc-step2-Loading_a_Kernel_Module_with_Custom_Parameters"><div class="para">
+ Load the module and list all custom parameters after the module name. For example, if you wanted to load the Intel PRO/1000 network driver with the interrupt throttle rate set to 3000 interrupts per second for the first, second and third instances of the driver, and Energy Efficient Ethernet (EEE) turned on<sup>[<a id="footnote-Energy_Efficient_Ethernet" href="#ftn.footnote-Energy_Efficient_Ethernet" class="footnote">4</a>]</sup> , you would run, as root:
+ </div><pre class="screen">~]# <code class="command">modprobe e1000e InterruptThrottleRate=3000,3000,3000 EEE=1</code>
+</pre><div class="para">
+ This example illustrates passing multiple valued to a single parameter by separating them with commas and omitting any spaces between them.
+ </div></li></ol></div></div><div class="section" title="22.6. Persistent Module Loading" id="sec-Persistent_Module_Loading"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Persistent_Module_Loading">22.6. Persistent Module Loading</h2></div></div></div><a id="id738939" class="indexterm"></a><a id="id739535" class="indexterm"></a><div class="para">
+ As shown in <a class="xref" href="#ex-Listing_information_about_a_kernel_module_with_lsmod" title="Example 22.1. Listing information about a kernel module with lsmod">Example 22.1, “Listing information about a kernel module with lsmod”</a>, many kernel modules are loaded automatically at boot time. You can specify additional modules to be loaded by creating a new <code class="filename"><em class="replaceable"><code><file_name></code></em>.modules</code> file in the <code class="filename">/etc/sysconfig/modules/</code> directory, where <em class="replaceable"><code><file_name></code></em> is any descriptive name of your choice. Your <code class="filename"><em class="replaceable"><code><file_name></code></em>.modules</code> files are treated by the system startup scripts as shell scripts, and as such should begin with an <em class="firstterm">interpreter directive</em> (also called a <span class="quote">“<span class="quote">bang line</span>”</sp
an>) as their first line:
+ </div><div class="example" title="Example 22.4. First line of a file_name.modules file" id="ex-First_line_of_a_file_name.modules_file"><h6>Example 22.4. First line of a <em class="replaceable"><code>file_name</code></em>.modules file</h6><div class="example-contents"><pre class="screen">#!/bin/sh</pre></div></div><br class="example-break" /><div class="para">
+ Additionally, the <code class="filename"><em class="replaceable"><code><file_name></code></em>.modules</code> file should be executable. You can make it executable by running:
+ </div><pre class="screen">modules]# <code class="command">chmod +x <em class="replaceable"><code><file_name></code></em>.modules</code>
+</pre><div class="para">
+ For example, the following <code class="filename">bluez-uinput.modules</code> script loads the <code class="systemitem">uinput</code> module:
+ </div><div class="example" title="Example 22.5. /etc/sysconfig/modules/bluez-uinput.modules" id="ex-bluez-uinput.modules"><h6>Example 22.5. /etc/sysconfig/modules/bluez-uinput.modules</h6><div class="example-contents"><pre class="programlisting"><span class="perl_Comment">#!/bin/sh</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+<span class="perl_Keyword">if</span><span class="perl_Reserved"> [</span> ! -c /dev/input/uinput<span class="perl_Reserved"> ]</span> ; <span class="perl_Keyword">then</span>
+ <span class="perl_Reserved">exec</span> /sbin/modprobe uinput <span class="perl_Operator">></span>/dev/null <span class="perl_Operator">2>&1</span>
+<span class="perl_Keyword">fi</span></pre><div class="para">
+ The <code class="literal">if</code>-conditional statement on the third line ensures that the <code class="filename">/dev/input/uinput</code> file does <span class="emphasis"><em>not</em></span> already exist (the <code class="literal">!</code> symbol negates the condition), and, if that is the case, loads the <code class="systemitem">uinput</code> module by calling <code class="command">exec /sbin/modprobe uinput</code>. Note that the <code class="systemitem">uinput</code> module creates the <code class="filename">/dev/input/uinput</code> file, so testing to see if that file exists serves as verification of whether the <code class="systemitem">uinput</code> module is loaded into the kernel.
+ </div><div class="para">
+ The following <code class="command">>/dev/null 2>&1</code> clause at the end of that line simply redirects any output to <code class="filename">/dev/null</code> so that the <code class="command">modprobe</code> command remains quiet.
+ </div></div></div><br class="example-break" /></div><div class="section" title="22.7. Specific Kernel Module Capabilities" id="sec-Specific_Kernel_Module_Capabilities"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Specific_Kernel_Module_Capabilities">22.7. Specific Kernel Module Capabilities</h2></div></div></div><div class="para">
+ This section explains how to enable specific kernel capabilities using various kernel modules.
+ </div><div class="section" title="22.7.1. Using Multiple Ethernet Cards" id="sec-Using_Multiple_Ethernet_Cards"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Using_Multiple_Ethernet_Cards">22.7.1. Using Multiple Ethernet Cards</h3></div></div></div><a id="id645772" class="indexterm"></a><div class="para">
+ It is possible to use multiple Ethernet cards on a single machine. For each card there must be an <code class="command">alias</code> and, possibly, <code class="command">options</code> lines for each card in a user-created <code class="filename"><em class="replaceable"><code><module_name></code></em>.conf</code> file in the <code class="filename">/etc/modprobe.d/</code> directory.
+ </div><div class="para">
+ For additional information about using multiple Ethernet cards, refer to the <em class="citetitle">Linux Ethernet-HOWTO</em> online at <a href="http://www.redhat.com/mirrors/LDP/HOWTO/Ethernet-HOWTO.html">http://www.redhat.com/mirrors/LDP/HOWTO/Ethernet-HOWTO.html</a>.
+ </div></div><div class="section" title="22.7.2. Using Channel Bonding" id="sec-Using_Channel_Bonding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Using_Channel_Bonding">22.7.2. Using Channel Bonding</h3></div></div></div><a id="id523537" class="indexterm"></a><a id="id523553" class="indexterm"></a><a id="id523565" class="indexterm"></a><a id="id537224" class="indexterm"></a><a id="id537236" class="indexterm"></a><div class="para">
+ Fedora allows administrators to bind NICs together into a single channel using the <code class="filename">bonding</code> kernel module and a special network interface, called a <em class="firstterm">channel bonding interface</em>. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
+ </div><a id="id537261" class="indexterm"></a><a id="id537273" class="indexterm"></a><div class="para">
+ To channel bond multiple network interfaces, the administrator must perform the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ As root, create a new file named <code class="filename"><em class="replaceable"><code><bonding></code></em>.conf</code> in the <code class="filename">/etc/modprobe.d/</code> directory. Note that you can name this file anything you like as long as it ends with a <code class="filename">.conf</code> extension. Insert the following line in this new file:
+ </div><pre class="screen">alias bond<em class="replaceable"><code><N></code></em> bonding</pre><div class="para">
+ Replace <em class="replaceable"><code><N></code></em> with the interface number, such as <code class="command">0</code>. For each configured channel bonding interface, there must be a corresponding entry in your new <code class="filename">/etc/modprobe.d/<em class="replaceable"><code><bonding></code></em>.conf</code> file.
+ </div></li><li class="listitem"><div class="para">
+ Configure a channel bonding interface as outlined in <a class="xref" href="#s2-networkscripts-interfaces-chan" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a>.
+ </div></li><li class="listitem"><div class="para">
+ To enhance performance, adjust available module options to ascertain what combination works best. Pay particular attention to the <code class="command">miimon</code> or <code class="command">arp_interval</code> and the <code class="command">arp_ip_target</code> parameters. Refer to <a class="xref" href="#s3-modules-bonding-directives" title="22.7.2.1. Bonding Module Directives">Section 22.7.2.1, “Bonding Module Directives”</a> for a list of available options and how to quickly determine the best ones for your bonded interface.
+ </div></li></ol></div><div class="section" title="22.7.2.1. Bonding Module Directives" id="s3-modules-bonding-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-modules-bonding-directives">22.7.2.1. Bonding Module Directives</h4></div></div></div><a id="id617922" class="indexterm"></a><a id="id617938" class="indexterm"></a><a id="id617954" class="indexterm"></a><div class="para">
+ It is a good idea to test which channel bonding module parameters work best for your bonded interfaces before adding them to the <em class="parameter"><code>BONDING_OPTS="<em class="replaceable"><code><bonding parameters></code></em>"</code></em> directive in your bonding interface configuration file (<code class="filename">ifcfg-bond0</code> for example). Parameters to bonded interfaces can be configured without unloading (and reloading) the bonding module by manipulating files in the <code class="systemitem">sysfs</code> file system.
+ </div><div class="para">
+ <code class="systemitem">sysfs</code> is a virtual file system that represents kernel objects as directories, files and symbolic links. <code class="systemitem">sysfs</code> can be used to query for information about kernel objects, and can also manipulate those objects through the use of normal file system commands. The <code class="systemitem">sysfs</code> virtual file system has a line in <code class="filename">/etc/fstab</code>, and is mounted under the <code class="filename">/sys/</code> directory. All bonding interfaces can be configured dynamically by interacting with and manipulating files under the <code class="filename">/sys/class/net/</code> directory.
+ </div><div class="para">
+ After you have created a channel bonding interface file such as <code class="filename">ifcfg-bond0</code> and inserted <em class="parameter"><code>SLAVE=yes</code></em> and <em class="parameter"><code>MASTER=bond0</code></em> directives in the configuration files for each interface bonded to bond0 following the instructions in <a class="xref" href="#s2-networkscripts-interfaces-chan" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a>, you can proceed to testing and determining the best parameters for your bonding interface.
+ </div><div class="para">
+ First, bring up the bond you created by running <code class="command">ifconfig <code class="option">bond<em class="replaceable"><code><N></code></em> </code> <code class="option">up</code> </code> as root:
+ </div><pre class="screen">~]# <code class="command">ifconfig bond0 up</code>
+</pre><div class="para">
+ If you have correctly created the <code class="filename">ifcfg-bond0</code> bonding interface file, you will be able to see <code class="computeroutput">bond0</code> listed in the output of running <code class="command">ifconfig</code> (without any options):
+ </div><pre class="screen">~]# <code class="command">ifconfig</code>
+bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
+ UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
+ RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
+eth0 Link encap:Ethernet HWaddr 52:54:00:26:9E:F1
+ inet addr:192.168.122.251 Bcast:192.168.122.255 Mask:255.255.255.0
+ inet6 addr: fe80::5054:ff:fe26:9ef1/64 Scope:Link
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:207 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:205 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:1000
+ RX bytes:70374 (68.7 KiB) TX bytes:25298 (24.7 KiB)
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em>
+</pre><div class="para">
+ To view all existing bonds, even if they are not up, run:
+ </div><pre class="screen">~]# <code class="command">cat /sys/class/net/bonding_masters</code>
+bond0</pre><div class="para">
+ You can configure each bond individually by manipulating the files located in the <code class="filename">/sys/class/net/bond<em class="replaceable"><code><N></code></em>/bonding/</code> directory. First, the bond you are configuring must be taken down:
+ </div><pre class="screen">~]# <code class="command">ifconfig bond0 down</code>
+</pre><div class="para">
+ As an example, to enable MII monitoring on bond0 with a 1 second interval, you could run (as root):
+ </div><pre class="screen">~]# <code class="command">echo 1000 > /sys/class/net/bond0/bonding/miimon</code>
+</pre><div class="para">
+ To configure bond0 for <em class="parameter"><code>balance-alb</code></em> mode, you could run either:
+ </div><pre class="screen">~]# <code class="command">echo 6 > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ ...or, using the name of the mode:
+ </div><pre class="screen">~]# <code class="command">echo balance-alb > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ After configuring some options for the bond in question, you can bring it up and test it by running <code class="command">ifconfig bond<em class="replaceable"><code><N></code></em> <code class="option">up</code> </code>. If you decide to change the options, take the interface down, modify its parameters using <code class="systemitem">sysfs</code>, bring it back up, and re-test.
+ </div><div class="para">
+ Once you have determined the best set of parameters for your bond, add those parameters as a space-separated list to the <em class="parameter"><code>BONDING_OPTS=</code></em> directive of the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond<em class="replaceable"><code><N></code></em> </code> file for the bonding interface you are configuring. Whenever that bond is brought up (for example, by the system during the boot sequence if the <em class="parameter"><code>ONBOOT=yes</code></em> directive is set), the bonding options specified in the <em class="parameter"><code>BONDING_OPTS</code></em> will take effect for that bond. For more information on configuring bonding interfaces (and <em class="parameter"><code>BONDING_OPTS</code></em>), refer to <a class="xref" href="#s2-networkscripts-interfaces-chan" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a>.
+ </div><div class="para">
+ The following list provides the names of many of the more common channel bonding parameters, along with a descriptions of what they do. For more information, refer to the brief descriptions for each <code class="computeroutput">parm</code> in <code class="command">modinfo bonding</code> output, or the exhaustive descriptions in the <code class="filename">bonding.txt</code> file in the <span class="package">kernel-doc</span> package (see <a class="xref" href="#s1-kernel-modules-additional-resources" title="22.8. Additional Resources">Section 22.8, “Additional Resources”</a>).
+ </div><div class="variablelist" title="Bonding Interface Parameters"><h6>Bonding Interface Parameters</h6><dl><dt class="varlistentry"><span class="term"> <code class="literal">arp_interval=<em class="replaceable"><code><time_in_milliseconds></code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how often ARP monitoring occurs.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div><div class="para">
+ If using this setting while in <code class="literal">mode=0</code> or <code class="literal">mode=1</code> (the two load-balancing modes), the network switch must be configured to distribute packets evenly across the NICs. For more information on how to accomplish this, refer to <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/networking/bonding.txt</code>
+ </div><div class="para">
+ The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_ip_target=<em class="replaceable"><code><ip_address></code></em>[<span class="optional">,<em class="replaceable"><code><ip_address_2></code></em>,…<em class="replaceable"><code><ip_address_16></code></em></span>] </code> </span></dt><dd><div class="para">
+ Specifies the target IP address of ARP requests when the <code class="literal">arp_interval</code> parameter is enabled. Up to 16 IP addresses can be specified in a comma separated list.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_validate=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ Validate source/distribution of ARP probes; default is <strong class="userinput"><code>none</code></strong>. Other valid values are <strong class="userinput"><code>active</code></strong>, <strong class="userinput"><code>backup</code></strong>, and <strong class="userinput"><code>all</code></strong>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">debug=<em class="replaceable"><code><number></code></em> </code> </span></dt><dd><div class="para">
+ Enables debug messages. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> — Debug messages are disabled. This is the default.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> — Debug messages are enabled.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">downdelay=<em class="replaceable"><code><time_in_milliseconds></code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait after link failure before disabling the link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term">lacp_rate=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ Specifies the rate at which link partners should transmit LACPDU packets in 802.3ad mode. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>slow</code></strong> or <strong class="userinput"><code>0</code></strong> — Default setting. This specifies that partners should transmit LACPDUs every 30 seconds.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>fast</code></strong> or <strong class="userinput"><code>1</code></strong> — Specifies that partners should transmit LACPDUs every 1 second.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">miimon=<em class="replaceable"><code><time_in_milliseconds></code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how often MII link monitoring occurs. This is useful if high availability is required because MII is used to verify that the NIC is active. To verify that the driver for a particular NIC supports the MII tool, type the following command as root:
+ </div><pre class="screen">~]# <code class="command">ethtool <em class="replaceable"><code><interface_name></code></em> | grep "Link detected:"</code>
+</pre><div class="para">
+ In this command, replace <em class="replaceable"><code><interface_name</code></em>> with the name of the device interface, such as <strong class="userinput"><code>eth0</code></strong>, not the bond interface. If MII is supported, the command returns:
+ </div><pre class="screen">Link detected: yes</pre><div class="para">
+ If using a bonded interface for high availability, the module for each NIC must support MII. Setting the value to <strong class="userinput"><code>0</code></strong> (the default), turns this feature off. When configuring this setting, a good starting point for this parameter is <strong class="userinput"><code>100</code></strong>.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">mode=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-rr</code></strong> or <strong class="userinput"><code>0</code></strong> — Sets a round-robin policy for fault tolerance and load balancing. Transmissions are received and sent out sequentially on each bonded slave interface beginning with the first one available.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>active-backup</code></strong> or <strong class="userinput"><code>1</code></strong> — Sets an active-backup policy for fault tolerance. Transmissions are received and sent out via the first available bonded slave interface. Another bonded slave interface is only used if the active bonded slave interface fails.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-xor</code></strong> or <strong class="userinput"><code>2</code></strong> — Sets an XOR (exclusive-or) policy for fault tolerance and load balancing. Using this method, the interface matches up the incoming request's MAC address with the MAC address for one of the slave NICs. Once this link is established, transmissions are sent out sequentially beginning with the first available interface.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>broadcast</code></strong> or <strong class="userinput"><code>3</code></strong> — Sets a broadcast policy for fault tolerance. All transmissions are sent on all slave interfaces.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>802.3ad</code></strong> or <strong class="userinput"><code>4</code></strong> — Sets an IEEE 802.3ad dynamic link aggregation policy. Creates aggregation groups that share the same speed and duplex settings. Transmits and receives on all slaves in the active aggregator. Requires a switch that is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-tlb</code></strong> or <strong class="userinput"><code>5</code></strong> — Sets a Transmit Load Balancing (TLB) policy for fault tolerance and load balancing. The outgoing traffic is distributed according to the current load on each slave interface. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed slave.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-alb</code></strong> or <strong class="userinput"><code>6</code></strong> — Sets an Active Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receive load balancing for IPV4 traffic. Receive load balancing is achieved through ARP negotiation.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">num_unsol_na=<em class="replaceable"><code><number></code></em> </code> </span></dt><dd><div class="para">
+ Specifies the number of unsolicited IPv6 Neighbor Advertisements to be issued after a failover event. One unsolicited NA is issued immediately after the failover.
+ </div><div class="para">
+ The valid range is <strong class="userinput"><code>0 - 255</code></strong>; the default value is <strong class="userinput"><code>1</code></strong>. This parameter affects only the active-backup mode.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary=<em class="replaceable"><code><interface_name></code></em> </code> </span></dt><dd><div class="para">
+ Specifies the interface name, such as <strong class="userinput"><code>eth0</code></strong>, of the primary device. The <code class="literal">primary</code> device is the first of the bonding interfaces to be used and is not abandoned unless it fails. This setting is particularly useful when one NIC in the bonding interface is faster and, therefore, able to handle a bigger load.
+ </div><div class="para">
+ This setting is only valid when the bonding interface is in <strong class="userinput"><code>active-backup</code></strong> mode. Refer to <code class="filename"> /usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel-version></code></em>/Documentation/networking/bonding.txt</code> for more information.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary_reselect=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ Specifies the reselection policy for the primary slave. This affects how the primary slave is chosen to become the active slave when failure of the active slave or recovery of the primary slave occurs. This parameter is designed to prevent flip-flopping between the primary slave and other slaves. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>always</code></strong> or <strong class="userinput"><code>0</code></strong> (default) — The primary slave becomes the active slave whenever it comes back up.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>better</code></strong> or <strong class="userinput"><code>1</code></strong> — The primary slave becomes the active slave when it comes back up, if the speed and duplex of the primary slave is better than the speed and duplex of the current active slave.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>failure</code></strong> or <strong class="userinput"><code>2</code></strong> — The primary slave becomes the active slave only if the current active slave fails and the primary slave is up.
+ </div></li></ul></div><div class="para">
+ The <code class="literal">primary_reselect</code> setting is ignored in two cases:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If no slaves are active, the first slave to recover is made the active slave.
+ </div></li><li class="listitem"><div class="para">
+ When initially enslaved, the primary slave is always made the active slave.
+ </div></li></ul></div><div class="para">
+ Changing the <code class="literal">primary_reselect</code> policy via <code class="systemitem">sysfs</code> will cause an immediate selection of the best active slave according to the new policy. This may or may not result in a change of the active slave, depending upon the circumstances
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">updelay=<em class="replaceable"><code><time_in_milliseconds></code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait before enabling a link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">use_carrier=<em class="replaceable"><code><number></code></em> </code> </span></dt><dd><div class="para">
+ Specifies whether or not <code class="literal">miimon</code> should use MII/ETHTOOL ioctls or <code class="function">netif_carrier_ok()</code> to determine the link state. The <code class="function">netif_carrier_ok()</code> function relies on the device driver to maintains its state with <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em> </code>; most device drivers support this function.
+ </div><div class="para">
+ The MII/ETHROOL ioctls tools utilize a deprecated calling sequence within the kernel. However, this is still configurable in case your device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em> </code>.
+ </div><div class="para">
+ Valid values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> — Default setting. Enables the use of <code class="function">netif_carrier_ok()</code>.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> — Enables the use of MII/ETHTOOL ioctls.
+ </div></li></ul></div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ If the bonding interface insists that the link is up when it should not be, it is possible that your network device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em> </code>.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">xmit_hash_policy=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ Selects the transmit hash policy used for slave selection in <strong class="userinput"><code>balance-xor</code></strong> and <strong class="userinput"><code>802.3ad</code></strong> modes. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> or <strong class="userinput"><code>layer2</code></strong> — Default setting. This parameter uses the XOR of hardware MAC addresses to generate the hash. The formula used is:
+ </div><pre class="screen">(<em class="replaceable"><code><source_MAC_address></code></em> XOR <em class="replaceable"><code><destination_MAC></code></em>) MODULO <em class="replaceable"><code><slave_count></code></em>
+</pre><div class="para">
+ This algorithhm will place all traffic to a particular network peer on the same slave, and is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> or <strong class="userinput"><code>layer3+4</code></strong> — Uses upper layer protocol information (when available) to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves.
+ </div><div class="para">
+ The formula for unfragmented TCP and UDP packets used is:
+ </div><pre class="screen">((<em class="replaceable"><code><source_port></code></em> XOR <em class="replaceable"><code><dest_port></code></em>) XOR
+ ((<em class="replaceable"><code><source_IP></code></em> XOR <em class="replaceable"><code><dest_IP></code></em>) AND <code class="constant">0xffff</code>)
+ MODULO <em class="replaceable"><code><slave_count></code></em>
+</pre><div class="para">
+ For fragmented TCP or UDP packets and all other IP protocol traffic, the source and destination port information is omitted. For non-IP traffic, the formula is the same as the <code class="command">layer2</code> transmit hash policy.
+ </div><div class="para">
+ This policy intends to mimic the behavior of certain switches; particularly, Cisco switches with PFC2 as well as some Foundry and IBM products.
+ </div><div class="para">
+ The algorithm used by this policy is not 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>2</code></strong> or <strong class="userinput"><code>layer2+3</code></strong> — Uses a combination of layer2 and layer3 protocol information to generate the hash.
+ </div><div class="para">
+ Uses XOR of hardware MAC addresses and IP addresses to generate the hash. The formula is:
+ </div><pre class="screen">(((<em class="replaceable"><code><source_IP></code></em> XOR <em class="replaceable"><code><dest_IP></code></em>) AND <code class="constant">0xffff</code>) XOR
+ ( <em class="replaceable"><code><source_MAC></code></em> XOR <em class="replaceable"><code><destination_MAC></code></em> ))
+ MODULO <em class="replaceable"><code><slave_count></code></em>
+</pre><div class="para">
+ This algorithm will place all traffic to a particular network peer on the same slave. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy.
+ </div><div class="para">
+ This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations.
+ </div><div class="para">
+ This algorithm is 802.3ad compliant.
+ </div></li></ul></div></dd></dl></div></div></div></div><div class="section" title="22.8. Additional Resources" id="s1-kernel-modules-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-modules-additional-resources">22.8. Additional Resources</h2></div></div></div><div class="para">
+ For more information on kernel modules and their utilities, refer to the following resources.
+ </div><h3>Manual Page Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man lsmod</code> — The <code class="command">lsmod</code> manual page contains usage information and explanation of all options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man modinfo</code> — The <code class="command">modinfo</code> manual page contains usage information and explanation of all options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man modprobe</code> — The <code class="command">modprobe</code> manual page contains usage information and explanation of all options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man rmmod</code> — The <code class="command">rmmod</code> manual page contains usage information and explanation of all options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ethtool</code> — The <code class="command">ethtool</code> manual page contains usage information and explanation of all options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man mii-tool</code> — The <code class="command">mii-tool</code> manual page contains usage information and explanation of all options.
+ </div></li></ul></div><h3>Installable and External Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/</code> — This directory, which is provided by the <span class="package">kernel-doc</span> package, contains information on the kernel, kernel modules, and their respective parameters. Before accessing the kernel documentation, you must run the following command as root:
+ </div><pre class="screen">~]# <code class="command">yum install kernel-doc</code>
+</pre></li><li class="listitem"><div class="para">
+ <a href="http://tldp.org/HOWTO/Module-HOWTO/">Linux Loadable Kernel Module HOWTO</a> — The <em class="citetitle">Linux Loadable Kernel Module HOWTO</em> from the Linux Documentation Project contains further information on working with kernel modules.
+ </div></li></ul></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div class="footnote" id="footnote-Energy_Efficient_Ethernet"><p><sup>[<a id="ftn.footnote-Energy_Efficient_Ethernet" href="#footnote-Energy_Efficient_Ethernet" class="para">4</a>] </sup>
+ Despite what the example might imply, Energy Efficient Ethernet is turned on by default in the <code class="systemitem">e1000e</code> driver.
+ </p></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 23. Manually Upgrading the Kernel" id="ch-Manually_Upgrading_the_Kernel" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 23. Manually Upgrading the Kernel</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-kernel-packages">23.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">23.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">23.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">23.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image">23.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">23.6. Verifying the Boot Loader</a></span></dt></dl></div><a id="id6
32292" class="indexterm"></a><a id="id448310" class="indexterm"></a><a id="id729876" class="indexterm"></a><a id="id485457" class="indexterm"></a><div class="para">
+ The Fedora kernel is custom-built by the Fedora kernel team to ensure its integrity and compatibility with supported hardware. Before Red Hat releases a kernel, it must first pass a rigorous set of quality assurance tests.
+ </div><div class="para">
+ Fedora kernels are packaged in the RPM format so that they are easy to upgrade and verify using the <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span> package managers. <span class="application"><strong>PackageKit</strong></span> automatically queries the Red Hat Network servers and informs you of packages with available updates, including kernel packages.
+ </div><div class="para">
+ This chapter is therefore <span class="emphasis"><em>only</em></span> useful for users who need to manually update a kernel package using the <code class="command">rpm</code> command instead of <code class="command">yum</code>.
+ </div><a id="id493364" class="indexterm"></a><a id="id469419" class="indexterm"></a><div class="warning" title="Use Yum to Install Kernels Whenever Possible"><div class="admonition_header"><h2>Use Yum to Install Kernels Whenever Possible</h2></div><div class="admonition"><div class="para">
+ Whenever possible, use either the <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span> package manager to install a new kernel because they always <span class="emphasis"><em>install</em></span> a new kernel instead of replacing the current one, which could potentially leave your system unable to boot.
+ </div></div></div><div class="warning" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Building a custom kernel is not supported by the Red Hat Global Services Support team, and therefore is not explored in this manual.
+ </div></div></div><a id="id631506" class="indexterm"></a><div class="para">
+ For more information on installing kernel packages with <span class="application"><strong>Yum</strong></span>, refer to <a class="xref" href="#sec-Updating_Packages" title="1.1.2. Updating Packages">Section 1.1.2, “Updating Packages”</a>.
+ </div><div class="section" title="23.1. Overview of Kernel Packages" id="s1-kernel-packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-packages">23.1. Overview of Kernel Packages</h2></div></div></div><a id="id696959" class="indexterm"></a><a id="id487668" class="indexterm"></a><a id="id487683" class="indexterm"></a><a id="id672149" class="indexterm"></a><a id="id672165" class="indexterm"></a><a id="id672180" class="indexterm"></a><a id="id672196" class="indexterm"></a><a id="id775502" class="indexterm"></a><a id="id775518" class="indexterm"></a><a id="id775534" class="indexterm"></a><a id="id775550" class="indexterm"></a><a id="id508839" class="indexterm"></a><a id="id508855" class="indexterm"></a><div class="para">
+ Fedora contains the following kernel packages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">kernel</span> — Contains the kernel for single, multicore and multiprocessor systems.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-debug</span> — Contains a kernel with numerous debugging options enabled for kernel diagnosis, at the expense of reduced performance.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-devel</span> — Contains the kernel headers and makefiles sufficient to build modules against the <span class="package">kernel</span> package.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-debug-devel</span> — Contains the development version of the kernel with numerous debugging options enabled for kernel diagnosis, at the expense of reduced performance.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-doc</span> — Documentation files from the kernel source. Various portions of the Linux kernel and the device drivers shipped with it are documented in these files. Installation of this package provides a reference to the options that can be passed to Linux kernel modules at load time.
+ </div><div class="para">
+ By default, these files are placed in the <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-headers</span> — Includes the C header files that specify the interface between the Linux kernel and user-space libraries and programs. The header files define structures and constants that are needed for building most standard programs.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-firmware</span> — Contains all of the firmware files that are required by various devices to operate.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">perf</span> — This package contains supporting scripts and documentation for the <span class="application"><strong>perf</strong></span> tool shipped in each kernel image subpackage.
+ </div></li></ul></div></div><div class="section" title="23.2. Preparing to Upgrade" id="s1-kernel-preparing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-preparing">23.2. Preparing to Upgrade</h2></div></div></div><a id="id796950" class="indexterm"></a><a id="id796960" class="indexterm"></a><a id="id796976" class="indexterm"></a><a id="id1053740" class="indexterm"></a><div class="para">
+ Before upgrading the kernel, it is recommended that you take some precautionary steps.
+ </div><div class="para">
+ First, ensure that working boot media exists for the system in case a problem occurs. If the boot loader is not configured properly to boot the new kernel, the system cannot be booted into Fedora without working boot media.
+ </div><div class="para">
+ USB media often comes in the form of flash devices sometimes called <em class="firstterm">pen drives</em>, <em class="firstterm">thumb disks</em>, or <em class="firstterm">keys</em>, or as an externally-connected hard disk device. Almost all media of this type is formatted as a <code class="systemitem">VFAT</code> file system. You can create bootable USB media on media formatted as <code class="systemitem">ext2</code>, <code class="systemitem">ext3</code>, or <code class="systemitem">VFAT</code>.
+ </div><div class="para">
+ You can transfer a distribution image file or a minimal boot media image file to USB media. Make sure that sufficient free space is available on the device. Around <code class="constant">4 GB</code> is required for a distribution DVD image, around <code class="constant">700 MB</code> for a distribution CD image, or around <code class="constant">10 MB</code> for a minimal boot media image.
+ </div><div class="para">
+ You must have a copy of the <code class="filename">boot.iso</code> file from a Fedora installation DVD, or installation CD-ROM#1, and you need a USB storage device formatted with the <code class="systemitem">VFAT</code> file system and around <code class="constant">16 MB</code> of free space. The following procedure will not affect existing files on the USB storage device unless they have the same path names as the files that you copy onto it. To create USB boot media, perform the following commands as the root user:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Install the <span class="application"><strong>SYSLINUX</strong></span> bootloader on the USB storage device:
+ </div><pre class="screen">~]# <code class="command">syslinux /dev/<em class="replaceable"><code>sdX1</code></em> </code>
+</pre><div class="para">
+ ...where <em class="replaceable"><code>sdX</code></em> is the device name.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Create mount points for <code class="filename">boot.iso</code> and the USB storage device:
+ </div><pre class="screen">~]# <code class="command">mkdir /mnt/isoboot /mnt/diskboot</code>
+</pre></li><li class="step" title="Step 3"><div class="para">
+ Mount <code class="filename">boot.iso</code>:
+ </div><pre class="screen">~]# <code class="command">mount -o loop boot.iso /mnt/isoboot</code>
+</pre></li><li class="step" title="Step 4"><div class="para">
+ Mount the USB storage device:
+ </div><pre class="screen">~]# <code class="command">mount /dev/<em class="replaceable"><code><sdX1></code></em> /mnt/diskboot</code>
+</pre></li><li class="step" title="Step 5"><div class="para">
+ Copy the <span class="application"><strong>ISOLINUX</strong></span> files from the <code class="filename">boot.iso</code> to the USB storage device:
+ </div><pre class="screen">~]# <code class="command">cp /mnt/isoboot/isolinux/* /mnt/diskboot</code>
+</pre></li><li class="step" title="Step 6"><div class="para">
+ Use the <code class="filename">isolinux.cfg</code> file from <code class="filename">boot.iso</code> as the <code class="filename">syslinux.cfg</code> file for the USB device:
+ </div><pre class="screen">~]# <code class="command">grep -v local /mnt/isoboot/isolinux/isolinux.cfg > /mnt/diskboot/syslinux.cfg</code>
+</pre></li><li class="step" title="Step 7"><div class="para">
+ Unmount <code class="filename">boot.iso</code> and the USB storage device:
+ </div><pre class="screen">~]# <code class="command">umount /mnt/isoboot /mnt/diskboot</code>
+</pre></li><li class="step" title="Step 8"><div class="para">
+ You should reboot the machine with the boot media and verify that you are able to boot with it before continuing.
+ </div></li></ol></div><div class="para">
+ Alternatively, on systems with a floppy drive, you can create a boot diskette by installing the <span class="package">mkbootdisk</span> package and running the <code class="command">mkbootdisk</code> command as root. Refer to <code class="command">man mkbootdisk</code> man page after installing the package for usage information.
+ </div><div class="para">
+ To determine which kernel packages are installed, execute the command <code class="command">yum list installed "kernel-*"</code> at a shell prompt. The output will comprise some or all of the following packages, depending on the system's architecture, and the version numbers may differ:
+ </div><pre class="screen">~]# <code class="command">yum list installed "kernel-*"</code>
+kernel.x86_64 2.6.32-17.el6 installed
+kernel-doc.noarch 2.6.32-17.el6 installed
+kernel-firmware.noarch 2.6.32-17.el6 installed
+kernel-headers.x86_64 2.6.32-17.el6 installed
+</pre><div class="para">
+ From the output, determine which packages need to be download for the kernel upgrade. For a single processor system, the only required package is the <span class="package">kernel</span> package. Refer to <a class="xref" href="#s1-kernel-packages" title="23.1. Overview of Kernel Packages">Section 23.1, “Overview of Kernel Packages”</a> for descriptions of the different packages.
+ </div></div><div class="section" title="23.3. Downloading the Upgraded Kernel" id="s1-kernel-download"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-download">23.3. Downloading the Upgraded Kernel</h2></div></div></div><a id="id1546797" class="indexterm"></a><a id="id1546810" class="indexterm"></a><a id="id1546822" class="indexterm"></a><a id="id580117" class="indexterm"></a><div class="para">
+ There are several ways to determine if an updated kernel is available for the system.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Security Errata — Refer to <a href="http://www.redhat.com/security/updates/">http://www.redhat.com/security/updates/</a> for information on security errata, including kernel upgrades that fix security issues.
+ </div></li><li class="listitem"><div class="para">
+ Via Red Hat Network — Download and install the kernel RPM packages. Red Hat Network can download the latest kernel, upgrade the kernel on the system, create an initial RAM disk image if needed, and configure the boot loader to boot the new kernel. For more information, refer to <a href="http://www.redhat.com/docs/manuals/RHNetwork/"> http://www.redhat.com/docs/manuals/RHNetwork/</a>.
+ </div></li></ul></div><div class="para">
+ If Red Hat Network was used to download and install the updated kernel, follow the instructions in <a class="xref" href="#sec-Verifying_the_Initial_RAM_Disk_Image" title="23.5. Verifying the Initial RAM Disk Image">Section 23.5, “Verifying the Initial RAM Disk Image”</a> and <a class="xref" href="#s1-kernel-boot-loader" title="23.6. Verifying the Boot Loader">Section 23.6, “Verifying the Boot Loader”</a>, only <span class="emphasis"><em>do not</em></span> change the kernel to boot by default. Red Hat Network automatically changes the default kernel to the latest version. To install the kernel manually, continue to <a class="xref" href="#s1-kernel-perform-upgrade" title="23.4. Performing the Upgrade">Section 23.4, “Performing the Upgrade”</a>.
+ </div></div><div class="section" title="23.4. Performing the Upgrade" id="s1-kernel-perform-upgrade"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-perform-upgrade">23.4. Performing the Upgrade</h2></div></div></div><a id="id700746" class="indexterm"></a><div class="para">
+ After retrieving all of the necessary packages, it is time to upgrade the existing kernel.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is strongly recommended that you keep the old kernel in case there are problems with the new kernel.
+ </div></div></div><div class="para">
+ At a shell prompt, change to the directory that contains the kernel RPM packages. Use <code class="option">-i</code> argument with the <code class="command">rpm</code> command to keep the old kernel. Do <span class="emphasis"><em>not</em></span> use the <code class="option">-U</code> option, since it overwrites the currently installed kernel, which creates boot loader problems. For example:
+ </div><pre class="screen">~]# <code class="command">rpm -ivh kernel-<em class="replaceable"><code><kernel_version></code></em>.<em class="replaceable"><code><arch></code></em>.rpm </code>
+</pre><div class="para">
+ The next step is to verify that the initial RAM disk image has been created. Refer to <a class="xref" href="#sec-Verifying_the_Initial_RAM_Disk_Image" title="23.5. Verifying the Initial RAM Disk Image">Section 23.5, “Verifying the Initial RAM Disk Image”</a> for details.
+ </div></div><div class="section" title="23.5. Verifying the Initial RAM Disk Image" id="sec-Verifying_the_Initial_RAM_Disk_Image"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Verifying_the_Initial_RAM_Disk_Image">23.5. Verifying the Initial RAM Disk Image</h2></div></div></div><a id="id640011" class="indexterm"></a><div class="para">
+ The job of the initial RAM disk image is to preload the block device modules, such as for IDE, SCSI or RAID, so that the root file system, on which those modules normally reside, can then be accessed and mounted. On Fedora 14 systems, whenever a new kernel is installed using either the <span class="application"><strong>Yum</strong></span>, <span class="application"><strong>PackageKit</strong></span>, or <span class="application"><strong>RPM</strong></span> package manager, the <span class="application"><strong>Dracut</strong></span> utility is always called by the installation scripts to create an <em class="firstterm">initramfs</em> (initial RAM disk image).
+ </div><div class="para">
+ On all architectures other than <span class="trademark">IBM</span>® <span class="trademark">eServer</span>™ <span class="trademark">System i</span>™ (see <a class="xref" href="#bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i" title="23.5. Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i">Section 23.5, “Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i”</a>), you can create an <code class="systemitem">initramfs</code> by running the <code class="command">dracut</code> command. However, you usually don't need to create an <code class="systemitem">initramfs</code> manually: this step is automatically performed if the kernel and its associated packages are installed or upgraded from RPM packages distributed by The Fedora Project.
+ </div><div class="para">
+ You can verify that an <code class="systemitem">initramfs</code> corresponding to your current kernel version exists and is specified correctly in the <code class="filename">grub.conf</code> configuration file by following this procedure:
+ </div><div class="procedure" title="Procedure 23.1. Verifying the Initial RAM Disk Image" id="procedure-Verifying_the_Initial_RAM_Disk_Image"><h6>Procedure 23.1. Verifying the Initial RAM Disk Image</h6><ol class="1"><li class="step" title="Step 1"><div class="para">
+ As root, list the contents in the <code class="filename">/boot/</code> directory and find the kernel (<code class="filename">vmlinuz-<em class="replaceable"><code><kernel_version></code></em> </code>) and <code class="filename">initramfs-<em class="replaceable"><code><kernel_version></code></em> </code> with the latest (most recent) version number:
+ </div><div class="example" title="Example 23.1. Ensuring that the kernel and initramfs versions match" id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"><h6>Example 23.1. Ensuring that the kernel and initramfs versions match</h6><div class="example-contents"><pre class="screen">~]# <code class="command">ls /boot/</code>
+config-2.6.32.10-90.fc12.x86_64
+config-2.6.32.11-99.fc12.x86_64
+config-2.6.32.9-70.fc12.x86_64
+efi
+elf-memtest86+-4.00
+grub
+initramfs-2.6.32.10-90.fc12.x86_64.img
+initramfs-2.6.32.11-99.fc12.x86_64.img
+initramfs-2.6.32.9-70.fc12.x86_64.img
+lost+found
+memtest86+-4.00
+System.map-2.6.32.10-90.fc12.x86_64
+System.map-2.6.32.11-99.fc12.x86_64
+System.map-2.6.32.9-70.fc12.x86_64
+vmlinuz-2.6.32.10-90.fc12.x86_64
+vmlinuz-2.6.32.11-99.fc12.x86_64
+vmlinuz-2.6.32.9-70.fc12.x86_64</pre></div></div><br class="example-break" /><div class="para">
+ <a class="xref" href="#ex-Ensuring_that_the_kernel_and_initramfs_versions_match" title="Example 23.1. Ensuring that the kernel and initramfs versions match">Example 23.1, “Ensuring that the kernel and initramfs versions match”</a> shows that:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ we have three kernels installed (or, more correctly, three kernel files are present in <code class="filename">/boot/</code>),
+ </div></li><li class="listitem"><div class="para">
+ the latest kernel is <code class="filename">vmlinuz-2.6.32.10-90.fc12.x86_64</code>, and
+ </div></li><li class="listitem"><div class="para">
+ an <code class="systemitem">initramfs</code> file matching our kernel version, <code class="filename">initramfs-2.6.32.10-90.fc12.x86_64.img</code>, also exists.
+ </div></li></ul></div><div class="important" title="initrd files in the /boot directory are not the same as initramfs files" id="important-initrd_files_in_the__boot_directory_are_not_the_same_as_initramfs_files"><div class="admonition_header"><h2>initrd files in the /boot directory are not the same as initramfs files</h2></div><div class="admonition"><div class="para">
+ In the <code class="filename">/boot/</code> directory you may find several <code class="filename">initrd-<em class="replaceable"><code><version></code></em>kdump.img</code> files. These are special files created by the <span class="application"><strong>Kdump</strong></span> mechanism for kernel debugging purposes, are not used to boot the system, and can safely be ignored.
+ </div></div></div></li><li class="step" title="Step 2"><div class="para">
+ (Optional) If your <code class="filename">initramfs-<em class="replaceable"><code><kernel_version></code></em> </code> file does not match the version of the latest kernel in <code class="filename">/boot/</code>, or, in certain other situations, you may need to generate an <code class="filename">initramfs</code> file with the <span class="application"><strong>Dracut</strong></span> utility. Simply invoking <code class="command">dracut</code> as root without options causes it to generate an <code class="filename">initramfs</code> file in the <code class="filename">/boot/</code> directory for the latest kernel present in that directory:
+ </div><pre class="screen">~]# <code class="command">dracut</code>
+</pre><div class="para">
+ You must use the <code class="option">--force</code> option if you want <code class="command">dracut</code> to overwrite an existing <code class="filename">initramfs</code> (for example, if your <code class="filename">initramfs</code> has become corrupt). Otherwise <code class="command">dracut</code> will refuse to overwrite the existing <code class="filename">initramfs</code> file:
+ </div><pre class="screen">~]# <code class="command">dracut</code>
+Will not override existing initramfs (/boot/initramfs-2.6.32.11-99.fc12.x86_64.img) without --force</pre><div class="para">
+ You can create an initramfs in the current directory by calling <code class="command">dracut <em class="replaceable"><code><initramfs_name></code></em> <em class="replaceable"><code><kernel_version></code></em></code>:
+ </div><pre class="screen">~]# <code class="command">dracut "initramfs-$(uname -r).img" $(uname -r)</code>
+</pre><div class="para">
+ If you need to specify specific kernel modules to be preloaded, add the names of those modules (minus any file name suffixes such as <code class="filename">.ko</code>) inside the parentheses of the <code class="computeroutput">add_dracutmodules="<em class="replaceable"><code><module></code></em> [<span class="optional"><em class="replaceable"><code><more_modules></code></em></span>]"</code> directive of the <code class="filename">/etc/dracut.conf</code> configuration file. You can list the file contents of an <code class="filename">initramfs</code> image file created by dracut by using the <code class="command">lsinitrd <em class="replaceable"><code><initramfs_file></code></em> </code> command:
+ </div><pre class="screen">~]# <code class="command">lsinitrd initramfs-2.6.32.11-99.fc12.x86_64.img</code>
+initramfs-2.6.32.11-99.fc12.x86_64.img:
+========================================================================
+drwxr-xr-x 23 root root 0 Apr 12 05:41 .
+drwxr-xr-x 2 root root 0 Apr 12 05:41 mount
+-rwxr-xr-x 1 root root 934 Jan 15 14:07 mount/99mount-root.sh
+-rwxr-xr-x 1 root root 230 Jan 15 14:07 mount/10resume.sh
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em>
+</pre><div class="para">
+ Refer to <code class="command">man dracut</code> and <code class="command">man dracut.conf</code> for more information on options and usage.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Examine the <code class="filename">grub.conf</code> configuration file in the <code class="filename">/boot/grub/</code> directory to ensure that an <code class="computeroutput">initrd <code class="filename">initramfs-<em class="replaceable"><code><kernel_version></code></em>.img</code> </code> exists for the kernel version you are booting. Refer to <a class="xref" href="#s1-kernel-boot-loader" title="23.6. Verifying the Boot Loader">Section 23.6, “Verifying the Boot Loader”</a> for more information.
+ </div></li></ol></div><h3>Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i</h3><a id="id770689" class="indexterm"></a><div class="para">
+ On IBM eSeries System i machines, the initial RAM disk and kernel files are combined into a single file, which is created with the <code class="command">addRamDisk</code> command. This step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by The Fedora Project; thus, it does not need to be executed manually. To verify that it was created, use the command <code class="command">ls -l /boot/</code> to make sure the <code class="filename">/boot/vmlinitrd-<em class="replaceable"><code><kernel_version></code></em> </code> file already exists (the <code class="filename"><em class="replaceable"><code><kernel_version></code></em> </code> should match the version of the kernel just installed).
+ </div></div><div class="section" title="23.6. Verifying the Boot Loader" id="s1-kernel-boot-loader"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-boot-loader">23.6. Verifying the Boot Loader</h2></div></div></div><a id="id1614771" class="indexterm"></a><div class="para">
+ When you install a kernel using <code class="command">rpm</code>, the kernel package creates an entry in the boot loader configuration file for that new kernel. However, <code class="command">rpm</code> does <span class="emphasis"><em>not</em></span> configure the new kernel to boot as the default kernel. You must do this manually when installing a new kernel with <code class="command">rpm</code>.
+ </div><div class="para">
+ It is always recommended to double-check the boot loader configuration file after installing a new kernel with <code class="command">rpm</code> to ensure that the configuration is correct. Otherwise, the system may not be able to boot into Fedora properly. If this happens, boot the system with the boot media created earlier and re-configure the boot loader.
+ </div><div class="para">
+ In the following table, find your system's architecture to determine the boot loader it uses, and then click on the "Refer to" link to jump to the correct instructions for your system.
+ </div><div class="table" title="Table 23.1. Boot Loaders by Architecture" id="tb-grub-arch-loaders"><h6>Table 23.1. Boot Loaders by Architecture</h6><div class="table-contents"><table summary="Boot Loaders by Architecture" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th>
+ Architecture
+ </th><th>
+ Boot Loader
+ </th><th>
+ Refer to
+ </th></tr></thead><tbody><tr><td>
+ x86
+ </td><td>
+ GRUB
+ </td><td>
+ <a class="xref" href="#s3-kernel-boot-loader-grub" title="23.6.1. Configuring the GRUB Boot Loader">Section 23.6.1, “Configuring the GRUB Boot Loader”</a>
+ </td></tr><tr><td>
+ <span class="trademark">AMD</span>® AMD64 <span class="emphasis"><em>or</em></span> <span class="trademark">Intel 64</span>®
+ </td><td>
+ GRUB
+ </td><td>
+ <a class="xref" href="#s3-kernel-boot-loader-grub" title="23.6.1. Configuring the GRUB Boot Loader">Section 23.6.1, “Configuring the GRUB Boot Loader”</a>
+ </td></tr><tr><td>
+ <span class="trademark">IBM</span>® <span class="trademark">eServer</span>™ <span class="trademark">System i</span>™
+ </td><td>
+ <span class="trademark">OS/400</span>®
+ </td><td>
+ <a class="xref" href="#s2-kernel-boot-loader-iseries" title="23.6.2. Configuring the OS/400® Boot Loader">Section 23.6.2, “Configuring the <span class="trademark">OS/400</span>® Boot Loader”</a>
+ </td></tr><tr><td>
+ <span class="trademark">IBM</span>® <span class="trademark">eServer</span>™ <span class="trademark">System p</span>™
+ </td><td>
+ YABOOT
+ </td><td>
+ <a class="xref" href="#s2-kernel-boot-loader-pseries" title="23.6.3. Configuring the YABOOT Boot Loader">Section 23.6.3, “Configuring the YABOOT Boot Loader”</a>
+ </td></tr><tr><td>
+ <span class="trademark">IBM</span>® <span class="trademark">System z</span>®
+ </td><td>
+ z/IPL
+ </td><td>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" title="23.6.1. Configuring the GRUB Boot Loader" id="s3-kernel-boot-loader-grub"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s3-kernel-boot-loader-grub">23.6.1. Configuring the GRUB Boot Loader</h3></div></div></div><a id="id535314" class="indexterm"></a><a id="id535326" class="indexterm"></a><div class="para">
+ GRUB's configuration file, <code class="filename">/boot/grub/grub.conf</code>, contains a few lines with directives, such as <code class="computeroutput">default</code>, <code class="computeroutput">timeout</code>, <code class="computeroutput">splashimage</code> and <code class="computeroutput">hiddenmenu</code> (the last directive has no argument). The remainder of the file contains 4-line <em class="firstterm">stanzas</em> that each refer to an installed kernel. These stanzas always start with a <code class="computeroutput">title</code> entry, after which the associated <code class="computeroutput">root</code>, <code class="computeroutput">kernel</code> and <code class="computeroutput">initrd</code> directives should always be indented. Ensure that each stanza starts with a <code class="computeroutput">title</code> that contains a version number (in parentheses) that matches the version number in the <code class="computeroutput">kernel /vmlinuz-<em class="replaceable">
<code><version_number></code></em> </code> line of the same stanza.
+ </div><div class="example" title="Example 23.2. /boot/grub/grub.conf" id="ex-_boot_grub_grub.conf"><h6>Example 23.2. /boot/grub/grub.conf</h6><div class="example-contents"><pre class="screen"># grub.conf generated by anaconda
+<em class="lineannotation"><span class="lineannotation">[comments omitted]</span></em>
+default=1
+timeout=0
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+
+title Fedora (2.6.32.11-99.fc12.x86_64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32.11-99.fc12.x86_64 ro root=UUID=39e5f931-5dd5-4a90-a0cf-52996767d592 noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=dvorak rhgb quiet
+ initrd /initramfs-2.6.32.11-99.fc12.x86_64.img
+
+title Fedora (2.6.32.10-90.fc12.x86_64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32.10-90.fc12.x86_64 ro root=UUID=39e5f931-5dd5-4a90-a0cf-52996767d592 noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=dvorak rhgb quiet
+ initrd /initramfs-2.6.32.10-90.fc12.x86_64.img
+
+title Fedora (2.6.32.9-70.fc12.x86_64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32.9-70.fc12.x86_64 ro root=UUID=39e5f931-5dd5-4a90-a0cf-52996767d592 noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=dvorak rhgb quiet
+ initrd /initramfs-2.6.32.9-70.fc12.x86_64.img</pre></div></div><br class="example-break" /><div class="para">
+ If a separate <code class="filename">/boot/</code> partition was created, the paths to the kernel and the <code class="systemitem">initramfs</code> image are relative to <code class="filename">/boot/</code>. This is the case in <a class="xref" href="#ex-_boot_grub_grub.conf" title="Example 23.2. /boot/grub/grub.conf">Example 23.2, “/boot/grub/grub.conf”</a>, above. Therefore the <code class="computeroutput">initrd <code class="filename">/initramfs-2.6.32.11-99.fc12.x86_64.img</code> </code> line in the first kernel stanza means that the <code class="systemitem">initramfs</code> image is actually located at <code class="filename">/boot/initramfs-2.6.32.11-99.fc12.x86_64.img</code> when the root file system is mounted, and likewise for the kernel path (for example: <code class="computeroutput">kernel <code class="filename">/vmlinuz-2.6.32.11-99.fc12.x86_64</code> </code>) in each stanza of <code class="filename">grub.conf</code>.
+ </div><div class="note" title="The initrd directive in grub.conf refers to an initramfs image" id="note-The_initrd_directive_in_grub.conf_refers_to_an_initramfs_image"><div class="admonition_header"><h2>The initrd directive in grub.conf refers to an initramfs image</h2></div><div class="admonition"><div class="para">
+ In kernel boot stanzas in <code class="filename">grub.conf</code>, the <code class="computeroutput">initrd</code> directive must point to the location (relative to the <code class="filename">/boot/</code> directory if it is on a separate partition), of the <span class="emphasis"><em><code class="filename">initramfs</code> </em></span> file corresponding to the same kernel version. This directive is called <code class="computeroutput">initrd</code> because the previous tool which created initial RAM disk images, <code class="command">mkinitrd</code>, created what were known as <code class="systemitem">initrd</code> files. Thus the <code class="filename">grub.conf</code> directive remains <code class="systemitem">initrd</code> to maintain compatibility with other tools. The file-naming convention of systems using the <code class="command">dracut</code> utility to create the initial RAM disk image is: <code class="filename">initramfs-<em class="replaceable"><code><kerne
l_version></code></em>.img</code>
+ </div><div class="para">
+ <span class="application"><strong>Dracut</strong></span> is a new utility available in Fedora 14, and much-improved over <code class="command">mkinitrd</code>. For information on using <span class="application"><strong>Dracut</strong></span>, refer to <a class="xref" href="#sec-Verifying_the_Initial_RAM_Disk_Image" title="23.5. Verifying the Initial RAM Disk Image">Section 23.5, “Verifying the Initial RAM Disk Image”</a>.
+ </div></div></div><div class="para">
+ You should ensure that the kernel version number as given on the <code class="computeroutput">kernel <code class="filename">/vmlinuz-<em class="replaceable"><code><kernel_version></code></em> </code> </code> line matches the version number of the <code class="systemitem">initramfs</code> image given on the <code class="computeroutput">initrd <code class="filename">/initramfs-<em class="replaceable"><code><kernel_version></code></em>.img</code> </code> line of each stanza. Refer to <a class="xref" href="#procedure-Verifying_the_Initial_RAM_Disk_Image" title="Procedure 23.1. Verifying the Initial RAM Disk Image">Procedure 23.1, “Verifying the Initial RAM Disk Image”</a> for more information.
+ </div><div class="para">
+ The <code class="computeroutput">default=</code> directive tells GRUB which kernel to boot <span class="emphasis"><em>by default</em></span>. Each <code class="computeroutput">title</code> in <code class="filename">grub.conf</code> represents a bootable kernel. GRUB counts the <code class="computeroutput">title</code>d stanzas representing bootable kernels starting with <code class="constant">0</code>. In <a class="xref" href="#ex-_boot_grub_grub.conf" title="Example 23.2. /boot/grub/grub.conf">Example 23.2, “/boot/grub/grub.conf”</a>, the line <code class="computeroutput">default=1</code> indicates that GRUB will boot, by default, the <span class="emphasis"><em>second</em></span> kernel entry, i.e. <code class="computeroutput">title Fedora (2.6.32.10-90.fc12.x86_64)</code>.
+ </div><div class="para">
+ In <a class="xref" href="#ex-_boot_grub_grub.conf" title="Example 23.2. /boot/grub/grub.conf">Example 23.2, “/boot/grub/grub.conf”</a> GRUB is therefore configured to boot an older kernel, when we compare by version numbers. In order to boot the newer kernel, which is the <span class="emphasis"><em>first</em></span> <code class="computeroutput">title</code> entry in <code class="filename">grub.conf</code>, we would need to change the <code class="computeroutput">default</code> value to <code class="constant">0</code>.
+ </div><div class="para">
+ After installing a new kernel with <code class="command">rpm</code>, verify that <code class="filename">/boot/grub/grub.conf</code> is correct, change the <code class="computeroutput">default=</code> value to the new kernel (while remembering to count from <code class="constant">0</code>), and reboot the computer into the new kernel. Ensure your hardware is detected by watching the boot process output.
+ </div><div class="para">
+ If GRUB presents an error and is unable to boot into the default kernel, it is often easiest to try to boot into an alternative or older kernel so that you can fix the problem.
+ </div><div class="important" title="Important: Causing the GRUB boot menu to display"><div class="admonition_header"><h2>Important: Causing the GRUB boot menu to display</h2></div><div class="admonition"><div class="para">
+ If you set the <code class="computeroutput">timeout</code> directive in <code class="filename">grub.conf</code> to <code class="constant">0</code>, GRUB will not display its list of bootable kernels when the system starts up. In order to display this list when booting, press and hold any alphanumeric key while and immediately after BIOS information is displayed, and GRUB will present you with the GRUB menu.
+ </div></div></div><div class="para">
+ Alternatively, use the boot media you created earlier to boot the system.
+ </div></div><div class="section" title="23.6.2. Configuring the OS/400® Boot Loader" id="s2-kernel-boot-loader-iseries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kernel-boot-loader-iseries">23.6.2. Configuring the <span class="trademark">OS/400</span>® Boot Loader</h3></div></div></div><a id="id774897" class="indexterm"></a><a id="id717309" class="indexterm"></a><div class="para">
+ The <code class="filename">/boot/vmlinitrd-<em class="replaceable"><code><kernel-version></code></em> </code> file is installed when you upgrade the kernel. However, you must use the <code class="command">dd</code> command to configure the system to boot the new kernel.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ As root, issue the command <code class="command">cat /proc/iSeries/mf/side</code> to determine the default side (either A, B, or C).
+ </div></li><li class="listitem"><div class="para">
+ As root, issue the following command, where <em class="replaceable"><code><kernel-version></code></em> is the version of the new kernel and <em class="replaceable"><code><side></code></em> is the side from the previous command:
+ </div><pre class="screen">
+<code class="command">dd if=/boot/vmlinitrd-<em class="replaceable"><code><kernel-version></code></em> of=/proc/iSeries/mf/<em class="replaceable"><code><side></code></em>/vmlinux bs=8k</code>
+</pre></li></ol></div><div class="para">
+ Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.
+ </div></div><div class="section" title="23.6.3. Configuring the YABOOT Boot Loader" id="s2-kernel-boot-loader-pseries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kernel-boot-loader-pseries">23.6.3. Configuring the YABOOT Boot Loader</h3></div></div></div><div class="para">
+ IBM eServer System p uses YABOOT as its boot loader. YABOOT uses <code class="filename">/etc/aboot.conf</code> as its configuration file. Confirm that the file contains an <code class="computeroutput">image</code> section with the same version as the <span class="package">kernel</span> package just installed, and likewise for the <code class="systemitem">initramfs</code> image:
+ </div><pre class="screen">boot=/dev/sda1 init-message=Welcome to Fedora! Hit <TAB> for boot options
+partition=2 timeout=30 install=/usr/lib/yaboot/yaboot delay=10 nonvram
+image=/vmlinuz-2.6.32-17.EL
+ label=old
+ read-only
+ initrd=/initramfs-2.6.32-17.EL.img
+ append="root=LABEL=/"
+image=/vmlinuz-2.6.32-19.EL
+ label=linux
+ read-only
+ initrd=/initramfs-2.6.32-19.EL.img
+ append="root=LABEL=/"</pre><div class="para">
+ Notice that the default is not set to the new kernel. The kernel in the first image is booted by default. To change the default kernel to boot either move its image stanza so that it is the first one listed or add the directive <code class="computeroutput">default</code> and set it to the <code class="computeroutput">label</code> of the image stanza that contains the new kernel.
+ </div><div class="para">
+ Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.
+ </div></div></div></div><div xml:lang="en-US" class="chapter" title="Chapter 24. The kdump Crash Recovery Service" id="ch-kdump" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 24. The <code class="systemitem">kdump</code> Crash Recovery Service</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="#s1-kdump-configuration">24.1. Configuring the <code class="systemitem">kdump</code> Service</a></span></dt><dt><span class="section"><a href="#s1-kdump-crash">24.2. Analyzing the Core Dump</a></span></dt><dt><span class="section"><a href="#s1-kdump-resources">24.3. Additional Resources</a></span></dt></dl></div><div class="para">
+ <code class="systemitem">kdump</code> is an advanced crash dumping mechanism. When enabled, the system is booted from the context of another kernel. This second kernel reserves a small amount of memory, and its only purpose is to capture the core dump image in case the system crashes. Since being able to analyze the core dump helps significantly to determine the exact cause of the system failure, it is strongly recommended to have this feature enabled.
+ </div><div class="para">
+ This chapter explains how to configure, test, and use the <code class="systemitem">kdump</code> service in Fedora, and provides a brief overview of how to analyze the resulting core dump using the <span class="application"><strong>crash</strong></span> debugging utility.
+ </div><div class="section" title="24.1. Configuring the kdump Service" id="s1-kdump-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kdump-configuration">24.1. Configuring the <code class="systemitem">kdump</code> Service</h2></div></div></div><div class="para">
+ This section covers three common means of configuring the <code class="systemitem">kdump</code> service: at the first boot, using the <span class="application"><strong>Kernel Dump Configuration</strong></span> graphical utility, and doing so manually on the command line. It also describes how to test the configuration to verify that everything works as expected.
+ </div><a id="id710426" class="indexterm"></a><div class="note" title="Note: Make Sure You Have kexec-tools Installed"><div class="admonition_header"><h2>Note: Make Sure You Have <span class="package">kexec-tools</span> Installed</h2></div><div class="admonition"><div class="para">
+ To use the <code class="systemitem">kdump</code> service, you must have the <span class="package">kexec-tools</span> package installed. Refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><div class="section" title="24.1.1. Configuring the kdump at First Boot" id="s2-kdump-configuration-firstboot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-configuration-firstboot">24.1.1. Configuring the <code class="systemitem">kdump</code> at First Boot</h3></div></div></div><div class="para">
+ When the system boots for the first time, the <span class="application"><strong>firstboot</strong></span> application is launched to guide a user through the initial configuration of the freshly installed system. To configure <code class="systemitem">kdump</code>, navigate to the <span class="guilabel"><strong>Kdump</strong></span> section, and follow the instructions below.
+ </div><div class="important" title="Important: Make Sure the System Has Enough Memory"><div class="admonition_header"><h2>Important: Make Sure the System Has Enough Memory</h2></div><div class="admonition"><div class="para">
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <em class="citetitle">Required minimums</em> section of the <a href="http://www.redhat.com/rhel/compare/"><em class="citetitle">Red Hat Enterprise Linux</em> comparison chart</a>. Note that when the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by a user, and defaults to 128 MB.
+ </div></div></div><div class="section" title="24.1.1.1. Enabling the Service" id="s3-kdump-configuration-firstboot-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-firstboot-enable">24.1.1.1. Enabling the Service</h4></div></div></div><a id="id675500" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">kdump</code> daemon at boot time, select the <span class="guilabel"><strong>Enable kdump?</strong></span> check box. This will enable the service for runlevels <code class="literal">2</code>, <code class="literal">3</code>, <code class="literal">4</code>, and <code class="literal">5</code>, and start it for the current session. Similarly, unselecting the check box will disable it for all runlevels and stop the service immediately.
+ </div></div><div class="section" title="24.1.1.2. Configuring the Memory Usage" id="s3-kdump-configuration-firstboot-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-firstboot-memory">24.1.1.2. Configuring the Memory Usage</h4></div></div></div><a id="id675554" class="indexterm"></a><div class="para">
+ To configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel, click the up and down arrow buttons next to the <span class="guilabel"><strong>Kdump Memory</strong></span> field to increase or decrease the value. Notice that the <span class="guilabel"><strong>Usable System Memory</strong></span> field changes accordingly showing you the remaining memory that will be available to the system.
+ </div></div></div><div class="section" title="24.1.2. Using the Kernel Dump Configuration Utility" id="s2-kdump-configuration-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-configuration-gui">24.1.2. Using the <span class="application"><strong>Kernel Dump Configuration</strong></span> Utility</h3></div></div></div><a id="id582402" class="indexterm"></a><a id="id582418" class="indexterm"></a><div class="para">
+ To start the <span class="application"><strong>Kernel Dump Configuration</strong></span> utility, select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Kernel crash dumps</strong></span> from the panel, or type <code class="command">system-config-kdump</code> at a shell prompt (for example, <span class="emphasis"><em>xterm</em></span> or <span class="emphasis"><em>GNOME Terminal</em></span>). You will be presented with a window as shown in <a class="xref" href="#fig-kdump-kernel_dump_configuration" title="Figure 24.1. Basic Settings">Figure 24.1, “<span class="guilabel">Basic Settings</span>”</a>.
+ </div><div class="para">
+ The utility allows you to configure <code class="systemitem">kdump</code> as well as to enable or disable starting the service at boot time. When you are done, click <span class="guibutton"><strong>Apply</strong></span> to save the changes. The system reboot will be requested, and unless you are already authenticated, you will be prompted to enter the superuser password.
+ </div><div class="important" title="Important: Make Sure the System Has Enough Memory"><div class="admonition_header"><h2>Important: Make Sure the System Has Enough Memory</h2></div><div class="admonition"><div class="para">
+ Unless the system has enough memory, the utility will not start, and you will be presented with the following error message:
+ </div><div class="mediaobject" align="center"><img src="images/kdump-kernel_dump_configuration-not_enough_memory.png" align="middle" /><div class="longdesc"><div class="para">
+ The <span class="quote">“<span class="quote">not enough memory</span>”</span> error
+ </div></div></div><div class="para">
+ For the information on minimum memory requirements, refer to the <em class="citetitle">Required minimums</em> section of the <a href="http://www.redhat.com/rhel/compare/"><em class="citetitle">Red Hat Enterprise Linux</em> comparison chart</a>. Note that when the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by a user, and defaults to 128 MB.
+ </div></div></div><div class="section" title="24.1.2.1. Enabling the Service" id="s3-kdump-configuration-gui-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-gui-enable">24.1.2.1. Enabling the Service</h4></div></div></div><a id="id519659" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">kdump</code> daemon at boot time, click the <span class="guibutton"><strong>Apply</strong></span> button on the toolbar. This will enable the service for runlevels <code class="literal">2</code>, <code class="literal">3</code>, <code class="literal">4</code>, and <code class="literal">5</code>, and start it for the current session. Similarly, clicking the <span class="guibutton"><strong>Disable</strong></span> button will disable it for all runlevels and stop the service immediately.
+ </div><div class="para">
+ For more information on runlevels and configuring services in general, refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div></div><div class="section" title="24.1.2.2. The Basic Settings Tab" id="s3-kdump-configuration-gui-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-gui-basic">24.1.2.2. The <span class="guilabel"><strong>Basic Settings</strong></span> Tab</h4></div></div></div><a id="id1809615" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Basic Settings</strong></span> tab enables you to configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel. To do so, select the <span class="guilabel"><strong>Manual kdump memory settings</strong></span> radio button, and click the up and down arrow buttons next to the <span class="guilabel"><strong>New kdump Memory</strong></span> field to increase or decrease the value. Notice that the <span class="guilabel"><strong>Usable Memory</strong></span> field changes accordingly showing you the remaining memory that will be available to the system.
+ </div><div class="figure" title="Figure 24.1. Basic Settings" id="fig-kdump-kernel_dump_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration.png" alt="Basic Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Basic Settings</strong></span>
+ </div></div></div></div><h6>Figure 24.1. <span class="guilabel">Basic Settings</span></h6></div><br class="figure-break" /></div><div class="section" title="24.1.2.3. The Target Settings Tab" id="s3-kdump-configuration-gui-target"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-gui-target">24.1.2.3. The <span class="guilabel"><strong>Target Settings</strong></span> Tab</h4></div></div></div><a id="id1520406" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Target Settings</strong></span> tab enables you to specify the target location for the <code class="filename">vmcore</code> dump. It can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol.
+ </div><div class="figure" title="Figure 24.2. Target Settings" id="fig-kdump-kernel_dump_configuration-target_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-target_settings.png" alt="Target Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Target Settings</strong></span>
+ </div></div></div></div><h6>Figure 24.2. <span class="guilabel">Target Settings</span></h6></div><br class="figure-break" /><div class="para">
+ To save the dump to the local file system, select the <span class="guilabel"><strong>Local filesystem</strong></span> radio button. Optionally, you can customize the settings by choosing a different partition from the <span class="guilabel"><strong>Partition</strong></span>, and a target directory from the <span class="guilabel"><strong>Path</strong></span> pulldown lists.
+ </div><div class="para">
+ To write the dump directly to a device, select the <span class="guilabel"><strong>Raw device</strong></span> radio button, and choose the desired target device from the pulldown list next to it.
+ </div><div class="para">
+ To store the dump to a remote machine, select the <span class="guilabel"><strong>Network</strong></span> radio button. To use the NFS protocol, select the <span class="guilabel"><strong>NFS</strong></span> radio button, and fill the <span class="guilabel"><strong>Server name</strong></span> and <span class="guilabel"><strong>Path to directory</strong></span> fields. To use the SSH protocol, select the <span class="guilabel"><strong>SSH</strong></span> radio button, and fill the <span class="guilabel"><strong>Server name</strong></span>, <span class="guilabel"><strong>Path to directory</strong></span>, and <span class="guilabel"><strong>User name</strong></span> fields with the remote server address, target directory, and a valid remote user name respectively.
+ </div><div class="para">
+ Refer to <a class="xref" href="#ch-OpenSSH" title="Chapter 9. OpenSSH">Chapter 9, <i>OpenSSH</i></a> for information on how to configure an SSH server, and how to set up a key-based authentication.
+ </div><a id="id596677" class="indexterm"></a><div class="important" title="Important: Using the hpsa Driver for a Storage"><div class="admonition_header"><h2>Important: Using the <code class="systemitem">hpsa</code> Driver for a Storage</h2></div><div class="admonition"><div class="para">
+ Due to known issue with the <code class="systemitem">hpsa</code> driver, <code class="systemitem">kdump</code> is unable to save the dump to a storage that uses this driver for HP Smart Array Controllers. If this applies to your machine, it is advised that you save the dump to a remote system using the NFS or SSH protocol instead.
+ </div></div></div></div><div class="section" title="24.1.2.4. The Filtering Settings Tab" id="s3-kdump-configuration-gui-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-gui-filtering">24.1.2.4. The <span class="guilabel"><strong>Filtering Settings</strong></span> Tab</h4></div></div></div><a id="id1051751" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Filtering Settings</strong></span> tab enables you to select the filtering level for the <code class="filename">vmcore</code> dump.
+ </div><div class="figure" title="Figure 24.3. Filtering Settings" id="fig-kdump-kernel_dump_configuration-filtering_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-filtering_settings.png" alt="Filtering Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Filtering Settings</strong></span>
+ </div></div></div></div><h6>Figure 24.3. <span class="guilabel">Filtering Settings</span></h6></div><br class="figure-break" /><div class="para">
+ To exclude the <span class="guilabel"><strong>zero page</strong></span>, <span class="guilabel"><strong>cache page</strong></span>, <span class="guilabel"><strong>cache private</strong></span>, <span class="guilabel"><strong>user data</strong></span>, or <span class="guilabel"><strong>free page</strong></span> from the dump, select the check box next to the appropriate label.
+ </div></div><div class="section" title="24.1.2.5. The Expert Settings Tab" id="s3-kdump-configuration-gui-expert"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-gui-expert">24.1.2.5. The <span class="guilabel"><strong>Expert Settings</strong></span> Tab</h4></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Expert Settings</strong></span> tab enables you to choose which kernel and initial RAM disk to use, as well as to customize the options that are passed to the kernel and the core collector program.
+ </div><div class="figure" title="Figure 24.4. Expert Settings" id="fig-kdump-kernel_dump_configuration-expert_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-expert_settings.png" alt="Expert Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Expert Settings</strong></span>
+ </div></div></div></div><h6>Figure 24.4. <span class="guilabel">Expert Settings</span></h6></div><br class="figure-break" /><a id="id508763" class="indexterm"></a><div class="para">
+ To use a different initial RAM disk, select the <span class="guilabel"><strong>Custom initrd</strong></span> radio button, and choose the desired RAM disk from the pulldown list next to it.
+ </div><a id="id508789" class="indexterm"></a><div class="para">
+ To capture a different kernel, select the <span class="guilabel"><strong>Custom kernel</strong></span> radio button, and choose the desired kernel image from the pulldown list on the right.
+ </div><a id="id508818" class="indexterm"></a><div class="para">
+ To adjust the list of options that are passed to the kernel at boot time, edit the content of the <span class="guilabel"><strong>Edited</strong></span> text field. Note that you can always revert your changes by clicking the <span class="guibutton"><strong>Refresh</strong></span> button.
+ </div><a id="id490693" class="indexterm"></a><div class="para">
+ To choose what steps should be taken when the kernel crash is captured, select the appropriate option from the <span class="guilabel"><strong>Default action</strong></span> pulldown list. Available options are <span class="guimenuitem"><strong>mount rootfs and run /sbin/init</strong></span> (the default action), <span class="guimenuitem"><strong>reboot</strong></span> (to reboot the system), <span class="guimenuitem"><strong>shell</strong></span> (to present a user with an interactive shell prompt), <span class="guimenuitem"><strong>halt</strong></span> (to halt the system), and <span class="guimenuitem"><strong>poweroff</strong></span> (to power the system off).
+ </div><a id="id490740" class="indexterm"></a><div class="para">
+ To customize the options that are passed to the <code class="command">makedumpfile</code> core collector, edit the <span class="guilabel"><strong>Core collector</strong></span> text field; see <a class="xref" href="#s3-kdump-configuration-cli-filtering" title="24.1.3.3. Configuring the Core Collector">Section 24.1.3.3, “Configuring the Core Collector”</a> for more information.
+ </div></div></div><div class="section" title="24.1.3. Configuring kdump on the Command Line" id="s2-kdump-configuration-cli"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-configuration-cli">24.1.3. Configuring <code class="systemitem">kdump</code> on the Command Line</h3></div></div></div><div class="para">
+ To perform actions described in this section, you have to be logged in as a superuser:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="section" title="24.1.3.1. Configuring the Memory Usage" id="s3-kdump-configuration-cli-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-cli-memory">24.1.3.1. Configuring the Memory Usage</h4></div></div></div><a id="id569916" class="indexterm"></a><div class="para">
+ To configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel, open the <code class="filename">/boot/grub/grub.conf</code> file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, and add the <code class="option">crashkernel=<em class="replaceable"><code><size></code></em>M</code> parameter to the list of kernel options as shown in <a class="xref" href="#ex-kdump-configuration-cli-memory-grub" title="Example 24.1. A sample /boot/grub/grub.conf file">Example 24.1, “A sample <code class="filename">/boot/grub/grub.conf</code> file”</a>.
+ </div><a id="id1118276" class="indexterm"></a><a id="id1118296" class="indexterm"></a><a id="id1118316" class="indexterm"></a><div class="example" title="Example 24.1. A sample /boot/grub/grub.conf file" id="ex-kdump-configuration-cli-memory-grub"><h6>Example 24.1. A sample <code class="filename">/boot/grub/grub.conf</code> file</h6><div class="example-contents"><pre class="screen"># grub.conf generated by anaconda
+#
+# Note that you do not have to rerun grub after making changes to this file
+# NOTICE: You have a /boot partition. This means that
+# all kernel and initrd paths are relative to /boot/, eg.
+# root (hd0,0)
+# kernel /vmlinuz-version ro root=/dev/sda3
+# initrd /initrd
+#boot=/dev/sda
+default=0
+timeout=5
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+title Red Hat Enterprise Linux (2.6.32-54.el6.i686)
+ root (hd0,0)
+ kernel /boot/vmlinuz-2.6.32-54.el6.i686 root=/dev/sda3 ro crashkernel=128M
+ initrd /initramfs-2.6.32-54.el6.i686.img
+</pre></div></div><br class="example-break" /><div class="important" title="Important: Make Sure the System Has Enough Memory"><div class="admonition_header"><h2>Important: Make Sure the System Has Enough Memory</h2></div><div class="admonition"><div class="para">
+ When the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by a user, and defaults to 128 MB, as lower values proved to be unreliable. For more information on minimum memory requirements for Fedora 14, refer to the <em class="citetitle">Required minimums</em> section of the <a href="http://www.redhat.com/rhel/compare/">Red Hat Enterprise Linux comparison chart</a>.
+ </div></div></div></div><div class="section" title="24.1.3.2. Configuring the Target Type" id="s3-kdump-configuration-cli-target"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-cli-target">24.1.3.2. Configuring the Target Type</h4></div></div></div><a id="id824585" class="indexterm"></a><div class="para">
+ When a kernel crash is captured, the core dump can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol. Note that only one of these options can be set at the moment. The default option is to store the <code class="filename">vmcore</code> file in the <code class="filename">/var/crash/</code> directory of the local file system. To change this, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, and edit the options as described below.
+ </div><div class="para">
+ To change the local directory in which the core dump is to be saved, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#path /var/crash</code> line, and replace the value with a desired directory path. Optionally, if you wish to write the file to a different partition, follow the same procedure with the <code class="literal">#ext4 /dev/sda3</code> line as well, and change both the file system type and the device (a device name, a file system label, and UUID are all supported) accordingly. For example:
+ </div><pre class="screen">ext3 /dev/sda4
+path /usr/local/cores</pre><div class="para">
+ To write the dump directly to a device, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#raw /dev/sda5</code> line, and replace the value with a desired device name. For example:
+ </div><pre class="screen">raw /dev/sdb1</pre><div class="para">
+ To store the dump to a remote machine using the NFS protocol, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#net my.server.com:/export/tmp</code> line, and replace the value with a valid hostname and directory path. For example:
+ </div><pre class="screen">net penguin.example.com:/export/cores</pre><div class="para">
+ To store the dump to a remote machine using the SSH protocol, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#net user at my.server.com</code> line, and replace the value with a valid username and hostname. For example:
+ </div><pre class="screen">net john at penguin.example.com</pre><div class="para">
+ Refer to <a class="xref" href="#ch-OpenSSH" title="Chapter 9. OpenSSH">Chapter 9, <i>OpenSSH</i></a> for information on how to configure an SSH server, and how to set up a key-based authentication.
+ </div><a id="id693393" class="indexterm"></a><div class="important" title="Important: Using the hpsa Driver for a Storage"><div class="admonition_header"><h2>Important: Using the <code class="systemitem">hpsa</code> Driver for a Storage</h2></div><div class="admonition"><div class="para">
+ Due to known issue with the <code class="systemitem">hpsa</code> driver, <code class="systemitem">kdump</code> is unable to save the dump to a storage that uses this driver for HP Smart Array Controllers. If this applies to your machine, it is advised that you save the dump to a remote system using the NFS or SSH protocol instead.
+ </div></div></div></div><div class="section" title="24.1.3.3. Configuring the Core Collector" id="s3-kdump-configuration-cli-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-cli-filtering">24.1.3.3. Configuring the Core Collector</h4></div></div></div><div class="para">
+ To reduce the size of the <code class="filename">vmcore</code> dump file, <code class="systemitem">kdump</code> allows you to specify an external application (that is, a core collector) to compress the data, and optionally leave out all irrelevant information. Currently, the only fully supported core collector is <code class="command">makedumpfile</code>.
+ </div><div class="para">
+ To enable the core collector, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#core_collector makedumpfile -c --message-level 1 -d 31</code> line, and edit the command line options as described below.
+ </div><a id="id584948" class="indexterm"></a><div class="para">
+ To enable the dump file compression, add the <code class="option">-c</code> parameter. For example:
+ </div><pre class="screen">core_collector makedumpfile -c</pre><a id="id584980" class="indexterm"></a><div class="para">
+ To remove certain pages from the dump, add the <code class="option">-d <em class="replaceable"><code>value</code></em></code> parameter, where <em class="replaceable"><code>value</code></em> is a sum of values of pages you want to omit as described in <a class="xref" href="#table-kdump-configuration-cli-filtering-makedumpfile" title="Table 24.1. Supported filtering levels">Table 24.1, “Supported filtering levels”</a>. For example, to remove both zero and free pages, use the following:
+ </div><pre class="screen">core_collector makedumpfile -d 17 -c</pre><div class="para">
+ Refer to the manual page for <code class="command">makedumpfile</code> for a complete list of available options.
+ </div><div class="table" title="Table 24.1. Supported filtering levels" id="table-kdump-configuration-cli-filtering-makedumpfile"><h6>Table 24.1. Supported filtering levels</h6><div class="table-contents"><table summary="Supported filtering levels" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">1</code>
+ </td><td>
+ Zero pages
+ </td></tr><tr><td>
+ <code class="option">2</code>
+ </td><td>
+ Cache pages
+ </td></tr><tr><td>
+ <code class="option">4</code>
+ </td><td>
+ Cache private
+ </td></tr><tr><td>
+ <code class="option">8</code>
+ </td><td>
+ User pages
+ </td></tr><tr><td>
+ <code class="option">16</code>
+ </td><td>
+ Free pages
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" title="24.1.3.4. Changing the Default Action" id="s3-kdump-configuration-cli-action"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-cli-action">24.1.3.4. Changing the Default Action</h4></div></div></div><a id="id743275" class="indexterm"></a><div class="para">
+ By default, when the kernel crash is captured, the root file system is mounted, and <code class="command">/sbin/init</code> is run. To change this behavior, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#default shell</code> line, and replace the value with a desired action as described in <a class="xref" href="#table-kdump-configuration-cli-action-actions" title="Table 24.2. Supported actions">Table 24.2, “Supported actions”</a>. For example:
+ </div><pre class="screen">default halt</pre><div class="table" title="Table 24.2. Supported actions" id="table-kdump-configuration-cli-action-actions"><h6>Table 24.2. Supported actions</h6><div class="table-contents"><table summary="Supported actions" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">reboot</code>
+ </td><td>
+ Reboot the system, losing the core in the process.
+ </td></tr><tr><td>
+ <code class="option">halt</code>
+ </td><td>
+ After attempting to capture a core, halt the system no matter if it succeeded.
+ </td></tr><tr><td>
+ <code class="option">poweroff</code>
+ </td><td>
+ Power off the system.
+ </td></tr><tr><td>
+ <code class="option">shell</code>
+ </td><td>
+ Run the <span class="application"><strong>msh</strong></span> session from within the initramfs, allowing a user to record the core manually.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" title="24.1.3.5. Enabling the Service" id="s3-kdump-configuration-cli-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-cli-enable">24.1.3.5. Enabling the Service</h4></div></div></div><a id="id562709" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">kdump</code> daemon at boot time, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">chkconfig kdump on</code></pre><div class="para">
+ This will enable the service for runlevels <code class="literal">2</code>, <code class="literal">3</code>, <code class="literal">4</code>, and <code class="literal">5</code>. Similarly, typing <code class="command">chkconfig kdump off</code> will disable it for all runlevels. To start the service in the current session, use the following command:
+ </div><a id="id588166" class="indexterm"></a><pre class="screen">~]# <code class="command">service kdump start</code>
+No kdump initial ramdisk found. [WARNING]
+Rebuilding /boot/initrd-2.6.32-54.el6.i686kdump.img
+Starting kdump: [ OK ]</pre><div class="para">
+ For more information on runlevels and configuring services in general, refer to <a class="xref" href="#ch-Controlling_Access_to_Services" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div></div></div><div class="section" title="24.1.4. Testing the Configuration" id="s2-kdump-configuration-testing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-configuration-testing">24.1.4. Testing the Configuration</h3></div></div></div><a id="id588211" class="indexterm"></a><div class="warning" title="Caution: Be Careful When Using These Commands"><div class="admonition_header"><h2>Caution: Be Careful When Using These Commands</h2></div><div class="admonition"><div class="para">
+ The commands below will cause the kernel to crash. Use caution when following these steps, and by no means use them on a production machine.
+ </div></div></div><div class="para">
+ To test the configuration, reboot the system with <code class="systemitem">kdump</code> enabled, and make sure that the service is running (refer to <a class="xref" href="#s1-services-running" title="7.3. Running the Services">Section 7.3, “Running the Services”</a> for more information on how to run a service in Fedora):
+ </div><pre class="screen">~]# <code class="command">service kdump status</code>
+Kdump is operational</pre><div class="para">
+ Then type the following commands at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">echo 1 > /proc/sys/kernel/sysrq</code>
+~]# <code class="command">echo c > /proc/sysrq-trigger</code></pre><div class="para">
+ This will force the Linux kernel to crash, and the <code class="filename"><em class="replaceable"><code>address</code></em>-<em class="replaceable"><code>YYYY-MM-DD</code></em>-<em class="replaceable"><code>HH:MM:SS</code></em>/vmcore</code> file will be copied to the location you have selected in the configuration (that is, to <code class="filename">/var/crash/</code> by default).
+ </div><div class="example" title="Example 24.2. Listing a content of /var/crash/ after a crash" id="ex-kdump-configuration-testing-vmcore"><h6>Example 24.2. Listing a content of <code class="filename">/var/crash/</code> after a crash</h6><div class="example-contents"><pre class="screen">~]# <code class="command">tree --charset=ascii /var/crash</code>
+/var/crash
+`-- 127.0.0.1-2010-08-25-08:45:02
+ `-- vmcore
+
+1 directory, 1 file</pre></div></div><br class="example-break" /></div></div><div class="section" title="24.2. Analyzing the Core Dump" id="s1-kdump-crash"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kdump-crash">24.2. Analyzing the Core Dump</h2></div></div></div><a id="id524471" class="indexterm"></a><div class="para">
+ To determine the cause of the system crash, you can use the <span class="application"><strong>crash</strong></span> utility. This utility allows you to interactively analyze a running Linux system as well as a core dump created by <code class="systemitem">netdump</code>, <code class="systemitem">diskdump</code>, <code class="systemitem">xendump</code>, or <code class="systemitem">kdump</code>. When started, it presents you with an interactive prompt very similar to the GNU Debugger (GDB).
+ </div><a id="id524517" class="indexterm"></a><div class="note" title="Note: Make Sure You Have Relevant Packages Installed"><div class="admonition_header"><h2>Note: Make Sure You Have Relevant Packages Installed</h2></div><div class="admonition"><div class="para">
+ To analyze the <code class="filename">vmcore</code> dump file, you must have the <span class="package">crash</span> and <span class="package">kernel-debuginfo</span> packages installed. To do so, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">yum install --enablerepo=rhel-debuginfo crash kernel-debuginfo</code></pre><div class="para">
+ Refer to <a class="xref" href="#sec-Installing" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><a id="id2231094" class="indexterm"></a><div class="para">
+ To start the utility, type the command in the following form at a shell prompt:
+ </div><pre class="screen"><code class="command">crash /var/crash/<em class="replaceable"><code>timestamp</code></em>/vmcore /usr/lib/debug/lib/modules/<em class="replaceable"><code>kernel</code></em>/vmlinux</code></pre><div class="para">
+ Note that the <em class="replaceable"><code>kernel</code></em> version should be the same that was captured by <code class="systemitem">kdump</code>. To find out which kernel you are currently running, use the <code class="command">uname -r</code> command.
+ </div><div class="example" title="Example 24.3. Running the crash utility" id="ex-kdump-crash-running"><h6>Example 24.3. Running the <code class="command">crash</code> utility</h6><div class="example-contents"><pre class="screen">~]# <code class="command">crash /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux \</code>
+<code class="command">/var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore</code>
+
+crash 5.0.0-23.el6
+Copyright (C) 2002-2010 Red Hat, Inc.
+Copyright (C) 2004, 2005, 2006 IBM Corporation
+Copyright (C) 1999-2006 Hewlett-Packard Co
+Copyright (C) 2005, 2006 Fujitsu Limited
+Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
+Copyright (C) 2005 NEC Corporation
+Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
+Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
+This program is free software, covered by the GNU General Public License,
+and you are welcome to change it and/or distribute copies of it under
+certain conditions. Enter "help copying" to see the conditions.
+This program has absolutely no warranty. Enter "help warranty" for details.
+
+GNU gdb (GDB) 7.0
+Copyright (C) 2009 Free Software Foundation, Inc.
+License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law. Type "show copying"
+and "show warranty" for details.
+This GDB was configured as "i686-pc-linux-gnu"...
+
+ KERNEL: /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux
+ DUMPFILE: /var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore [PARTIAL DUMP]
+ CPUS: 4
+ DATE: Wed Aug 25 08:44:47 2010
+ UPTIME: 00:09:02
+LOAD AVERAGE: 0.00, 0.01, 0.00
+ TASKS: 140
+ NODENAME: hp-dl320g5-02.lab.bos.redhat.com
+ RELEASE: 2.6.32-69.el6.i686
+ VERSION: #1 SMP Tue Aug 24 10:31:45 EDT 2010
+ MACHINE: i686 (2394 Mhz)
+ MEMORY: 8 GB
+ PANIC: "Oops: 0002 [#1] SMP " (check log for details)
+ PID: 5591
+ COMMAND: "bash"
+ TASK: f196d560 [THREAD_INFO: ef4da000]
+ CPU: 2
+ STATE: TASK_RUNNING (PANIC)
+
+crash></pre></div></div><br class="example-break" /><div class="para">
+ To exit the interactive prompt and terminate <span class="application"><strong>crash</strong></span>, type <code class="command">exit</code>.
+ </div><div class="section" title="24.2.1. Displaying the Message Buffer" id="s2-kdump-crash-log"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-crash-log">24.2.1. Displaying the Message Buffer</h3></div></div></div><a id="id1775692" class="indexterm"></a><div class="para">
+ To display the kernel message buffer, type the <code class="command">log</code> command at the interactive prompt.
+ </div><div class="example" title="Example 24.4. Displaying the kernel message buffer" id="ex-kdump-crash-log"><h6>Example 24.4. Displaying the kernel message buffer</h6><div class="example-contents"><pre class="screen">crash> <code class="command">log</code>
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+EIP: 0060:[<c068124f>] EFLAGS: 00010096 CPU: 2
+EIP is at sysrq_handle_crash+0xf/0x20
+EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000
+ESI: c0a09ca0 EDI: 00000286 EBP: 00000000 ESP: ef4dbf24
+ DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
+Process bash (pid: 5591, ti=ef4da000 task=f196d560 task.ti=ef4da000)
+Stack:
+ c068146b c0960891 c0968653 00000003 00000000 00000002 efade5c0 c06814d0
+<0> fffffffb c068150f b7776000 f2600c40 c0569ec4 ef4dbf9c 00000002 b7776000
+<0> efade5c0 00000002 b7776000 c0569e60 c051de50 ef4dbf9c f196d560 ef4dbfb4
+Call Trace:
+ [<c068146b>] ? __handle_sysrq+0xfb/0x160
+ [<c06814d0>] ? write_sysrq_trigger+0x0/0x50
+ [<c068150f>] ? write_sysrq_trigger+0x3f/0x50
+ [<c0569ec4>] ? proc_reg_write+0x64/0xa0
+ [<c0569e60>] ? proc_reg_write+0x0/0xa0
+ [<c051de50>] ? vfs_write+0xa0/0x190
+ [<c051e8d1>] ? sys_write+0x41/0x70
+ [<c0409adc>] ? syscall_call+0x7/0xb
+Code: a0 c0 01 0f b6 41 03 19 d2 f7 d2 83 e2 03 83 e0 cf c1 e2 04 09 d0 88 41 03 f3 c3 90 c7 05 c8 1b 9e c0 01 00 00 00 0f ae f8 89 f6 <c6> 05 00 00 00 00 01 c3 89 f6 8d bc 27 00 00 00 00 8d 50 d0 83
+EIP: [<c068124f>] sysrq_handle_crash+0xf/0x20 SS:ESP 0068:ef4dbf24
+CR2: 0000000000000000</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help log</code> for more information on the command usage.
+ </div></div><div class="section" title="24.2.2. Displaying a Backtrace" id="s2-kdump-crash-backtrace"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-crash-backtrace">24.2.2. Displaying a Backtrace</h3></div></div></div><a id="id1338223" class="indexterm"></a><div class="para">
+ To display the kernel stack trace, type the <code class="command">bt</code> command at the interactive prompt. You can use <code class="command">bt <em class="replaceable"><code>pid</code></em></code> to display the backtrace of the selected process.
+ </div><div class="example" title="Example 24.5. Displaying the kernel stack trace" id="ex-kdump-crash-backtrace"><h6>Example 24.5. Displaying the kernel stack trace</h6><div class="example-contents"><pre class="screen">crash> <code class="command">bt</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ #0 [ef4dbdcc] crash_kexec at c0494922
+ #1 [ef4dbe20] oops_end at c080e402
+ #2 [ef4dbe34] no_context at c043089d
+ #3 [ef4dbe58] bad_area at c0430b26
+ #4 [ef4dbe6c] do_page_fault at c080fb9b
+ #5 [ef4dbee4] error_code (via page_fault) at c080d809
+ EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000 EBP: 00000000
+ DS: 007b ESI: c0a09ca0 ES: 007b EDI: 00000286 GS: 00e0
+ CS: 0060 EIP: c068124f ERR: ffffffff EFLAGS: 00010096
+ #6 [ef4dbf18] sysrq_handle_crash at c068124f
+ #7 [ef4dbf24] __handle_sysrq at c0681469
+ #8 [ef4dbf48] write_sysrq_trigger at c068150a
+ #9 [ef4dbf54] proc_reg_write at c0569ec2
+#10 [ef4dbf74] vfs_write at c051de4e
+#11 [ef4dbf94] sys_write at c051e8cc
+#12 [ef4dbfb0] system_call at c0409ad5
+ EAX: ffffffda EBX: 00000001 ECX: b7776000 EDX: 00000002
+ DS: 007b ESI: 00000002 ES: 007b EDI: b7776000
+ SS: 007b ESP: bfcb2088 EBP: bfcb20b4 GS: 0033
+ CS: 0073 EIP: 00edc416 ERR: 00000004 EFLAGS: 00000246</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help bt</code> for more information on the command usage.
+ </div></div><div class="section" title="24.2.3. Displaying a Process Status" id="s2-kdump-crash-processes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-crash-processes">24.2.3. Displaying a Process Status</h3></div></div></div><a id="id470468" class="indexterm"></a><div class="para">
+ To display status of processes in the system, type the <code class="command">ps</code> command at the interactive prompt. You can use <code class="command">ps <em class="replaceable"><code>pid</code></em></code> to display the status of the selected process.
+ </div><div class="example" title="Example 24.6. Displaying status of processes in the system" id="ex-kdump-crash-processes"><h6>Example 24.6. Displaying status of processes in the system</h6><div class="example-contents"><pre class="screen">crash> <code class="command">ps</code>
+ PID PPID CPU TASK ST %MEM VSZ RSS COMM
+> 0 0 0 c09dc560 RU 0.0 0 0 [swapper]
+> 0 0 1 f7072030 RU 0.0 0 0 [swapper]
+ 0 0 2 f70a3a90 RU 0.0 0 0 [swapper]
+> 0 0 3 f70ac560 RU 0.0 0 0 [swapper]
+ 1 0 1 f705ba90 IN 0.0 2828 1424 init
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+ 5566 1 1 f2592560 IN 0.0 12876 784 auditd
+ 5567 1 2 ef427560 IN 0.0 12876 784 auditd
+ 5587 5132 0 f196d030 IN 0.0 11064 3184 sshd
+> 5591 5587 2 f196d560 RU 0.0 5084 1648 bash</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help ps</code> for more information on the command usage.
+ </div></div><div class="section" title="24.2.4. Displaying Virtual Memory Information" id="s2-kdump-crash-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-crash-memory">24.2.4. Displaying Virtual Memory Information</h3></div></div></div><a id="id528924" class="indexterm"></a><div class="para">
+ To display basic virtual memory information, type the <code class="command">vm</code> command at the interactive prompt. You can use <code class="command">vm <em class="replaceable"><code>pid</code></em></code> to display information on the selected process.
+ </div><div class="example" title="Example 24.7. Displaying virtual memory information of the current context" id="ex-kdump-crash-memory"><h6>Example 24.7. Displaying virtual memory information of the current context</h6><div class="example-contents"><pre class="screen">crash> <code class="command">vm</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ MM PGD RSS TOTAL_VM
+f19b5900 ef9c6000 1648k 5084k
+ VMA START END FLAGS FILE
+f1bb0310 242000 260000 8000875 /lib/ld-2.12.so
+f26af0b8 260000 261000 8100871 /lib/ld-2.12.so
+efbc275c 261000 262000 8100873 /lib/ld-2.12.so
+efbc2a18 268000 3ed000 8000075 /lib/libc-2.12.so
+efbc23d8 3ed000 3ee000 8000070 /lib/libc-2.12.so
+efbc2888 3ee000 3f0000 8100071 /lib/libc-2.12.so
+efbc2cd4 3f0000 3f1000 8100073 /lib/libc-2.12.so
+efbc243c 3f1000 3f4000 100073
+efbc28ec 3f6000 3f9000 8000075 /lib/libdl-2.12.so
+efbc2568 3f9000 3fa000 8100071 /lib/libdl-2.12.so
+efbc2f2c 3fa000 3fb000 8100073 /lib/libdl-2.12.so
+f26af888 7e6000 7fc000 8000075 /lib/libtinfo.so.5.7
+f26aff2c 7fc000 7ff000 8100073 /lib/libtinfo.so.5.7
+efbc211c d83000 d8f000 8000075 /lib/libnss_files-2.12.so
+efbc2504 d8f000 d90000 8100071 /lib/libnss_files-2.12.so
+efbc2950 d90000 d91000 8100073 /lib/libnss_files-2.12.so
+f26afe00 edc000 edd000 4040075
+f1bb0a18 8047000 8118000 8001875 /bin/bash
+f1bb01e4 8118000 811d000 8101873 /bin/bash
+f1bb0c70 811d000 8122000 100073
+f26afae0 9fd9000 9ffa000 100073
+<span class="emphasis"><em>... several lines omitted ...</em></span></pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help vm</code> for more information on the command usage.
+ </div></div><div class="section" title="24.2.5. Displaying Open Files" id="s2-kdump-crash-files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-crash-files">24.2.5. Displaying Open Files</h3></div></div></div><a id="id493161" class="indexterm"></a><div class="para">
+ To display information about open files, type the <code class="command">files</code> command at the interactive prompt. You can use <code class="command">files <em class="replaceable"><code>pid</code></em></code> to display files opened by the selected process.
+ </div><div class="example" title="Example 24.8. Displaying information about open files of the current context" id="ex-kdump-crash-files"><h6>Example 24.8. Displaying information about open files of the current context</h6><div class="example-contents"><pre class="screen">crash> <code class="command">files</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ROOT: / CWD: /root
+ FD FILE DENTRY INODE TYPE PATH
+ 0 f734f640 eedc2c6c eecd6048 CHR /pts/0
+ 1 efade5c0 eee14090 f00431d4 REG /proc/sysrq-trigger
+ 2 f734f640 eedc2c6c eecd6048 CHR /pts/0
+ 10 f734f640 eedc2c6c eecd6048 CHR /pts/0
+255 f734f640 eedc2c6c eecd6048 CHR /pts/0</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help files</code> for more information on the command usage.
+ </div></div></div><div class="section" title="24.3. Additional Resources" id="s1-kdump-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kdump-resources">24.3. Additional Resources</h2></div></div></div><div class="section" title="24.3.1. Installed Documentation" id="s2-kdump-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-resources-installed">24.3.1. Installed Documentation</h3></div></div></div><a id="id599113" class="indexterm"></a><a id="id599133" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="command">man kdump.conf</code></span></dt><dd><div class="para">
+ The manual page for the <code class="filename">/etc/kdump.conf</code> configuration file containing the full documentation of available options.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man makedumpfile</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">makedumpfile</code> core collector containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man kexec</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">kexec</code> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man crash</code></span></dt><dd><div class="para">
+ The manual page for the <span class="application"><strong>crash</strong></span> utility containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/kexec-tools-<em class="replaceable"><code>version</code></em>/kexec-kdump-howto.txt</code></span></dt><dd><div class="para">
+ An overview of the <code class="systemitem">kdump</code> and <code class="command">kexec</code> installation and usage.
+ </div></dd></dl></div></div><div class="section" title="24.3.2. Useful Websites" id="s2-kdump-resources-online"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-resources-online">24.3.2. Useful Websites</h3></div></div></div><a id="id630705" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><a href="https://access.redhat.com/kb/docs/DOC-6039">https://access.redhat.com/kb/docs/DOC-6039</a></span></dt><dd><div class="para">
+ The Red Hat Knowledgebase article about the <code class="command">kexec</code> and <code class="systemitem">kdump</code> configuration.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://people.redhat.com/anderson/">http://people.redhat.com/anderson/</a></span></dt><dd><div class="para">
+ The <span class="application"><strong>crash</strong></span> utility homepage.
+ </div></dd></dl></div></div></div></div></div><div xml:lang="en-US" class="appendix" title="Appendix A. Revision History" id="app-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 2</td><td align="left">Sun Nov 14 2010</td><td align="left"><span class="author"><span class="firstname">Jaromír</span> <span class="surname">Hradílek</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Fedora 14 Release of the <em class="citetitle">Deployment Guide</em>.</td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 1</td><td align="left">Mon Nov 16 2009</td><td align="left"><span class="author"><span class="firstname">Douglas</span> <span class="surname">Silas</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Initialization of the Fedora 13 <em class="citetitle">Deployment Guide</em>.</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><div class="index" title="Index" id="id703416"><div class="titlepage"><div><div><h2 class="title">Index</h2></div></div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt> .fetchmailrc , <a class="indexterm" href="#s3-email-mda-fetchmail-configuration">Fetchmail Configuration Options</a></dt><dd><dl><dt>server options, <a class="indexterm" href="#s3-email-mda-fetchmail-configuration-server">Server Options</a></dt><dt>user options, <a class="indexterm" href="#s3-email-fetchmail-configuration-user">User Options</a></dt></dl></dd><dt>.htaccess, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dd><dl><dt>(see also Apache HTTP Server)</dt></dl></dd><dt>.htpasswd, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dd><dl><dt>(see also Apache HTTP Server)</dt></dl></dd><dt> .procmailrc , <a class="indexterm" href="#s2-email-procmail-configuration">Procmai
l Configuration</a></dt><dt> /dev/shm , <a class="indexterm" href="#s1-sysinfo-filesystems">File Systems</a></dt><dt>/etc/named.conf (see BIND)</dt><dt> /etc/sysconfig/ directory (see sysconfig directory)</dt><dt> /etc/sysconfig/dhcpd , <a class="indexterm" href="#id634664">Starting and Stopping the Server</a></dt><dt> /proc/ directory, <a class="indexterm" href="#s2-sysinfo-installed-docs">Installed Documentation</a> (see proc file system)</dt><dt> /var/spool/anacron , <a class="indexterm" href="#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt><dt> /var/spool/cron , <a class="indexterm" href="#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>Access Control</dt><dd><dl><dt>configuring in SSSD, <a class="indexterm" href="#id777113">Configuring Access Control</a></dt><dt>in SSSD, rules, <a class="indexterm" href="#id734737">The Simple Access Provider</a></dt></dl></dd><dt>adding</dt><dd><dl><dt>group, <a
class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt><dt>user, <a class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>anacron, <a class="indexterm" href="#s1-autotasks-cron-anacron">Cron and Anacron</a></dt><dd><dl><dt>anacron configuration file, <a class="indexterm" href="#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt><dt>user-defined tasks, <a class="indexterm" href="#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt></dl></dd><dt> anacrontab , <a class="indexterm" href="#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt><dt>Apache HTTP Server</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-apache-resources-installed">Installed Documentation</a></dt><dt>useful websites, <a class="indexterm" href="#s2-apache-resources-web">Useful Websites</a></dt></dl></dd><dt>checking configuration, <a class="indexterm" hre
f="#s1-apache-editing">Editing the Configuration Files</a></dt><dt>checking status, <a class="indexterm" href="#s3-apache-running-status">Checking the Service Status</a></dt><dt>directives</dt><dd><dl><dt><Directory>, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt><IfDefine>, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt><IfModule>, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt><Location>, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt><Proxy>, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt><VirtualHost>, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AccessFileName, <a class="indexterm" href="#s2-apache-httpdconf-direc
tives">Common httpd.conf Directives</a></dt><dt>Action, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddDescription, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddEncoding, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddHandler, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddIcon, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddIconByEncoding, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddIconByType, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddLanguage, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddType, <a class="indexterm
" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Alias, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Allow, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AllowOverride, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>BrowserMatch, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheDefaultExpire, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheDisable, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheEnable, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheLastModifiedFactor, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directi
ves</a></dt><dt>CacheMaxExpire, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheNegotiatedDocs, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheRoot, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CustomLog, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>DefaultIcon, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>DefaultType, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Deny, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>DirectoryIndex, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>DocumentRoot, <a class="indexterm" href="#s2-apache-httpdc
onf-directives">Common httpd.conf Directives</a></dt><dt>ErrorDocument, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ErrorLog, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ExtendedStatus, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Group, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>HeaderName, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>HostnameLookups, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Include, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>IndexIgnore, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>IndexOptions, <a class="i
ndexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>KeepAlive, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>KeepAliveTimeout, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>LanguagePriority, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Listen, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>LoadModule, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>LogFormat, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>LogLevel, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>MaxClients, <a class="indexterm" href="#s2-apache-mpm-common">Common Multi-Processing Module Directives<
/a></dt><dt>MaxKeepAliveRequests, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>MaxSpareServers, <a class="indexterm" href="#s2-apache-mpm-common">Common Multi-Processing Module Directives</a></dt><dt>MaxSpareThreads, <a class="indexterm" href="#s2-apache-mpm-common">Common Multi-Processing Module Directives</a></dt><dt>MinSpareServers, <a class="indexterm" href="#s2-apache-mpm-common">Common Multi-Processing Module Directives</a></dt><dt>MinSpareThreads, <a class="indexterm" href="#s2-apache-mpm-common">Common Multi-Processing Module Directives</a></dt><dt>NameVirtualHost, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Options, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Order, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>PidFile, <a class="indexterm" href
="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ProxyRequests, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ReadmeName, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Redirect, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ScriptAlias, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ServerAdmin, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ServerName, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ServerRoot, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ServerSignature, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>S
erverTokens, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>SetEnvIf, <a class="indexterm" href="#s2-apache-sslconf-common">Common ssl.conf Directives</a></dt><dt>StartServers, <a class="indexterm" href="#s2-apache-mpm-common">Common Multi-Processing Module Directives</a></dt><dt>SuexecUserGroup, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ThreadsPerChild, <a class="indexterm" href="#s2-apache-mpm-common">Common Multi-Processing Module Directives</a></dt><dt>Timeout, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>TypesConfig, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>UseCanonicalName, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>User, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common
httpd.conf Directives</a></dt><dt>UserDir, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/httpd/, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/etc/httpd/conf.d/, <a class="indexterm" href="#s1-apache-editing">Editing the Configuration Files</a>, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/usr/lib/httpd/modules/, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a>, <a class="indexterm" href="#s1-apache-dso">Working with Modules</a></dt><dt>/usr/lib64/httpd/modules/, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a>, <a class="indexterm" href="#s1-apache-dso">Working with Modules</a></dt><dt>/var/cache/mod_proxy/, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd
.conf Directives</a></dt><dt>/var/www/cgi-bin/, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/var/www/html/, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/var/www/icons/, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>~/public_html/, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt></dl></dd><dt>files</dt><dd><dl><dt>.htaccess, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>.htpasswd, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/etc/httpd/conf.d/ssl.conf, <a class="indexterm" href="#s2-apache-sslconf-common">Common ssl.conf Directives</a>, <a class="indexterm" href="#s2-apache-mod_ssl-enabling">Enabling the mod_ssl Module</a></dt><dt>/etc/httpd/conf/httpd.
conf, <a class="indexterm" href="#s1-apache-editing">Editing the Configuration Files</a>, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a>, <a class="indexterm" href="#s2-apache-mpm-common">Common Multi-Processing Module Directives</a></dt><dt>/etc/httpd/logs/access_log, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/etc/httpd/logs/error_log, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/etc/httpd/run/httpd.pid, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/etc/mime.types, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt></dl></dd><dt>modules</dt><dd><dl><dt>developing, <a class="indexterm" href="#s2-apache-dso-writing">Writing a Module</a></dt><dt>loading, <a class="indexterm" href="#s2-apache-dso-loading">Loading a Mod
ule</a></dt><dt>mod_asis, <a class="indexterm" href="#s2-apache-version2-changes">Notable Changes</a></dt><dt>mod_cache, <a class="indexterm" href="#s2-apache-version2-features">New Features</a></dt><dt>mod_cern_meta, <a class="indexterm" href="#s2-apache-version2-changes">Notable Changes</a></dt><dt>mod_disk_cache, <a class="indexterm" href="#s2-apache-version2-features">New Features</a></dt><dt>mod_ext_filter, <a class="indexterm" href="#s2-apache-version2-changes">Notable Changes</a></dt><dt>mod_proxy_balancer, <a class="indexterm" href="#s2-apache-version2-features">New Features</a></dt><dt>mod_rewrite, <a class="indexterm" href="#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>mod_ssl, <a class="indexterm" href="#s1-apache-mod_ssl">Setting Up an SSL Server</a></dt><dt>mod_userdir, <a class="indexterm" href="#s1-apache-version2-migrating">Updating the Configuration</a></dt></dl></dd><dt>restarting, <a class="indexterm" href="#s3-apache-running-re
starting">Restarting the Service</a></dt><dt>SSL server</dt><dd><dl><dt>certificate, <a class="indexterm" href="#s2-apache-mod_ssl-certificates">An Overview of Certificates and Security</a>, <a class="indexterm" href="#s2-apache-mod_ssl-keypair">Using an Existing Key and Certificate</a>, <a class="indexterm" href="#s2-apache-mod_ssl-genkey">Generating a New Key and Certificate</a></dt><dt>certificate authority, <a class="indexterm" href="#s2-apache-mod_ssl-certificates">An Overview of Certificates and Security</a></dt><dt>private key, <a class="indexterm" href="#s2-apache-mod_ssl-certificates">An Overview of Certificates and Security</a>, <a class="indexterm" href="#s2-apache-mod_ssl-keypair">Using an Existing Key and Certificate</a>, <a class="indexterm" href="#s2-apache-mod_ssl-genkey">Generating a New Key and Certificate</a></dt><dt>public key, <a class="indexterm" href="#s2-apache-mod_ssl-certificates">An Overview of Certificates and Security</a></dt></dl></dd><dt>starti
ng, <a class="indexterm" href="#s2-apache-running-starting">Starting the Service</a></dt><dt>stopping, <a class="indexterm" href="#s2-apache-running-stopping">Stopping the Service</a></dt><dt>version 2.2</dt><dd><dl><dt>changes, <a class="indexterm" href="#s2-apache-version2-changes">Notable Changes</a></dt><dt>features, <a class="indexterm" href="#s2-apache-version2-features">New Features</a></dt><dt>updating from version 2.0, <a class="indexterm" href="#s1-apache-version2-migrating">Updating the Configuration</a></dt></dl></dd><dt>virtual host, <a class="indexterm" href="#s1-apache-virtualhosts">Setting Up Virtual Hosts</a></dt></dl></dd><dt> at , <a class="indexterm" href="#s1-autotasks-at-batch">At and Batch</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-autotasks-additional-resources">Additional Resources</a></dt></dl></dd><dt> authconfig (see Authentication Configuration Tool )</dt><dd><dl><dt> commands , <a class="indexterm" href="#sect-The
_Authentication_Configuration_Tool-Command_Line_Version">Command Line Version</a></dt></dl></dd><dt>authentication</dt><dd><dl><dt> Authentication Configuration Tool , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool">The Authentication Configuration Tool</a></dt><dt> using fingerprint support , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">Advanced Options</a></dt><dt> using smart card authentication , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Advanced_Options">Advanced Options</a></dt></dl></dd><dt> Authentication Configuration Tool </dt><dd><dl><dt> and Kerberos authentication , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt><dt> and LDAP , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt><dt> and NIS ,
<a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt><dt> and NIS authentication , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt><dt> and Winbind , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt><dt> and Winbind authentication , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt></dl></dd><dt>authoritative nameserver (see BIND)</dt><dt>Automated Tasks, <a class="indexterm" href="#ch-Automated_Tasks">Automated Tasks</a></dt></dl></div><div class="indexdiv"><h3>B</h3><dl><dt> batch , <a class="indexterm" href="#s1-autotasks-at-batch">At and Batch</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-autotasks
-additional-resources">Additional Resources</a></dt></dl></dd><dt>Berkeley Internet Name Domain (see BIND)</dt><dt>BIND</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-bind-installed-docs">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="#s2-bind-related-books">Related Books</a></dt><dt>useful websites, <a class="indexterm" href="#s2-bind-useful-websites">Useful Websites</a></dt></dl></dd><dt>common mistakes, <a class="indexterm" href="#s1-bind-mistakes">Common Mistakes to Avoid</a></dt><dt>configuration</dt><dd><dl><dt>acl statement, <a class="indexterm" href="#s2-bind-namedconf-state">Common Statement Types</a></dt><dt>comment tags, <a class="indexterm" href="#s2-bind-namedconf-comm">Comment Tags</a></dt><dt>controls statement, <a class="indexterm" href="#s2-bind-namedconf-state-other">Other Statement Types</a></dt><dt>include statement, <a class="indexterm" href="#s2-bind-namedconf-s
tate">Common Statement Types</a></dt><dt>key statement, <a class="indexterm" href="#s2-bind-namedconf-state-other">Other Statement Types</a></dt><dt>logging statement, <a class="indexterm" href="#s2-bind-namedconf-state-other">Other Statement Types</a></dt><dt>options statement, <a class="indexterm" href="#s2-bind-namedconf-state">Common Statement Types</a></dt><dt>server statement, <a class="indexterm" href="#s2-bind-namedconf-state-other">Other Statement Types</a></dt><dt>trusted-keys statement, <a class="indexterm" href="#s2-bind-namedconf-state-other">Other Statement Types</a></dt><dt>view statement, <a class="indexterm" href="#s2-bind-namedconf-state-other">Other Statement Types</a></dt><dt>zone statement, <a class="indexterm" href="#s2-bind-namedconf-state">Common Statement Types</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/named/, <a class="indexterm" href="#s1-bind-namedconf">Configuring the named Service</a></dt><dt>/var/named/, <a class="indexterm" href="
#s1-bind-zone">Editing Zone Files</a></dt><dt>/var/named/data/, <a class="indexterm" href="#s1-bind-zone">Editing Zone Files</a></dt><dt>/var/named/dynamic/, <a class="indexterm" href="#s1-bind-zone">Editing Zone Files</a></dt><dt>/var/named/slaves/, <a class="indexterm" href="#s1-bind-zone">Editing Zone Files</a></dt></dl></dd><dt>features</dt><dd><dl><dt>Automatic Zone Transfer (AXFR), <a class="indexterm" href="#s2-bind-features-ixfr">Incremental Zone Transfers (IXFR)</a></dt><dt>DNS Security Extensions (DNSSEC), <a class="indexterm" href="#s2-bind-features-dnssec">DNS Security Extensions (DNSSEC)</a></dt><dt>Incremental Zone Transfer (IXFR), <a class="indexterm" href="#s2-bind-features-ixfr">Incremental Zone Transfers (IXFR)</a></dt><dt>Internet Protocol version 6 (IPv6), <a class="indexterm" href="#s2-bind-features-ipv6">Internet Protocol version 6 (IPv6)</a></dt><dt>multiple views, <a class="indexterm" href="#s2-bind-features-views">Multiple Views</a></dt><dt>Transacti
on SIGnature (TSIG), <a class="indexterm" href="#s2-bind-features-tsig">Transaction SIGnatures (TSIG)</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/etc/named.conf, <a class="indexterm" href="#s1-bind-namedconf">Configuring the named Service</a>, <a class="indexterm" href="#s2-bind-rndc-configuration">Configuring the Utility</a></dt><dt>/etc/rndc.conf, <a class="indexterm" href="#s2-bind-rndc-configuration">Configuring the Utility</a></dt><dt>/etc/rndc.key, <a class="indexterm" href="#s2-bind-rndc-configuration">Configuring the Utility</a></dt></dl></dd><dt>resource record, <a class="indexterm" href="#s2-bind-introduction-zones">Nameserver Zones</a></dt><dt>types</dt><dd><dl><dt>authoritative nameserver, <a class="indexterm" href="#s2-bind-introduction-nameservers">Nameserver Types</a></dt><dt>primary (master) nameserver, <a class="indexterm" href="#s2-bind-introduction-zones">Nameserver Zones</a>, <a class="indexterm" href="#s2-bind-introduction-nameservers">Nameserver Types<
/a></dt><dt>recursive nameserver, <a class="indexterm" href="#s2-bind-introduction-nameservers">Nameserver Types</a></dt><dt>secondary (slave) nameserver, <a class="indexterm" href="#s2-bind-introduction-zones">Nameserver Zones</a>, <a class="indexterm" href="#s2-bind-introduction-nameservers">Nameserver Types</a></dt></dl></dd><dt>utilities</dt><dd><dl><dt>dig, <a class="indexterm" href="#s2-bind-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="#s1-bind-dig">Using the dig Utility</a>, <a class="indexterm" href="#s2-bind-features-dnssec">DNS Security Extensions (DNSSEC)</a></dt><dt>named, <a class="indexterm" href="#s2-bind-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="#s1-bind-namedconf">Configuring the named Service</a></dt><dt>rndc, <a class="indexterm" href="#s2-bind-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="#s1-bind-rndc">Using the rndc Utility</a></dt></dl></dd><dt>zones</dt><dd><dl><dt>$INC
LUDE directive, <a class="indexterm" href="#s2-bind-zone-directives">Common Directives</a></dt><dt>$ORIGIN directive, <a class="indexterm" href="#s2-bind-zone-directives">Common Directives</a></dt><dt>$TTL directive, <a class="indexterm" href="#s2-bind-zone-directives">Common Directives</a></dt><dt>A (Address) resource record, <a class="indexterm" href="#s3-bind-zone-rr">Common Resource Records</a></dt><dt>CNAME (Canonical Name) resource record, <a class="indexterm" href="#s3-bind-zone-rr">Common Resource Records</a></dt><dt>comment tags, <a class="indexterm" href="#s2-bind-zone-comm">Comment Tags</a></dt><dt>description, <a class="indexterm" href="#s2-bind-introduction-zones">Nameserver Zones</a></dt><dt>example usage, <a class="indexterm" href="#s3-bind-zone-examples-basic">A Simple Zone File</a>, <a class="indexterm" href="#s2-bind-configuration-zone-reverse">A Reverse Name Resolution Zone File</a></dt><dt>MX (Mail Exchange) resource record, <a class="indexterm" href="#s3
-bind-zone-rr">Common Resource Records</a></dt><dt>NS (Nameserver) resource record, <a class="indexterm" href="#s3-bind-zone-rr">Common Resource Records</a></dt><dt>PTR (Pointer) resource record, <a class="indexterm" href="#s3-bind-zone-rr">Common Resource Records</a></dt><dt>SOA (Start of Authority) resource record, <a class="indexterm" href="#s3-bind-zone-rr">Common Resource Records</a></dt></dl></dd></dl></dd><dt>block devices, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt><dd><dl><dt>(see also /proc/devices )</dt><dt>definition of, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt></dl></dd><dt>bonding (see channel bonding)</dt><dt>boot loader</dt><dd><dl><dt>verifying, <a class="indexterm" href="#s1-kernel-boot-loader">Verifying the Boot Loader</a></dt></dl></dd><dt>boot media, <a class="indexterm" href="#s1-kernel-preparing">Preparing to Upgrade</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>ch-email .fetchmailrc <
/dt><dd><dl><dt>global options, <a class="indexterm" href="#s3-email-mda-fetchmail-configuration-global">Global Options</a></dt></dl></dd><dt> chage command</dt><dd><dl><dt>forcing password expiration with, <a class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>channel bonding</dt><dd><dl><dt>configuration, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dt>description, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dt>interface</dt><dd><dl><dt>configuration of, <a class="indexterm" href="#s2-networkscripts-interfaces-chan">Channel Bonding Interfaces</a></dt></dl></dd><dt>parameters to bonded interfaces, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>channel bonding interface (see kernel module)</dt><dt>character devices, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt><dd><dl><d
t>(see also /proc/devices )</dt><dt>definition of, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt></dl></dd><dt> chkconfig (see services configuration)</dt><dt>Configuration File Changes, <a class="indexterm" href="#sec-Preserving_Configuration_File_Changes">Preserving Configuration File Changes</a></dt><dt>crash</dt><dd><dl><dt>analyzing the dump</dt><dd><dl><dt>message buffer, <a class="indexterm" href="#s2-kdump-crash-log">Displaying the Message Buffer</a></dt><dt>open files, <a class="indexterm" href="#s2-kdump-crash-files">Displaying Open Files</a></dt><dt>processes, <a class="indexterm" href="#s2-kdump-crash-processes">Displaying a Process Status</a></dt><dt>stack trace, <a class="indexterm" href="#s2-kdump-crash-backtrace">Displaying a Backtrace</a></dt><dt>virtual memory, <a class="indexterm" href="#s2-kdump-crash-memory">Displaying Virtual Memory Information</a></dt></dl></dd><dt>opening the dump image, <a class="indexterm" href="#s1-kdump-cr
ash">Analyzing the Core Dump</a></dt><dt>system requirements, <a class="indexterm" href="#s1-kdump-crash">Analyzing the Core Dump</a></dt></dl></dd><dt>Cron, <a class="indexterm" href="#ch-Automated_Tasks">Automated Tasks</a></dt><dt> cron , <a class="indexterm" href="#s1-autotasks-cron-anacron">Cron and Anacron</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-autotasks-additional-resources">Additional Resources</a></dt><dt>cron configuration file, <a class="indexterm" href="#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt><dt>user-defined tasks, <a class="indexterm" href="#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></dd><dt> crontab , <a class="indexterm" href="#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt> date (see date configuration)</dt><dt>date configuration</dt><dd><dl><dt> date , <a class="indexterm" href="#sect-Date_and_Time_Configuration-Command_Line_Con
figuration-Date_and_Time">Date and Time Setup</a></dt><dt> system-config-date , <a class="indexterm" href="#sect-Date_and_Time_Configuration-Date_and_Time">Date and Time Properties</a></dt></dl></dd><dt>deleting cache files</dt><dd><dl><dt>in SSSD, <a class="indexterm" href="#sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">Support for Multiple Domains</a></dt></dl></dd><dt>Denial of Service attack, <a class="indexterm" href="#s3-proc-sys-net"> /proc/sys/net/ </a></dt><dd><dl><dt>(see also /proc/sys/net/ directory)</dt><dt>definition of, <a class="indexterm" href="#s3-proc-sys-net"> /proc/sys/net/ </a></dt></dl></dd><dt> df , <a class="indexterm" href="#s1-sysinfo-filesystems">File Systems</a></dt><dt>DHCP, <a class="indexterm" href="#ch-Dynamic_Host_Configuration_Protocol_DHCP">Dynamic Host Configuration Protocol (DHCP)</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-dhcp-additional-resources">Additional Resources</a></dt><dt>client
configuration, <a class="indexterm" href="#s1-dhcp-configuring-client">Configuring a DHCP Client</a></dt><dt>command line options, <a class="indexterm" href="#id634664">Starting and Stopping the Server</a></dt><dt>connecting to, <a class="indexterm" href="#s1-dhcp-configuring-client">Configuring a DHCP Client</a></dt><dt>dhcpd.conf, <a class="indexterm" href="#config-file">Configuration File</a></dt><dt> dhcpd.leases , <a class="indexterm" href="#id634664">Starting and Stopping the Server</a></dt><dt>dhcpd6.conf, <a class="indexterm" href="#s1-dhcp_for_ipv6_dhcpv6">DHCP for IPv6 (DHCPv6)</a></dt><dt>DHCPv6, <a class="indexterm" href="#s1-dhcp_for_ipv6_dhcpv6">DHCP for IPv6 (DHCPv6)</a></dt><dt> dhcrelay , <a class="indexterm" href="#dhcp-relay-agent">DHCP Relay Agent</a></dt><dt>global parameters, <a class="indexterm" href="#config-file">Configuration File</a></dt><dt>group, <a class="indexterm" href="#config-file">Configuration File</a></dt><dt>options, <a class="indexterm
" href="#config-file">Configuration File</a></dt><dt>reasons for using, <a class="indexterm" href="#s1-dhcp-why">Why Use DHCP?</a></dt><dt>Relay Agent, <a class="indexterm" href="#dhcp-relay-agent">DHCP Relay Agent</a></dt><dt>server configuration, <a class="indexterm" href="#s1-dhcp-configuring-server">Configuring a DHCP Server</a></dt><dt> shared-network , <a class="indexterm" href="#config-file">Configuration File</a></dt><dt>starting the server, <a class="indexterm" href="#id634664">Starting and Stopping the Server</a></dt><dt>stopping the server, <a class="indexterm" href="#id634664">Starting and Stopping the Server</a></dt><dt>subnet, <a class="indexterm" href="#config-file">Configuration File</a></dt></dl></dd><dt>dhcpd.conf, <a class="indexterm" href="#config-file">Configuration File</a></dt><dt>dhcpd.leases, <a class="indexterm" href="#id634664">Starting and Stopping the Server</a></dt><dt> dhcrelay , <a class="indexterm" href="#dhcp-relay-agent">DHCP Relay Agent</a
></dt><dt>dig (see BIND)</dt><dt>DNS</dt><dd><dl><dt>definition, <a class="indexterm" href="#ch-The_BIND_DNS_Server">The BIND DNS Server</a></dt><dd><dl><dt>(see also BIND)</dt></dl></dd></dl></dd><dt>documentation</dt><dd><dl><dt>finding installed, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt></dl></dd><dt>DoS attack (see Denial of Service attack)</dt><dt>drivers (see kernel module)</dt><dt>DSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt> du , <a class="indexterm" href="#s1-sysinfo-filesystems">File Systems</a></dt><dt>Dynamic Host Configuration Protocol (see DHCP)</dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>email</dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-email-additional-resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-email-
installed-docs">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="#s2-email-related-books">Related Books</a></dt><dt>useful websites, <a class="indexterm" href="#s2-email-useful-websites">Useful Websites</a></dt></dl></dd><dt>Fetchmail, <a class="indexterm" href="#s2-email-mta-fetchmail">Fetchmail</a></dt><dt>history of, <a class="indexterm" href="#ch-email">Email</a></dt><dt>mail server</dt><dd><dl><dt>Dovecot, <a class="indexterm" href="#s3-mail-server-dovecot">Dovecot</a></dt></dl></dd><dt>Postfix, <a class="indexterm" href="#s2-email-mta-postfix">Postfix</a></dt><dt>Procmail, <a class="indexterm" href="#s1-email-mda">Mail Delivery Agents</a></dt><dt>program classifications, <a class="indexterm" href="#s1-email-types">Email Program Classifications</a></dt><dt>protocols, <a class="indexterm" href="#s1-email-protocols">Email Protocols</a></dt><dd><dl><dt>IMAP, <a class="indexterm" href="#s3-email-protocols-imap">IMAP</a></dt><dt>POP, <a class="in
dexterm" href="#s3-email-protocols-pop">POP</a></dt><dt>SMTP, <a class="indexterm" href="#s3-email-protocols-smtp">SMTP</a></dt></dl></dd><dt>security, <a class="indexterm" href="#s2-email-security">Securing Communication</a></dt><dd><dl><dt>clients, <a class="indexterm" href="#s3-email-security-clients">Secure Email Clients</a></dt><dt>servers, <a class="indexterm" href="#s3-email-security-servers">Securing Email Client Communications</a></dt></dl></dd><dt>Sendmail, <a class="indexterm" href="#s2-email-mta-sendmail">Sendmail</a></dt><dt>spam</dt><dd><dl><dt>filtering out, <a class="indexterm" href="#s3-email-mda-spam">Spam Filters</a></dt></dl></dd><dt>types</dt><dd><dl><dt>Mail Delivery Agent, <a class="indexterm" href="#s2-email-types-mda">Mail Delivery Agent</a></dt><dt>Mail Transport Agent, <a class="indexterm" href="#s2-email-types-mta">Mail Transport Agent</a></dt><dt>Mail User Agent, <a class="indexterm" href="#s2-email-types-mua">Mail User Agent</a></dt></dl></dd></
dl></dd><dt>epoch, <a class="indexterm" href="#s2-proc-stat"> /proc/stat </a></dt><dd><dl><dt>(see also /proc/stat )</dt><dt>definition of, <a class="indexterm" href="#s2-proc-stat"> /proc/stat </a></dt></dl></dd><dt>Ethernet (see network)</dt><dt> exec-shield </dt><dd><dl><dt>enabling, <a class="indexterm" href="#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt>introducing, <a class="indexterm" href="#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt></dl></dd><dt>execution domains, <a class="indexterm" href="#s2-proc-execdomains"> /proc/execdomains </a></dt><dd><dl><dt>(see also /proc/execdomains )</dt><dt>definition of, <a class="indexterm" href="#s2-proc-execdomains"> /proc/execdomains </a></dt></dl></dd><dt>expiration of password, forcing, <a class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt>Fedora installation media</dt><dd><dl><dt>installable packages, <a class="indexterm" href="#s2-rpm
-finding">Finding RPM Packages</a></dt></dl></dd><dt>feedback</dt><dd><dl><dt>contact information for this manual, <a class="indexterm" href="#sect-RedHat-We_Need_Feedback">We Need Feedback!</a></dt></dl></dd><dt>Fetchmail, <a class="indexterm" href="#s2-email-mta-fetchmail">Fetchmail</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-email-additional-resources">Additional Resources</a></dt><dt>command options, <a class="indexterm" href="#s3-email-mda-fetchmail-commands">Fetchmail Command Options</a></dt><dd><dl><dt>informational, <a class="indexterm" href="#s3-email-mda-fetchmail-commands-info">Informational or Debugging Options</a></dt><dt>special, <a class="indexterm" href="#s3-email-mda-fetchmail-commands-special">Special Options</a></dt></dl></dd><dt>configuration options, <a class="indexterm" href="#s3-email-mda-fetchmail-configuration">Fetchmail Configuration Options</a></dt><dd><dl><dt>global options, <a class="indexterm" href="#s3-email-mda-fet
chmail-configuration-global">Global Options</a></dt><dt>server options, <a class="indexterm" href="#s3-email-mda-fetchmail-configuration-server">Server Options</a></dt><dt>user options, <a class="indexterm" href="#s3-email-fetchmail-configuration-user">User Options</a></dt></dl></dd></dl></dd><dt>file system</dt><dd><dl><dt>virtual (see proc file system)</dt></dl></dd><dt>file systems, <a class="indexterm" href="#s1-sysinfo-filesystems">File Systems</a></dt><dt>files, proc file system</dt><dd><dl><dt>changing, <a class="indexterm" href="#s2-proc-change">Changing Virtual Files</a>, <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt><dt>viewing, <a class="indexterm" href="#s2-proc-viewing">Viewing Virtual Files</a>, <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt></dl></dd><dt>FQDN (see fully qualified domain name)</dt><dt>frame buffer device, <a class="indexterm" href="#s2-proc-fb"> /proc/fb </a></dt><dd><dl><dt>(see als
o /proc/fb )</dt></dl></dd><dt> free , <a class="indexterm" href="#s1-sysinfo-memory-usage">Memory Usage</a></dt><dt>fully qualified domain name, <a class="indexterm" href="#s2-bind-introduction-zones">Nameserver Zones</a></dt></dl></div><div class="indexdiv"><h3>G</h3><dl><dt> GNOME System Monitor , <a class="indexterm" href="#s1-sysinfo-system-processes">System Processes</a></dt><dt> gnome-system-log (see Log File Viewer )</dt><dt> gnome-system-monitor , <a class="indexterm" href="#s1-sysinfo-system-processes">System Processes</a></dt><dt>GnuPG</dt><dd><dl><dt>checking RPM package signatures, <a class="indexterm" href="#s1-check-rpm-sig">Checking a Package's Signature</a></dt></dl></dd><dt>group confi/sbin/nologinguration</dt><dd><dl><dt>adding groups, <a class="indexterm" href="#s2-redhat-config-users-group-new">Adding a New Group</a></dt></dl></dd><dt>group configuration</dt><dd><dl><dt>filtering list of groups, <a class="indexterm" href="#s1-users-configui">User and
Group Configuration</a></dt><dt> groupadd , <a class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt><dt>modify users in groups, <a class="indexterm" href="#s2-redhat-config-users-group-properties">Modifying Group Properties</a></dt><dt>modifying group properties, <a class="indexterm" href="#s2-redhat-config-users-group-properties">Modifying Group Properties</a></dt><dt>viewing list of groups, <a class="indexterm" href="#s1-users-configui">User and Group Configuration</a></dt></dl></dd><dt>groups (see group configuration)</dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-users-groups-additional-resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-users-groups-documentation">Installed Documentation</a></dt></dl></dd><dt>GID, <a class="indexterm" href="#Users_and_Groups">Users and Groups</a></dt><dt>introducing, <a class="indexterm" href="#Users_and_Groups">Users and Groups</a></
dt><dt>shared directories, <a class="indexterm" href="#s2-users-groups-rationale">Group Directories</a></dt><dt>standard, <a class="indexterm" href="#s1-users-groups-standard-groups">Standard Groups</a></dt><dt>tools for management of</dt><dd><dl><dt> groupadd , <a class="indexterm" href="#s1-users-tools">User and Group Management Tools</a>, <a class="indexterm" href="#s1-users-groups-private-groups">User Private Groups</a></dt><dt> system-config-users , <a class="indexterm" href="#s1-users-groups-private-groups">User Private Groups</a></dt><dt> User Manager , <a class="indexterm" href="#s1-users-tools">User and Group Management Tools</a></dt></dl></dd><dt>user private, <a class="indexterm" href="#s1-users-groups-private-groups">User Private Groups</a></dt></dl></dd><dt>GRUB boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="#s3-kernel-boot-loader-grub">Configuring the GRUB Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="#s3-kernel-boo
t-loader-grub">Configuring the GRUB Boot Loader</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hardware</dt><dd><dl><dt>viewing, <a class="indexterm" href="#s1-sysinfo-hardware">Hardware</a></dt></dl></dd><dt> Hardware Browser , <a class="indexterm" href="#s1-sysinfo-hardware">Hardware</a></dt><dt>HTTP server (see Apache HTTP Server)</dt><dt>httpd (see Apache HTTP Server)</dt><dt>hugepages</dt><dd><dl><dt>configuration of, <a class="indexterm" href="#s3-proc-sys-vm"> /proc/sys/vm/ </a></dt></dl></dd><dt> hwbrowser , <a class="indexterm" href="#s1-sysinfo-hardware">Hardware</a></dt></dl></div><div class="indexdiv"><h3>I</h3><dl><dt> ifdown , <a class="indexterm" href="#s1-networkscripts-control">Interface Control Scripts</a></dt><dt> ifup , <a class="indexterm" href="#s1-networkscripts-control">Interface Control Scripts</a></dt><dt>information</dt><dd><dl><dt>about your system, <a class="indexterm" href="#ch-Gathering_System_Information">Gathering System
Information</a></dt></dl></dd><dt>initial RAM disk image</dt><dd><dl><dt>verifying, <a class="indexterm" href="#sec-Verifying_the_Initial_RAM_Disk_Image">Verifying the Initial RAM Disk Image</a></dt><dd><dl><dt>IBM eServer System i, <a class="indexterm" href="#sec-Verifying_the_Initial_RAM_Disk_Image">Verifying the Initial RAM Disk Image</a></dt></dl></dd></dl></dd><dt>initial RPM repositories</dt><dd><dl><dt>installable packages, <a class="indexterm" href="#s2-rpm-finding">Finding RPM Packages</a></dt></dl></dd><dt> insmod , <a class="indexterm" href="#sec-Loading_a_Module">Loading a Module</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt>installing package groups</dt><dd><dl><dt>installing package groups with PackageKit, <a class="indexterm" href="#sec-Installing_and_Removing_Package_Groups">Installing and Removing Package Groups</a></dt></dl></dd><dt>installing the kernel, <a class="indexterm" href="#ch-Manually_Upgrading_the_Kernel">Manually Upgrading the
Kernel</a></dt><dt>introduction, <a class="indexterm" href="#ch-intro">Introduction</a></dt></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>kdump</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installed documents, <a class="indexterm" href="#s2-kdump-resources-installed">Installed Documentation</a></dt><dt>manual pages, <a class="indexterm" href="#s2-kdump-resources-installed">Installed Documentation</a></dt><dt>websites, <a class="indexterm" href="#s2-kdump-resources-online">Useful Websites</a></dt></dl></dd><dt>analyzing the dump (see crash)</dt><dt>configuring the service</dt><dd><dl><dt>default action, <a class="indexterm" href="#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-action">Changing the Default Action</a></dt><dt>dump image compression, <a class="indexterm" href="#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-
filtering">Configuring the Core Collector</a></dt><dt>filtering level, <a class="indexterm" href="#s3-kdump-configuration-gui-filtering">The Filtering Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-filtering">Configuring the Core Collector</a></dt><dt>initial RAM disk, <a class="indexterm" href="#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>kernel image, <a class="indexterm" href="#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>kernel options, <a class="indexterm" href="#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>memory usage, <a class="indexterm" href="#s3-kdump-configuration-firstboot-
memory">Configuring the Memory Usage</a>, <a class="indexterm" href="#s3-kdump-configuration-gui-basic">The Basic Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>target location, <a class="indexterm" href="#s3-kdump-configuration-gui-target">The Target Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-target">Configuring the Target Type</a></dt></dl></dd><dt>enabling the service, <a class="indexterm" href="#s3-kdump-configuration-firstboot-enable">Enabling the Service</a>, <a class="indexterm" href="#s3-kdump-configuration-gui-enable">Enabling the Service</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-enable">Enabling the Service</a></dt><dt>known issues</dt><dd><dl><dt>hpsa driver, <a class="indexterm" href="#s3-kdump-configuration-gui-target">The Target Settings Tab</a>, <a class="indexterm" href="#s3-kdump-configuration-cli-target">Configuring the Target Type</a><
/dt></dl></dd><dt>running the service, <a class="indexterm" href="#s3-kdump-configuration-cli-enable">Enabling the Service</a></dt><dt>system requirements, <a class="indexterm" href="#s1-kdump-configuration">Configuring the kdump Service</a></dt><dt>testing the configuration, <a class="indexterm" href="#s2-kdump-configuration-testing">Testing the Configuration</a></dt></dl></dd><dt>kernel</dt><dd><dl><dt>downloading, <a class="indexterm" href="#s1-kernel-download">Downloading the Upgraded Kernel</a></dt><dt>installing kernel packages, <a class="indexterm" href="#ch-Manually_Upgrading_the_Kernel">Manually Upgrading the Kernel</a></dt><dt>kernel packages, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt><dt>package, <a class="indexterm" href="#ch-Manually_Upgrading_the_Kernel">Manually Upgrading the Kernel</a></dt><dt>performing kernel upgrade, <a class="indexterm" href="#s1-kernel-perform-upgrade">Performing the Upgrade</a></dt><dt>RPM packa
ge, <a class="indexterm" href="#ch-Manually_Upgrading_the_Kernel">Manually Upgrading the Kernel</a></dt><dt>upgrade kernel available, <a class="indexterm" href="#s1-kernel-download">Downloading the Upgraded Kernel</a></dt><dd><dl><dt>Security Errata, <a class="indexterm" href="#s1-kernel-download">Downloading the Upgraded Kernel</a></dt><dt>via Red Hat network, <a class="indexterm" href="#s1-kernel-download">Downloading the Upgraded Kernel</a></dt></dl></dd><dt>upgrading</dt><dd><dl><dt>preparing, <a class="indexterm" href="#s1-kernel-preparing">Preparing to Upgrade</a></dt><dt>working boot media, <a class="indexterm" href="#s1-kernel-preparing">Preparing to Upgrade</a></dt></dl></dd><dt>upgrading the kernel, <a class="indexterm" href="#ch-Manually_Upgrading_the_Kernel">Manually Upgrading the Kernel</a></dt></dl></dd><dt>Kernel Dump Configuration (see kdump)</dt><dt>kernel module</dt><dd><dl><dt>bonding module, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Cha
nnel Bonding</a></dt><dd><dl><dt>description, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>definition, <a class="indexterm" href="#ch-Working_with_Kernel_Modules">Working with Kernel Modules</a></dt><dt>directories</dt><dd><dl><dt> /etc/sysconfig/modules/ , <a class="indexterm" href="#sec-Persistent_Module_Loading">Persistent Module Loading</a></dt><dt> /lib/modules/<kernel_version>/kernel/drivers/ , <a class="indexterm" href="#sec-Loading_a_Module">Loading a Module</a></dt></dl></dd><dt>Ethernet module</dt><dd><dl><dt>supporting multiple cards, <a class="indexterm" href="#sec-Using_Multiple_Ethernet_Cards">Using Multiple Ethernet Cards</a></dt></dl></dd><dt>files</dt><dd><dl><dt> /proc/modules , <a class="indexterm" href="#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Mo
dules</a></dt></dl></dd><dt>listing</dt><dd><dl><dt>currently loaded modules, <a class="indexterm" href="#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt><dt>module information, <a class="indexterm" href="#sec-Displaying_Information_About_a_Module">Displaying Information About a Module</a></dt></dl></dd><dt>loading</dt><dd><dl><dt>at the boot time, <a class="indexterm" href="#sec-Persistent_Module_Loading">Persistent Module Loading</a></dt><dt>for the current session, <a class="indexterm" href="#sec-Loading_a_Module">Loading a Module</a></dt></dl></dd><dt>module parameters</dt><dd><dl><dt>bonding module parameters, <a class="indexterm" href="#s3-modules-bonding-directives">Bonding Module Directives</a></dt><dt>supplying, <a class="indexterm" href="#sec-Setting_Module_Parameters">Setting Module Parameters</a></dt></dl></dd><dt>unloading, <a class="indexterm" href="#sec-Unloading_a_Module">Unloading a Module</a></dt><dt>utilities</dt><dd><dl><dt>
insmod , <a class="indexterm" href="#sec-Loading_a_Module">Loading a Module</a></dt><dt> lsmod , <a class="indexterm" href="#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt><dt> modinfo , <a class="indexterm" href="#sec-Displaying_Information_About_a_Module">Displaying Information About a Module</a></dt><dt> modprobe , <a class="indexterm" href="#sec-Loading_a_Module">Loading a Module</a>, <a class="indexterm" href="#sec-Unloading_a_Module">Unloading a Module</a></dt><dt> rmmod , <a class="indexterm" href="#sec-Unloading_a_Module">Unloading a Module</a></dt></dl></dd></dl></dd><dt>kernel package</dt><dd><dl><dt>kernel</dt><dd><dl><dt>for single,multicore and multiprocessor systems, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-devel</dt><dd><dl><dt>kernel headers and makefiles, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-doc<
/dt><dd><dl><dt> documentation files, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-firmware</dt><dd><dl><dt> firmware files, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-headers</dt><dd><dl><dt> C header files files, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>perf</dt><dd><dl><dt>firmware files, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd></dl></dd><dt>kernel upgrading</dt><dd><dl><dt>preparing, <a class="indexterm" href="#s1-kernel-preparing">Preparing to Upgrade</a></dt></dl></dd><dt>keyboard configuration, <a class="indexterm" href="#ch-Keyboard_Configuration">Keyboard Configuration</a></dt><dd><dl><dt>Keyboard Indicator applet, <a class="indexterm" href="#s1-keyboard-indicator">Adding the Keyboard Layout Indicator</a></dt><dt>Keyboard Preferences uti
lity, <a class="indexterm" href="#s1-keyboard-layout">Changing the Keyboard Layout</a></dt><dt>layout, <a class="indexterm" href="#s1-keyboard-layout">Changing the Keyboard Layout</a></dt><dt>typing break, <a class="indexterm" href="#s1-keyboard-break">Setting Up a Typing Break</a></dt></dl></dd><dt>Keyboard Indicator (see keyboard configuration)</dt><dt>Keyboard Preferences (see keyboard configuration)</dt></dl></div><div class="indexdiv"><h3>L</h3><dl><dt> Log File Viewer </dt><dd><dl><dt>filtering, <a class="indexterm" href="#s1-logfiles-viewing">Viewing Log Files</a></dt><dt>monitoring, <a class="indexterm" href="#s1-logfiles-examining">Monitoring Log Files</a></dt><dt>searching, <a class="indexterm" href="#s1-logfiles-viewing">Viewing Log Files</a></dt></dl></dd><dt>log files, <a class="indexterm" href="#ch-Log_Files">Log Files</a></dt><dd><dl><dt>(see also Log Viewer )</dt><dt>additional resources</dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2
-log-files-installed-docs">Installed Documentation</a></dt><dt>useful websites, <a class="indexterm" href="#s2-log-files-useful-websites">Useful Websites</a></dt></dl></dd><dt>description, <a class="indexterm" href="#ch-Log_Files">Log Files</a></dt><dt>locating, <a class="indexterm" href="#s1-logfiles-locating">Locating Log Files</a></dt><dt>monitoring, <a class="indexterm" href="#s1-logfiles-examining">Monitoring Log Files</a></dt><dt>rotating, <a class="indexterm" href="#s1-logfiles-locating">Locating Log Files</a></dt><dt> rsyslod daemon , <a class="indexterm" href="#ch-Log_Files">Log Files</a></dt><dt>viewing, <a class="indexterm" href="#s1-logfiles-viewing">Viewing Log Files</a></dt></dl></dd><dt> Log Viewer </dt><dd><dl><dt>refresh rate, <a class="indexterm" href="#s1-logfiles-viewing">Viewing Log Files</a></dt></dl></dd><dt> logrotate , <a class="indexterm" href="#s1-logfiles-locating">Locating Log Files</a></dt><dt> lsmod , <a class="indexterm" href="#sec-Listing_Cur
rently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt> lspci , <a class="indexterm" href="#s2-proc-pci"> /proc/bus/pci </a>, <a class="indexterm" href="#s1-sysinfo-hardware">Hardware</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>Mail Delivery Agent (see email)</dt><dt>Mail Transport Agent (see email) (see MTA)</dt><dt> Mail Transport Agent Switcher , <a class="indexterm" href="#s2-email-switchmail">Mail Transport Agent (MTA) Configuration</a></dt><dt>Mail User Agent, <a class="indexterm" href="#s2-email-switchmail">Mail Transport Agent (MTA) Configuration</a> (see email)</dt><dt>MDA (see Mail Delivery Agent)</dt><dt>memory usage, <a class="indexterm" href="#s1-sysinfo-memory-usage">Memory Usage</a></dt><dt> modinfo , <a class="indexterm" href="#sec-Displaying_Information_About_a_Module">Displaying Information About a Module</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt> modprobe ,
<a class="indexterm" href="#sec-Loading_a_Module">Loading a Module</a>, <a class="indexterm" href="#sec-Unloading_a_Module">Unloading a Module</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt>module (see kernel module)</dt><dt>module parameters (see kernel module)</dt><dt>MTA (see Mail Transport Agent)</dt><dd><dl><dt>setting default, <a class="indexterm" href="#s2-email-switchmail">Mail Transport Agent (MTA) Configuration</a></dt><dt>switching with Mail Transport Agent Switcher , <a class="indexterm" href="#s2-email-switchmail">Mail Transport Agent (MTA) Configuration</a></dt></dl></dd><dt>MUA, <a class="indexterm" href="#s2-email-switchmail">Mail Transport Agent (MTA) Configuration</a> (see Mail User Agent)</dt><dt>Multihomed DHCP</dt><dd><dl><dt>host configuration, <a class="indexterm" href="#sect-dns_Host_Configuration">Host Configuration</a></dt><dt>server configuration, <a class="indexterm" href="#sect-Configuring_a_Multihomed_DHCP_Server">Configuring a M
ultihomed DHCP Server</a></dt></dl></dd><dt>multiple domains</dt><dd><dl><dt>specifying in SSSD, <a class="indexterm" href="#sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">Support for Multiple Domains</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>named (see BIND)</dt><dt>nameserver (see DNS)</dt><dt>network</dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-networkscripts-resources">Additional Resources</a></dt><dt>commands</dt><dd><dl><dt> /sbin/ifdown , <a class="indexterm" href="#s1-networkscripts-control">Interface Control Scripts</a></dt><dt> /sbin/ifup , <a class="indexterm" href="#s1-networkscripts-control">Interface Control Scripts</a></dt><dt> /sbin/service network , <a class="indexterm" href="#s1-networkscripts-control">Interface Control Scripts</a></dt></dl></dd><dt>configuration, <a class="indexterm" href="#s1-networkscripts-interfaces">Interface Configuration Files</a></dt><dt>configuration files, <a cla
ss="indexterm" href="#s1-networkscripts-files">Network Configuration Files</a></dt><dt>functions, <a class="indexterm" href="#s1-networkscripts-functions">Network Function Files</a></dt><dt>interface configuration files, <a class="indexterm" href="#s1-networkscripts-interfaces">Interface Configuration Files</a></dt><dt>interfaces</dt><dd><dl><dt>alias, <a class="indexterm" href="#s2-networkscripts-interfaces-alias">Alias and Clone Files</a></dt><dt>channel bonding, <a class="indexterm" href="#s2-networkscripts-interfaces-chan">Channel Bonding Interfaces</a></dt><dt>clone, <a class="indexterm" href="#s2-networkscripts-interfaces-alias">Alias and Clone Files</a></dt><dt>dialup, <a class="indexterm" href="#s2-networkscripts-interfaces-ppp0">Dialup Interfaces</a></dt><dt>Ethernet, <a class="indexterm" href="#s2-networkscripts-interfaces-eth0">Ethernet Interfaces</a></dt></dl></dd><dt>scripts, <a class="indexterm" href="#ch-Network_Interfaces">Network Interfaces</a></dt></dl></dd
><dt>Network Time Protocol (see NTP)</dt><dt>NIC</dt><dd><dl><dt>binding into single channel, <a class="indexterm" href="#sec-Using_Channel_Bonding">Using Channel Bonding</a></dt></dl></dd><dt>NTP</dt><dd><dl><dt>configuring, <a class="indexterm" href="#sect-Date_and_Time_Configuration-Network_Time_Protocol">Network Time Protocol Properties</a>, <a class="indexterm" href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">Network Time Protocol Setup</a></dt><dt> ntpd , <a class="indexterm" href="#sect-Date_and_Time_Configuration-Network_Time_Protocol">Network Time Protocol Properties</a>, <a class="indexterm" href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">Network Time Protocol Setup</a></dt><dt> ntpdate , <a class="indexterm" href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">Network Time Protocol Setup</a></dt></dl></dd><dt> ntpd (see NTP)</dt><dt> ntpdate (s
ee NTP)</dt><dt> ntsysv (see services configuration)</dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>OpenSSH, <a class="indexterm" href="#ch-OpenSSH">OpenSSH</a>, <a class="indexterm" href="#s2-ssh-features">Main Features</a></dt><dd><dl><dt>(see also SSH)</dt><dt>additional resources, <a class="indexterm" href="#s1-openssh-additional-resources">Additional Resources</a></dt><dt>client, <a class="indexterm" href="#s1-ssh-clients">OpenSSH Clients</a></dt><dd><dl><dt> scp , <a class="indexterm" href="#s2-ssh-clients-scp">Using the scp Utility</a></dt><dt> sftp , <a class="indexterm" href="#s2-ssh-clients-sftp">Using the sftp Utility</a></dt><dt> ssh , <a class="indexterm" href="#s2-ssh-clients-ssh">Using the ssh Utility</a></dt></dl></dd><dt>DSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>RSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="#s3-ssh-configurat
ion-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>RSA Version 1 keys</dt><dd><dl><dt>generating, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>server, <a class="indexterm" href="#s2-ssh-configuration-sshd">Starting an OpenSSH Server</a></dt><dd><dl><dt>starting, <a class="indexterm" href="#s2-ssh-configuration-sshd">Starting an OpenSSH Server</a></dt><dt>stopping, <a class="indexterm" href="#s2-ssh-configuration-sshd">Starting an OpenSSH Server</a></dt></dl></dd><dt> ssh-add , <a class="indexterm" href="#s3-ssh-configuration-keypairs-agent">Configuring ssh-agent</a></dt><dt> ssh-agent , <a class="indexterm" href="#s3-ssh-configuration-keypairs-agent">Configuring ssh-agent</a></dt><dt>ssh-keygen</dt><dd><dl><dt>DSA, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt><dt>RSA, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">G
enerating Key Pairs</a></dt><dt>RSA Version 1, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>using key-based authentication, <a class="indexterm" href="#s2-ssh-configuration-keypairs">Using a Key-Based Authentication</a></dt></dl></dd><dt>OpenSSL</dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-openssh-additional-resources">Additional Resources</a></dt><dt>SSL (see SSL)</dt><dt>TLS (see TLS)</dt></dl></dd><dt>OS/400 boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="#s2-kernel-boot-loader-iseries">Configuring the OS/400® Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="#s2-kernel-boot-loader-iseries">Configuring the OS/400® Boot Loader</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>package</dt><dd><dl><dt>kernel RPM, <a class="indexterm" href="#ch-Manually_Upgrading_the_Kernel">Manually Upgrading the Kernel</a></dt></dl></dd><d
t>PackageKit, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dd><dl><dt>adding and removing, <a class="indexterm" href="#sec-Using_Add_Remove_Software">Using Add/Remove Software</a></dt><dt>architecture, <a class="indexterm" href="#sec-PackageKit_Architecture">PackageKit Architecture</a></dt><dt>installing and removing package groups, <a class="indexterm" href="#sec-Installing_and_Removing_Package_Groups">Installing and Removing Package Groups</a></dt><dt>installing packages , <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>managing packages , <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>PolicyKit</dt><dd><dl><dt>authentication, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>uninstalling packages , <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>updating packages , <a class="indexterm" href="#ch-PackageKit">PackageKit<
/a></dt><dt>viewing packages , <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>viewing transaction log, <a class="indexterm" href="#sec-Viewing_the_Transaction_Log">Viewing the Transaction Log</a></dt></dl></dd><dt>packages</dt><dd><dl><dt>adding and removing with PackageKit, <a class="indexterm" href="#sec-Using_Add_Remove_Software">Using Add/Remove Software</a></dt><dt>dependencies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">Unresolved Dependency</a></dt><dt>determining file ownership with, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>displaying packages</dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>displaying packages with Yum, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displayin
g Package Information</a></dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>filtering with PackageKit, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dd><dl><dt>Development, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>Free, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>Graphical, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>hide subpackages, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>installed, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>no filter, <a class="indexterm" href="#sec-Finding_
Packages_with_Filters">Finding Packages with Filters</a></dt><dt>only available, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>only development, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>only end user files, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>only installed, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>only native packages, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>only newest items, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt></dl></dd><dt>filtering with PackageKit for packages, <a class="indexterm" href="#sec-Finding_Packages_with_Filters">Finding Packages with Filters</a></dt><dt>finding deleted files from,
<a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>finding RPM packages, <a class="indexterm" href="#s2-rpm-finding">Finding RPM Packages</a></dt><dt>iFedora installation media, <a class="indexterm" href="#s2-rpm-finding">Finding RPM Packages</a></dt><dt>initial RPM repositories, <a class="indexterm" href="#s2-rpm-finding">Finding RPM Packages</a></dt><dt>installing a package group with Yum, <a class="indexterm" href="#sec-Installing">Installing</a></dt><dt>installing and removing package groups, <a class="indexterm" href="#sec-Installing_and_Removing_Package_Groups">Installing and Removing Package Groups</a></dt><dt>installing packages with PackageKit, <a class="indexterm" href="#ch-PackageKit">PackageKit</a>, <a class="indexterm" href="#sec-Installing_and_Removing_Packages_and_Dependencies">Installing and Removing Packages (and Dependencies)</a></dt><dd><dl><dt>dependencies, <a class="indexterm" href="#sec-Installing_and_
Removing_Packages_and_Dependencies">Installing and Removing Packages (and Dependencies)</a></dt></dl></dd><dt>installing RPM, <a class="indexterm" href="#sec-Installing_and_Upgrading">Installing and Upgrading</a></dt><dt>installing with Yum, <a class="indexterm" href="#sec-Installing">Installing</a></dt><dt>kernel</dt><dd><dl><dt>for single,multicore and multiprocessor systems, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-devel</dt><dd><dl><dt>kernel headers and makefiles, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-doc</dt><dd><dl><dt> documentation files, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-firmware</dt><dd><dl><dt> firmware files, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-headers</dt><dd><dl><dt> C header files files, <a cl
ass="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>listing packages with Yum, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dd><dl><dt> Glob expressions, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum grouplist, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list all, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list available, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list installed, <a class="ind
exterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum repolist, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum search, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>locating documentation for, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>managing packages with PackageKit, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>obtaining list of files, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>packages and package groups, <a class="indexterm" href="#sec-Packages_and_Package_Groups">Packages and Package Groups</a></dt><dt>perf</dt><dd><dl><dt>
firmware files, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>querying uninstalled, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>removing, <a class="indexterm" href="#s2-rpm-uninstalling">Uninstalling</a></dt><dt>removing package groups with Yum, <a class="indexterm" href="#sec-Removing">Removing</a></dt><dt>removing packages with PackageKit, <a class="indexterm" href="#sec-Installing_and_Removing_Packages_and_Dependencies">Installing and Removing Packages (and Dependencies)</a></dt><dt>RPM, <a class="indexterm" href="#ch-RPM">RPM</a></dt><dd><dl><dt>already installed, <a class="indexterm" href="#s3-rpm-errors">Package Already Installed</a></dt><dt>configuration file changes, <a class="indexterm" href="#sec-Configuration_File_Changes">Configuration File Changes</a></dt><dt>conflict, <a class="indexterm" href="#s3-rpm-conflicting-files">Conflicting Files</a></dt><dt>fa
iled dependancies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">Unresolved Dependency</a></dt><dt>freshening, <a class="indexterm" href="#s2-rpm-freshening">Freshening</a></dt><dt>prisitne sources, <a class="indexterm" href="#s1-rpm-design">RPM Design Goals</a></dt><dt>querying, <a class="indexterm" href="#s2-rpm-querying">Querying</a></dt><dt>removing, <a class="indexterm" href="#s2-rpm-uninstalling">Uninstalling</a></dt><dt>source and binary packages, <a class="indexterm" href="#ch-RPM">RPM</a></dt><dt>tips, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>uninstalling, <a class="indexterm" href="#s2-rpm-uninstalling">Uninstalling</a></dt><dt>verifying, <a class="indexterm" href="#s2-rpm-verifying">Verifying</a></dt></dl></dd><dt>searching for packages with Yum</dt><dd><dl><dt>yum search, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying P
ackage Information</a></dt></dl></dd><dt>searching packages with Yum, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>setting packages with PackageKit</dt><dd><dl><dt>checking interval, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>uninstalling packages with PackageKit, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>uninstalling packages with Yum, <a class="indexterm" href="#sec-Removing">Removing</a></dt><dd><dl><dt>yum remove package_name, <a class="indexterm" href="#sec-Removing">Removing</a></dt></dl></dd><dt>updating currently installed packages</dt><dd><dl><dt>available updates, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>updating packages with PackageKit, <a class="indexterm
" href="#ch-PackageKit">PackageKit</a></dt><dd><dl><dt>PolicyKit, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt><dt>Software Update, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>upgrading RPM, <a class="indexterm" href="#sec-Installing_and_Upgrading">Installing and Upgrading</a></dt><dt>viewing packages with PackageKit, <a class="indexterm" href="#ch-PackageKit">PackageKit</a></dt><dt>viewing transaction log, <a class="indexterm" href="#sec-Viewing_the_Transaction_Log">Viewing the Transaction Log</a></dt><dt>viewing Yum repositories with PackageKit, <a class="indexterm" href="#sec-Refreshing_Software_Sources_Yum_Repositories">Refreshing Software Sources (Yum Repositories)</a></dt><dt>Yum insead of RPM, <a class="indexterm" href="#ch-RPM">RPM</a></dt></dl></dd><dt>password</dt><dd><dl><dt>aging, <a class="indexterm" h
ref="#s2-users-cmd-line">Command Line Configuration</a></dt><dt>expire, <a class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>passwords</dt><dd><dl><dt>shadow, <a class="indexterm" href="#s1-users-groups-shadow-utilities">Shadow Passwords</a></dt></dl></dd><dt>PCI devices</dt><dd><dl><dt>listing, <a class="indexterm" href="#s1-sysinfo-hardware">Hardware</a></dt></dl></dd><dt>PolicyKit, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt><dt>Postfix, <a class="indexterm" href="#s2-email-mta-postfix">Postfix</a></dt><dd><dl><dt>default installation, <a class="indexterm" href="#s3-email-mta-postfix-default">The Default Postfix Installation</a></dt></dl></dd><dt>postfix, <a class="indexterm" href="#s2-email-switchmail">Mail Transport Agent (MTA) Configuration</a></dt><dt>primary nameserver (see BIND)</dt><dt> proc file system</dt><dd><dl><dt> /proc/buddyinfo , <a class="i
ndexterm" href="#s2-proc-buddyinfo"> /proc/buddyinfo </a></dt><dt> /proc/bus/ directory, <a class="indexterm" href="#s2-proc-dir-bus"> /proc/bus/ </a></dt><dt> /proc/bus/pci </dt><dd><dl><dt>viewing using lspci , <a class="indexterm" href="#s2-proc-pci"> /proc/bus/pci </a></dt></dl></dd><dt> /proc/cmdline , <a class="indexterm" href="#s2-proc-cmdline"> /proc/cmdline </a></dt><dt> /proc/cpuinfo , <a class="indexterm" href="#s2-proc-cpuinfo"> /proc/cpuinfo </a></dt><dt> /proc/crypto , <a class="indexterm" href="#s2-proc-crypto"> /proc/crypto </a></dt><dt> /proc/devices </dt><dd><dl><dt>block devices, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt><dt>character devices, <a class="indexterm" href="#s2-proc-devices"> /proc/devices </a></dt></dl></dd><dt> /proc/dma , <a class="indexterm" href="#s2-proc-dma"> /proc/dma </a></dt><dt> /proc/driver/ directory, <a class="indexterm" href="#s2-proc-dir-driver"> /proc/driver/ </a></dt><dt> /proc/execdomains , <a clas
s="indexterm" href="#s2-proc-execdomains"> /proc/execdomains </a></dt><dt> /proc/fb , <a class="indexterm" href="#s2-proc-fb"> /proc/fb </a></dt><dt> /proc/filesystems , <a class="indexterm" href="#s2-proc-filesystems"> /proc/filesystems </a></dt><dt> /proc/fs/ directory, <a class="indexterm" href="#s2-proc-dir-fs"> /proc/fs </a></dt><dt> /proc/interrupts , <a class="indexterm" href="#s2-proc-interrupts"> /proc/interrupts </a></dt><dt> /proc/iomem , <a class="indexterm" href="#s2-proc-iomem"> /proc/iomem </a></dt><dt> /proc/ioports , <a class="indexterm" href="#s2-proc-ioports"> /proc/ioports </a></dt><dt> /proc/irq/ directory, <a class="indexterm" href="#s2-proc-dir-irq"> /proc/irq/ </a></dt><dt> /proc/kcore , <a class="indexterm" href="#s2-proc-kcore"> /proc/kcore </a></dt><dt> /proc/kmsg , <a class="indexterm" href="#s2-proc-kmsg"> /proc/kmsg </a></dt><dt> /proc/loadavg , <a class="indexterm" href="#s2-proc-loadavg"> /proc/loadavg </a></dt><dt> /proc/locks , <a class="ind
exterm" href="#s2-proc-locks"> /proc/locks </a></dt><dt> /proc/mdstat , <a class="indexterm" href="#s2-proc-mdstat"> /proc/mdstat </a></dt><dt> /proc/meminfo , <a class="indexterm" href="#s2-proc-meminfo"> /proc/meminfo </a></dt><dt> /proc/misc , <a class="indexterm" href="#s2-proc-misc"> /proc/misc </a></dt><dt> /proc/modules , <a class="indexterm" href="#s2-proc-modules"> /proc/modules </a></dt><dt> /proc/mounts , <a class="indexterm" href="#s2-proc-mounts"> /proc/mounts </a></dt><dt> /proc/mtrr , <a class="indexterm" href="#s2-proc-mtrr"> /proc/mtrr </a></dt><dt> /proc/net/ directory, <a class="indexterm" href="#s2-proc-dir-net"> /proc/net/ </a></dt><dt> /proc/partitions , <a class="indexterm" href="#s2-proc-partitions"> /proc/partitions </a></dt><dt> /proc/PID/ directory, <a class="indexterm" href="#s2-proc-pid"> /proc/PID/ </a></dt><dt> /proc/scsi/ directory, <a class="indexterm" href="#s2-proc-dir-scsi"> /proc/scsi/ </a></dt><dt> /proc/self/ directory, <a class="indext
erm" href="#s3-proc-self"> /proc/self/ </a></dt><dt> /proc/slabinfo , <a class="indexterm" href="#s2-proc-slabinfo"> /proc/slabinfo </a></dt><dt> /proc/stat , <a class="indexterm" href="#s2-proc-stat"> /proc/stat </a></dt><dt> /proc/swaps , <a class="indexterm" href="#s2-proc-swaps"> /proc/swaps </a></dt><dt> /proc/sys/ directory, <a class="indexterm" href="#s2-proc-dir-sys"> /proc/sys/ </a>, <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt><dd><dl><dt>(see also sysctl )</dt><dt> /proc/sys/dev/ directory, <a class="indexterm" href="#s3-proc-sys-dev"> /proc/sys/dev/ </a></dt><dt> /proc/sys/fs/ directory, <a class="indexterm" href="#s3-proc-sys-fs"> /proc/sys/fs/ </a></dt><dt> /proc/sys/kernel/ directory, <a class="indexterm" href="#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt> /proc/sys/kernel/exec-shield , <a class="indexterm" href="#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt>/proc/sys/kernel/sysrq (see system request key)</dt><dt
> /proc/sys/net/ directory, <a class="indexterm" href="#s3-proc-sys-net"> /proc/sys/net/ </a></dt><dt> /proc/sys/vm/ directory, <a class="indexterm" href="#s3-proc-sys-vm"> /proc/sys/vm/ </a></dt></dl></dd><dt> /proc/sysrq-trigger , <a class="indexterm" href="#s2-proc-sysrq-trigger"> /proc/sysrq-trigger </a></dt><dt> /proc/sysvipc/ directory, <a class="indexterm" href="#s2-proc-dir-sysvipc"> /proc/sysvipc/ </a></dt><dt> /proc/tty/ directory, <a class="indexterm" href="#s2-proc-tty"> /proc/tty/ </a></dt><dt> /proc/uptime , <a class="indexterm" href="#s2-proc-uptime"> /proc/uptime </a></dt><dt> /proc/version , <a class="indexterm" href="#s2-proc-version"> /proc/version </a></dt><dt>additional resources, <a class="indexterm" href="#s1-proc-additional-resources">References</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-proc-installed-documentation">Installed Documentation</a></dt><dt>useful websites, <a class="indexterm" href="#s2-proc-useful-website
s">Useful Websites</a></dt></dl></dd><dt>changing files within, <a class="indexterm" href="#s2-proc-change">Changing Virtual Files</a>, <a class="indexterm" href="#s2-proc-dir-sys"> /proc/sys/ </a>, <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt><dt>files within, top-level, <a class="indexterm" href="#s1-proc-topfiles">Top-level Files within the proc File System</a></dt><dt>introduced, <a class="indexterm" href="#ch-proc">The proc File System</a></dt><dt>process directories, <a class="indexterm" href="#s2-proc-processdirs">Process Directories</a></dt><dt>subdirectories within, <a class="indexterm" href="#s1-proc-directories">Directories within /proc/ </a></dt><dt>viewing files within, <a class="indexterm" href="#s2-proc-viewing">Viewing Virtual Files</a></dt></dl></dd><dt>processes, <a class="indexterm" href="#s1-sysinfo-system-processes">System Processes</a></dt><dt>Procmail, <a class="indexterm" href="#s1-email-mda">Mail Delivery Agents</a></d
t><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-email-additional-resources">Additional Resources</a></dt><dt>configuration, <a class="indexterm" href="#s2-email-procmail-configuration">Procmail Configuration</a></dt><dt>recipes, <a class="indexterm" href="#s2-email-procmail-recipes">Procmail Recipes</a></dt><dd><dl><dt>delivering, <a class="indexterm" href="#s2-email-procmail-recipes-delivering">Delivering vs. Non-Delivering Recipes</a></dt><dt>examples, <a class="indexterm" href="#s3-email-procmail-recipes-examples">Recipe Examples</a></dt><dt>flags, <a class="indexterm" href="#s3-email-procmail-recipes-flags">Flags</a></dt><dt>local lockfiles, <a class="indexterm" href="#s3-email-procmail-recipes-lockfile">Specifying a Local Lockfile</a></dt><dt>non-delivering, <a class="indexterm" href="#s2-email-procmail-recipes-delivering">Delivering vs. Non-Delivering Recipes</a></dt><dt>SpamAssassin, <a class="indexterm" href="#s3-email-mda-spam">Spam Filters</a></d
t><dt>special actions, <a class="indexterm" href="#s3-email-procmail-recipes-special">Special Conditions and Actions</a></dt><dt>special conditions, <a class="indexterm" href="#s3-email-procmail-recipes-special">Special Conditions and Actions</a></dt></dl></dd></dl></dd><dt> ps , <a class="indexterm" href="#s1-sysinfo-system-processes">System Processes</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAM, <a class="indexterm" href="#s1-sysinfo-memory-usage">Memory Usage</a></dt><dt> rcp , <a class="indexterm" href="#s2-ssh-clients-scp">Using the scp Utility</a></dt><dt>recursive nameserver (see BIND)</dt><dt> Red Hat RPM Guide , <a class="indexterm" href="#s2-rpm-related-books">Related Books</a></dt><dt>removing package groups</dt><dd><dl><dt>removing package groups with PackageKit, <a class="indexterm" href="#sec-Installing_and_Removing_Package_Groups">Installing and Removing Package Groups</a></dt></dl></dd><dt>resource record (see BIND)</dt><dt> rmmod , <a class
="indexterm" href="#sec-Unloading_a_Module">Unloading a Module</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt>rndc (see BIND)</dt><dt>root nameserver (see BIND)</dt><dt>RPM, <a class="indexterm" href="#ch-RPM">RPM</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-rpm-additional-resources">Additional Resources</a></dt><dt>already installed, <a class="indexterm" href="#s3-rpm-errors">Package Already Installed</a></dt><dt>basic modes, <a class="indexterm" href="#s1-rpm-using">Using RPM</a></dt><dt>book about, <a class="indexterm" href="#s2-rpm-related-books">Related Books</a></dt><dt>checking package signatures, <a class="indexterm" href="#s1-check-rpm-sig">Checking a Package's Signature</a></dt><dt>configuration file changes, <a class="indexterm" href="#sec-Configuration_File_Changes">Configuration File Changes</a></dt><dd><dl><dt>conf.rpmsave, <a class="indexterm" href="#sec-Configuration_File_Changes">Configuration File Changes</a></dt>
</dl></dd><dt>conflicts, <a class="indexterm" href="#s3-rpm-conflicting-files">Conflicting Files</a></dt><dt>dependencies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">Unresolved Dependency</a></dt><dt>design goals, <a class="indexterm" href="#s1-rpm-design">RPM Design Goals</a></dt><dd><dl><dt>powerful querying, <a class="indexterm" href="#s1-rpm-design">RPM Design Goals</a></dt><dt>system verification, <a class="indexterm" href="#s1-rpm-design">RPM Design Goals</a></dt><dt>upgradability, <a class="indexterm" href="#s1-rpm-design">RPM Design Goals</a></dt></dl></dd><dt>determining file ownership with, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>documentation with, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>failed dependancies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">Unresolved Dependency</a></dt><dt>file conflicts</dt><dd><dl><d
t>resolving, <a class="indexterm" href="#s3-rpm-conflicting-files">Conflicting Files</a></dt></dl></dd><dt>file name, <a class="indexterm" href="#sec-Installing_and_Upgrading">Installing and Upgrading</a></dt><dt>finding deleted files with, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>finding RPM packages, <a class="indexterm" href="#s2-rpm-finding">Finding RPM Packages</a></dt><dt>freshening, <a class="indexterm" href="#s2-rpm-freshening">Freshening</a></dt><dt>GnuPG, <a class="indexterm" href="#s1-check-rpm-sig">Checking a Package's Signature</a></dt><dt>installing, <a class="indexterm" href="#sec-Installing_and_Upgrading">Installing and Upgrading</a></dt><dt>md5sum, <a class="indexterm" href="#s1-check-rpm-sig">Checking a Package's Signature</a></dt><dt>querying, <a class="indexterm" href="#s2-rpm-querying">Querying</a></dt><dt>querying for file list, <a class="indexterm" href="#s1-rpm-impressing">Practical and Comm
on Examples of RPM Usage</a></dt><dt>querying uninstalled packages, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>tips, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>uninstalling, <a class="indexterm" href="#s2-rpm-uninstalling">Uninstalling</a></dt><dt>upgrading, <a class="indexterm" href="#sec-Installing_and_Upgrading">Installing and Upgrading</a></dt><dt>verifying, <a class="indexterm" href="#s2-rpm-verifying">Verifying</a></dt><dt>website, <a class="indexterm" href="#s2-rpm-useful-websites">Useful Websites</a></dt></dl></dd><dt>RPM Package Manager (see RPM)</dt><dt>RSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>RSA Version 1 keys</dt><dd><dl><dt>generating, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl>
</dd><dt> rsyslog , <a class="indexterm" href="#ch-Log_Files">Log Files</a></dt><dt> runlevel (see services configuration)</dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt> scp (see OpenSSH)</dt><dt>secondary nameserver (see BIND)</dt><dt>security plugin (see Security )</dt><dt>Security-Related Packages</dt><dd><dl><dt>updating security-related packages, <a class="indexterm" href="#sec-Updating_Security-Related_Packages">Updating Security-Related Packages</a></dt></dl></dd><dt>Sendmail, <a class="indexterm" href="#s2-email-mta-sendmail">Sendmail</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-email-additional-resources">Additional Resources</a></dt><dt>aliases, <a class="indexterm" href="#s3-email-sendmail-changes-masquerading">Masquerading</a></dt><dt>common configuration changes, <a class="indexterm" href="#s3-email-mta-sendmail-changes">Common Sendmail Configuration Changes</a></dt><dt>default installation, <a class="indexterm" href="#s3-e
mail-mta-sendmail-default">The Default Sendmail Installation</a></dt><dt>LDAP and, <a class="indexterm" href="#s3-email-mta-sendmail-ldap">Using Sendmail with LDAP</a></dt><dt>limitations, <a class="indexterm" href="#s3-email-mta-sendmail-purpose">Purpose and Limitations</a></dt><dt>masquerading, <a class="indexterm" href="#s3-email-sendmail-changes-masquerading">Masquerading</a></dt><dt>purpose, <a class="indexterm" href="#s3-email-mta-sendmail-purpose">Purpose and Limitations</a></dt><dt>spam, <a class="indexterm" href="#s3-email-sendmail-stopping-spam">Stopping Spam</a></dt><dt>with UUCP, <a class="indexterm" href="#s3-email-mta-sendmail-changes">Common Sendmail Configuration Changes</a></dt></dl></dd><dt>sendmail, <a class="indexterm" href="#s2-email-switchmail">Mail Transport Agent (MTA) Configuration</a></dt><dt> service (see services configuration)</dt><dt>services configuration, <a class="indexterm" href="#ch-Controlling_Access_to_Services">Controlling Access to Ser
vices</a></dt><dd><dl><dt> chkconfig , <a class="indexterm" href="#s2-services-chkconfig">Using the chkconfig Utility</a></dt><dt> ntsysv , <a class="indexterm" href="#s2-services-ntsysv">Using the ntsysv Utility</a></dt><dt> runlevel , <a class="indexterm" href="#s1-services-runlevels">Configuring the Default Runlevel</a></dt><dt> service , <a class="indexterm" href="#s2-services-service">Using the service Utility</a></dt><dt> system-config-services , <a class="indexterm" href="#s2-services-serviceconf">Using the Service Configuration Utility</a></dt></dl></dd><dt> sftp (see OpenSSH)</dt><dt>shadow passwords</dt><dd><dl><dt>overview of, <a class="indexterm" href="#s1-users-groups-shadow-utilities">Shadow Passwords</a></dt></dl></dd><dt>slab pools (see /proc/slabinfo )</dt><dt>SpamAssassin</dt><dd><dl><dt>using with Procmail, <a class="indexterm" href="#s3-email-mda-spam">Spam Filters</a></dt></dl></dd><dt> ssh (see OpenSSH)</dt><dt>SSH protocol</dt><dd><dl><dt>authentica
tion, <a class="indexterm" href="#s2-ssh-protocol-authentication">Authentication</a></dt><dt>configuration files, <a class="indexterm" href="#s2-ssh-configuration-configs">Configuration Files</a></dt><dd><dl><dt>system-wide configuration files, <a class="indexterm" href="#s2-ssh-configuration-configs">Configuration Files</a></dt><dt>user-specific configuration files, <a class="indexterm" href="#s2-ssh-configuration-configs">Configuration Files</a></dt></dl></dd><dt>connection sequence, <a class="indexterm" href="#s2-ssh-conn">Event Sequence of an SSH Connection</a></dt><dt>features, <a class="indexterm" href="#s2-ssh-features">Main Features</a></dt><dt>insecure protocols, <a class="indexterm" href="#s2-ssh-configuration-requiring">Requiring SSH for Remote Connections</a></dt><dt>layers</dt><dd><dl><dt>channels, <a class="indexterm" href="#s2-ssh-protocol-connection">Channels</a></dt><dt>transport layer, <a class="indexterm" href="#s2-ssh-protocol-conn-transport">Transport La
yer</a></dt></dl></dd><dt>port forwarding, <a class="indexterm" href="#s2-ssh-beyondshell-tcpip">Port Forwarding</a></dt><dt>requiring for remote login, <a class="indexterm" href="#s2-ssh-configuration-requiring">Requiring SSH for Remote Connections</a></dt><dt>security risks, <a class="indexterm" href="#s2-ssh-why">Why Use SSH?</a></dt><dt>version 1, <a class="indexterm" href="#s2-ssh-versions">Protocol Versions</a></dt><dt>version 2, <a class="indexterm" href="#s2-ssh-versions">Protocol Versions</a></dt><dt>X11 forwarding, <a class="indexterm" href="#s2-ssh-beyondshell-x11">X11 Forwarding</a></dt></dl></dd><dt> ssh-add , <a class="indexterm" href="#s3-ssh-configuration-keypairs-agent">Configuring ssh-agent</a></dt><dt> ssh-agent , <a class="indexterm" href="#s3-ssh-configuration-keypairs-agent">Configuring ssh-agent</a></dt><dt>SSL, <a class="indexterm" href="#s1-apache-mod_ssl">Setting Up an SSL Server</a></dt><dd><dl><dt>(see also Apache HTTP Server)</dt></dl></dd><dt>SS
L server (see Apache HTTP Server)</dt><dt>SSSD</dt><dd><dl><dt>Configuring a Microsoft Active Directory Domain for, <a class="indexterm" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain">Configuring a Microsoft Active Directory Domain</a></dt><dt>Configuring a proxy domain for, <a class="indexterm" href="#sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">Configuring a Proxy Domain</a></dt><dt>Configuring an LDAP domain for, <a class="indexterm" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LDAP Domain</a></dt><dt>Selecting an LDAP schema for, <a class="indexterm" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LDAP Domain</a></dt><dt>Setting Up Kerberos authentication for, <a class="indexterm" href="#sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">Setting Up Kerberos Authent
ication</a></dt><dt>Specifying timeout values for, <a class="indexterm" href="#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LDAP Domain</a></dt></dl></dd><dt> stunnel , <a class="indexterm" href="#s3-email-security-servers">Securing Email Client Communications</a></dt><dt> sysconfig directory</dt><dd><dl><dt> /etc/sysconfig/apm-scripts/ directory, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/arpwatch , <a class="indexterm" href="#s2-sysconfig-arpwatch"> /etc/sysconfig/arpwatch </a></dt><dt> /etc/sysconfig/authconfig , <a class="indexterm" href="#s2-sysconfig-authconfig"> /etc/sysconfig/authconfig </a></dt><dt> /etc/sysconfig/autofs , <a class="indexterm" href="#s2-sysconfig-autofs"> /etc/sysconfig/autofs </a></dt><dt> /etc/sysconfig/cbq/ directory, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Director
y</a></dt><dt> /etc/sysconfig/clock , <a class="indexterm" href="#s2-sysconfig-clock"> /etc/sysconfig/clock </a></dt><dt> /etc/sysconfig/dhcpd , <a class="indexterm" href="#s2-sysconfig-dhcpd"> /etc/sysconfig/dhcpd </a></dt><dt> /etc/sysconfig/firstboot , <a class="indexterm" href="#s2-sysconfig-firewall"> /etc/sysconfig/firstboot </a></dt><dt> /etc/sysconfig/init , <a class="indexterm" href="#s2-sysconfig-init"> /etc/sysconfig/init </a></dt><dt> /etc/sysconfig/ip6tables-config , <a class="indexterm" href="#s2-sysconfig-ip6tables"> /etc/sysconfig/ip6tables-config </a></dt><dt> /etc/sysconfig/keyboard , <a class="indexterm" href="#s2-sysconfig-kybd"> /etc/sysconfig/keyboard </a></dt><dt> /etc/sysconfig/ldap , <a class="indexterm" href="#s2-sysconfig-ldap"> /etc/sysconfig/ldap </a></dt><dt> /etc/sysconfig/named , <a class="indexterm" href="#s2-sysconfig-named"> /etc/sysconfig/named </a></dt><dt> /etc/sysconfig/network , <a class="indexterm" href="#s2-sysconfig-network"> /etc/s
ysconfig/network </a></dt><dt> /etc/sysconfig/network-scripts/ directory, <a class="indexterm" href="#ch-Network_Interfaces">Network Interfaces</a>, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Directory</a></dt><dd><dl><dt>(see also network)</dt></dl></dd><dt> /etc/sysconfig/networking/ directory, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/ntpd , <a class="indexterm" href="#s2-sysconfig-ntpd"> /etc/sysconfig/ntpd </a></dt><dt> /etc/sysconfig/quagga , <a class="indexterm" href="#s2-sysconfig-quagga"> /etc/sysconfig/quagga </a></dt><dt> /etc/sysconfig/radvd , <a class="indexterm" href="#s2-sysconfig-radvd"> /etc/sysconfig/radvd </a></dt><dt> /etc/sysconfig/rhn/ directory, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/samba , <a class="indexterm" href="#s2-syscon
fig-samba"> /etc/sysconfig/samba </a></dt><dt> /etc/sysconfig/selinux , <a class="indexterm" href="#s2-sysconfig-selinux"> /etc/sysconfig/selinux </a></dt><dt> /etc/sysconfig/sendmail , <a class="indexterm" href="#s2-sysconfig-sendmail"> /etc/sysconfig/sendmail </a></dt><dt> /etc/sysconfig/spamassassin , <a class="indexterm" href="#s2-sysconfig-spamd"> /etc/sysconfig/spamassassin </a></dt><dt> /etc/sysconfig/squid , <a class="indexterm" href="#s2-sysconfig-squid"> /etc/sysconfig/squid </a></dt><dt> /etc/sysconfig/system-config-users , <a class="indexterm" href="#s2-sysconfig-rcu"> /etc/sysconfig/system-config-users </a></dt><dt> /etc/sysconfig/vncservers , <a class="indexterm" href="#s2-sysconfig-vncservers"> /etc/sysconfig/vncservers </a></dt><dt> /etc/sysconfig/xinetd , <a class="indexterm" href="#s2-sysconfig-xinetd"> /etc/sysconfig/xinetd </a></dt><dt>additional information about, <a class="indexterm" href="#ch-The_sysconfig_Directory">The sysconfig Directory</a></dt><dt
>additional resources, <a class="indexterm" href="#s1-sysconfig-additional-resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-sysconfig-installed-documentation">Installed Documentation</a></dt></dl></dd><dt>directories in, <a class="indexterm" href="#s1-sysconfig-etcsysconf-dir">Directories in the /etc/sysconfig/ Directory</a></dt><dt>files found in, <a class="indexterm" href="#s1-sysconfig-files">Files in the /etc/sysconfig/ Directory</a></dt></dl></dd><dt> sysctl </dt><dd><dl><dt>configuring with /etc/sysctl.conf , <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt><dt>controlling /proc/sys/ , <a class="indexterm" href="#s1-proc-sysctl">Using the sysctl Command</a></dt></dl></dd><dt>SysRq (see system request key)</dt><dt>system information</dt><dd><dl><dt>file systems, <a class="indexterm" href="#s1-sysinfo-filesystems">File Systems</a></dt><dd><dl><dt> /dev/shm , <a class="indexterm" href="
#s1-sysinfo-filesystems">File Systems</a></dt></dl></dd><dt>gathering, <a class="indexterm" href="#ch-Gathering_System_Information">Gathering System Information</a></dt><dt>hardware, <a class="indexterm" href="#s1-sysinfo-hardware">Hardware</a></dt><dt>memory usage, <a class="indexterm" href="#s1-sysinfo-memory-usage">Memory Usage</a></dt><dt>processes, <a class="indexterm" href="#s1-sysinfo-system-processes">System Processes</a></dt><dd><dl><dt>currently running, <a class="indexterm" href="#s1-sysinfo-system-processes">System Processes</a></dt></dl></dd></dl></dd><dt>system request key</dt><dd><dl><dt>enabling, <a class="indexterm" href="#s2-proc-dir-sys"> /proc/sys/ </a></dt></dl></dd><dt>System Request Key</dt><dd><dl><dt>definition of, <a class="indexterm" href="#s2-proc-dir-sys"> /proc/sys/ </a></dt><dt>setting timing for, <a class="indexterm" href="#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt></dl></dd><dt> system-config-authentication (see Authentication Configu
ration Tool )</dt><dt> system-config-date (see time configuration, date configuration)</dt><dt>system-config-kdump (see kdump)</dt><dt> system-config-services (see services configuration)</dt><dt> system-config-users (see user configuration and group configuration)</dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>time configuration</dt><dd><dl><dt> date , <a class="indexterm" href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">Date and Time Setup</a></dt><dt>synchronize with NTP server, <a class="indexterm" href="#sect-Date_and_Time_Configuration-Network_Time_Protocol">Network Time Protocol Properties</a>, <a class="indexterm" href="#sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">Network Time Protocol Setup</a></dt><dt> system-config-date , <a class="indexterm" href="#sect-Date_and_Time_Configuration-Date_and_Time">Date and Time Properties</a></dt></dl></dd><dt>time zone configuration, <a class="index
term" href="#sect-Date_and_Time_Configuration-Time_Zone">Time Zone Properties</a></dt><dt>TLB cache (see hugepages)</dt><dt>TLS, <a class="indexterm" href="#s1-apache-mod_ssl">Setting Up an SSL Server</a></dt><dd><dl><dt>(see also Apache HTTP Server)</dt></dl></dd><dt>tool</dt><dd><dl><dt> Authentication Configuration Tool , <a class="indexterm" href="#sect-The_Authentication_Configuration_Tool">The Authentication Configuration Tool</a></dt></dl></dd><dt> top , <a class="indexterm" href="#s1-sysinfo-system-processes">System Processes</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>updating currently installed packages</dt><dd><dl><dt>available updates, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>updating packages with PackageKit</dt><dd><dl><dt>PolicyKit, <a class="indexterm" href="#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl
></dd><dt>user configuration</dt><dd><dl><dt>adding users, <a class="indexterm" href="#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing full name, <a class="indexterm" href="#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing home directory, <a class="indexterm" href="#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing login shell, <a class="indexterm" href="#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing password, <a class="indexterm" href="#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>command line configuration, <a class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt><dd><dl><dt> passwd , <a class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt><dt> useradd , <a class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>filtering list of users, <a class="indexterm" href="#s1-users-co
nfigui">User and Group Configuration</a></dt><dt>modify groups for a user, <a class="indexterm" href="#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>modifying users, <a class="indexterm" href="#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>password</dt><dd><dl><dt>forcing expiration of, <a class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>viewing list of users, <a class="indexterm" href="#s1-users-configui">User and Group Configuration</a></dt></dl></dd><dt> User Manager (see user configuration)</dt><dt>user private groups (see groups)</dt><dd><dl><dt>and shared directories, <a class="indexterm" href="#s2-users-groups-rationale">Group Directories</a></dt></dl></dd><dt> useradd command</dt><dd><dl><dt>user account creation using, <a class="indexterm" href="#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>users (see user configuration)</dt><dd><dl><dt> /etc/passwd , <a class="inde
xterm" href="#s1-users-groups-standard-users">Standard Users</a></dt><dt>additional resources, <a class="indexterm" href="#s1-users-groups-additional-resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s2-users-groups-documentation">Installed Documentation</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="#Users_and_Groups">Users and Groups</a></dt><dt>standard, <a class="indexterm" href="#s1-users-groups-standard-users">Standard Users</a></dt><dt>tools for management of</dt><dd><dl><dt> User Manager , <a class="indexterm" href="#s1-users-tools">User and Group Management Tools</a></dt><dt> useradd , <a class="indexterm" href="#s1-users-tools">User and Group Management Tools</a></dt></dl></dd><dt>UID, <a class="indexterm" href="#Users_and_Groups">Users and Groups</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>virtual file system (see proc file system)</dt><dt>virtual files (see proc file
system)</dt><dt>virtual host (see Apache HTTP Server)</dt></dl></div><div class="indexdiv"><h3>W</h3><dl><dt>web server (see Apache HTTP Server)</dt></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>Yum</dt><dd><dl><dt>Additional Resources, <a class="indexterm" href="#sec-Additional_Resources">Additional Resources</a></dt><dt>configuring plugins, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring and Disabling Yum Plugins</a></dt><dt>configuring Yum and Yum repositories, <a class="indexterm" href="#sec-Configuring_Yum_and_Yum_Repositories">Configuring Yum and Yum Repositories</a></dt><dt>disabling plugins, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring and Disabling Yum Plugins</a></dt><dt>displaying packages</dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Informati
on</a></dt></dl></dd><dt>displaying packages with Yum, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>enabling plugins, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring and Disabling Yum Plugins</a></dt><dt>installing a package group with Yum, <a class="indexterm" href="#sec-Installing">Installing</a></dt><dt>installing with Yum, <a class="indexterm" href="#sec-Installing">Installing</a></dt><dt>listing packages with Yum, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dd><dl><dt>Glob expressions, <a class="indexterm" href="#sec-Searching_Listi
ng_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum grouplist, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list all, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list available, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list installed, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum repolist, <a class="indexterm" href="#sec
-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>packages and package groups, <a class="indexterm" href="#sec-Packages_and_Package_Groups">Packages and Package Groups</a></dt><dt>plugins</dt><dd><dl><dt>PackageKit-yum-plugin, <a class="indexterm" href="#sec-Plugin_Descriptions">Plugin Descriptions</a></dt><dt>rhnplugin, <a class="indexterm" href="#sec-Plugin_Descriptions">Plugin Descriptions</a></dt><dt>yum-plugin-protect-packages, <a class="indexterm" href="#sec-Plugin_Descriptions">Plugin Descriptions</a></dt><dt>yum-plugin-security, <a class="indexterm" href="#sec-Plugin_Descriptions">Plugin Descriptions</a></dt><dt>yum-presto, <a class="indexterm" href="#sec-Plugin_Descriptions">Plugin Descriptions</a></dt><dt>yum-rhn-plugin, <a class="indexterm" href="#sec-Plugin_Descriptions">Plugin Descriptions</a></dt></dl></dd><dt>repository, <a class="indexterm" href="#sec-Creating_a_Yum_Repository">C
reating a Yum Repository</a></dt><dt>searching for packages with Yum</dt><dd><dl><dt>yum search, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>searching packages with Yum, <a class="indexterm" href="#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>setting [main] options, <a class="indexterm" href="#sec-Setting_main_Options">Setting [main] Options</a></dt><dt>setting [repository] options, <a class="indexterm" href="#sec-Setting_repository_Options">Setting [repository] Options</a></dt><dt>uninstalling package groups with Yum, <a class="indexterm" href="#sec-Removing">Removing</a></dt><dt>uninstalling packages with Yum, <a class="indexterm" href="#sec-Removing">Removing</a></dt><dd><dl><dt>yum remove package_name, <a class="indexterm" href="#sec-Removing">Removing</a></dt></dl></dd><dt>var
iables, <a class="indexterm" href="#sec-Using_Yum_Variables">Using Yum Variables</a></dt><dt>Yum plugins, <a class="indexterm" href="#sec-Yum_Plugins">Yum Plugins</a></dt><dt>Yum repositories</dt><dd><dl><dt>configuring Yum and Yum repositories, <a class="indexterm" href="#sec-Configuring_Yum_and_Yum_Repositories">Configuring Yum and Yum Repositories</a></dt></dl></dd></dl></dd><dt>Yum repositories</dt><dd><dl><dt>viewing Yum repositories with PackageKit, <a class="indexterm" href="#sec-Refreshing_Software_Sources_Yum_Repositories">Refreshing Software Sources (Yum Repositories)</a></dt></dl></dd><dt>Yum Updates</dt><dd><dl><dt>checking for updates, <a class="indexterm" href="#sec-Checking_For_Updates">Checking For Updates</a></dt><dt>updating a single package, <a class="indexterm" href="#sec-Updating_Packages">Updating Packages</a></dt><dt>updating all packages and dependencies, <a class="indexterm" href="#sec-Updating_Packages">Updating Packages</a></dt><dt>updating package
s, <a class="indexterm" href="#sec-Updating_Packages">Updating Packages</a></dt><dt>updating security-related packages, <a class="indexterm" href="#sec-Updating_Security-Related_Packages">Updating Security-Related Packages</a></dt></dl></dd></dl></div></div></div></div></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Acknowledgements.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/Acknowledgements.html
new file mode 100644
index 0000000..79f5a22
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Acknowledgements.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3. Acknowledgements</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pr01.html" title="Preface" /><link rel="prev" href="sect-RedHat-We_Need_Feedback.html" title="2. We Need Feedback!" /><link rel="next" href="ch-intro.html" title="Introduction" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-RedHat-We_Need_Feedback.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-intro.html"><strong>Next</strong></a></l
i></ul><div class="section" title="3. Acknowledgements" id="Acknowledgements"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="Acknowledgements">3. Acknowledgements</h2></div></div></div><div class="para">
+ Certain portions of this text first appeared in the <em class="citetitle">Deployment Guide</em>, copyright © 2007 Red Hat, Inc., available at <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/index.html">http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/index.html</a>.
+ </div><div class="para">
+ The authors of this book would like to thank the following people for their valuable contributions: Adam Tkáč, Andrew Fitzsimon, Andrius Benokraitis, Brian Cleary Edward Bailey, Garrett LeSage, Jeffrey Fearn, Joe Orton, Joshua Wulf, KarstenWade, Lucy Ringland, Marcela Mašláňová, Mark Johnson, Michael Behm, Michael Behm, Miroslav Lichvár, Radek Vokál, Rahul Kavalapara, Rahul Sundaram, Sandra Moore, and Zbyšek Mráz, among many others.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-RedHat-We_Need_Feedback.html"><strong>Prev</strong>2. We Need Feedback!</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-intro.html"><strong>Next</strong>Introduction</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/common.css b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/common.css
new file mode 100644
index 0000000..9d2ddca
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/common.css
@@ -0,0 +1,1474 @@
+body, h1, h2, h3, h4, h5, h6, pre, li, div {
+ line-height: 1.29em;
+}
+
+body {
+ background-color: white;
+ margin:0 auto;
+ font-family: "liberation sans", "Myriad ", "Bitstream Vera Sans", "Lucida Grande", "Luxi Sans", "Trebuchet MS", helvetica, verdana, arial, sans-serif;
+ font-size:12px;
+ max-width:55em;
+ color:black;
+}
+
+body.toc_embeded {
+ /*for web hosting system only*/
+ margin-left: 300px;
+}
+
+object.toc, iframe.toc {
+ /*for web hosting system only*/
+ border-style:none;
+ position:fixed;
+ width:290px;
+ height:99.99%;
+ top:0;
+ left:0;
+ z-index: 100;
+ border-style:none;
+ border-right:1px solid #999;
+}
+
+/* desktop styles */
+body.desktop {
+ margin-left: 26em;
+}
+
+body.desktop .book > .toc {
+ display:block;
+ width:24em;
+ height:99%;
+ position:fixed;
+ overflow:auto;
+ top:0px;
+ left:0px;
+ padding-left:1em;
+ background-color:#EEEEEE;
+}
+
+.toc {
+ line-height:1.35em;
+}
+
+.toc .glossary,
+.toc .chapter, .toc .appendix {
+ margin-top:1em;
+}
+
+.toc .part {
+ margin-top:1em;
+ display:block;
+}
+
+span.glossary,
+span.appendix {
+ display:block;
+ margin-top:0.5em;
+}
+
+div {
+ padding-top:0px;
+}
+
+div.section {
+ padding-top:1em;
+}
+
+p, div.para, div.formalpara {
+ padding-top:0px;
+ margin-top:0.3em;
+ padding-bottom:0px;
+ margin-bottom:1em;
+}
+
+/*Links*/
+a {
+ outline: none;
+}
+
+a:link {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#3366cc;
+}
+
+a:visited {
+ text-decoration:none;
+ border-bottom: 1px dotted ;
+ color:#003366;
+}
+
+div.longdesc-link {
+ float:right;
+ color:#999;
+}
+
+.toc a, .qandaset a {
+ font-weight:normal;
+}
+
+/*headings*/
+h1, h2, h3, h4, h5, h6 {
+ color: #336699;
+ margin-top: 0em;
+ margin-bottom: 0em;
+ background-color: transparent;
+}
+
+h1 {
+ font-size:2.0em;
+}
+
+.titlepage h1.title {
+ font-size: 3.0em;
+ padding-top: 1em;
+ text-align:left;
+}
+
+.book > .titlepage h1.title {
+ text-align:center;
+}
+
+.article > .titlepage h1.title {
+ text-align:center;
+}
+
+.set .titlepage > div > div > h1.title {
+ text-align:center;
+}
+
+.producttitle {
+ margin-top: 0em;
+ margin-bottom: 0em;
+ font-size: 3.0em;
+ font-weight: bold;
+ background: #003d6e url(../images/h1-bg.png) top left repeat-x;
+ color: white;
+ text-align: center;
+ padding: 0.7em;
+}
+
+.titlepage .corpauthor {
+ margin-top: 1em;
+ text-align: center;
+}
+
+.section h1.title {
+ font-size: 1.6em;
+ padding: 0em;
+ color: #336699;
+ text-align: left;
+ background: white;
+}
+
+h2 {
+ font-size:1.6em;
+}
+
+
+h2.subtitle, h3.subtitle {
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ text-align: center;
+}
+
+.preface > div > div > div > h2.title {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+.appendix h2 {
+ margin-top: 1em;
+ font-size: 2.0em;
+}
+
+
+
+h3 {
+ font-size:1.3em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+h4 {
+ font-size:1.1em;
+ padding-top:0em;
+ padding-bottom:0em;
+}
+
+h5 {
+ font-size:1em;
+}
+
+h6 {
+ font-size:1em;
+}
+
+h5.formalpara {
+ font-size:1em;
+ margin-top:2em;
+ margin-bottom:.8em;
+}
+
+.abstract h6 {
+ margin-top:1em;
+ margin-bottom:.5em;
+ font-size:2em;
+}
+
+/*element rules*/
+hr {
+ border-collapse: collapse;
+ border-style:none;
+ border-top: 1px dotted #ccc;
+ width:100%;
+ margin-top: 3em;
+}
+
+/* web site rules */
+ul.languages, .languages li {
+ display:inline;
+ padding:0em;
+}
+
+.languages li a {
+ padding:0em .5em;
+ text-decoration: none;
+}
+
+.languages li p, .languages li div.para {
+ display:inline;
+}
+
+.languages li a:link, .languages li a:visited {
+ color:#444;
+}
+
+.languages li a:hover, .languages li a:focus, .languages li a:active {
+ color:black;
+}
+
+ul.languages {
+ display:block;
+ background-color:#eee;
+ padding:.5em;
+}
+
+/*supporting stylesheets*/
+
+/*unique to the webpage only*/
+.books {
+ position:relative;
+}
+
+.versions li {
+ width:100%;
+ clear:both;
+ display:block;
+}
+
+a.version {
+ font-size:2em;
+ text-decoration:none;
+ width:100%;
+ display:block;
+ padding:1em 0em .2em 0em;
+ clear:both;
+}
+
+a.version:before {
+ content:"Version";
+ font-size:smaller;
+}
+
+a.version:visited, a.version:link {
+ color:#666;
+}
+
+a.version:focus, a.version:hover {
+ color:black;
+}
+
+.books {
+ display:block;
+ position:relative;
+ clear:both;
+ width:100%;
+}
+
+.books li {
+ display:block;
+ width:200px;
+ float:left;
+ position:relative;
+ clear: none ;
+}
+
+.books .html {
+ width:170px;
+ display:block;
+}
+
+.books .pdf {
+ position:absolute;
+ left:170px;
+ top:0px;
+ font-size:smaller;
+}
+
+.books .pdf:link, .books .pdf:visited {
+ color:#555;
+}
+
+.books .pdf:hover, .books .pdf:focus {
+ color:#000;
+}
+
+.books li a {
+ text-decoration:none;
+}
+
+.books li a:hover {
+ color:black;
+}
+
+/*products*/
+.products li {
+ display: block;
+ width:300px;
+ float:left;
+}
+
+.products li a {
+ width:300px;
+ padding:.5em 0em;
+}
+
+.products ul {
+ clear:both;
+}
+
+/*revision history*/
+.revhistory {
+ display:block;
+}
+
+.revhistory table {
+ background-color:transparent;
+ border-color:#fff;
+ padding:0em;
+ margin: 0;
+ border-collapse:collapse;
+ border-style:none;
+}
+
+.revhistory td {
+ text-align :left;
+ padding:0em;
+ border: none;
+ border-top: 1px solid #fff;
+ font-weight: bold;
+}
+
+.revhistory .simplelist td {
+ font-weight: normal;
+}
+
+.revhistory .simplelist {
+ margin-bottom: 1.5em;
+ margin-left: 1em;
+}
+
+.revhistory table th {
+ display: none;
+}
+
+
+/*credits*/
+.authorgroup div {
+ clear:both;
+ text-align: center;
+}
+
+h3.author {
+ margin: 0em;
+ padding: 0em;
+ padding-top: 1em;
+}
+
+.authorgroup h4 {
+ padding: 0em;
+ margin: 0em;
+ padding-top: 1em;
+ margin-top: 1em;
+}
+
+.author,
+.editor,
+.translator,
+.othercredit,
+.contrib {
+ display: block;
+}
+
+.revhistory .author {
+ display: inline;
+}
+
+.othercredit h3 {
+ padding-top: 1em;
+}
+
+
+.othercredit {
+ margin:0em;
+ padding:0em;
+}
+
+.releaseinfo {
+ clear: both;
+}
+
+.copyright {
+ margin-top: 1em;
+}
+
+/* qanda sets */
+.answer {
+ margin-bottom:1em;
+ border-bottom:1px dotted #ccc;
+}
+
+.qandaset .toc {
+ border-bottom:1px dotted #ccc;
+}
+
+.question {
+ font-weight:bold;
+}
+
+.answer .data, .question .data {
+ padding-left: 2.6em;
+}
+
+.answer label, .question label {
+ float:left;
+ font-weight:bold;
+}
+
+/* inline syntax highlighting */
+.perl_Alert {
+ color: #0000ff;
+}
+
+.perl_BaseN {
+ color: #007f00;
+}
+
+.perl_BString {
+ color: #5C3566;
+}
+
+.perl_Char {
+ color: #ff00ff;
+}
+
+.perl_Comment {
+ color: #FF00FF;
+}
+
+
+.perl_DataType {
+ color: #0000ff;
+}
+
+
+.perl_DecVal {
+ color: #00007f;
+}
+
+
+.perl_Error {
+ color: #ff0000;
+}
+
+
+.perl_Float {
+ color: #00007f;
+}
+
+
+.perl_Function {
+ color: #007f00;
+}
+
+
+.perl_IString {
+ color: #5C3566;
+}
+
+
+.perl_Keyword {
+ color: #002F5D;
+}
+
+
+.perl_Operator {
+ color: #ffa500;
+}
+
+
+.perl_Others {
+ color: #b03060;
+}
+
+
+.perl_RegionMarker {
+ color: #96b9ff;
+}
+
+
+.perl_Reserved {
+ color: #9b30ff;
+}
+
+
+.perl_String {
+ color: #5C3566;
+}
+
+
+.perl_Variable {
+ color: #0000ff;
+}
+
+
+.perl_Warning {
+ color: #0000ff;
+}
+
+/*Lists*/
+ul {
+ padding-left:1.6em;
+ list-style-image:url(../images/dot.png);
+ list-style-type: circle;
+}
+
+ul ul {
+ list-style-image:url(../images/dot2.png);
+ list-style-type: circle;
+}
+
+ol {
+ list-style-image:none;
+ list-style-type: decimal;
+}
+
+ol ol {
+ list-style-type: lower-alpha;
+}
+
+ol.arabic {
+ list-style-type: decimal;
+}
+
+ol.loweralpha {
+ list-style-type: lower-alpha;
+}
+
+ol.lowerroman {
+ list-style-type: lower-roman;
+}
+
+ol.upperalpha {
+ list-style-type: upper-alpha;
+}
+
+ol.upperroman {
+ list-style-type: upper-roman;
+}
+
+dt {
+ font-weight:bold;
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+dd {
+ margin:0em;
+ margin-left:2em;
+ padding-top:0em;
+ padding-bottom: 1em;
+}
+
+li {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.4em;
+}
+
+li p, li div.para {
+ padding-top:0px;
+ margin-top:0em;
+ padding-bottom:0px;
+ margin-bottom:0.3em;
+}
+
+/*images*/
+img {
+ display:block;
+ margin: 2em 0;
+}
+
+.inlinemediaobject, .inlinemediaobject img {
+ display:inline;
+ margin:0em;
+}
+
+.figure img {
+ display:block;
+ margin:0;
+}
+
+.figure .title {
+ margin:0em;
+ margin-bottom:2em;
+ padding:0px;
+}
+
+/*document modes*/
+.confidential {
+ background-color:#900;
+ color:White;
+ padding:.5em .5em;
+ text-transform:uppercase;
+ text-align:center;
+}
+
+.longdesc-link {
+ display:none;
+}
+
+.longdesc {
+ display:none;
+}
+
+.prompt {
+ padding:0em .3em;
+}
+
+/*user interface styles*/
+.screen .replaceable {
+}
+
+.guibutton, .guilabel {
+ font-family: "liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight: bold;
+ white-space: nowrap;
+}
+
+.example {
+ background-color: #ffffff;
+ border-left: 3px solid #aaaaaa;
+ padding-top: 1em;
+ padding-bottom: 0.1em;
+}
+
+.example h6 {
+ padding-left: 10px;
+}
+
+.example-contents {
+ padding-left: 10px;
+ background-color: #ffffff;
+}
+
+.example-contents .para {
+/* padding: 10px;*/
+}
+
+/*terminal/console text*/
+.computeroutput,
+.option {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+.replaceable {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-style: italic;
+}
+
+.command, .filename, .keycap, .classname, .literal {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ font-weight:bold;
+}
+
+/* no bold in toc */
+.toc * {
+ font-weight: inherit;
+}
+
+pre {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ display:block;
+ background-color: #f5f5f5;
+ color: #000000;
+ border: 1px solid #aaaaaa;
+ margin-bottom: 0.3em;
+ padding:.5em 1em;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+ font-size: 0.9em;
+}
+
+pre .replaceable,
+pre .keycap {
+}
+
+code {
+ font-family:"liberation mono", "bitstream vera mono", "dejavu mono", monospace;
+ white-space: nowrap;
+ font-weight:bold;
+}
+
+.parameter code {
+ display: inline;
+ white-space: pre-wrap; /* css-3 */
+ white-space: -moz-pre-wrap !important; /* Mozilla, since 1999 */
+ white-space: -pre-wrap; /* Opera 4-6 */
+ white-space: -o-pre-wrap; /* Opera 7 */
+ word-wrap: break-word; /* Internet Explorer 5.5+ */
+}
+
+/*Notifications*/
+div.warning:before {
+ content:url(../images/warning.png);
+ padding-left: 5px;
+}
+
+div.note:before {
+ content:url(../images/note.png);
+ padding-left: 5px;
+}
+
+div.important:before {
+ content:url(../images/important.png);
+ padding-left: 5px;
+}
+
+div.warning, div.note, div.important {
+ color: black;
+ margin: 0em;
+ padding: 0em;
+ background: none;
+ background-color: white;
+ margin-bottom: 1em;
+ border-bottom: 1px solid #aaaaaa;
+}
+
+div.warning h2, div.note h2,div.important h2 {
+ margin: 0em;
+ padding: 0em;
+ color: #eeeeec;
+ padding-top: 0px;
+ padding-bottom: 0px;
+ height: 1.4em;
+ line-height: 1.4em;
+ font-size: 1.4em;
+ display:inline;
+}
+
+div.admonition_header {
+ clear: both;
+ margin: 0em;
+ padding: 0em;
+ margin-top: -3.3em;
+ padding-left: 58px;
+ line-height: 1.0em;
+ font-size: 1.0em;
+}
+
+div.warning div.admonition_header {
+ background: url(../images/red.png) top left repeat-x;
+ background-color: #590000;
+}
+
+div.note div.admonition_header {
+ background: url(../images/green.png) top right repeat-x;
+ background-color: #597800;
+}
+
+div.important div.admonition_header {
+ background: url(../images/yellow.png) top right repeat-x;
+ background-color: #a6710f;
+}
+
+div.warning p, div.warning div.para,
+div.note p, div.note div.para,
+div.important p, div.important div.para {
+ padding: 0em;
+ margin: 0em;
+}
+
+div.admonition {
+ border: none;
+ border-left: 1px solid #aaaaaa;
+ border-right: 1px solid #aaaaaa;
+ padding:0em;
+ margin:0em;
+ padding-top: 1.5em;
+ padding-bottom: 1em;
+ padding-left: 2em;
+ padding-right: 1em;
+ background-color: #eeeeec;
+ -moz-border-radius: 0px;
+ -webkit-border-radius: 0px;
+ border-radius: 0px;
+}
+
+/*Page Title*/
+#title {
+ display:block;
+ height:45px;
+ padding-bottom:1em;
+ margin:0em;
+}
+
+#title a.left{
+ display:inline;
+ border:none;
+}
+
+#title a.left img{
+ border:none;
+ float:left;
+ margin:0em;
+ margin-top:.7em;
+}
+
+#title a.right {
+ padding-bottom:1em;
+}
+
+#title a.right img {
+ border:none;
+ float:right;
+ margin:0em;
+ margin-top:.7em;
+}
+
+/*Table*/
+table {
+ border:1px solid #6c614b;
+ width:100%;
+ border-collapse:collapse;
+}
+
+table.simplelist, .calloutlist table {
+ border-style: none;
+}
+
+table th {
+ text-align:left;
+ background-color:#6699cc;
+ padding:.3em .5em;
+ color:white;
+}
+
+table td {
+ padding:.15em .5em;
+}
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+table th p:first-child, table td p:first-child, table li p:first-child,
+table th div.para:first-child, table td div.para:first-child, table li div.para:first-child {
+ margin-top:0em;
+ padding-top:0em;
+ display:inline;
+}
+
+th, td {
+ border-style:none;
+ vertical-align: top;
+ border: 1px solid #000;
+}
+
+.simplelist th, .simplelist td {
+ border: none;
+}
+
+table table td {
+ border-bottom:1px dotted #aaa;
+ background-color:white;
+ padding:.6em 0em;
+}
+
+table table {
+ border:1px solid white;
+}
+
+td.remarkval {
+ color:#444;
+}
+
+td.fieldval {
+ font-weight:bold;
+}
+
+.lbname, .lbtype, .lbdescr, .lbdriver, .lbhost {
+ color:white;
+ font-weight:bold;
+ background-color:#999;
+ width:120px;
+}
+
+td.remarkval {
+ width:230px;
+}
+
+td.tname {
+ font-weight:bold;
+}
+
+th.dbfield {
+ width:120px;
+}
+
+th.dbtype {
+ width:70px;
+}
+
+th.dbdefault {
+ width:70px;
+}
+
+th.dbnul {
+ width:70px;
+}
+
+th.dbkey {
+ width:70px;
+}
+
+span.book {
+ margin-top:4em;
+ display:block;
+}
+
+span.chapter {
+ display:block;
+ margin-top:0.5em;
+}
+
+table.simplelist td, .calloutlist table td {
+ border-style: none;
+}
+
+/*Breadcrumbs*/
+#breadcrumbs ul li.first:before {
+ content:" ";
+}
+
+#breadcrumbs {
+ color:#900;
+ padding:3px;
+ margin-bottom:25px;
+}
+
+#breadcrumbs ul {
+ margin-left:0;
+ padding-left:0;
+ display:inline;
+ border:none;
+}
+
+#breadcrumbs ul li {
+ margin-left:0;
+ padding-left:2px;
+ border:none;
+ list-style:none;
+ display:inline;
+}
+
+#breadcrumbs ul li:before {
+ content:"\0020 \0020 \0020 \00BB \0020";
+ color:#333;
+}
+
+/*index*/
+.glossary h3,
+.index h3 {
+ font-size: 2em;
+ color:#aaa;
+ margin:0em;
+}
+
+.indexdiv {
+ margin-bottom:1em;
+}
+
+.glossary dt,
+.index dt {
+ color:#444;
+ padding-top:.5em;
+}
+
+.glossary dl dl dt,
+.index dl dl dt {
+ color:#777;
+ font-weight:normal;
+ padding-top:0em;
+}
+
+.index dl dl dt:before {
+ content:"- ";
+ color:#ccc;
+}
+
+/*changes*/
+.footnote {
+ font-size: .7em;
+ margin:0em;
+ color:#222;
+}
+
+table .footnote {
+}
+
+sup {
+ color:#999;
+ margin:0em;
+ padding:0em;
+ line-height: .4em;
+ font-size: 1em;
+ padding-left:0em;
+}
+
+.footnote {
+ position:relative;
+}
+
+.footnote sup {
+ color:#e3dcc0;
+ position:absolute;
+ left: .4em;
+}
+
+.footnote sup a:link,
+.footnote sup a:visited {
+ color:#92917d;
+ text-decoration:none;
+}
+
+.footnote:hover sup a {
+ text-decoration:none;
+}
+
+.footnote p,.footnote div.para {
+ padding-left:2em;
+}
+
+.footnote a:link,
+.footnote a:visited {
+ color:#00537c;
+}
+
+.footnote a:hover {
+}
+
+/**/
+div.chapter {
+ margin-top:3em;
+}
+
+div.section {
+ margin-top:1em;
+}
+
+div.note .replaceable,
+div.important .replaceable,
+div.warning .replaceable,
+div.note .keycap,
+div.important .keycap,
+div.warning .keycap
+{
+}
+
+ul li p:last-child, ul li div.para:last-child {
+ margin-bottom:0em;
+ padding-bottom:0em;
+}
+
+/*document navigation*/
+.docnav a, .docnav strong {
+ border:none;
+ text-decoration:none;
+ font-weight:normal;
+}
+
+.docnav {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ position:relative;
+ width:100%;
+ padding-bottom:2em;
+ padding-top:1em;
+ border-top:1px dotted #ccc;
+}
+
+.docnav li {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+ display:inline;
+ font-size:.8em;
+}
+
+.docnav li:before {
+ content:" ";
+}
+
+.docnav li.previous, .docnav li.next {
+ position:absolute;
+ top:1em;
+}
+
+.docnav li.up, .docnav li.home {
+ margin:0em 1.5em;
+}
+
+.docnav li.previous {
+ left:0px;
+ text-align:left;
+}
+
+.docnav li.next {
+ right:0px;
+ text-align:right;
+}
+
+.docnav li.previous strong, .docnav li.next strong {
+ height:22px;
+ display:block;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+.docnav li.next a strong {
+ background: url(../images/stock-go-forward.png) top right no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-right:28px;
+ font-size:1.2em;
+}
+
+.docnav li.previous a strong {
+ background: url(../images/stock-go-back.png) top left no-repeat;
+ padding-top:3px;
+ padding-bottom:4px;
+ padding-left:28px;
+ padding-right:0.5em;
+ font-size:1.2em;
+}
+
+.docnav li.home a strong {
+ background: url(../images/stock-home.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav li.up a strong {
+ background: url(../images/stock-go-up.png) top left no-repeat;
+ padding:5px;
+ padding-left:28px;
+ font-size:1.2em;
+}
+
+.docnav a:link, .docnav a:visited {
+ color:#666;
+}
+
+.docnav a:hover, .docnav a:focus, .docnav a:active {
+ color:black;
+}
+
+.docnav a {
+ max-width: 10em;
+ overflow:hidden;
+}
+
+.docnav a:link strong {
+ text-decoration:none;
+}
+
+.docnav {
+ margin:0 auto;
+ text-align:center;
+}
+
+ul.docnav {
+ margin-bottom: 1em;
+}
+/* Reports */
+.reports ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.reports li{
+ margin:0em;
+ padding:0em;
+}
+
+.reports li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.reports dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.reports dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.reports h2, .reports h3{
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.reports div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/*uniform*/
+body.results, body.reports {
+ max-width:57em ;
+ padding:0em;
+}
+
+/*Progress Bar*/
+div.progress {
+ display:block;
+ float:left;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ height:1em;
+}
+
+div.progress span {
+ height:1em;
+ float:left;
+}
+
+div.progress span.translated {
+ background:#6c3 url(../images/shine.png) top left repeat-x;
+}
+
+div.progress span.fuzzy {
+ background:#ff9f00 url(../images/shine.png) top left repeat-x;
+}
+
+
+/*Results*/
+
+.results ul {
+ list-style:none;
+ margin:0em;
+ padding:0em;
+}
+
+.results li{
+ margin:0em;
+ padding:0em;
+}
+
+.results li.odd {
+ background-color: #eeeeee;
+ margin:0em;
+ padding:0em;
+}
+
+.results dl {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ float:right;
+ margin-right: 17em;
+ margin-top:-1.3em;
+}
+
+.results dt {
+ display:inline;
+ margin:0em;
+ padding:0em;
+}
+
+.results dd {
+ display:inline;
+ margin:0em;
+ padding:0em;
+ padding-right:.5em;
+}
+
+.results h2, .results h3 {
+ display:inline;
+ padding-right:.5em;
+ font-size:10pt;
+ font-weight:normal;
+}
+
+.results div.progress {
+ display:inline;
+ float:right;
+ width:16em;
+ background:#c00 url(../images/shine.png) top left repeat-x;
+ margin:0em;
+ margin-top:-1.3em;
+ padding:0em;
+ border:none;
+}
+
+/* Dirty EVIL Mozilla hack for round corners */
+pre {
+ -moz-border-radius:11px;
+ -webkit-border-radius:11px;
+ border-radius: 11px;
+}
+
+.example {
+ -moz-border-radius:0px;
+ -webkit-border-radius:0px;
+ border-radius: 0px;
+}
+
+.package, .citetitle {
+ font-style: italic;
+}
+
+.titlepage .edition {
+ color: #336699;
+ background-color: transparent;
+ margin-top: 1em;
+ margin-bottom: 1em;
+ font-size: 1.4em;
+ font-weight: bold;
+ text-align: center;
+}
+
+span.remark {
+ background-color: #ff00ff;
+}
+
+.draft {
+ background-image: url(../images/watermark-draft.png);
+ background-repeat: repeat-y;
+ background-position: center;
+}
+
+.foreignphrase {
+ font-style: inherit;
+}
+
+dt {
+ clear:both;
+}
+
+dt img {
+ border-style: none;
+ max-width: 112px;
+}
+
+dt object {
+ max-width: 112px;
+}
+
+dt .inlinemediaobject, dt object {
+ display: inline;
+ float: left;
+ margin-bottom: 1em;
+ padding-right: 1em;
+ width: 112px;
+}
+
+dl:after {
+ display: block;
+ clear: both;
+ content: "";
+}
+
+.toc dd {
+ padding-bottom: 0em;
+ margin-bottom: 1em;
+ padding-left: 1.3em;
+ margin-left: 0em;
+}
+
+div.toc > dl > dt {
+ padding-bottom: 0em;
+ margin-bottom: 0em;
+ margin-top: 1em;
+}
+
+
+.strikethrough {
+ text-decoration: line-through;
+}
+
+.underline {
+ text-decoration: underline;
+}
+
+.calloutlist img, .callout {
+ padding: 0em;
+ margin: 0em;
+ width: 12pt;
+ display: inline;
+ vertical-align: middle;
+}
+
+.stepalternatives {
+ list-style-image: none;
+ list-style-type: none;
+}
+
+
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/default.css b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/default.css
new file mode 100644
index 0000000..bf38ebb
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/default.css
@@ -0,0 +1,3 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/lang.css b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/lang.css
new file mode 100644
index 0000000..81c3115
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/lang.css
@@ -0,0 +1,2 @@
+/* place holder */
+
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/overrides.css b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/overrides.css
new file mode 100644
index 0000000..057be29
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/overrides.css
@@ -0,0 +1,51 @@
+a:link {
+ color:#0066cc;
+}
+
+a:hover, a:active {
+ color:#003366;
+}
+
+a:visited {
+ color:#6699cc;
+}
+
+
+h1 {
+ color:#3c6eb4
+}
+
+.producttitle {
+ background: #3c6eb4 url(../images/h1-bg.png) top left repeat;
+}
+
+.section h1.title {
+ color:#3c6eb4;
+}
+
+
+h2,h3,h4,h5,h6 {
+ color:#3c6eb4;
+}
+
+table {
+ border:1px solid #3c6eb4;
+}
+
+table th {
+ background-color:#3c6eb4;
+}
+
+
+table tr.even td {
+ background-color:#f5f5f5;
+}
+
+.revhistory table th {
+ color:#3c6eb4;
+}
+
+.titlepage .edition {
+ color: #3c6eb4;
+}
+
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/print.css b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/print.css
new file mode 100644
index 0000000..773d8ae
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/css/print.css
@@ -0,0 +1,16 @@
+ at import url("common.css");
+ at import url("overrides.css");
+ at import url("lang.css");
+
+#tocframe {
+ display: none;
+}
+
+body.toc_embeded {
+ margin-left: 30px;
+}
+
+.producttitle {
+ color: #336699;
+}
+
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/1.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/1.png
new file mode 100644
index 0000000..c21d7a3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/1.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/1.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/1.svg
new file mode 100644
index 0000000..a2b3903
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/1.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#000000;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 17.853468,22.008438 -2.564941,0 0,-7.022461 c -5e-6,-0.143873 -5e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224122,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08854,0.08302 -0.17432,0.157723 -0.257324,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/10.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/10.png
new file mode 100644
index 0000000..15b81da
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/10.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/10.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/10.svg
new file mode 100644
index 0000000..af015ab
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/10.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/11.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/11.png
new file mode 100644
index 0000000..2fcc2dd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/11.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/11.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/11.svg
new file mode 100644
index 0000000..cb82b70
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/11.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/12.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/12.png
new file mode 100644
index 0000000..edebe20
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/12.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/12.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/12.svg
new file mode 100644
index 0000000..3b6d822
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/12.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/13.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/13.png
new file mode 100644
index 0000000..ec48cef
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/13.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/13.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/13.svg
new file mode 100644
index 0000000..226e461
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/13.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/14.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/14.png
new file mode 100644
index 0000000..33d5637
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/14.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/14.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/14.svg
new file mode 100644
index 0000000..5aaa3a3
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/14.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/15.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/15.png
new file mode 100644
index 0000000..f1a4eb2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/15.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/15.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/15.svg
new file mode 100644
index 0000000..f51dd96
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/15.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2839"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2841"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/16.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/16.png
new file mode 100644
index 0000000..d38a155
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/16.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/16.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/16.svg
new file mode 100644
index 0000000..cb7e2f5
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/16.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/17.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/17.png
new file mode 100644
index 0000000..d83e898
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/17.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/17.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/17.svg
new file mode 100644
index 0000000..5d6f0ad
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/17.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/18.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/18.png
new file mode 100644
index 0000000..9e39de4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/18.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/18.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/18.svg
new file mode 100644
index 0000000..9ea672c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/18.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/19.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/19.png
new file mode 100644
index 0000000..9eeedfb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/19.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/19.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/19.svg
new file mode 100644
index 0000000..80d1d09
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/19.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 13.215925,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141118,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168787,0.157724 -0.257325,0.240723 -0.08854,0.08302 -0.1743194,0.157723 -0.2573238,0.224121 L 8.442976,14.529434 7.1978588,12.985489 11.107527,9.8726959 l 2.108398,0 0,12.1357421"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/2.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/2.png
new file mode 100644
index 0000000..ff9cc57
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/2.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/2.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/2.svg
new file mode 100644
index 0000000..8e94260
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/2.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.89546,22.008438 -8.143066,0 0,-1.784668 2.855468,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979493,-1.0708 0.293289,-0.326492 0.545079,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.373529,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.17431,-0.666821 0.174316,-1.037598 -6e-6,-0.409496 -0.124517,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827313,0.522958 -1.270019,0.921386 l -1.394531,-1.651855 c 0.249022,-0.226877 0.509113,-0.442698 0.780273,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079102,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319824,-0.1494141 0.58105,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187012,0.6889648 0.326489,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.893727 0.265625,1.41
9433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/20.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/20.png
new file mode 100644
index 0000000..b28b4aa
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/20.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/20.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/20.svg
new file mode 100644
index 0000000..409ac6e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/20.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/21.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/21.png
new file mode 100644
index 0000000..eda952c
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/21.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/21.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/21.svg
new file mode 100644
index 0000000..7bc03af
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/21.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/22.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/22.png
new file mode 100644
index 0000000..90b14b0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/22.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/22.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/22.svg
new file mode 100644
index 0000000..fe086f6
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/22.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/23.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/23.png
new file mode 100644
index 0000000..8b35a74
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/23.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/23.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/23.svg
new file mode 100644
index 0000000..f17ec29
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/23.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/24.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/24.png
new file mode 100644
index 0000000..6041b02
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/24.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/24.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/24.svg
new file mode 100644
index 0000000..42a5333
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/24.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/25.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/25.png
new file mode 100644
index 0000000..ecb15e6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/25.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/25.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/25.svg
new file mode 100644
index 0000000..a8d4672
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/25.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/26.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/26.png
new file mode 100644
index 0000000..4b2f560
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/26.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/26.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/26.svg
new file mode 100644
index 0000000..3cf00ec
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/26.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/27.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/27.png
new file mode 100644
index 0000000..ecf058e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/27.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/27.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/27.svg
new file mode 100644
index 0000000..c8d6440
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/27.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/28.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/28.png
new file mode 100644
index 0000000..e64efb2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/28.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/28.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/28.svg
new file mode 100644
index 0000000..5acce93
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/28.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/29.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/29.png
new file mode 100644
index 0000000..dbbca1b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/29.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/29.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/29.svg
new file mode 100644
index 0000000..507dd44
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/29.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.257917,22.008438 -8.143066,0 0,-1.784668 2.8554687,-3.07959 c 0.3596963,-0.387364 0.6861933,-0.744297 0.9794923,-1.0708 0.293289,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373536,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437178,10e-6 -0.857751,0.10792 -1.2617183,0.323731 C 9.3422244,12.379541 8.918885,12.68667 8.4761791,13.085098 L 7.0816479,11.433243 C 7.3306704,11.206366 7.5907613,10.990545 7.8619213,10.785782 8.1330785,10.575507 8.4319063,10.390123 8.7584057,10.22963 9.0849004,10.06916 9.4446006,9.9418812 9.8375072,9.8477936 10.230407,9.7481965 10.670348,9.6983918 11.157331,9.6983795 c 0.58105,1.23e-5 1.101232,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860508,0.3901488 1.187012,0.6889648 0.32649,0.293305 0.575513,0.650239 0.74707,1.070801 0.177075,0.420583 0.265617,0.89
3727 0.265625,1.419433 -8e-6,0.47592 -0.08302,0.932463 -0.249023,1.369629 -0.166024,0.431648 -0.392912,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622566,0.830083 -1.004395,1.245117 -0.376308,0.40951 -0.780279,0.827315 -1.211914,1.253418 l -1.460937,1.469238 0,0.116211 4.947265,0 0,2.158203"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/3.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/3.png
new file mode 100644
index 0000000..4febe43
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/3.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/3.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/3.svg
new file mode 100644
index 0000000..5e87e1f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/3.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.422316,12.587051 c -9e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.23243,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315437,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.392911,0.332031 -0.890957,0.592122 -1.494141,0.780273 -0.597661,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267255,-0.05534 -1.842773,-0.166016 -0.575523,-0.105143 -1.112306,-0.268392 -1.610352,-0.489746 l 0,-2.183105 c 0.249023,0.132815 0.511881,0.249025 0.788574,0.348632 0.276692,0.09961 0.553384,0.185387 0.830079,0.257325 0.27669,0.06641 0.547848,0.116212 0.813476,0.149414 0.271156,0.0332 0.525713,0.04981 0.763672,0.0498 0.475907,2e-6 0.871577,-0.04427 1.187012,-0.132812 0.315424,-
0.08854 0.567214,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320957,-0.351397 0.398437,-0.572754 0.083,-0.226885 0.124506,-0.473141 0.124512,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.265631,-0.376297 -0.498047,-0.514648 -0.226893,-0.143876 -0.525721,-0.254553 -0.896484,-0.332032 -0.370773,-0.07747 -0.827315,-0.116205 -1.369629,-0.116211 l -0.863281,0 0,-1.801269 0.846679,0 c 0.509111,7e-6 0.932451,-0.04426 1.27002,-0.132813 0.33756,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.43164,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.68897,-0.365224 -1.27002,-0.365234 -0.265629,10e-6 -0.514652,0.02768 -0.74707,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193688,0.07748 -0.373538,0.166026 -0.539551,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439941,0.282227 l -1.294922,-1.70
9961 c 0.232421,-0.171538 0.484211,-0.329253 0.755371,-0.473145 0.276691,-0.143868 0.575519,-0.26838 0.896484,-0.373535 0.320961,-0.1106647 0.666827,-0.1964393 1.037598,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492506,0.1272911 0.913079,0.3154421 1.261718,0.5644531 0.348626,0.243501 0.617017,0.545096 0.805176,0.904786 0.193677,0.354177 0.290519,0.760914 0.290528,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/30.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/30.png
new file mode 100644
index 0000000..f4ffb14
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/30.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/30.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/30.svg
new file mode 100644
index 0000000..434e663
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/30.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/31.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/31.png
new file mode 100644
index 0000000..0b29e87
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/31.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/31.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/31.svg
new file mode 100644
index 0000000..08c3f2d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/31.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 22.579206,22.008438 -2.564941,0 0,-7.022461 c -4e-6,-0.143873 -4e-6,-0.315422 0,-0.514648 0.0055,-0.204745 0.01106,-0.415031 0.0166,-0.63086 0.01106,-0.221345 0.01936,-0.442699 0.0249,-0.664062 0.01106,-0.221345 0.01936,-0.423331 0.0249,-0.605957 -0.02767,0.03321 -0.07471,0.08302 -0.141113,0.149414 -0.06641,0.06642 -0.141117,0.141122 -0.224121,0.224121 -0.08301,0.07748 -0.168786,0.157724 -0.257324,0.240723 -0.08855,0.08302 -0.17432,0.157723 -0.257325,0.224121 l -1.394531,1.120605 -1.245117,-1.543945 3.909668,-3.1127931 2.108398,0 0,12.1357421"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/32.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/32.png
new file mode 100644
index 0000000..a4740a3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/32.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/32.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/32.svg
new file mode 100644
index 0000000..aa099c3
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/32.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.621199,22.008438 -8.143067,0 0,-1.784668 2.855469,-3.07959 c 0.359697,-0.387364 0.686194,-0.744297 0.979492,-1.0708 0.29329,-0.326492 0.54508,-0.644688 0.755371,-0.95459 0.210281,-0.309889 0.37353,-0.625318 0.489746,-0.946289 0.116205,-0.320956 0.174311,-0.666821 0.174317,-1.037598 -6e-6,-0.409496 -0.124518,-0.727692 -0.373535,-0.95459 -0.243495,-0.226878 -0.572759,-0.340322 -0.987793,-0.340332 -0.437179,10e-6 -0.857751,0.10792 -1.261719,0.323731 -0.403974,0.215829 -0.827314,0.522958 -1.27002,0.921386 l -1.394531,-1.651855 c 0.249023,-0.226877 0.509114,-0.442698 0.780274,-0.647461 0.271157,-0.210275 0.569985,-0.395659 0.896484,-0.556152 0.326495,-0.16047 0.686195,-0.2877488 1.079101,-0.3818364 0.3929,-0.099597 0.832841,-0.1494018 1.319825,-0.1494141 0.581049,1.23e-5 1.101231,0.080253 1.560547,0.2407227 0.464837,0.1604938 0.860507,0.3901488 1.187011,0.6889648 0.32649,0.293305 0.575513,0.650239 0.747071,1.070801 0.177075,0.420583 0.265616,0.893727 0.265625,1.419
433 -9e-6,0.47592 -0.08302,0.932463 -0.249024,1.369629 -0.166024,0.431648 -0.392911,0.857754 -0.680664,1.278321 -0.287768,0.415044 -0.622565,0.830083 -1.004394,1.245117 -0.376309,0.40951 -0.78028,0.827315 -1.211914,1.253418 l -1.460938,1.469238 0,0.116211 4.947266,0 0,2.158203"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/33.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/33.png
new file mode 100644
index 0000000..f23ccea
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/33.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/33.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/33.svg
new file mode 100644
index 0000000..fce979c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/33.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.148054,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.207519,1.137207 -0.132821,0.33204 -0.318205,0.625334 -0.556153,0.879883 -0.232429,0.249031 -0.509121,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979486,0.121751 1.721021,0.420579 2.22461,0.896485 0.503572,0.470382 0.755362,1.106775 0.755371,1.909179 -9e-6,0.531253 -0.09685,1.023766 -0.290528,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879882,1.170411 -0.392911,0.332031 -0.890958,0.592122 -1.494141,0.780273 -0.597662,0.182617 -1.303227,0.273926 -2.116699,0.273926 -0.652998,0 -1.267256,-0.05534 -1.842774,-0.166016 -0.575522,-0.105143 -1.112305,-0.268392 -1.610351,-0.489746 l 0,-2.183105 c 0.249022,0.132815 0.51188,0.249025 0.788574,0.348632 0.276691,0.09961 0.553384,0.185387 0.830078,0.257325 0.27669,0.06641 0.547849,0.116212 0.813477,0.149414 0.271155,0.0332 0.525712,0.04981 0.763671,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132812 0.315425,
-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188146,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124512,-0.73877 -7e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.20474 -0.265631,-0.376289 -0.498047,-0.51464 -0.226893,-0.143876 -0.525721,-0.254553 -0.896485,-0.332032 -0.370772,-0.07747 -0.827315,-0.116205 -1.369628,-0.116211 l -0.863282,0 0,-1.801269 0.84668,0 c 0.509111,7e-6 0.93245,-0.04426 1.270019,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124512,-0.672363 -6e-6,-0.431632 -0.135585,-0.769197 -0.406739,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,1e-5 -0.514652,0.02768 -0.747071,0.08301 -0.226891,0.04981 -0.439944,0.116221 -0.63916,0.199218 -0.193687,0.07748 -0.373537,0.166026 -0.53955,0.265625 -0.160484,0.09409 -0.307131,0.188161 -0.439942,0.282227 l -1.294922,-1.7
09961 c 0.232421,-0.171538 0.484212,-0.329253 0.755371,-0.473145 0.276692,-0.143868 0.575519,-0.26838 0.896485,-0.373535 0.320961,-0.1106647 0.666826,-0.1964393 1.037597,-0.2573239 0.370765,-0.06086 0.766435,-0.091296 1.187012,-0.091309 0.597651,1.23e-5 1.139969,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/34.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/34.png
new file mode 100644
index 0000000..7e2ab31
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/34.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/34.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/34.svg
new file mode 100644
index 0000000..c67f8ec
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/34.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.803816,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262862,0.520191 -0.42334,0.780274 l -2.02539,3.071289 2.755859,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/35.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/35.png
new file mode 100644
index 0000000..02118e3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/35.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/35.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/35.svg
new file mode 100644
index 0000000..da7780a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/35.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.761335,14.255508 c 0.520177,8e-6 1.004389,0.08025 1.452637,0.240723 0.448235,0.160489 0.838372,0.395678 1.17041,0.705566 0.332024,0.309903 0.592114,0.697272 0.780274,1.16211 0.188142,0.459315 0.282218,0.987797 0.282226,1.585449 -8e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.20476,0.520184 -0.506355,0.962892 -0.904785,1.328125 -0.398444,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261723,0.290528 -2.02539,0.290528 -0.304366,0 -0.605961,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863282,-0.124512 -0.27116,-0.04981 -0.531251,-0.116211 -0.780273,-0.199219 -0.243491,-0.08301 -0.464845,-0.17985 -0.664063,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672364,0.31543 0.254555,0.09408 0.517413,0.177086 0.788574,0.249024 0.27669,0.06641 0.553383,0.121746 0.830078,0.166015 0.276689,0.03874 0.539547,0.05811 0.788574,0.05811 0.741532,2e-6 1.305985,-0.152179 1.69336,-0.456543 0.387364,-0.309893 0.581048
,-0.799639 0.581054,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751464,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320967,0.03874 -0.481446,0.06641 -0.15495,0.02768 -0.304364,0.05811 -0.448242,0.09131 -0.143882,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456543,-6.1840821 6.408203,0 0,2.1748051 -4.183594,0 -0.199218,2.382324 c 0.177079,-0.03873 0.381832,-0.07747 0.614257,-0.116211 0.237952,-0.03873 0.542314,-0.0581 0.913086,-0.05811"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/36.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/36.png
new file mode 100644
index 0000000..30f4fdf
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/36.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/36.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/36.svg
new file mode 100644
index 0000000..348549a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/36.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 16.428328,16.853653 c -1e-6,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.06641,-0.575514 0.17985,-1.126132 0.340332,-1.651856 0.166015,-0.531241 0.387369,-1.023753 0.664063,-1.477539 0.282224,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431637,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603185,-0.1936727 1.305984,-0.2905151 2.108398,-0.2905274 0.116205,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.13834,0.00555 0.276686,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251783,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210294,-0.04979 -0.434415,-0.08853 -0.672363,-0.116211 -0.232429,-0.03319 -0.467618,-0.04979 -0.705567,-0.0498 -0.747076,1e-5 -1.361333,0.09408 -1.842773,0.282226 -0.48145,0.182627 -0.863285,0.439951 -1.145508,0.771973 -0.28223,0.33204 -0.484215,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.21582,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243487,-0.384596 0.398438,-0
.556153 0.160478,-0.177076 0.345862,-0.32649 0.556152,-0.448242 0.210282,-0.127271 0.445471,-0.22688 0.705566,-0.298828 0.265621,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419434,0.257324 0.420565,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.154939,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282227,1.768066 -0.182625,0.520184 -0.445483,0.962892 -0.788574,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643555,0.282227 -0.59766,0 -1.156579,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.97396,-0.542317 -1.361328,-0.979492 -0.381837,-0.437173 -0.683432,-0.987791 -0.904785,-1.651856 -0.215821,-0.669593 -0.323731,-1.460933 -0.32373,-2.374023 m 4.216796,3.270508 c 0.226883,2e-6 0.431636,-0.0415 0.614258,-0.124512 0.188146,-0.08854 0.348627,-0.218585 0.481446,-0.390137 0.13834,-0.17708 0.243483,-0.3984
34 0.315429,-0.664062 0.07747,-0.265622 0.116205,-0.581051 0.116211,-0.946289 -6e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243495,-0.343094 -0.61703,-0.514643 -1.120605,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.390141,0.229661 -0.539551,0.390137 -0.149417,0.160487 -0.265628,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.315429,0.755371 0.143877,0.221357 0.318193,0.401207 0.52295,0.539551 0.210282,0.138349 0.453771,0.207522 0.730468,0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/37.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/37.png
new file mode 100644
index 0000000..6174706
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/37.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/37.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/37.svg
new file mode 100644
index 0000000..7bc04d9
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/37.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 17.51573,22.008438 4.316406,-9.960937 -5.578125,0 0,-2.1582035 8.367188,0 0,1.6103515 -4.424317,10.508789 -2.681152,0"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/38.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/38.png
new file mode 100644
index 0000000..161661d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/38.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/38.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/38.svg
new file mode 100644
index 0000000..ec2ad98
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/38.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 20.48741,9.7149811 c 0.503575,1.23e-5 0.979486,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337557,0.243501 0.605949,0.547862 0.805176,0.913086 0.19921,0.365244 0.298819,0.794118 0.298828,1.286621 -9e-6,0.365243 -0.05535,0.697274 -0.166016,0.996094 -0.110685,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193692,0.237963 -0.423347,0.451017 -0.688965,0.639161 -0.265631,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.63362,0.362473 0.937988,0.572754 0.309889,0.210292 0.583814,0.448247 0.821778,0.713867 0.237947,0.260096 0.428865,0.55339 0.572754,0.879883 0.143871,0.326501 0.215811,0.691735 0.21582,1.095703 -9e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478687,0.758139 -0.838379,1.045898 -0.359708,0.287761 -0.791348,0.509115 -1.294922,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651855,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.93799
1,-0.362467 -1.286622,-0.639161 -0.348634,-0.276691 -0.614258,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265625,-0.857744 -0.265625,-1.361328 0,-0.415035 0.06087,-0.78857 0.182618,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498046,-0.896485 0.210285,-0.265619 0.456542,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271161,-0.171543 -0.525718,-0.356927 -0.763672,-0.556152 -0.237957,-0.204746 -0.445477,-0.428866 -0.622558,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -1e-6,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478676,-0.669585 0.821777,-0.913086 0.343097,-0.249012 0.738767,-0.434396 1.187012,-0.5561527 0.448238,-0.1217326 0.918615,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.10791,0.614258 0.07194,0.18262 0.17708,0.340334 0.31543,0.473145 0.143876,0.132814 0.32096,0.23
7957 0.53125,0.315429 0.210282,0.07194 0.453771,0.107912 0.730468,0.10791 0.58105,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.431641,-1.087402 -7e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218594,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.32097,-0.307125 -0.514649,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 20.3878,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664062,0.398438 -0.199223,0.138351 -0.370772,0.293299 -0.514649,0.464844 -0.138349,0.16602 -0.246259,0.348637 -0.32373,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.70166,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514648,0.08301 -0.154952,0.05535 -0.290532,0.13559 -0.406739,0.240723 -0.11068,0.105153 -0.199222,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.315438 0.282227,0
.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160477,0.09962 0.32926,0.199226 0.506348,0.298828 0.171544,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154942,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.121739,-0.138338 0.218581,-0.293286 0.290527,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.15772,-0.284984 -0.273926,-0.390137 -0.116216,-0.105133 -0.254562,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/39.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/39.png
new file mode 100644
index 0000000..2d46b24
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/39.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/39.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/39.svg
new file mode 100644
index 0000000..664ffdd
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/39.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 14.784773,12.587051 c -8e-6,0.420582 -0.06918,0.799651 -0.20752,1.137207 -0.13282,0.33204 -0.318204,0.625334 -0.556152,0.879883 -0.232429,0.249031 -0.509122,0.459317 -0.830078,0.63086 -0.315436,0.166022 -0.658535,0.2933 -1.029297,0.381836 l 0,0.0498 c 0.979485,0.121751 1.721021,0.420579 2.224609,0.896485 0.503573,0.470382 0.755363,1.106775 0.755371,1.909179 -8e-6,0.531253 -0.09685,1.023766 -0.290527,1.477539 -0.188159,0.448244 -0.481453,0.83838 -0.879883,1.170411 -0.39291,0.332031 -0.890957,0.592122 -1.49414,0.780273 -0.597662,0.182617 -1.303228,0.273926 -2.1167,0.273926 -0.6529976,0 -1.2672548,-0.05534 -1.842773,-0.166016 C 7.9421607,21.903295 7.4053774,21.740046 6.9073315,21.518692 l 0,-2.183105 c 0.2490227,0.132815 0.5118805,0.249025 0.7885742,0.348632 0.2766912,0.09961 0.5533836,0.185387 0.8300781,0.257325 0.2766904,0.06641 0.5478489,0.116212 0.8134766,0.149414 0.2711557,0.0332 0.5257127,0.04981 0.7636716,0.0498 0.475908,2e-6 0.871578,-0.04427 1.187012,-0.132
812 0.315424,-0.08854 0.567215,-0.213051 0.755371,-0.373535 0.188145,-0.16048 0.320958,-0.351397 0.398438,-0.572754 0.083,-0.226885 0.124505,-0.473141 0.124511,-0.73877 -6e-6,-0.249019 -0.05258,-0.47314 -0.157715,-0.672363 -0.09962,-0.204748 -0.26563,-0.376297 -0.498046,-0.514648 C 11.685809,16.992 11.386981,16.881323 11.016218,16.803844 10.645446,16.726374 10.188903,16.687639 9.6465893,16.687633 l -0.8632813,0 0,-1.801269 0.8466797,0 c 0.5091113,7e-6 0.9324503,-0.04426 1.2700193,-0.132813 0.337561,-0.09407 0.605952,-0.218579 0.805176,-0.373535 0.204747,-0.160474 0.348627,-0.345858 0.431641,-0.556152 0.083,-0.210278 0.124506,-0.434399 0.124511,-0.672363 -5e-6,-0.431632 -0.135585,-0.769197 -0.406738,-1.012696 -0.26563,-0.243479 -0.688969,-0.365224 -1.270019,-0.365234 -0.265629,10e-6 -0.514653,0.02768 -0.7470708,0.08301 -0.2268911,0.04981 -0.4399443,0.116221 -0.6391601,0.199218 -0.1936875,0.07748 -0.3735376,0.166026 -0.5395508,0.265625 -0.1604838,0.09409 -0.3071308,0.188161 -0
.4399414,0.282227 L 6.923933,10.893692 c 0.2324212,-0.171538 0.4842113,-0.329253 0.7553711,-0.473145 0.2766912,-0.143868 0.575519,-0.26838 0.8964844,-0.373535 0.3209611,-0.1106647 0.6668266,-0.1964393 1.0375977,-0.2573239 0.3707646,-0.06086 0.7664348,-0.091296 1.1870118,-0.091309 0.597651,1.23e-5 1.139968,0.066419 1.626953,0.1992188 0.492507,0.1272911 0.913079,0.3154421 1.261719,0.5644531 0.348625,0.243501 0.617017,0.545096 0.805176,0.904786 0.193676,0.354177 0.290519,0.760914 0.290527,1.220214"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.554792,15.052383 c -8e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340332,1.651856 -0.16049,0.525719 -0.381844,1.018232 -0.664063,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426112,0.332032 -0.94076,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.300459,0.282227 -2.108398,0.282227 -0.116214,0 -0.243493,-0.0028 -0.381836,-0.0083 -0.138349,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273928,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237953,0.02767 0.478675,0.04151 0.722168,0.0415 0.747066,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.48144,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.28222,-0.337562 0.481439,-0.738766 0.597656,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.10791,0 c -0.110683,0.199225 -0.243496,0.384609 -0.398438,0.556153 -0.1549
53,0.171554 -0.33757,0.320968 -0.547851,0.448242 -0.210292,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.26563,0.07194 -0.561691,0.107914 -0.888184,0.10791 -0.525719,4e-6 -0.998863,-0.08577 -1.419433,-0.257324 -0.420575,-0.171545 -0.777509,-0.420568 -1.070801,-0.74707 -0.287762,-0.326492 -0.509116,-0.727696 -0.664063,-1.203614 -0.154948,-0.475904 -0.232422,-1.020988 -0.232422,-1.635253 0,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453775,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758136,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043128,-0.2905151 1.651856,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520175,0.210298 0.971184,0.534028 1.353027,0.971192 0.381828,0.437185 0.683423,0.990569 0.904785,1.660156 0.221346,0.669605 0.332023,1.458178 0.332031,2.365722 m -4.216796,-3.262207 c -0.226893,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188155,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132816,0.171559 -0.2379
59,0.392913 -0.31543,0.664062 -0.07194,0.265634 -0.107913,0.581063 -0.10791,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373535,1.394532 0.24902,0.343105 0.625322,0.514654 1.128906,0.514648 0.254553,6e-6 0.486975,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.539551,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124505,-0.401197 0.124512,-0.605958 -7e-6,-0.282218 -0.03598,-0.561677 -0.107911,-0.838378 -0.06641,-0.282218 -0.171555,-0.534008 -0.315429,-0.755372 -0.138352,-0.226878 -0.312669,-0.409495 -0.52295,-0.547851 -0.204757,-0.138336 -0.44548,-0.207509 -0.722167,-0.20752"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/4.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/4.png
new file mode 100644
index 0000000..9b9dd88
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/4.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/4.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/4.svg
new file mode 100644
index 0000000..bc06c73
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/4.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 20.078077,19.493301 -1.460937,0 0,2.515137 -2.498535,0 0,-2.515137 -5.013672,0 0,-1.784668 5.154785,-7.8359371 2.357422,0 0,7.6284181 1.460937,0 0,1.992187 m -3.959472,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09962,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.12175,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.025391,3.071289 2.75586,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/40.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/40.png
new file mode 100644
index 0000000..fe2a68f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/40.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/40.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/40.svg
new file mode 100644
index 0000000..5a94d1b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/40.svg
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.440535,19.493301 -1.460938,0 0,2.515137 -2.498535,0 0,-2.515137 -5.0136719,0 0,-1.784668 5.1547849,-7.8359371 2.357422,0 0,7.6284181 1.460938,0 0,1.992187 m -3.959473,-1.992187 0,-2.058594 c -5e-6,-0.07193 -5e-6,-0.17431 0,-0.307129 0.0055,-0.138339 0.01106,-0.293287 0.0166,-0.464844 0.0055,-0.171541 0.01106,-0.348625 0.0166,-0.53125 0.01106,-0.182609 0.01936,-0.356925 0.0249,-0.522949 0.01106,-0.166007 0.01936,-0.309887 0.0249,-0.43164 0.01106,-0.12727 0.01936,-0.218579 0.0249,-0.273926 l -0.07471,0 c -0.09961,0.232431 -0.213058,0.478687 -0.340332,0.738769 -0.121749,0.2601 -0.262863,0.520191 -0.42334,0.780274 l -2.0253904,3.071289 2.7558594,0"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ <path
+ d="m 24.6378,15.940567 c -9e-6,0.979497 -0.07748,1.853845 -0.232422,2.623047 -0.149422,0.769208 -0.392912,1.422202 -0.730468,1.958984 -0.332039,0.536785 -0.763679,0.94629 -1.294922,1.228516 -0.525722,0.282226 -1.162115,0.42334 -1.90918,0.42334 -0.702803,0 -1.314294,-0.141114 -1.834473,-0.42334 -0.520184,-0.282226 -0.951824,-0.691731 -1.294922,-1.228516 -0.3431,-0.536782 -0.600424,-1.189776 -0.771972,-1.958984 -0.166016,-0.769202 -0.249024,-1.64355 -0.249024,-2.623047 0,-0.979485 0.07471,-1.8566 0.224121,-2.631348 0.154948,-0.77473 0.398437,-1.430491 0.730469,-1.967285 0.33203,-0.536772 0.760903,-0.946277 1.286621,-1.228515 0.525713,-0.2877487 1.162106,-0.4316287 1.90918,-0.431641 0.69726,1.23e-5 1.305984,0.1411254 1.826172,0.42334 0.520175,0.282238 0.954582,0.691743 1.303223,1.228515 0.348624,0.536794 0.608715,1.192555 0.780273,1.967286 0.171541,0.774747 0.257315,1.654629 0.257324,2.639648 m -5.760742,0 c -3e-6,1.383468 0.118975,2.423832 0.356934,3.121094 0.237952,0.6
97268 0.650223,1.0459 1.236816,1.045898 0.575516,2e-6 0.987787,-0.345863 1.236816,-1.037597 0.254552,-0.691729 0.38183,-1.734859 0.381836,-3.129395 -6e-6,-1.38899 -0.127284,-2.43212 -0.381836,-3.129395 -0.249029,-0.702789 -0.6613,-1.054188 -1.236816,-1.054199 -0.293299,1.1e-5 -0.542322,0.08855 -0.74707,0.265625 -0.199223,0.177093 -0.362471,0.439951 -0.489746,0.788574 -0.127282,0.348642 -0.218591,0.785816 -0.273926,1.311524 -0.05534,0.52019 -0.08301,1.126146 -0.08301,1.817871"
+ id="path2820"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/5.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/5.png
new file mode 100644
index 0000000..f239fb6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/5.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/5.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/5.svg
new file mode 100644
index 0000000..82fb03d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/5.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 16.035597,14.255508 c 0.520177,8e-6 1.004388,0.08025 1.452637,0.240723 0.448235,0.160489 0.838371,0.395678 1.17041,0.705566 0.332023,0.309903 0.592114,0.697272 0.780273,1.16211 0.188143,0.459315 0.282218,0.987797 0.282227,1.585449 -9e-6,0.658532 -0.102385,1.250654 -0.307129,1.776367 -0.204761,0.520184 -0.506356,0.962892 -0.904785,1.328125 -0.398445,0.359701 -0.893724,0.636394 -1.48584,0.830078 -0.586594,0.193685 -1.261724,0.290528 -2.025391,0.290528 -0.304365,0 -0.60596,-0.01384 -0.904785,-0.0415 -0.298831,-0.02767 -0.586591,-0.06917 -0.863281,-0.124512 -0.271161,-0.04981 -0.531252,-0.116211 -0.780274,-0.199219 -0.24349,-0.08301 -0.464844,-0.17985 -0.664062,-0.290527 l 0,-2.216309 c 0.193684,0.11068 0.417805,0.215823 0.672363,0.31543 0.254556,0.09408 0.517414,0.177086 0.788574,0.249024 0.276691,0.06641 0.553383,0.121746 0.830078,0.166015 0.27669,0.03874 0.539548,0.05811 0.788575,0.05811 0.741532,2e-6 1.305984,-0.152179 1.693359,-0.456543 0.387364,-0.309893 0.5810
49,-0.799639 0.581055,-1.469239 -6e-6,-0.597651 -0.190924,-1.051427 -0.572754,-1.361328 -0.376307,-0.315424 -0.960128,-0.473139 -1.751465,-0.473144 -0.143884,5e-6 -0.298832,0.0083 -0.464844,0.0249 -0.160485,0.01661 -0.320966,0.03874 -0.481445,0.06641 -0.154951,0.02768 -0.304365,0.05811 -0.448242,0.09131 -0.143883,0.02767 -0.268394,0.05811 -0.373535,0.09131 l -1.020996,-0.547852 0.456542,-6.1840821 6.408204,0 0,2.1748051 -4.183594,0 -0.199219,2.382324 c 0.17708,-0.03873 0.381832,-0.07747 0.614258,-0.116211 0.237951,-0.03873 0.542313,-0.0581 0.913086,-0.05811"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/6.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/6.png
new file mode 100644
index 0000000..18866e6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/6.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/6.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/6.svg
new file mode 100644
index 0000000..e2f62af
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/6.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 11.702589,16.853653 c -10e-7,-0.581049 0.03044,-1.159336 0.09131,-1.734863 0.0664,-0.575514 0.179849,-1.126132 0.340332,-1.651856 0.166014,-0.531241 0.387368,-1.023753 0.664062,-1.477539 0.282225,-0.453765 0.636391,-0.846669 1.0625,-1.178711 0.431638,-0.337553 0.946285,-0.600411 1.543945,-0.788574 0.603186,-0.1936727 1.305984,-0.2905151 2.108399,-0.2905274 0.116204,1.23e-5 0.243483,0.00278 0.381836,0.0083 0.138339,0.00555 0.276685,0.013847 0.415039,0.024902 0.143873,0.00555 0.282219,0.016614 0.415039,0.033203 0.132805,0.016614 0.251782,0.035982 0.356934,0.058105 l 0,2.0502924 c -0.210295,-0.04979 -0.434416,-0.08853 -0.672364,-0.116211 -0.232429,-0.03319 -0.467617,-0.04979 -0.705566,-0.0498 -0.747076,1e-5 -1.361334,0.09408 -1.842774,0.282226 -0.481449,0.182627 -0.863285,0.439951 -1.145507,0.771973 -0.28223,0.33204 -0.484216,0.730477 -0.605957,1.195312 -0.116214,0.464852 -0.188154,0.9795 -0.215821,1.543946 l 0.09961,0 c 0.110674,-0.199212 0.243486,-0.384596 0.39843
7,-0.556153 0.160478,-0.177076 0.345862,-0.32649 0.556153,-0.448242 0.210282,-0.127271 0.44547,-0.22688 0.705566,-0.298828 0.26562,-0.07193 0.561681,-0.107902 0.888184,-0.10791 0.52571,8e-6 0.998854,0.08578 1.419433,0.257324 0.420566,0.171557 0.774732,0.42058 1.0625,0.74707 0.293286,0.326504 0.517407,0.727708 0.672363,1.203614 0.15494,0.475916 0.232413,1.021 0.232422,1.635254 -9e-6,0.658532 -0.09408,1.247887 -0.282226,1.768066 -0.182626,0.520184 -0.445484,0.962892 -0.788575,1.328125 -0.343106,0.359701 -0.758145,0.636394 -1.245117,0.830078 -0.486985,0.188151 -1.034836,0.282227 -1.643554,0.282227 -0.597661,0 -1.15658,-0.105144 -1.676758,-0.31543 -0.520185,-0.21582 -0.973961,-0.542317 -1.361328,-0.979492 -0.381838,-0.437173 -0.683433,-0.987791 -0.904785,-1.651856 -0.215822,-0.669593 -0.323732,-1.460933 -0.323731,-2.374023 m 4.216797,3.270508 c 0.226883,2e-6 0.431635,-0.0415 0.614258,-0.124512 0.188145,-0.08854 0.348627,-0.218585 0.481445,-0.390137 0.13834,-0.17708 0.243483,-0.3
98434 0.31543,-0.664062 0.07747,-0.265622 0.116204,-0.581051 0.116211,-0.946289 -7e-6,-0.592118 -0.124518,-1.056961 -0.373535,-1.394531 -0.243496,-0.343094 -0.617031,-0.514643 -1.120606,-0.514649 -0.254562,6e-6 -0.486984,0.04981 -0.697266,0.149414 -0.21029,0.09962 -0.39014,0.229661 -0.53955,0.390137 -0.149418,0.160487 -0.265629,0.340337 -0.348633,0.539551 -0.07748,0.199223 -0.116214,0.401209 -0.116211,0.605957 -3e-6,0.28223 0.0332,0.564456 0.09961,0.846679 0.07194,0.276696 0.17708,0.528486 0.31543,0.755371 0.143876,0.221357 0.318193,0.401207 0.522949,0.539551 0.210282,0.138349 0.453772,0.207522 0.730469,0.20752"
+ id="path2846"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/7.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/7.png
new file mode 100644
index 0000000..52c3a18
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/7.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/7.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/7.svg
new file mode 100644
index 0000000..a43460f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/7.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 12.789991,22.008438 4.316407,-9.960937 -5.578125,0 0,-2.1582035 8.367187,0 0,1.6103515 -4.424316,10.508789 -2.681153,0"
+ id="path2832"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/8.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/8.png
new file mode 100644
index 0000000..8a8cb21
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/8.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/8.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/8.svg
new file mode 100644
index 0000000..2c82d3f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/8.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 15.761671,9.7149811 c 0.503576,1.23e-5 0.979487,0.060885 1.427734,0.1826172 0.448236,0.1217567 0.841139,0.3043737 1.178711,0.5478517 0.337558,0.243501 0.60595,0.547862 0.805176,0.913086 0.199211,0.365244 0.29882,0.794118 0.298828,1.286621 -8e-6,0.365243 -0.05535,0.697274 -0.166015,0.996094 -0.110686,0.293302 -0.262866,0.561694 -0.456543,0.805175 -0.193693,0.237963 -0.423348,0.451017 -0.688965,0.639161 -0.265632,0.188157 -0.553392,0.359707 -0.863281,0.514648 0.320957,0.171556 0.633619,0.362473 0.937988,0.572754 0.309888,0.210292 0.583814,0.448247 0.821777,0.713867 0.237948,0.260096 0.428866,0.55339 0.572754,0.879883 0.143872,0.326501 0.215812,0.691735 0.21582,1.095703 -8e-6,0.503583 -0.09962,0.960126 -0.298828,1.369629 -0.199227,0.409506 -0.478686,0.758139 -0.838379,1.045898 -0.359707,0.287761 -0.791348,0.509115 -1.294921,0.664063 -0.498053,0.154948 -1.048671,0.232422 -1.651856,0.232422 -0.652999,0 -1.234053,-0.07471 -1.743164,-0.224121 -0.509117,-0.149414 -0.9379
9,-0.362467 -1.286621,-0.639161 -0.348634,-0.276691 -0.614259,-0.617023 -0.796875,-1.020996 -0.177084,-0.403969 -0.265626,-0.857744 -0.265625,-1.361328 -10e-7,-0.415035 0.06087,-0.78857 0.182617,-1.120605 0.121744,-0.332027 0.287759,-0.630855 0.498047,-0.896485 0.210285,-0.265619 0.456541,-0.500808 0.73877,-0.705566 0.282224,-0.204747 0.583819,-0.384597 0.904785,-0.539551 -0.271162,-0.171543 -0.525719,-0.356927 -0.763672,-0.556152 -0.237958,-0.204746 -0.445477,-0.428866 -0.622559,-0.672363 -0.171551,-0.249016 -0.309897,-0.522942 -0.415039,-0.821778 -0.09961,-0.298819 -0.149415,-0.628083 -0.149414,-0.987793 -10e-7,-0.481435 0.09961,-0.902008 0.298828,-1.261718 0.204751,-0.365224 0.478677,-0.669585 0.821778,-0.913086 0.343096,-0.249012 0.738766,-0.434396 1.187011,-0.5561527 0.448239,-0.1217326 0.918616,-0.1826049 1.411133,-0.1826172 m -1.718262,9.0644529 c -3e-6,0.221357 0.03597,0.42611 0.107911,0.614258 0.07194,0.18262 0.17708,0.340334 0.315429,0.473145 0.143877,0.132814 0.32
096,0.237957 0.53125,0.315429 0.210283,0.07194 0.453772,0.107912 0.730469,0.10791 0.581049,2e-6 1.015457,-0.135577 1.303223,-0.406738 0.287754,-0.27669 0.431634,-0.639157 0.43164,-1.087402 -6e-6,-0.232419 -0.04981,-0.439938 -0.149414,-0.622559 -0.09408,-0.188147 -0.218593,-0.359696 -0.373535,-0.514648 -0.14942,-0.160478 -0.320969,-0.307125 -0.514648,-0.439942 -0.19369,-0.132807 -0.387375,-0.260086 -0.581055,-0.381836 L 15.662062,16.72084 c -0.243494,0.12175 -0.464848,0.254563 -0.664063,0.398438 -0.199222,0.138351 -0.370772,0.293299 -0.514648,0.464844 -0.13835,0.16602 -0.24626,0.348637 -0.323731,0.547851 -0.07748,0.199223 -0.116214,0.415043 -0.116211,0.647461 m 1.701661,-7.188476 c -0.182622,10e-6 -0.354171,0.02768 -0.514649,0.08301 -0.154952,0.05535 -0.290531,0.13559 -0.406738,0.240723 -0.110681,0.105153 -0.199223,0.235199 -0.265625,0.390137 -0.06641,0.154957 -0.09961,0.329274 -0.09961,0.522949 -3e-6,0.232431 0.0332,0.434416 0.09961,0.605957 0.07194,0.166024 0.166012,0.31543
8 0.282226,0.448242 0.121741,0.127287 0.260087,0.243498 0.415039,0.348633 0.160478,0.09962 0.32926,0.199226 0.506348,0.298828 0.171545,-0.08853 0.334793,-0.185376 0.489746,-0.290527 0.154943,-0.105135 0.290522,-0.224113 0.406738,-0.356934 0.12174,-0.138338 0.218582,-0.293286 0.290528,-0.464843 0.07193,-0.171541 0.107904,-0.367993 0.10791,-0.589356 -6e-6,-0.193675 -0.03321,-0.367992 -0.09961,-0.522949 -0.06641,-0.154938 -0.157721,-0.284984 -0.273926,-0.390137 -0.116217,-0.105133 -0.254563,-0.185374 -0.415039,-0.240723 -0.160487,-0.05533 -0.334803,-0.083 -0.522949,-0.08301"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/9.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/9.png
new file mode 100644
index 0000000..0ae412f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/9.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/9.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/9.svg
new file mode 100644
index 0000000..b0f04c4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/9.svg
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="32"
+ height="32"
+ id="svg2">
+ <defs
+ id="defs15" />
+ <circle
+ cx="16"
+ cy="16"
+ r="14"
+ id="circle"
+ style="fill:#3c6eb4" />
+ <g
+ id="text2820"
+ style="font-size:10px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:start;text-anchor:start;fill:#ffffff;fill-opacity:1;stroke:none;font-family:Droid Sans;-inkscape-font-specification:Droid Sans">
+ <path
+ d="m 19.829054,15.052383 c -9e-6,0.581061 -0.03321,1.162116 -0.09961,1.743164 -0.06088,0.575526 -0.174325,1.126144 -0.340333,1.651856 -0.160489,0.525719 -0.381843,1.018232 -0.664062,1.477539 -0.2767,0.453778 -0.630866,0.846681 -1.0625,1.178711 -0.426113,0.332032 -0.940761,0.59489 -1.543945,0.788574 -0.597661,0.188151 -1.30046,0.282227 -2.108399,0.282227 -0.116214,0 -0.243492,-0.0028 -0.381836,-0.0083 -0.138348,-0.0055 -0.279462,-0.01384 -0.42334,-0.0249 -0.138348,-0.0055 -0.273927,-0.0166 -0.406738,-0.0332 -0.132814,-0.01107 -0.249025,-0.02767 -0.348633,-0.0498 l 0,-2.058594 c 0.204751,0.05534 0.423338,0.09961 0.655762,0.132813 0.237954,0.02767 0.478676,0.04151 0.722168,0.0415 0.747067,2e-6 1.361324,-0.09131 1.842773,-0.273925 0.481441,-0.188149 0.863276,-0.44824 1.145508,-0.780274 0.282221,-0.337562 0.481439,-0.738766 0.597657,-1.203613 0.121738,-0.464839 0.196445,-0.97672 0.224121,-1.535645 l -0.107911,0 c -0.110683,0.199225 -0.243495,0.384609 -0.398437,0.556153 -0.
154954,0.171554 -0.337571,0.320968 -0.547852,0.448242 -0.210291,0.127283 -0.448247,0.226892 -0.713867,0.298828 -0.265629,0.07194 -0.56169,0.107914 -0.888183,0.10791 -0.52572,4e-6 -0.998864,-0.08577 -1.419434,-0.257324 -0.420575,-0.171545 -0.777508,-0.420568 -1.070801,-0.74707 -0.287761,-0.326492 -0.509115,-0.727696 -0.664062,-1.203614 -0.154949,-0.475904 -0.232423,-1.020988 -0.232422,-1.635253 -10e-7,-0.65852 0.09131,-1.247875 0.273926,-1.768067 0.18815,-0.520172 0.453774,-0.960113 0.796875,-1.319824 0.343097,-0.365223 0.758135,-0.644682 1.245117,-0.838379 0.49251,-0.1936727 1.043127,-0.2905151 1.651855,-0.2905274 0.597651,1.23e-5 1.15657,0.1079224 1.676758,0.3237304 0.520176,0.210298 0.971184,0.534028 1.353027,0.971192 0.381829,0.437185 0.683423,0.990569 0.904786,1.660156 0.221345,0.669605 0.332022,1.458178 0.332031,2.365722 m -4.216797,-3.262207 c -0.226892,1.1e-5 -0.434412,0.04151 -0.622559,0.124512 -0.188154,0.08302 -0.351403,0.213063 -0.489746,0.390137 -0.132815,0.17155
9 -0.237959,0.392913 -0.315429,0.664062 -0.07194,0.265634 -0.107914,0.581063 -0.107911,0.946289 -3e-6,0.586596 0.124509,1.05144 0.373536,1.394532 0.249019,0.343105 0.625321,0.514654 1.128906,0.514648 0.254552,6e-6 0.486974,-0.0498 0.697266,-0.149414 0.210281,-0.0996 0.390131,-0.229648 0.53955,-0.390137 0.149408,-0.160475 0.262852,-0.340325 0.340332,-0.53955 0.083,-0.199212 0.124506,-0.401197 0.124512,-0.605958 -6e-6,-0.282218 -0.03598,-0.561677 -0.10791,-0.838378 -0.06641,-0.282218 -0.171556,-0.534008 -0.31543,-0.755372 -0.138352,-0.226878 -0.312668,-0.409495 -0.522949,-0.547851 -0.204758,-0.138336 -0.44548,-0.207509 -0.722168,-0.20752"
+ id="path2818"
+ style="font-size:17px;font-weight:bold;fill:#ffffff;-inkscape-font-specification:Bitstream Vera Sans Bold" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png
new file mode 100644
index 0000000..2333a6d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/bkgrnd_greydots.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/bullet_arrowblue.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/bullet_arrowblue.png
new file mode 100644
index 0000000..c235534
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/bullet_arrowblue.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/documentation.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/documentation.png
new file mode 100644
index 0000000..79d0a80
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/documentation.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/dot.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/dot.png
new file mode 100644
index 0000000..36a6859
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/dot.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/dot2.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/dot2.png
new file mode 100644
index 0000000..40aff92
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/dot2.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/green.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/green.png
new file mode 100644
index 0000000..ebb3c24
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/green.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/h1-bg.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/h1-bg.png
new file mode 100644
index 0000000..a2aad24
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/h1-bg.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/image_left.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/image_left.png
new file mode 100644
index 0000000..e8fe7a4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/image_left.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/image_right.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/image_right.png
new file mode 100644
index 0000000..5b67443
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/image_right.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/important.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/important.png
new file mode 100644
index 0000000..f7594a3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/important.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/important.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/important.svg
new file mode 100644
index 0000000..2d33045
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/important.svg
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="important.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/important.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2611">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="681"
+ inkscape:window-width="738"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2613" />
+ </defs>
+ <g
+ transform="matrix(0.4626799,0,0,0.4626799,-5.2934127,-3.3160376)"
+ id="g5485">
+ <path
+ d="M 29.97756,91.885882 L 55.586992,80.409826 L 81.231619,91.807015 L 78.230933,63.90468 L 96.995009,43.037218 L 69.531053,37.26873 L 55.483259,12.974592 L 41.510292,37.311767 L 14.064204,43.164717 L 32.892392,63.97442 L 29.97756,91.885882 z"
+ id="path6799"
+ style="fill:#f3de82;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.536215,56.538729 L 55.48324,12.974601 L 41.51028,37.311813 L 55.536215,56.538729 z"
+ id="path6824"
+ style="opacity:0.91005291;fill:#f9f2cb;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 78.241135,63.937979 L 96.976198,43.044318 L 55.57947,56.614318 z"
+ id="use6833"
+ style="opacity:1;fill:#d0bc64;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 55.667994,80.684281 L 81.379011,91.931065 L 55.523838,56.869126 z"
+ id="use6835"
+ style="opacity:1;fill:#e0c656;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 13.877363,43.200977 L 32.640089,64.069652 L 55.283346,56.742618 z"
+ id="use6831"
+ style="opacity:1;fill:#d1ba59;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 55.32792,80.684281 L 29.616903,91.931065 L 55.472076,56.869126 z"
+ id="use6837"
+ style="opacity:1;fill:#d2b951;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.57947,56.614318 L 96.976198,43.044318 L 69.504294,37.314027 L 55.57947,56.614318 z"
+ id="path7073"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.523838,56.869126 L 81.379011,91.931065 L 78.214821,64.046881 L 55.523838,56.869126 z"
+ id="path7075"
+ style="opacity:1;fill:#f6e7a3;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.283346,56.742618 L 41.341708,37.434209 L 13.877363,43.200977 L 55.283346,56.742618 z"
+ id="path7077"
+ style="opacity:1;fill:#f6e59d;fill-opacity:1;enable-background:new" />
+ <path
+ d="M 55.472076,56.869126 L 29.616903,91.931065 L 32.781093,64.046881 L 55.472076,56.869126 z"
+ id="path7079"
+ style="opacity:1;fill:#f3df8b;fill-opacity:1;enable-background:new" />
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/logo.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/logo.png
new file mode 100644
index 0000000..66a3104
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/logo.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/note.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/note.png
new file mode 100644
index 0000000..d6c4518
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/note.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/note.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/note.svg
new file mode 100644
index 0000000..70e43b6
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/note.svg
@@ -0,0 +1,111 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="note.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/note.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata16">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="1024"
+ inkscape:window-width="1205"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="22.217181"
+ inkscape:cy="20"
+ inkscape:window-x="334"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective18" />
+ </defs>
+ <g
+ transform="matrix(0.468275,0,0,0.468275,-5.7626904,-7.4142703)"
+ id="layer1">
+ <g
+ transform="matrix(0.115136,0,0,0.115136,9.7283,21.77356)"
+ id="g8014"
+ style="enable-background:new">
+ <g
+ id="g8518"
+ style="opacity:1">
+ <path
+ d="M -2512.4524,56.33197 L 3090.4719,56.33197 L 3090.4719,4607.3813 L -2512.4524,4607.3813 L -2512.4524,56.33197 z"
+ transform="matrix(0.1104659,-2.3734892e-2,2.2163258e-2,0.1031513,308.46782,74.820675)"
+ id="rect8018"
+ style="fill:#ffe680;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ <g
+ transform="matrix(0.5141653,-7.1944682e-2,7.1944682e-2,0.5141653,146.04015,-82.639785)"
+ id="g8020">
+ <path
+ d="M 511.14114,441.25315 C 527.3248,533.52772 464.31248,622.82928 370.39916,640.71378 C 276.48584,658.59828 187.23462,598.29322 171.05095,506.01865 C 154.86728,413.74408 217.8796,324.44253 311.79292,306.55803 C 405.70624,288.67353 494.95747,348.97858 511.14114,441.25315 z"
+ id="path8022"
+ style="opacity:1;fill:#e0c96f;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(1.2585415,-0.2300055,0.2168789,1.1867072,-248.76141,68.254424)"
+ id="path8024"
+ style="opacity:1;fill:#c00000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.0804934;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 358.5625,281.15625 C 348.09597,281.05155 337.43773,281.94729 326.71875,283.90625 C 240.96686,299.57789 183.37901,377.92385 198.15625,458.78125 C 209.70749,521.98673 262.12957,567.92122 325.40625,577.5625 L 357.25,433.6875 L 509.34375,405.875 C 509.14405,404.58166 509.0804,403.29487 508.84375,402 C 495.91366,331.24978 431.82821,281.88918 358.5625,281.15625 z"
+ id="path8026"
+ style="opacity:1;fill:#b60000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.1;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 294.2107,361.9442 L 282.79367,370.38482 L 261.73414,386.13346 C 253.13706,404.40842 254.3359,423.7989 259.7176,444.39774 C 273.6797,497.83861 313.42636,523.96124 369.50989,517.58957 C 398.21848,514.32797 424.51832,504.67345 440.64696,484.15958 L 469.89512,447.48298 L 294.2107,361.9442 z"
+ id="path8028"
+ style="fill:#750000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.09999999;stroke-linecap:butt;stroke-miterlimit:4;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-78.013985,79.234385)"
+ id="path8030"
+ style="opacity:1;fill:#d40000;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ <path
+ d="M 527.8214,393.1416 C 527.8214,461.31268 472.55783,516.57625 404.38675,516.57625 C 336.21567,516.57625 280.9521,461.31268 280.9521,393.1416 C 280.9521,324.97052 336.21567,269.70695 404.38675,269.70695 C 472.55783,269.70695 527.8214,324.97052 527.8214,393.1416 z"
+ transform="matrix(0.9837071,-0.1797787,0.1695165,0.9275553,-69.306684,71.273294)"
+ id="path8032"
+ style="opacity:1;fill:#e11212;fill-opacity:1;fill-rule:nonzero;stroke:none;stroke-width:0.10298239;stroke-linecap:butt;stroke-miterlimit:4;stroke-dasharray:none;stroke-dashoffset:0;stroke-opacity:1" />
+ </g>
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/red.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/red.png
new file mode 100644
index 0000000..d32d5e2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/red.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/shade.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/shade.png
new file mode 100644
index 0000000..a73afdf
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/shade.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/shine.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/shine.png
new file mode 100644
index 0000000..a18f7c4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/shine.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-go-back.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-go-back.png
new file mode 100644
index 0000000..d320f26
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-go-back.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-go-forward.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-go-forward.png
new file mode 100644
index 0000000..1ee5a29
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-go-forward.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-go-up.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-go-up.png
new file mode 100644
index 0000000..1cd7332
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-go-up.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-home.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-home.png
new file mode 100644
index 0000000..122536d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/stock-home.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/title_logo.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/title_logo.png
new file mode 100644
index 0000000..d5182b4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/title_logo.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/title_logo.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/title_logo.svg
new file mode 100644
index 0000000..e8fd52b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/title_logo.svg
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ version="1.0"
+ width="220"
+ height="70"
+ id="svg6180">
+ <defs
+ id="defs6182" />
+ <g
+ transform="translate(-266.55899,-345.34488)"
+ id="layer1">
+ <path
+ d="m 316.7736,397.581 c 0,0 0,0 -20.53889,0 0.3327,4.45245 3.92157,7.77609 8.70715,7.77609 3.38983,0 6.31456,-1.39616 8.64094,-3.65507 0.46553,-0.46679 0.99726,-0.59962 1.59519,-0.59962 0.79781,0 1.59561,0.39932 2.12692,1.06388 0.3327,0.46553 0.53216,0.99726 0.53216,1.52857 0,0.73118 -0.3327,1.52857 -0.93106,2.12734 -2.7919,2.99052 -7.51086,4.98503 -12.16403,4.98503 -8.44149,0 -15.22074,-6.77967 -15.22074,-15.22158 0,-8.44149 6.58022,-15.22074 15.02171,-15.22074 8.37529,0 14.62323,6.51317 14.62323,15.08749 0,1.26418 -1.12924,2.12861 -2.39258,2.12861 z m -12.23065,-11.76512 c -4.45329,0 -7.51085,2.92473 -8.17499,7.17731 10.03626,0 16.35083,0 16.35083,0 -0.59836,-4.05355 -3.78874,-7.17731 -8.17584,-7.17731 z"
+ id="path11"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 375.46344,410.80807 c -8.44106,0 -15.22074,-6.77968 -15.22074,-15.22159 0,-8.44149 6.77968,-15.22074 15.22074,-15.22074 8.44234,0 15.22159,6.77925 15.22159,15.22074 -4.2e-4,8.44149 -6.77968,15.22159 -15.22159,15.22159 z m 0,-24.65992 c -5.31688,0 -8.77377,4.25427 -8.77377,9.43833 0,5.18364 3.45689,9.43833 8.77377,9.43833 5.31731,0 8.77504,-4.25469 8.77504,-9.43833 -4.2e-4,-5.18406 -3.45773,-9.43833 -8.77504,-9.43833 z"
+ id="path13"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 412.66183,380.36574 c -4.45963,0 -7.40966,1.319 -10.01391,4.62956 l -0.24036,-1.53995 0,0 c -0.20198,-1.60743 -1.57326,-2.84926 -3.23382,-2.84926 -1.80139,0 -3.26206,1.459 -3.26206,3.26081 0,0.003 0,0.005 0,0.008 l 0,0 0,0.003 0,0 0,23.40712 c 0,1.79464 1.46194,3.25743 3.257,3.25743 1.79465,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-12.56209 c 0,-5.71621 4.98502,-8.57432 10.23613,-8.57432 1.59519,0 2.85726,-1.32953 2.85726,-2.92515 0,-1.59561 -1.26207,-2.85726 -2.85768,-2.85726 z"
+ id="path15"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 447.02614,395.58648 c 0.0666,-8.17541 -5.78326,-15.22074 -15.222,-15.22074 -8.44192,0 -15.28779,6.77925 -15.28779,15.22074 0,8.44191 6.64684,15.22159 14.68985,15.22159 4.01434,0 7.62682,-2.06621 9.23846,-4.22518 l 0.79359,2.01434 0,0 c 0.42589,1.13177 1.5176,1.93717 2.7978,1.93717 1.65001,0 2.98756,-1.33671 2.99009,-2.98545 l 0,0 0,-7.80687 0,0 0,-4.1556 z m -15.222,9.43833 c -5.31773,0 -8.77419,-4.25469 -8.77419,-9.43833 0,-5.18406 3.45604,-9.43833 8.77419,-9.43833 5.3173,0 8.77419,4.25427 8.77419,9.43833 0,5.18364 -3.45689,9.43833 -8.77419,9.43833 z"
+ id="path17"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 355.01479,368.3337 c 0,-1.7938 -1.46194,-3.18997 -3.25659,-3.18997 -1.79422,0 -3.25743,1.39659 -3.25743,3.18997 l 0,17.1499 c -1.66097,-3.05756 -5.25026,-5.11786 -9.50495,-5.11786 -8.64052,0 -14.42336,6.51318 -14.42336,15.22074 0,8.70757 5.98229,15.22159 14.42336,15.22159 3.76555,0 7.03057,-1.55429 8.98587,-4.25554 l 0.72317,1.83428 c 0.44782,1.25912 1.64917,2.16024 3.06051,2.16024 1.78621,0 3.24984,-1.45435 3.24984,-3.24815 0,-0.005 0,-0.009 0,-0.0139 l 0,0 0,-38.95128 -4.2e-4,0 z m -15.22116,36.69111 c -5.31731,0 -8.70715,-4.25469 -8.70715,-9.43833 0,-5.18406 3.38984,-9.43833 8.70715,-9.43833 5.31773,0 8.70714,4.0544 8.70714,9.43833 0,5.38309 -3.38941,9.43833 -8.70714,9.43833 z"
+ id="path19"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 287.21553,365.34023 c -0.59414,-0.0877 -1.19966,-0.13198 -1.80097,-0.13198 -6.73118,0 -12.20746,5.4767 -12.20746,12.20788 l 0,3.8132 -3.98903,0 c -1.46237,0 -2.65908,1.19671 -2.65908,2.65781 0,1.46321 1.19671,2.93738 2.65908,2.93738 l 3.98819,0 0,20.46004 c 0,1.79464 1.46236,3.25743 3.25658,3.25743 1.79507,0 3.25744,-1.46279 3.25744,-3.25743 l 0,-20.46004 4.40986,0 c 1.46194,0 2.65823,-1.47417 2.65823,-2.93738 0,-1.46152 -1.19629,-2.65823 -2.65823,-2.65823 l -4.40733,0 0,-3.8132 c 0,-3.13852 2.55323,-6.11469 5.69175,-6.11469 0.28294,0 0.56757,0.0211 0.84672,0.062 1.78031,0.26355 3.4358,-0.54269 3.70019,-2.32342 0.2627,-1.77904 -0.96606,-3.43538 -2.74594,-3.69935 z"
+ id="path21"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 482.01243,363.57426 c 0,-10.06788 -8.16108,-18.22938 -18.22897,-18.22938 -10.06282,0 -18.22179,8.15475 -18.22854,18.21631 l -4.2e-4,-4.2e-4 0,14.1071 4.2e-4,4.2e-4 c 0.005,2.28463 1.85832,4.13409 4.14463,4.13409 0.007,0 0.0127,-8.4e-4 0.0194,-8.4e-4 l 0.001,8.4e-4 14.07083,0 0,0 c 10.06409,-0.004 18.22138,-8.16276 18.22138,-18.22812 z"
+ id="path25"
+ style="fill:#294172" />
+ <path
+ d="m 469.13577,349.66577 c -4.72528,0 -8.55576,3.83049 -8.55576,8.55577 0,0.002 0,0.004 0,0.006 l 0,4.52836 -4.51444,0 c -8.5e-4,0 -8.5e-4,0 -0.001,0 -4.72528,0 -8.55576,3.81193 -8.55576,8.53678 0,4.72528 3.83048,8.55577 8.55576,8.55577 4.72486,0 8.55534,-3.83049 8.55534,-8.55577 0,-0.002 0,-0.004 0,-0.006 l 0,-4.54733 4.51444,0 c 8.5e-4,0 0.001,0 0.002,0 4.72486,0 8.55534,-3.79296 8.55534,-8.51781 0,-4.72528 -3.83048,-8.55577 -8.55534,-8.55577 z m -8.55576,21.63483 c -0.004,2.48998 -2.02446,4.50811 -4.51571,4.50811 -2.49378,0 -4.53426,-2.02193 -4.53426,-4.5157 0,-2.49421 2.04048,-4.55366 4.53426,-4.55366 0.002,0 0.004,4.2e-4 0.006,4.2e-4 l 3.86971,0 c 0.001,0 0.002,-4.2e-4 0.003,-4.2e-4 0.35209,0 0.63799,0.28505 0.63799,0.63715 0,4.2e-4 -4.2e-4,8.4e-4 -4.2e-4,0.001 l 0,3.92284 -4.2e-4,0 z m 8.55534,-8.5448 c -0.001,0 -0.003,0 -0.004,0 l -3.87223,0 c -8.4e-4,0 -0.002,0 -0.002,0 -0.35252,0 -0.63757,-0.28506 -0.63757,-0.63758 l 0,-4.2e-4 0,-3.90343 c 0.004,-2.49083 2.02
446,-4.50854 4.51571,-4.50854 2.49378,0 4.53468,2.02193 4.53468,4.51613 4.2e-4,2.49336 -2.04048,4.53384 -4.53426,4.53384 z"
+ id="path29"
+ style="fill:#3c6eb4" />
+ <path
+ d="m 460.58001,362.7558 0,-4.52836 c 0,-0.002 0,-0.004 0,-0.006 0,-4.72528 3.83048,-8.55577 8.55576,-8.55577 0.71685,0 1.22623,0.0805 1.88952,0.25469 0.96774,0.25385 1.75796,1.04618 1.75838,1.96922 4.2e-4,1.11575 -0.80919,1.92621 -2.0194,1.92621 -0.57642,0 -0.78473,-0.11048 -1.62892,-0.11048 -2.49125,0 -4.51149,2.01771 -4.51571,4.50854 l 0,3.90385 0,4.2e-4 c 0,0.35252 0.28505,0.63758 0.63757,0.63758 4.3e-4,0 0.001,0 0.002,0 l 2.96521,0 c 1.10521,0 1.99747,0.88467 1.99832,1.99283 0,1.10816 -0.89353,1.99114 -1.99832,1.99114 l -3.60489,0 0,4.54733 c 0,0.002 0,0.004 0,0.006 0,4.72485 -3.83048,8.55534 -8.55534,8.55534 -0.71684,0 -1.22623,-0.0805 -1.88952,-0.25469 -0.96774,-0.25343 -1.75838,-1.04618 -1.7588,-1.9688 0,-1.11575 0.80919,-1.92663 2.01982,-1.92663 0.576,0 0.78473,0.11048 1.6285,0.11048 2.49125,0 4.51191,-2.01771 4.51613,-4.50811 0,0 0,-3.92368 0,-3.9241 0,-0.35168 -0.2859,-0.63673 -0.63799,-0.63673 -4.3e-4,0 -8.5e-4,0 -0.002,0 l -2.96521,-4.2e-4 c -1.10521,0 -1.
99831,-0.88214 -1.99831,-1.9903 -4.3e-4,-1.11533 0.90238,-1.99367 2.01939,-1.99367 l 3.58339,0 0,0 z"
+ id="path31"
+ style="fill:#ffffff" />
+ <path
+ d="m 477.41661,378.55292 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="text6223"
+ style="fill:#294172;enable-background:new" />
+ </g>
+ <path
+ d="m 181.98344,61.675273 2.81558,0 0,0.37898 -1.18152,0 0,2.94935 -0.45254,0 0,-2.94935 -1.18152,0 0,-0.37898 m 3.26144,0 0.67101,0 0.84937,2.26496 0.85381,-2.26496 0.67102,0 0,3.32833 -0.43917,0 0,-2.9226 -0.85828,2.28279 -0.45255,0 -0.85827,-2.28279 0,2.9226 -0.43694,0 0,-3.32833"
+ id="path2391"
+ style="fill:#294172;enable-background:new" />
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/warning.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/warning.png
new file mode 100644
index 0000000..ce09951
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/warning.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/warning.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/warning.svg
new file mode 100644
index 0000000..5f2612c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/warning.svg
@@ -0,0 +1,89 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://creativecommons.org/ns#"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="48"
+ height="48"
+ id="svg5921"
+ sodipodi:version="0.32"
+ inkscape:version="0.46"
+ sodipodi:docname="warning.svg"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ inkscape:export-filename="/home/jfearn/Build/src/fedora/publican/trunk/publican-fedora/en-US/images/warning.png"
+ inkscape:export-xdpi="111.32"
+ inkscape:export-ydpi="111.32">
+ <metadata
+ id="metadata2482">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="910"
+ inkscape:window-width="1284"
+ inkscape:pageshadow="2"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ showgrid="false"
+ inkscape:zoom="11.5"
+ inkscape:cx="20"
+ inkscape:cy="20"
+ inkscape:window-x="0"
+ inkscape:window-y="51"
+ inkscape:current-layer="svg5921" />
+ <defs
+ id="defs5923">
+ <inkscape:perspective
+ sodipodi:type="inkscape:persp3d"
+ inkscape:vp_x="0 : 20 : 1"
+ inkscape:vp_y="0 : 1000 : 0"
+ inkscape:vp_z="40 : 20 : 1"
+ inkscape:persp3d-origin="20 : 13.333333 : 1"
+ id="perspective2484" />
+ </defs>
+ <g
+ transform="matrix(0.4536635,0,0,0.4536635,-5.1836431,-4.6889387)"
+ id="layer1">
+ <g
+ transform="translate(2745.6887,-1555.5977)"
+ id="g8304"
+ style="enable-background:new">
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.8233528,8.9983906e-3,-8.9983906e-3,0.8233528,-1398.5561,740.7914)"
+ id="path8034"
+ style="opacity:1;fill:#efd259;fill-opacity:1;stroke:#efd259;stroke-opacity:1" />
+ <path
+ d="M -1603,1054.4387 L -1577.0919,1027.891 L -1540,1027.4387 L -1513.4523,1053.3468 L -1513,1090.4387 L -1538.9081,1116.9864 L -1576,1117.4387 L -1602.5477,1091.5306 L -1603,1054.4387 z"
+ transform="matrix(0.6467652,7.0684723e-3,-7.0684723e-3,0.6467652,-1675.7492,927.16391)"
+ id="path8036"
+ style="opacity:1;fill:#a42324;fill-opacity:1;stroke:#a42324;stroke-opacity:1" />
+ <path
+ d="M -2686.7886,1597.753 C -2686.627,1596.5292 -2686.5462,1595.6987 -2686.5462,1595.218 C -2686.5462,1593.1637 -2688.0814,1592.0711 -2690.9899,1592.0711 C -2693.8985,1592.0711 -2695.4336,1593.12 -2695.4336,1595.218 C -2695.4336,1595.961 -2695.3528,1596.7914 -2695.1912,1597.753 L -2692.929,1614.4491 L -2689.0508,1614.4491 L -2686.7886,1597.753"
+ id="path8038"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ <path
+ d="M -2690.9899,1617.8197 C -2693.6124,1617.8197 -2695.8118,1619.9346 -2695.8118,1622.6416 C -2695.8118,1625.3486 -2693.6124,1627.4635 -2690.9899,1627.4635 C -2688.2829,1627.4635 -2686.168,1625.264 -2686.168,1622.6416 C -2686.168,1619.9346 -2688.2829,1617.8197 -2690.9899,1617.8197"
+ id="path8040"
+ style="font-size:107.13574219px;font-style:normal;font-weight:normal;text-align:center;text-anchor:middle;fill:#ffffff;fill-opacity:1;stroke:none;stroke-width:1px;stroke-linecap:butt;stroke-linejoin:miter;stroke-opacity:1;font-family:Bitstream Charter" />
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/watermark-draft.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/watermark-draft.png
new file mode 100644
index 0000000..0ead5af
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/watermark-draft.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/yellow.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/yellow.png
new file mode 100644
index 0000000..223865d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/Common_Content/images/yellow.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/Users_and_Groups.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/Users_and_Groups.html
new file mode 100644
index 0000000..2aeb3c5
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/Users_and_Groups.html
@@ -0,0 +1,80 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 15. Users and Groups</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-sysconfig.html" title="Part III. System Configuration" /><link rel="prev" href="s1-keyboard-break.html" title="14.3. Setting Up a Typing Break" /><link rel="next" href="s1-users-tools.html" title="15.2. User and Group Management Tools" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-keyboard-break.html"><strong>Prev</strong></a></li><li class="next"><a accesskey
="n" href="s1-users-tools.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 15. Users and Groups" id="Users_and_Groups" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Users and Groups</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="Users_and_Groups.html#s1-users-configui">15.1. User and Group Configuration</a></span></dt><dt><span class="section"><a href="s1-users-tools.html">15.2. User and Group Management Tools</a></span></dt><dt><span class="section"><a href="s1-users-groups-standard-users.html">15.3. Standard Users</a></span></dt><dt><span class="section"><a href="s1-users-groups-standard-groups.html">15.4. Standard Groups</a></span></dt><dt><span class="section"><a href="s1-users-groups-private-groups.html">15.5. User Private Groups</a></span></dt><dt><span class="section"><a href="s1-users-groups-shadow-utilities.html">15.6. Shadow Passwords</a></span></dt><dt><sp
an class="section"><a href="s1-users-groups-additional-resources.html">15.7. Additional Resources</a></span></dt></dl></div><a id="id515085" class="indexterm"></a><a id="id819720" class="indexterm"></a><a id="id694456" class="indexterm"></a><a id="id473306" class="indexterm"></a><div class="para">
+ The control of <em class="firstterm">users</em> and <em class="firstterm">groups</em> is a core element of Fedora system administration.
+ </div><div class="para">
+ <em class="firstterm">Users</em> can be either people (meaning accounts tied to physical users) or accounts which exist for specific applications to use.
+ </div><div class="para">
+ <em class="firstterm">Groups</em> are logical expressions of organization, tying users together for a common purpose. Users within a group can read, write, or execute files owned by that group.
+ </div><div class="para">
+ Each user is associated with a unique numerical identification number called a <em class="firstterm">userid</em> (<em class="firstterm">UID</em>); likewise, each group is associated with a <em class="firstterm">groupid</em> (<em class="firstterm">GID</em>).
+ </div><div class="para">
+ A user who creates a file is also the owner and group owner of that file. The file is assigned separate read, write, and execute permissions for the owner, the group, and everyone else. The file owner can be changed only by the root user, and access permissions can be changed by both the root user and file owner.
+ </div><div class="para">
+ Fedora also supports <em class="firstterm">access control lists</em> (<em class="firstterm">ACLs</em>) for files and directories which allow permissions for specific users outside of the owner to be set.
+ </div><div class="section" title="15.1. User and Group Configuration" id="s1-users-configui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-configui">15.1. User and Group Configuration</h2></div></div></div><a id="id674344" class="indexterm"></a><a id="id705856" class="indexterm"></a><a id="id1830473" class="indexterm"></a><a id="id1830491" class="indexterm"></a><a id="id748311" class="indexterm"></a><a id="id748325" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>User Manager</strong></span> allows you to view, modify, add, and delete local users and groups.
+ </div><div class="figure" title="Figure 15.1. The GNOME User Manager" id="fig-Users_Groups-User_Manager"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Users_Groups-User_Manager.png" align="middle" alt="The GNOME User Manager" /><div class="longdesc"><div class="para">
+ the gnome user manager lets you manage users
+ </div></div></div></div><h6>Figure 15.1. The GNOME <span class="application">User Manager</span> </h6></div><br class="figure-break" /><div class="para">
+ You can start the <span class="application"><strong>User Manager</strong></span> by clicking <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Users and Groups</strong></span>. Alternatively, you can enter <code class="command">system-config-users</code> at the shell prompt to open the <span class="application"><strong>User Manager</strong></span>. Viewing and modifying user and group information requires superuser privileges. If you are not the superuser when you open the <span class="application"><strong>User Manager</strong></span>, it will prompt you for the superuser password.
+ </div><a id="id417979" class="indexterm"></a><a id="id836759" class="indexterm"></a><div class="para">
+ To view a list of local users on the system, click the <span class="guilabel"><strong>Users</strong></span> tab. To view a list of local groups on the system, click the <span class="guilabel"><strong>Groups</strong></span> tab.
+ </div><div class="para">
+ To find a specific user or group, type the first few letters of the name in the <span class="guilabel"><strong>Search filter</strong></span> field. Press <span class="keycap"><strong>Enter</strong></span> or click the <span class="guibutton"><strong>Apply filter</strong></span> button. The filtered list is displayed.
+ </div><div class="para">
+ To sort the users, click on the column User Name and for groups click on Group Name. The users or groups are sorted according to the value of that column.
+ </div><div class="para">
+ Fedora reserves user IDs below 500 for system users. By default, the <span class="application"><strong>User Manager</strong></span> does not display system users. To view all users, including the system users, go to <span class="guimenuitem"><strong>Edit</strong></span> > <span class="guimenuitem"><strong>Preferences</strong></span> and uncheck <span class="guimenuitem"><strong>Hide system users and groups</strong></span> from the dialog box.
+ </div><div class="section" title="15.1.1. Adding a New User" id="s2-redhat-config-users-user-new"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-redhat-config-users-user-new">15.1.1. Adding a New User</h3></div></div></div><a id="id847223" class="indexterm"></a><div class="para">
+ To add a new user, click the <span class="guibutton"><strong>Add User</strong></span> button. A window as shown in <a class="xref" href="Users_and_Groups.html#user-new-fig" title="Figure 15.2. Creating a new user">Figure 15.2, “Creating a new user”</a> appears. Type the username and full name for the new user in the appropriate fields. Type the user's password in the <span class="guilabel"><strong>Password</strong></span> and <span class="guilabel"><strong>Confirm Password</strong></span> fields. The password must be at least six characters.
+ </div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ It is advisable to use a much longer password, as this makes it more difficult for an intruder to guess it and access the account without permission. It is also recommended that the password not be based on a dictionary term; use a combination of letters, numbers and special characters.
+ </div></div></div><div class="para">
+ Select a login shell from the pulldown list. If you are not sure which shell to select, accept the default value of <code class="computeroutput">/bin/bash</code>. The default home directory is <code class="filename">/home/<em class="replaceable"><code><username></code></em>/</code>. You can change the home directory that is created for the user, or you can choose not to create the home directory by unselecting <span class="guilabel"><strong>Create home directory</strong></span>.
+ </div><div class="para">
+ If you select to create the home directory, default configuration files are copied from the <code class="filename">/etc/skel/</code> directory into the new home directory.
+ </div><div class="para">
+ Fedora uses a <em class="firstterm">user private group</em> (UPG) scheme. The UPG scheme does not add or change anything in the standard UNIX way of handling groups; it offers a new convention. Whenever you create a new user, by default, a unique group with the same name as the user is created. If you do not want to create this group, unselect <span class="guilabel"><strong>Create a private group for the user</strong></span>.
+ </div><div class="para">
+ To specify a user ID for the user, select <span class="guibutton"><strong>Specify user ID manually</strong></span>. If the option is not selected, the next available user ID above 500 is assigned to the new user. Because Fedora reserves user IDs below 500 for system users, it is not advisable to manually assign user IDs 1-499.
+ </div><div class="para">
+ Click <span class="guibutton"><strong>OK</strong></span> to create the user.
+ </div><div class="figure" title="Figure 15.2. Creating a new user" id="user-new-fig"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Users_Groups-Create_New_User.png" align="middle" alt="Creating a new user" /><div class="longdesc"><div class="para">
+ creating a new user with the create new user dialog
+ </div></div></div></div><h6>Figure 15.2. Creating a new user</h6></div><br class="figure-break" /><div class="para">
+ To configure more advanced user properties, such as password expiration, modify the user's properties after adding the user.
+ </div><h4 id="id723301">Modifying User Properties</h4><a id="id723304" class="indexterm"></a><a id="id723318" class="indexterm"></a><div class="para">
+ To view the properties of an existing user, click on the <span class="guilabel"><strong>Users</strong></span> tab, select the user from the user list, and click <span class="guibutton"><strong>Properties</strong></span> from the menu (or choose <span class="guimenu"><strong>File</strong></span> > <span class="guimenuitem"><strong>Properties</strong></span> from the pulldown menu). A window similar to <a class="xref" href="Users_and_Groups.html#user-properties-fig" title="Figure 15.3. User Properties">Figure 15.3, “User Properties”</a> appears.
+ </div><div class="figure" title="Figure 15.3. User Properties" id="user-properties-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/user-properties.png" alt="User Properties" /><div class="longdesc"><div class="para">
+ Modifying user properties
+ </div></div></div></div><h6>Figure 15.3. User Properties</h6></div><br class="figure-break" /><div class="para">
+ The <span class="guilabel"><strong>User Properties</strong></span> window is divided into multiple tabbed pages:
+ </div><a id="id723397" class="indexterm"></a><a id="id723411" class="indexterm"></a><a id="id620511" class="indexterm"></a><a id="id620525" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>User Data</strong></span> — Shows the basic user information configured when you added the user. Use this tab to change the user's full name, password, home directory, or login shell.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Account Info</strong></span> — Select <span class="guibutton"><strong>Enable account expiration</strong></span> if you want the account to expire on a certain date. Enter the date in the provided fields. Select <span class="guilabel"><strong>Local password is locked</strong></span> to lock the user account and prevent the user from logging into the system.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Password Info</strong></span> — Displays the date that the user's password last changed. To force the user to change passwords after a certain number of days, select <span class="guilabel"><strong>Enable password expiration</strong></span> and enter a desired value in the <span class="guilabel"><strong>Days before change required:</strong></span> field. The number of days before the user's password expires, the number of days before the user is warned to change passwords, and days before the account becomes inactive can also be changed.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Groups</strong></span> — Allows you to view and configure the Primary Group of the user, as well as other groups that you want the user to be a member of.
+ </div></li></ul></div></div><div class="section" title="15.1.2. Adding a New Group" id="s2-redhat-config-users-group-new"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-redhat-config-users-group-new">15.1.2. Adding a New Group</h3></div></div></div><a id="id620619" class="indexterm"></a><div class="para">
+ To add a new user group, select <span class="guibutton"><strong>Add Group</strong></span> from the toolbar. A window similar to <a class="xref" href="Users_and_Groups.html#group-new-fig" title="Figure 15.4. New Group">Figure 15.4, “New Group”</a> appears. Type the name of the new group. To specify a group ID for the new group, select <span class="guibutton"><strong>Specify group ID manually</strong></span> and select the GID. Note that Fedora also reserves group IDs lower than 500 for system groups.
+ </div><div class="figure" title="Figure 15.4. New Group" id="group-new-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/group-new.png" alt="New Group" /><div class="longdesc"><div class="para">
+ Creating a new group
+ </div></div></div></div><h6>Figure 15.4. New Group</h6></div><br class="figure-break" /><div class="para">
+ Click <span class="guibutton"><strong>OK</strong></span> to create the group. The new group appears in the group list.
+ </div></div><div class="section" title="15.1.3. Modifying Group Properties" id="s2-redhat-config-users-group-properties"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-redhat-config-users-group-properties">15.1.3. Modifying Group Properties</h3></div></div></div><a id="id492548" class="indexterm"></a><div class="para">
+ To view the properties of an existing group, select the group from the group list and click <span class="guibutton"><strong>Properties</strong></span> from the menu (or choose <span class="guimenu"><strong>File</strong></span> > <span class="guimenuitem"><strong>Properties</strong></span> from the pulldown menu). A window similar to <a class="xref" href="Users_and_Groups.html#group-properties-fig" title="Figure 15.5. Group Properties">Figure 15.5, “Group Properties”</a> appears.
+ </div><div class="figure" title="Figure 15.5. Group Properties" id="group-properties-fig"><div class="figure-contents"><div class="mediaobject"><img src="images/group-properties.png" alt="Group Properties" /><div class="longdesc"><div class="para">
+ Modifying group properties
+ </div></div></div></div><h6>Figure 15.5. Group Properties</h6></div><br class="figure-break" /><a id="id492614" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Group Users</strong></span> tab displays which users are members of the group. Use this tab to add or remove users from the group. Click <span class="guibutton"><strong>OK</strong></span> to save your changes.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-keyboard-break.html"><strong>Prev</strong>14.3. Setting Up a Typing Break</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-users-tools.html"><strong>Next</strong>15.2. User and Group Management Tools</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/abrt-plugins.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/abrt-plugins.html
new file mode 100644
index 0000000..57fdb07
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/abrt-plugins.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.3. ABRT Plugins</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-abrt.html" title="Chapter 21. ABRT" /><link rel="prev" href="ch21s02.html" title="21.2. Installing and Running ABRT" /><link rel="next" href="reporter-plugins.html" title="21.3.2. Reporter Plugins" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="reporter-plugins.html"><strong>Next</
strong></a></li></ul><div class="section" title="21.3. ABRT Plugins" id="abrt-plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="abrt-plugins">21.3. <span class="application"><strong>ABRT</strong></span> Plugins</h2></div></div></div><div class="para">
+ <span class="application"><strong>ABRT</strong></span> offers a variety of analyzer plugins and reporter plugins. These plugins are described in the following two sections. Not all of the plugins mentioned in the following sections are installed by default. To view all available plugins, run the following command:
+<pre class="screen">
+<code class="command">]$ yum list all | grep abrt-plugin-*</code>
+</pre>
+
+ </div><div class="section" title="21.3.1. Analyzer Plugins" id="analyzer-plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="analyzer-plugins">21.3.1. Analyzer Plugins</h3></div></div></div><div class="para">
+ These plugins serve as analyzers and crash information collectors for specific types of crashes. For example, the <span class="application"><strong>Kerneloops</strong></span> analyzer plugin checks for crashes in the kernel only. These plugins can be enabled/disabled from loading at start-up in their corresponding configuration files placed in the <code class="filename">/etc/abrt/plugins/</code> directory. The following is a list of all analyzer plugins.
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Kerneloops</span></dt><dd><div class="para">
+ — Checks for crashes in the kernel and consequently collects kernel crash information. It can be enabled/disabled from loading at start-up in the <code class="filename">/etc/abrt/plugins/Kerneloops.conf</code> file.
+ </div></dd><dt class="varlistentry"><span class="term">Python</span></dt><dd><div class="para">
+ — Checks for crashes in Python programs and consequently collects the crash information. It can be enabled/disabled from loading at start-up in the <code class="filename">/etc/abrt/plugins/Python.conf</code> file.
+ </div></dd><dt class="varlistentry"><span class="term">CCpp</span></dt><dd><div class="para">
+ — Checks for crashes in C and C++ programs and consequently collects the crash information. It can be enabled/disabled from loading at start-up in the <code class="filename">/etc/abrt/plugins/CCpp.conf</code> file.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s02.html"><strong>Prev</strong>21.2. Installing and Running ABRT</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="reporter-plugins.html"><strong>Next</strong>21.3.2. Reporter Plugins</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/app-Revision_History.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/app-Revision_History.html
new file mode 100644
index 0000000..d79a46b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/app-Revision_History.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Appendix A. Revision History</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="s2-kdump-resources-online.html" title="24.3.2. Useful Websites" /><link rel="next" href="ix01.html" title="Index" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-resources-online.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><strong>Next</strong></a></li></ul><
div xml:lang="en-US" class="appendix" title="Appendix A. Revision History" id="app-Revision_History" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Revision History</h1></div></div></div><div class="para">
+ <div class="revhistory"><table border="0" width="100%" summary="Revision history"><tr><th align="left" valign="top" colspan="3"><b>Revision History</b></th></tr><tr><td align="left">Revision 2</td><td align="left">Sun Nov 14 2010</td><td align="left"><span class="author"><span class="firstname">Jaromír</span> <span class="surname">Hradílek</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Fedora 14 Release of the <em class="citetitle">Deployment Guide</em>.</td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 1</td><td align="left">Mon Nov 16 2009</td><td align="left"><span class="author"><span class="firstname">Douglas</span> <span class="surname">Silas</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Initialization of the Fedora 13 <em class="citetitle">Deployment Guide</em>.</td></tr></table>
+
+ </td></tr></table></div>
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-resources-online.html"><strong>Prev</strong>24.3.2. Useful Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><strong>Next</strong>Index</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Authentication_Configuration.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Authentication_Configuration.html
new file mode 100644
index 0000000..bef06e6
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Authentication_Configuration.html
@@ -0,0 +1,424 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 8. Authentication Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /><link rel="prev" href="s2-services-additional-resources-books.html" title="7.4.2. Related Books" /><link rel="next" href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System Security Services Daemon (SSSD)" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-services-additional-
resources-books.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Introduction.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 8. Authentication Configuration" id="ch-Authentication_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. Authentication Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool">8.1. The Authentication Configuration Tool</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html">8.2. The System Security Services Daemon (SSSD)</a></span></dt></dl></div><div class="section" title="8.1. The Authentication Configuration Tool" id="sect-The_Authentication_Configuration_Tool"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-The_Aut
hentication_Configuration_Tool">8.1. The Authentication Configuration Tool</h2></div></div></div><a id="id678428" class="indexterm"></a><a id="id683928" class="indexterm"></a><div class="para">
+ When a user logs in to a Fedora system, the username and password combination must be verified, or <em class="firstterm">authenticated</em>, as a valid and active user. Sometimes the information to verify the user is located on the local system, and other times the system defers the authentication to a user database on a remote system.
+ </div><div class="para">
+ The <span class="application"><strong>Authentication Configuration Tool</strong></span> provides a graphical interface for configuring user information retrieval from <em class="firstterm">Lightweight Directory Access Protocol</em> (LDAP), <em class="firstterm"> Network Information Service</em> (NIS), and <em class="firstterm">Winbind</em> user account databases. This tool also allows you to configure Kerberos to be used as the authentication protocol when using LDAP or NIS.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you configured a medium or high security level during installation (or with the <span class="application"><strong>Security Level Configuration Tool</strong></span>), then the firewall will prevent NIS authentication. For more information about firewalls, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/14/html/Security_Guide/sect-Security_Guide-Firewalls.html"><em class="citetitle"><span class="quote">“<span class="quote">Firewalls</span>”</span></em> section</a> of the Fedora 14 <a href="http://docs.fedoraproject.org/en-US/Fedora/14/html/Security_Guide/index.html"><em class="citetitle">Security Guide</em></a>.
+ </div></div></div><a id="id684001" class="indexterm"></a><a id="id683986" class="indexterm"></a><div class="para">
+ To start the graphical version of the <span class="application"><strong>Authentication Configuration Tool</strong></span> from the desktop, click <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Authentication</strong></span> or type the command <code class="command">system-config-authentication</code> at a shell prompt (for example, in an <span class="application"><strong>XTerm</strong></span> or a <span class="application"><strong>GNOME</strong></span> terminal).
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ After exiting the authentication program, any changes you made take effect immediately.
+ </div></div></div><div class="section" title="8.1.1. Identity & Authentication" id="sect-The_Authentication_Configuration_Tool-Identity_and_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">8.1.1. Identity & Authentication</h3></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Identity & Authentication</strong></span> tab allows you to configure how users should be authenticated, and has several options for each method of authentication. To select which user account database should be used, select an option from the drop-down list.
+ </div><div class="figure" title="Figure 8.1. Identity & Authentication; changing the option in the User Account Database drop-down list changes the contents of the tab."><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/authconfig_LDAP_kerb.png" align="middle" alt="Identity & Authentication; changing the option in the User Account Database drop-down list changes the contents of the tab." /></div></div><h6>Figure 8.1. <span class="guilabel">Identity & Authentication</span>; changing the option in the <span class="guilabel">User Account Database</span> drop-down list changes the contents of the tab.</h6></div><br class="figure-break" /><div class="para">
+ The following list explains what each option configures:
+ </div><h4 id="id734173">LDAP</h4><a id="id734171" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>LDAP</strong></span> option instructs the system to retrieve user information via LDAP. It contains the following specifications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP Search Base DN</strong></span> — Specifies that user information should be retrieved using the listed Distinguished Name (DN).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP Server</strong></span> — Specifies the address of the <code class="systemitem">LDAP</code> server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Use TLS to encrypt connections</strong></span> — When enabled, <code class="systemitem">Transport Layer Security</code> (TLC) will be used to encrypt passwords sent to the <code class="systemitem">LDAP</code> server. The <span class="guibutton"><strong>Download CA Certificate</strong></span> option allows you to specify a URL from which to download a valid <em class="firstterm">Certificate Authority certificate</em> (CA). A valid CA certificate must be in the <em class="firstterm">Privacy Enhanced Mail</em> (PEM) format.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <span class="guilabel"><strong>Use TLS to encrypt connections</strong></span> option must not be ticked if an <code class="systemitem">ldaps://</code> server address is specified in the <span class="guilabel"><strong>LDAP Server</strong></span> field.
+ </div></div></div><div class="para">
+ For more information about CA Certificates, refer to <a class="xref" href="s1-apache-mod_ssl.html#s2-apache-mod_ssl-certificates" title="11.6.1. An Overview of Certificates and Security">Section 11.6.1, “An Overview of Certificates and Security”</a>.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">openldap-clients</code> package must be installed for this option to work.
+ </div><div class="para">
+ LDAP provides the following methods of authentication:
+ </div><div class="itemizedlist"><ul><li class="listitem"><a id="id734014" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Kerberos password</strong></span> — This option enables Kerberos authentication. It contains the following specifications:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Realm</strong></span> — Configures the realm for the Kerberos server. The realm is the network that uses Kerberos, composed of one or more KDCs and a potentially large number of clients.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>KDCs</strong></span> — Defines the Key Distribution Centers (KDC), which are servers that issue Kerberos tickets.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Admin Servers</strong></span> — Specifies the administration server(s) running <code class="command">kadmind</code>.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The <span class="guimenu"><strong>Kerberos Settings</strong></span> dialog also allows you to use DNS to resolve hosts to realms and locate KDCs for realms.
+ </div><div class="para">
+ The <code class="filename">krb5-libs</code> and <code class="filename">krb5-workstation</code> packages must be installed for this option to work. For more information about Kerberos, refer to section <em class="citetitle">Using Kerberos</em> of the Fedora 14 <em class="citetitle">Managing Single Sign-On and Smart Cards</em> guide.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>LDAP password</strong></span> — This option instructs standard PAM-enabled applications to use LDAP authentication with options specified in the User Account Configuration of LDAP. When using this option, you must provide an <code class="systemitem">ldaps://</code> server address or use TLS for LDAP authentication.
+ </div></li></ul></div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The SSSD service is used as a client for LDAP and Kerberos servers. Thus, offline login is enabled and supported by default. No user interaction is needed to set up the SSSD service with the <span class="application"><strong>Authentication Configuration Tool</strong></span>. For more information about the SSSD service, refer to <a class="xref" href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System Security Services Daemon (SSSD)">Section 8.2, “The System Security Services Daemon (SSSD)”</a>
+ </div></div></div><h4 id="id631753">NIS</h4><a id="id631749" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>NIS</strong></span> option configures the system to connect to a NIS server (as an NIS client) for user and password authentication. To configure this option, specify the NIS domain and NIS server. If the NIS server is not specified, the daemon attempts to find it via broadcast.
+ </div><div class="para">
+ The <span class="package">ypbind</span> package must be installed for this option to work. If the NIS user account databse is used, the <code class="systemitem">portmap</code> and <code class="systemitem">ypbind</code> services are started and are also enabled to start at boot time.
+ </div><div class="para">
+ For more information about NIS, refer to <a href="http://docs.fedoraproject.org/en-US/Fedora/14/html/Security_Guide/sect-Security_Guide-Server_Security-Securing_NIS.html">section <em class="citetitle"><span class="quote">“<span class="quote">Securing NIS</span>”</span></em></a> of the Fedora 14 <em class="citetitle">Security Guide</em>.
+ </div><div class="para">
+ NIS provides the following methods of authentication:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Kerberos password</strong></span> — This option enables Kerberos authentication. For more information about configuration of the Kerberos authentication method, refer to the previous section on LDAP.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id598976" class="indexterm"></a>
+ <span class="guilabel"><strong>NIS password</strong></span> — This option enables NIS authentication. NIS can provide authentication information to outside processes to authenticate users.
+ </div></li></ul></div><h4 id="id598944">Winbind</h4><a id="id598930" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Winbind</strong></span> option configures the system to connect to a Windows Active Directory or a Windows domain controller. User information from the specified directory or domain controller can then be accessed, and server authentication options can be configured. It contains the following specifications:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind Domain</strong></span> — Specifies the Windows Active Directory or domain controller to connect to.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Security Model</strong></span> — Allows you to select a security model, which configures the Samba client mode of operation. The drop-down list allows you to select any of the following:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>ads</strong></span> — This mode instructs Samba to act as a domain member in an Active Directory Server (ADS) realm. To operate in this mode, the <code class="filename">krb5-server</code> package must be installed, and Kerberos must be configured properly.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>domain</strong></span> — In this mode, Samba will attempt to validate the username/password by authenticating it through a Windows NT Primary or Backup Domain Controller, similar to how a Windows NT Server would.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>server</strong></span> — In this mode, Samba will attempt to validate the username/password by authenticating it through another SMB server (for example, a Windows NT Server). If the attempt fails, the <span class="guilabel"><strong>user</strong></span> mode will take effect instead.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>user</strong></span> — This is the default mode. With this level of security, a client must first log in with a valid username and password. Encrypted passwords can also be used in this security mode.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind ADS Realm</strong></span> — When the <span class="guilabel"><strong>ads</strong></span> Security Model is selected, this allows you to specify the ADS Realm the Samba server should act as a domain member of.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Winbind Domain Controllers</strong></span> — Use this option to specify which domain controller <code class="command">winbind</code> should use.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Template Shell</strong></span> — When filling out the user information for a Windows NT user, the <code class="command">winbindd</code> daemon uses the value chosen here to to specify the login shell for that user.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Allow offline login</strong></span> — By checking this option, you allow authentication information to be stored in a local cache (provided by SSSD). This information is then used when a user attempts to authenticate while offline.
+ </div></li></ul></div><a id="id502909" class="indexterm"></a><div class="para">
+ Winbind provides only one method of authentication, <span class="guilabel"><strong>Winbind password</strong></span>. This method of authentication uses the options specified in the User Account Configuration of Winbind to connect to a Windows Active Directory or a Windows domain controller.
+ </div></div><div class="section" title="8.1.2. Advanced Options" id="sect-The_Authentication_Configuration_Tool-Advanced_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-The_Authentication_Configuration_Tool-Advanced_Options">8.1.2. Advanced Options</h3></div></div></div><div class="para">
+ This tab allows you to configure advanced options, as listed below.
+ </div><div class="figure" title="Figure 8.2. Advanced Options"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/authconfig_advanced.png" align="middle" width="444" alt="Advanced Options" /></div></div><h6>Figure 8.2. <span class="guilabel">Advanced Options</span></h6></div><br class="figure-break" /><h4 id="id502850">Local Authentication Options</h4><div class="itemizedlist"><ul><li class="listitem"><a id="id502840" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Enable fingerprint reader support</strong></span> — By checking this option, you enable fingerprint authentication to log in by scanning your finger with the fingerprint reader.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Enable local access control</strong></span> — When enabled, <code class="filename">/etc/security/access.conf</code> is consulted for authorization of a user.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Password Hashing Algorithm</strong></span> — This option lets you specify which hashing or cryptographic algorithm should be used to encrypt locally stored passwords.
+ </div></li></ul></div><h4 id="id739594">Other Authentication Options</h4><div class="para">
+ <span class="guilabel"><strong>Create home directories on the first login</strong></span> — When enabled, the user's home directory is automatically created when they log in if it does not already exist.
+ </div><h4 id="id739582">Smart Card Authentication Options</h4><a id="id739578" class="indexterm"></a><div class="para">
+ <span class="guilabel"><strong>Enable smart card support</strong></span> — This option enables smart card authentication. Smart card authentication allows you to log in using a certificate and a key associated with a smart card.
+ </div><div class="para">
+ When the <span class="guilabel"><strong>Enable smart card support</strong></span> option is checked, the following options can be specified:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Card Removal Action</strong></span> — This option defines what action the system performs when the card is removed from the card reader during an active session. Two alternatives are available:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Ignore</strong></span> — The card removal is ignored and the system continues to function as normal.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Lock</strong></span> — The current session is immediately locked.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Require smart card login</strong></span> — Requires the user to login and authenticate with a smart card. It essentially disables any other type of password authentication. This option should not be selected until after you have successfully logged in using a smart card.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The <span class="package">pam_pkcs11</span> and the <span class="package">coolkey</span> packages must be installed for this option to work. For more information about smart cards, refer to the Fedora 14 <em class="citetitle">Managing Single Sign-On and Smart Cards</em> guide. <div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ You can restore all of the options specified in the <span class="application"><strong>Authentication Configuration Tool</strong></span> to the previous configuration setup by clicking <span class="guibutton"><strong>Revert</strong></span>.
+ </div></div></div>
+
+ </div></div><div class="section" title="8.1.3. Command Line Version" id="sect-The_Authentication_Configuration_Tool-Command_Line_Version"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-The_Authentication_Configuration_Tool-Command_Line_Version">8.1.3. Command Line Version</h3></div></div></div><a id="id739413" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Authentication Configuration Tool</strong></span> also supports a command line interface. The command line version can be used in a configuration script or a kickstart script. The authentication options are summarized in <a class="xref" href="ch-Authentication_Configuration.html#tb-authconfig-cmd-line" title="Table 8.1. Command Line Options">Table 8.1, “Command Line Options”</a>.
+ </div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ These options can also be found in the <code class="command">authconfig</code> man page or by typing <code class="command">authconfig --help</code> at the shell prompt.
+ </div></div></div><div class="table" title="Table 8.1. Command Line Options" id="tb-authconfig-cmd-line"><h6>Table 8.1. Command Line Options</h6><div class="table-contents"><table summary="Command Line Options" border="1"><colgroup><col width="60%" /><col width="40%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">--enableshadow, --useshadow</code>
+ </td><td>
+ Enable shadow passwords
+ </td></tr><tr><td>
+ <code class="command">--disableshadow</code>
+ </td><td>
+ Disable shadow passwords
+ </td></tr><tr><td>
+ <code class="command">--passalgo=<em class="replaceable"><code><descrypt|bigcrypt|md5|sha256|sha512></code></em></code>
+ </td><td>
+ Hash/crypt algorithm to be used
+ </td></tr><tr><td>
+ <code class="command">--enablenis</code>
+ </td><td>
+ Enable NIS for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disablenis</code>
+ </td><td>
+ Disable NIS for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--nisdomain=<em class="replaceable"><code><domain></code></em> </code>
+ </td><td>
+ Specify an NIS domain
+ </td></tr><tr><td>
+ <code class="command">--nisserver=<em class="replaceable"><code><server></code></em> </code>
+ </td><td>
+ Specify an NIS server
+ </td></tr><tr><td>
+ <code class="command">--enableldap</code>
+ </td><td>
+ Enable LDAP for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disableldap</code>
+ </td><td>
+ Disable LDAP for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--enableldaptls</code>
+ </td><td>
+ Enable use of TLS with LDAP
+ </td></tr><tr><td>
+ <code class="command">--disableldaptls</code>
+ </td><td>
+ Disable use of TLS with LDAP
+ </td></tr><tr><td>
+ <code class="command">--enablerfc2307bis</code>
+ </td><td>
+ Enable use of RFC-2307bis schema for LDAP user information lookups
+ </td></tr><tr><td>
+ <code class="command">--disablerfc2307bis</code>
+ </td><td>
+ Disable use of RFC-2307bis schema for LDAP user information lookups
+ </td></tr><tr><td>
+ <code class="command">--enableldapauth</code>
+ </td><td>
+ Enable LDAP for authentication
+ </td></tr><tr><td>
+ <code class="command">--disableldapauth</code>
+ </td><td>
+ Disable LDAP for authentication
+ </td></tr><tr><td>
+ <code class="command">--ldapserver=<em class="replaceable"><code><server></code></em> </code>
+ </td><td>
+ Specify an LDAP server
+ </td></tr><tr><td>
+ <code class="command">--ldapbasedn=<em class="replaceable"><code><dn></code></em> </code>
+ </td><td>
+ Specify an LDAP base DN (Distinguished Name)
+ </td></tr><tr><td>
+ <code class="command">--ldaploadcacert=<em class="replaceable"><code><URL></code></em> </code>
+ </td><td>
+ Load a CA certificate from the specified URL
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5</code>
+ </td><td>
+ Enable Kerberos for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5</code>
+ </td><td>
+ Disable Kerberos for authentication
+ </td></tr><tr><td>
+ <code class="command">--krb5kdc=<em class="replaceable"><code><server></code></em> </code>
+ </td><td>
+ Specify Kerberos KDC server
+ </td></tr><tr><td>
+ <code class="command">--krb5adminserver=<em class="replaceable"><code><server></code></em> </code>
+ </td><td>
+ Specify Kerberos administration server
+ </td></tr><tr><td>
+ <code class="command">--krb5realm=<em class="replaceable"><code><realm></code></em> </code>
+ </td><td>
+ Specify Kerberos realm
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5kdcdns</code>
+ </td><td>
+ Enable use of DNS to find Kerberos KDCs
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5kdcdns</code>
+ </td><td>
+ Disable use of DNS to find Kerberos KDCs
+ </td></tr><tr><td>
+ <code class="command">--enablekrb5realmdns</code>
+ </td><td>
+ Enable use of DNS to find Kerberos realms
+ </td></tr><tr><td>
+ <code class="command">--disablekrb5realmdns</code>
+ </td><td>
+ Disable use of DNS to find Kerberos realms
+ </td></tr><tr><td>
+ <code class="command">--enablewinbind</code>
+ </td><td>
+ Enable winbind for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--disablewinbind</code>
+ </td><td>
+ Disable winbind for user account configuration
+ </td></tr><tr><td>
+ <code class="command">--enablewinbindauth</code>
+ </td><td>
+ Enable winbindauth for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablewinbindauth</code>
+ </td><td>
+ Disable winbindauth for authentication
+ </td></tr><tr><td>
+ <code class="command">--winbindseparator=<em class="replaceable"><code><\></code></em> </code>
+ </td><td>
+ Character used to separate the domain and user part of winbind usernames if <code class="command">winbindusedefaultdomain</code> is not enabled
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplatehomedir=<em class="replaceable"><code></home/%D/%U></code></em> </code>
+ </td><td>
+ Directory that winbind users have as their home
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplateprimarygroup=<em class="replaceable"><code><nobody></code></em> </code>
+ </td><td>
+ Group that winbind users have as their primary group
+ </td></tr><tr><td>
+ <code class="command">--winbindtemplateshell=<em class="replaceable"><code></bin/false></code></em> </code>
+ </td><td>
+ Shell that winbind users have as their default login shell
+ </td></tr><tr><td>
+ <code class="command">--enablewinbindusedefaultdomain</code>
+ </td><td>
+ Configures winbind to assume that users with no domain in their usernames are domain users
+ </td></tr><tr><td>
+ <code class="command">--disablewinbindusedefaultdomain</code>
+ </td><td>
+ Configures winbind to assume that users with no domain in their usernames are not domain users
+ </td></tr><tr><td>
+ <code class="command">--winbindjoin=<em class="replaceable"><code><Administrator></code></em> </code>
+ </td><td>
+ Joins the winbind domain or ADS realm as the specified administrator
+ </td></tr><tr><td>
+ <code class="command">--enablewinbindoffline</code>
+ </td><td>
+ Configures winbind to allow offline login
+ </td></tr><tr><td>
+ <code class="command">--disablewinbindoffline</code>
+ </td><td>
+ Configures winbind to prevent offline login
+ </td></tr><tr><td>
+ <code class="command">--smbsecurity=<em class="replaceable"><code><user|server|domain|ads></code></em></code>
+ </td><td>
+ Security mode to use for the Samba and Winbind services
+ </td></tr><tr><td>
+ <code class="command">--smbrealm=<em class="replaceable"><code><realm></code></em></code>
+ </td><td>
+ Default realm for Samba and Winbind services when <span class="guilabel"><strong>security</strong></span> is set to <span class="guimenuitem"><strong>ads</strong></span>
+ </td></tr><tr><td>
+ <code class="command">--enablewins</code>
+ </td><td>
+ Enable Wins for hostname resolution
+ </td></tr><tr><td>
+ <code class="command">--disablewins</code>
+ </td><td>
+ Disable Wins for hostname resolution
+ </td></tr><tr><td>
+ <code class="command">--enablesssd</code>
+ </td><td>
+ Enable SSSD for user information
+ </td></tr><tr><td>
+ <code class="command">--disablesssd</code>
+ </td><td>
+ Disable SSSD for user information
+ </td></tr><tr><td>
+ <code class="command">--enablecache</code>
+ </td><td>
+ Enable <code class="command">nscd</code>
+ </td></tr><tr><td>
+ <code class="command">--disablecache</code>
+ </td><td>
+ Disable <code class="command">nscd</code>
+ </td></tr><tr><td>
+ <code class="command">--enablelocauthorize</code>
+ </td><td>
+ Local authorization is sufficient for local users
+ </td></tr><tr><td>
+ <code class="command">--disablelocauthorize</code>
+ </td><td>
+ Local users are also authorized through a remote service
+ </td></tr><tr><td>
+ <code class="command">--enablesysnetauth</code>
+ </td><td>
+ Authenticate system accounts with network services
+ </td></tr><tr><td>
+ <code class="command">--disablesysnetauth</code>
+ </td><td>
+ Authenticate system accounts with local files only
+ </td></tr><tr><td>
+ <code class="command">--enablepamaccess</code>
+ </td><td>
+ Check <code class="filename">/etc/security/access.conf</code> during account authorization
+ </td></tr><tr><td>
+ <code class="command">--disablepamaccess</code>
+ </td><td>
+ Do not check <code class="filename">/etc/security/access.conf</code> during account authorization
+ </td></tr><tr><td>
+ <code class="command">--enablemkhomedir</code>
+ </td><td>
+ Create a home directory for a user on the first login
+ </td></tr><tr><td>
+ <code class="command">--disablemkhomedir</code>
+ </td><td>
+ Do not create a home directory for a user on the first login
+ </td></tr><tr><td>
+ <code class="command">--enablesmartcard</code>
+ </td><td>
+ Enable authentication with a smart card
+ </td></tr><tr><td>
+ <code class="command">--disablesmartcard</code>
+ </td><td>
+ Disable authentication with a smart card
+ </td></tr><tr><td>
+ <code class="command">--enablerequiresmartcard</code>
+ </td><td>
+ Require smart card for authentication
+ </td></tr><tr><td>
+ <code class="command">--disablerequiresmartcard</code>
+ </td><td>
+ Do not require smart card for authentication
+ </td></tr><tr><td>
+ <code class="command">--smartcardmodule=<em class="replaceable"><code><module></code></em></code>
+ </td><td>
+ Default smart card module to use
+ </td></tr><tr><td>
+ <code class="command">--smartcardaction=<em class="replaceable"><code><0=Lock|1=Ignore></code></em></code>
+ </td><td>
+ Action to be taken when smart card removal is detected
+ </td></tr><tr><td>
+ <code class="command">--enablefingerprint</code>
+ </td><td>
+ Enable fingerprint authentication
+ </td></tr><tr><td>
+ <code class="command">--disablefingerprint</code>
+ </td><td>
+ Disnable fingerprint authentication
+ </td></tr><tr><td>
+ <code class="command">--nostart</code>
+ </td><td>
+ Do not start or stop the <code class="command">portmap</code>, <code class="command">ypbind</code>, or <code class="command">nscd</code> services even if they are configured
+ </td></tr><tr><td>
+ <code class="command">--test</code>
+ </td><td>
+ Do not update the configuration files, only print the new settings
+ </td></tr><tr><td>
+ <code class="command">--update, --kickstart</code>
+ </td><td>
+ Opposite of <code class="command">--test</code>, update configuration files with changed settings
+ </td></tr><tr><td>
+ <code class="command">--updateall</code>
+ </td><td>
+ Update all configuration files
+ </td></tr><tr><td>
+ <code class="command">--probe</code>
+ </td><td>
+ Probe and display network defaults
+ </td></tr><tr><td>
+ <code class="command">--savebackup=<em class="replaceable"><code><name></code></em></code>
+ </td><td>
+ Save a backup of all configuration files
+ </td></tr><tr><td>
+ <code class="command">--restorebackup=<em class="replaceable"><code><name></code></em></code>
+ </td><td>
+ Restore a backup of all configuration files
+ </td></tr><tr><td>
+ <code class="command">--restorelastbackup</code>
+ </td><td>
+ Restore the backup of configuration files saved before the previous configuration change
+ </td></tr></tbody></table></div></div><br class="table-break" /></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-services-additional-resources-books.html"><strong>Prev</strong>7.4.2. Related Books</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Introduction.html"><strong>Next</strong>8.2. The System Security Services Daemon (SSSD)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Automated_Tasks.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Automated_Tasks.html
new file mode 100644
index 0000000..a640ed8
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Automated_Tasks.html
@@ -0,0 +1,151 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 16. Automated Tasks</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-sysconfig.html" title="Part III. System Configuration" /><link rel="prev" href="s1-users-groups-additional-resources.html" title="15.7. Additional Resources" /><link rel="next" href="s1-autotasks-at-batch.html" title="16.2. At and Batch" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-additional-resources.html"><strong>Prev</strong></a></li><li clas
s="next"><a accesskey="n" href="s1-autotasks-at-batch.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 16. Automated Tasks" id="ch-Automated_Tasks" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 16. Automated Tasks</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Automated_Tasks.html#s1-autotasks-cron-anacron">16.1. Cron and Anacron</a></span></dt><dt><span class="section"><a href="s1-autotasks-at-batch.html">16.2. At and Batch</a></span></dt><dt><span class="section"><a href="s1-autotasks-additional-resources.html">16.3. Additional Resources</a></span></dt></dl></div><a id="id549030" class="indexterm"></a><div class="para">
+ In Linux, tasks, which are also known as <em class="firstterm">jobs</em>, can be configured to run automatically within a specified period of time, on a specified date, or when the system load average is below a specified number. Fedora is pre-configured to run important system tasks to keep the system updated. For example, the slocate database used by the <code class="command">locate</code> command is updated daily. A system administrator can use automated tasks to perform periodic backups, monitor the system, run custom scripts, and more.
+ </div><div class="para">
+ Fedora comes with several automated tasks utilities: <code class="command">cron</code>, <code class="command">at</code>, and <code class="command">batch</code>.
+ </div><a id="id551489" class="indexterm"></a><div class="section" title="16.1. Cron and Anacron" id="s1-autotasks-cron-anacron"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-autotasks-cron-anacron">16.1. Cron and Anacron</h2></div></div></div><a id="id715782" class="indexterm"></a><a id="id576380" class="indexterm"></a><div class="para">
+ Both, Cron and Anacron, are daemons that can be used to schedule the execution of recurring tasks according to a combination of the time, day of the month, month, day of the week, and week.
+ </div><div class="para">
+ Cron assumes that the system is on continuously. If the system is not on when a job is scheduled, it is not executed. Cron allows jobs to be run as often as every minute. Anacron does not assume the system is always on, remembers every scheduled job, and executes it the next time the system is up. However, Anacron can only run a job once a day. To schedule reccurring jobs, refer to <a class="xref" href="ch-Automated_Tasks.html#s2-configuring-anacron-jobs" title="16.1.2. Configuring Anacron Jobs">Section 16.1.2, “Configuring Anacron Jobs”</a> or <a class="xref" href="ch-Automated_Tasks.html#s2-configuring-cron-jobs" title="16.1.3. Configuring Cron Jobs">Section 16.1.3, “Configuring Cron Jobs”</a>. To schedule one-time jobs, refer to <a class="xref" href="s1-autotasks-at-batch.html" title="16.2. At and Batch">Section 16.2, “At and Batch”</a>.
+ </div><div class="para">
+ To use the cron service, the <code class="filename">cronie</code> RPM package must be installed and the <code class="command">crond</code> service must be running. <code class="filename">anacron</code> is a sub-package of <code class="filename">cronie</code>. To determine if these packages are installed, use the <code class="command">rpm -q cronie cronie-anacron</code> command.
+ </div><div class="section" title="16.1.1. Starting and Stopping the Service" id="s2-autotasks-cron-service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-cron-service">16.1.1. Starting and Stopping the Service</h3></div></div></div><div class="para">
+ To determine if the service is running, use the command <code class="command">/sbin/service crond status</code>. To start the cron service, use the command <code class="command">/sbin/service crond start</code>. To stop the service, use the command <code class="command">/sbin/service crond stop</code>. It is recommended that you start the service at boot time. Refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for details on starting the cron service automatically at boot time.
+ </div></div><div class="section" title="16.1.2. Configuring Anacron Jobs" id="s2-configuring-anacron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-configuring-anacron-jobs">16.1.2. Configuring Anacron Jobs</h3></div></div></div><a id="id700831" class="indexterm"></a><a id="id700844" class="indexterm"></a><a id="id700858" class="indexterm"></a><a id="id1768373" class="indexterm"></a><div class="para">
+ The main configuration file to schedule jobs is <code class="filename">/etc/anacrontab</code> (only root is allowed to modify this file), which contains the following lines:
+ </div><pre class="screen">
+SHELL=/bin/sh
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+# the maximal random delay added to the base delay of the jobs
+RANDOM_DELAY=45
+# the jobs will be started during the following hours only
+START_HOURS_RANGE=3-22
+
+#period in days delay in minutes job-identifier command
+1 5 cron.daily nice run-parts /etc/cron.daily
+7 25 cron.weekly nice run-parts /etc/cron.weekly
+ at monthly 45 cron.monthly nice run-parts /etc/cron.monthly
+</pre><div class="para">
+ The first three lines are variables used to configure the environment in which the anacron tasks are run. The <code class="computeroutput">SHELL</code> variable tells the system which shell environment to use (in this example the bash shell). The <code class="computeroutput">PATH</code> variable defines the path used to execute commands. The output of the anacron jobs are emailed to the username defined with the <code class="computeroutput">MAILTO</code> variable. If the <code class="computeroutput">MAILTO</code> variable is not defined, (i.e. is empty, <code class="computeroutput">MAILTO=</code>), email is not sent.
+ </div><div class="para">
+ The next two lines are variables that modify the time for each scheduled job. The <code class="computeroutput">RANDOM_DELAY</code> variable denotes the maximum number of minutes that will be added to the <code class="filename">delay in minutes</code> variable which is specified for each job. The minimum delay value is set, by default, to 6 minutes. A <code class="computeroutput">RANDOM_DELAY</code> set to 12 would therefore add, randomly, between 6 and 12 minutes to the <code class="filename">delay in minutes</code> for each job in that particular anacrontab. <code class="computeroutput">RANDOM_DELAY</code> can also be set to a value below 6, or even 0. When set to 0, no random delay is added. This proves to be useful when, for example, more computers that share one network connection need to download the same data every day. The <code class="computeroutput">START_HOURS_RANGE</code> variable defines an interval (in hours) when scheduled jobs can be run. In case this time
interval is missed, for example, due to a power down, then scheduled jobs are not executed that day.
+ </div><div class="para">
+ The rest of the lines in the <code class="filename">/etc/anacrontab</code> file represent scheduled jobs and have the following format:
+ </div><pre class="screen">
+period in days delay in minutes job-identifier command
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">period in days</code> — specifies the frequency of execution of a job in days. This variable can be represented by an integer or a macro (<code class="computeroutput">@daily</code>, <code class="computeroutput">@weekly</code>, <code class="computeroutput">@monthly</code>), where <code class="computeroutput">@daily</code> denotes the same value as the integer 1, <code class="computeroutput">@weekly</code> the same as 7, and <code class="computeroutput">@monthly</code> specifies that the job is run once a month, independent on the length of the month.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">delay in minutes</code> — specifies the number of minutes anacron waits, if necessary, before executing a job. This variable is represented by an integer where 0 means no delay.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">job-identifier</code> — specifies a unique name of a job which is used in the log files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">command</code> — specifies the command to execute. The command can either be a command such as <code class="computeroutput">ls /proc >> /tmp/proc</code> or a command to execute a custom script.
+ </div></li></ul></div><div class="para">
+ Any lines that begin with a hash sign (#) are comments and are not processed.
+ </div><div class="section" title="16.1.2.1. Examples of Anacron Jobs" id="s3-anacron-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-anacron-examples">16.1.2.1. Examples of Anacron Jobs </h4></div></div></div><div class="para">
+ The following example shows a simple <code class="filename">/etc/anacrontab</code> file:
+ </div><pre class="screen">
+SHELL=/bin/sh
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+
+# the maximal random delay added to the base delay of the jobs
+RANDOM_DELAY=30
+# the jobs will be started during the following hours only
+START_HOURS_RANGE=16-20
+
+#period in days delay in minutes job-identifier command
+1 20 dailyjob nice run-parts /etc/cron.daily
+7 25 weeklyjob /etc/weeklyjob.bash
+ at monthly 45 monthlyjob ls /proc >> /tmp/proc
+</pre><div class="para">
+ All jobs defined in this <code class="filename">anacrontab</code> file are randomly delayed by 6-30 minutes and can be executed between 16:00 and 20:00. Thus, the first defined job will run anywhere between 16:26 and 16:50 every day. The command specified for this job will execute all present programs in the <code class="filename">/etc/cron.daily</code> directory (using the <code class="command">run-parts</code> script which takes a directory as a command-line argument and sequentially executes every program within that directory). The second specified job will be executed once a week and will execute the <code class="filename">weeklyjob.bash</code> script in the <code class="filename">/etc</code> directory. The third job is executed once a month and runs a command to write the contents of the <code class="filename">/proc</code> to the <code class="filename">/tmp/proc</code> file (e.g. <code class="computeroutput">ls /proc >> /tmp/proc</code>).
+ </div><div class="section" title="16.1.2.1.1. Disabling Anacron" id="s3-disabling-anacron"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="s3-disabling-anacron">16.1.2.1.1. Disabling Anacron</h5></div></div></div><div class="para">
+ In case your system is continuously on and you do not require anacron to run your scheduled jobs, you may uninstall the <code class="filename">cronie-anacron</code> package. Thus, you will be able to define jobs using crontabs only.
+ </div></div></div></div><div class="section" title="16.1.3. Configuring Cron Jobs" id="s2-configuring-cron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-configuring-cron-jobs">16.1.3. Configuring Cron Jobs</h3></div></div></div><a id="id745807" class="indexterm"></a><a id="id844656" class="indexterm"></a><a id="id844669" class="indexterm"></a><a id="id844683" class="indexterm"></a><div class="para">
+ The configuration file to configure cron jobs, <code class="filename">/etc/crontab</code> (only root is allowed to modify this file), contains the following lines:
+ </div><pre class="screen">
+SHELL=/bin/bash
+PATH=/sbin:/bin:/usr/sbin:/usr/bin
+MAILTO=root
+HOME=/
+# For details see man 4 crontabs
+# Example of job definition:
+# .---------------- minute (0 - 59)
+# | .------------- hour (0 - 23)
+# | | .---------- day of month (1 - 31)
+# | | | .------- month (1 - 12) OR jan,feb,mar,apr ...
+# | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat
+# | | | | |
+# * * * * * user command to be executed
+</pre><div class="para">
+ The first three lines contain the same variables as an <code class="filename">anacrontab</code> file, <code class="computeroutput">SHELL</code>, <code class="computeroutput">PATH</code> and <code class="computeroutput">MAILTO</code>. For more information about these variables, refer to <a class="xref" href="ch-Automated_Tasks.html#s2-configuring-anacron-jobs" title="16.1.2. Configuring Anacron Jobs">Section 16.1.2, “Configuring Anacron Jobs”</a>. The fourth line contains the <code class="computeroutput">HOME</code> variable. The <code class="computeroutput">HOME</code> variable can be used to set the home directory to use when executing commands or scripts.
+ </div><div class="para">
+ The rest of the lines in the <code class="filename">/etc/crontab</code> file represent scheduled jobs and have the following format:
+ </div><pre class="screen">
+minute hour day month day of week user command
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">minute</code> — any integer from 0 to 59
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">hour</code> — any integer from 0 to 23
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">day</code> — any integer from 1 to 31 (must be a valid day if a month is specified)
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">month</code> — any integer from 1 to 12 (or the short name of the month such as jan or feb)
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">day of week</code> — any integer from 0 to 7, where 0 or 7 represents Sunday (or the short name of the week such as sun or mon)
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">user</code> — specifies the user under which the jobs are run
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">command</code> — the command to execute (the command can either be a command such as <code class="command">ls /proc >> /tmp/proc</code> or the command to execute a custom script)
+ </div></li></ul></div><div class="para">
+ For any of the above values, an asterisk (*) can be used to specify all valid values. For example, an asterisk for the month value means execute the command every month within the constraints of the other values.
+ </div><div class="para">
+ A hyphen (-) between integers specifies a range of integers. For example, <strong class="userinput"><code>1-4</code></strong> means the integers 1, 2, 3, and 4.
+ </div><div class="para">
+ A list of values separated by commas (,) specifies a list. For example, <strong class="userinput"><code>3, 4, 6, 8</code></strong> indicates those four specific integers.
+ </div><div class="para">
+ The forward slash (/) can be used to specify step values. The value of an integer can be skipped within a range by following the range with <strong class="userinput"><code>/<<em class="replaceable"><code>integer</code></em>></code></strong>. For example, <strong class="userinput"><code>0-59/2</code></strong> can be used to define every other minute in the minute field. Step values can also be used with an asterisk. For instance, the value <strong class="userinput"><code>*/3</code></strong> can be used in the month field to run the task every third month.
+ </div><div class="para">
+ Any lines that begin with a hash sign (#) are comments and are not processed.
+ </div><div class="para">
+ Users other than root can configure cron tasks by using the <code class="command">crontab</code> utility. All user-defined crontabs are stored in the <code class="filename">/var/spool/cron/</code> directory and are executed using the usernames of the users that created them. To create a crontab as a user, login as that user and type the command <code class="command">crontab -e</code> to edit the user's crontab using the editor specified by the <code class="computeroutput">VISUAL</code> or <code class="computeroutput">EDITOR</code> environment variable. The file uses the same format as <code class="filename">/etc/crontab</code>. When the changes to the crontab are saved, the crontab is stored according to username and written to the file <code class="filename">/var/spool/cron/<em class="replaceable"><code>username</code></em> </code>. To list the contents of your own personal crontab file, use the <code class="command">crontab -l</code> command.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When using the <code class="command">crontab</code> utility, there is no need to specify a user when defining a job.
+ </div></div></div><div class="para">
+ The <code class="filename">/etc/cron.d/</code> directory contains files that have the same syntax as the <code class="filename">/etc/crontab</code> file. Only root is allowed to create and modify files in this directory.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The cron daemon checks the <code class="filename">/etc/anacrontab</code> file, the <code class="filename">/etc/crontab</code> file, the <code class="filename">/etc/cron.d/</code> directory, and the <code class="filename">/var/spool/cron/</code> directory every minute for any changes. If any changes are found, they are loaded into memory. Thus, the daemon does not need to be restarted if an anacrontab or a crontab file is changed.
+ </div></div></div></div><div class="section" title="16.1.4. Controlling Access to Cron" id="s2-autotasks-cron-access"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-cron-access">16.1.4. Controlling Access to Cron</h3></div></div></div><div class="para">
+ The <code class="filename">/etc/cron.allow</code> and <code class="filename">/etc/cron.deny</code> files are used to restrict access to cron. The format of both access control files is one username on each line. Whitespace is not permitted in either file. The cron daemon (<code class="command">crond</code>) does not have to be restarted if the access control files are modified. The access control files are checked each time a user tries to add or delete a cron job.
+ </div><div class="para">
+ The root user can always use cron, regardless of the usernames listed in the access control files.
+ </div><div class="para">
+ If the file <code class="filename">cron.allow</code> exists, only users listed in it are allowed to use cron, and the <code class="filename">cron.deny</code> file is ignored.
+ </div><div class="para">
+ If <code class="filename">cron.allow</code> does not exist, users listed in <code class="filename">cron.deny</code> are not allowed to use cron.
+ </div><div class="para">
+ Access can also be controlled through Pluggable Authentication Modules (PAM). These settings are stored in <code class="filename">/etc/security/access.conf</code>. For example, adding the following line in this file forbids creating crontabs for all users except the root user:
+ </div><pre class="screen">
+-:ALL EXCEPT root :cron
+</pre><div class="para">
+ The forbidden jobs are logged in an appropriate log file or, when using “crontab -e”, returned to the standard output. For more information, refer to <code class="filename">access.conf.5</code> (i.e. <code class="command">man 5 access.conf</code>).
+ </div></div><div class="section" title="16.1.5. Black/White Listing of Cron Jobs" id="s2-black-white-listing-of-cron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-black-white-listing-of-cron-jobs">16.1.5. Black/White Listing of Cron Jobs</h3></div></div></div><div class="para">
+ Black/White listing of jobs is used to omit parts of the defined jobs that do not need to be executed. When calling the <code class="command">run-parts</code> script on a cron folder, such as <code class="filename">/etc/cron.daily</code>, we can define which of the programs in this folder will not be executed by <code class="command">run-parts</code>.
+ </div><div class="para">
+ To define a black list, create a <code class="filename">jobs.deny</code> file in the folder that <code class="command">run-parts</code> will be executing from. For example, if we need to omit a particular program from /etc/cron.daily, then, a file <code class="filename">/etc/cron.daily/jobs.deny</code> has to be created. In this file, specify the names of the omitted programs from the same directory. These will not be executed when a command, such as <code class="computeroutput">run-parts /etc/cron.daily</code>, is executed by a specific job.
+ </div><div class="para">
+ To define a white list, create a <code class="filename">jobs.allow</code> file.
+ </div><div class="para">
+ The principles of <code class="filename">jobs.deny</code> and <code class="filename">jobs.allow</code> are the same as those of <code class="filename">cron.deny</code> and <code class="filename">cron.allow</code> described in section <a class="xref" href="ch-Automated_Tasks.html#s2-autotasks-cron-access" title="16.1.4. Controlling Access to Cron">Section 16.1.4, “Controlling Access to Cron”</a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-additional-resources.html"><strong>Prev</strong>15.7. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-autotasks-at-batch.html"><strong>Next</strong>16.2. At and Batch</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Controlling_Access_to_Services.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Controlling_Access_to_Services.html
new file mode 100644
index 0000000..1796f78
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Controlling_Access_to_Services.html
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 7. Controlling Access to Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /><link rel="prev" href="s1-dhcp-additional-resources.html" title="6.6. Additional Resources" /><link rel="next" href="s1-services-configuring.html" title="7.2. Configuring the Services" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp-additional-resources.html"><strong>Prev</strong>
</a></li><li class="next"><a accesskey="n" href="s1-services-configuring.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 7. Controlling Access to Services" id="ch-Controlling_Access_to_Services" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. Controlling Access to Services</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Controlling_Access_to_Services.html#s1-services-runlevels">7.1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="s1-services-configuring.html">7.2. Configuring the Services</a></span></dt><dt><span class="section"><a href="s1-services-running.html">7.3. Running the Services</a></span></dt><dt><span class="section"><a href="s1-services-additional-resources.html">7.4. Additional Resources</a></span></dt></dl></div><a id="id802739" class="indexterm"></a><div class="para">
+ Maintaining security on your system is extremely important, and one approach for this task is to manage access to system services carefully. Your system may need to provide open access to particular services (for example, <code class="command">httpd</code> if you are running a web server). However, if you do not need to provide a service, you should turn it off to minimize your exposure to possible bug exploits.
+ </div><div class="para">
+ This chapter explains the concept of runlevels, and describes how to set the default one. It also covers the setup of the services to be run in each of them using three different utilities: the <span class="application"><strong>Service Configuration</strong></span> graphical application, the <span class="application"><strong>ntsysv</strong></span> text user interface, and the <span class="application"><strong>chkconfig</strong></span> command line tool. Finally, it describes how to start, stop, and restart the services on a command line using the <span class="application"><strong>service</strong></span> command.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When you allow access for new services, always remember that both the firewall and <span class="application"><strong>SELinux</strong></span> need to be configured as well. One of the most common mistakes committed when configuring a new service is neglecting to implement the necessary firewall configuration and SELinux policies to allow access for it. Refer to the Fedora <em class="citetitle">Security Guide</em> (see <a class="xref" href="s1-services-additional-resources.html" title="7.4. Additional Resources">Section 7.4, “Additional Resources”</a>) for more information.
+ </div></div></div><div class="section" title="7.1. Configuring the Default Runlevel" id="s1-services-runlevels"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-services-runlevels">7.1. Configuring the Default Runlevel</h2></div></div></div><div class="para">
+ A <em class="firstterm">runlevel</em> is a state, or <em class="firstterm">mode</em>, defined by services that are meant to be run when this runlevel is selected. Seven numbered runlevels exist (indexed from <span class="emphasis"><em>0</em></span>):
+ </div><div class="table" title="Table 7.1. Runlevels in Fedora" id="table-services-runlevels"><h6>Table 7.1. Runlevels in Fedora</h6><div class="table-contents"><table summary="Runlevels in Fedora" border="1"><colgroup><col width="14%" /><col width="86%" /></colgroup><thead><tr><th>
+ Runlevel
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">0</code>
+ </td><td>
+ Used to halt the system. This runlevel is reserved and cannot be changed.
+ </td></tr><tr><td>
+ <code class="option">1</code>
+ </td><td>
+ Used to run in a single-user mode. This runlevel is reserved and cannot be changed.
+ </td></tr><tr><td>
+ <code class="option">2</code>
+ </td><td>
+ Not used by default. You are free to define it yourself.
+ </td></tr><tr><td>
+ <code class="option">3</code>
+ </td><td>
+ Used to run in a full multi-user mode with a command line user interface.
+ </td></tr><tr><td>
+ <code class="option">4</code>
+ </td><td>
+ Not used by default. You are free to define it yourself.
+ </td></tr><tr><td>
+ <code class="option">5</code>
+ </td><td>
+ Used to run in a full multi-user mode with a graphical user interface.
+ </td></tr><tr><td>
+ <code class="option">6</code>
+ </td><td>
+ Used to reboot the system. This runlevel is reserved and cannot be changed.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ To check in which runlevel you are operating, type the following:
+ </div><a id="id455111" class="indexterm"></a><a id="id455129" class="indexterm"></a><pre class="screen">~]$ <code class="command">runlevel</code>
+N 5</pre><div class="para">
+ The <code class="command">runlevel</code> command displays previous and current runlevel. In this case it is number <span class="emphasis"><em>5</em></span>, which means the system is running in a full multi-user mode with a graphical user interface.
+ </div><div class="para">
+ The default runlevel can be changed by modifying the <code class="filename">/etc/inittab</code> file, which contains a line near the end of the file similar to the following:
+ </div><pre class="screen">id:5:initdefault:</pre><div class="para">
+ In order to edit this file, you must have superuser privileges. To obtain them, log in as root by typing the following command:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="para">
+ Now open the file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>:
+ </div><pre class="screen">~]# <code class="command">nano /etc/inittab</code></pre><div class="para">
+ Then change the number in this line to the desired value and exit the editor. Note that the change does not take effect until you reboot the system.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp-additional-resources.html"><strong>Prev</strong>6.6. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-services-configuring.html"><strong>Next</strong>7.2. Configuring the Services</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Dynamic_Host_Configuration_Protocol_DHCP.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Dynamic_Host_Configuration_Protocol_DHCP.html
new file mode 100644
index 0000000..3ba4d25
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Dynamic_Host_Configuration_Protocol_DHCP.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 6. Dynamic Host Configuration Protocol (DHCP)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /><link rel="prev" href="sec-Configuring_Connection_Settings.html" title="5.3. Configuring Connection Settings" /><link rel="next" href="s1-dhcp-configuring-server.html" title="6.2. Configuring a DHCP Server" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Connection_Setting
s.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-dhcp-configuring-server.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)" id="ch-Dynamic_Host_Configuration_Protocol_DHCP" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 6. Dynamic Host Configuration Protocol (DHCP)</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html#s1-dhcp-why">6.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-server.html">6.2. Configuring a DHCP Server</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-client.html">6.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html">6.4. Configuring a Multihomed DHCP Server</a></span></dt><dt><span class="section"><a h
ref="s1-dhcp_for_ipv6_dhcpv6.html">6.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="s1-dhcp-additional-resources.html">6.6. Additional Resources</a></span></dt></dl></div><a id="id689413" class="indexterm"></a><a id="id604219" class="indexterm"></a><div class="para">
+ Dynamic Host Configuration Protocol (<acronym class="acronym">DHCP</acronym>) is a network protocol that automatically assigns TCP/IP information to client machines. Each DHCP client connects to the centrally located DHCP server, which returns that client's network configuration (including the IP address, gateway, and DNS servers).
+ </div><div class="section" title="6.1. Why Use DHCP?" id="s1-dhcp-why"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-dhcp-why">6.1. Why Use DHCP?</h2></div></div></div><a id="id543999" class="indexterm"></a><div class="para">
+ DHCP is useful for automatic configuration of client network interfaces. When configuring the client system, the administrator chooses DHCP instead of specifying an IP address, netmask, gateway, or DNS servers. The client retrieves this information from the DHCP server. DHCP is also useful if an administrator wants to change the IP addresses of a large number of systems. Instead of reconfiguring all the systems, he can just edit one DHCP configuration file on the server for the new set of IP addresses. If the DNS servers for an organization changes, the changes are made on the DHCP server, not on the DHCP clients. When the administrator restarts the network or reboots the clients, the changes will go into effect.
+ </div><div class="para">
+ If an organization has a functional DHCP server properly connected to a network, laptops and other mobile computer users can move these devices from office to office.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Connection_Settings.html"><strong>Prev</strong>5.3. Configuring Connection Settings</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-dhcp-configuring-server.html"><strong>Next</strong>6.2. Configuring a DHCP Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Gathering_System_Information.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Gathering_System_Information.html
new file mode 100644
index 0000000..5da0183
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Gathering_System_Information.html
@@ -0,0 +1,121 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 20. Gathering System Information</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-system-monitoring.html" title="Part IV. System Monitoring" /><link rel="prev" href="pt-system-monitoring.html" title="Part IV. System Monitoring" /><link rel="next" href="s1-sysinfo-memory-usage.html" title="20.2. Memory Usage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-system-monitoring.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n"
href="s1-sysinfo-memory-usage.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 20. Gathering System Information" id="ch-Gathering_System_Information" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. Gathering System Information</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">20.1. System Processes</a></span></dt><dt><span class="section"><a href="s1-sysinfo-memory-usage.html">20.2. Memory Usage</a></span></dt><dt><span class="section"><a href="s1-sysinfo-filesystems.html">20.3. File Systems</a></span></dt><dt><span class="section"><a href="s1-sysinfo-hardware.html">20.4. Hardware</a></span></dt><dt><span class="section"><a href="s1-sysinfo-additional-resources.html">20.5. Additional Resources</a></span></dt></dl></div><a id="id743251" class="indexterm"></a><a id="id543980" class="indexterm"></a><div class
="para">
+ Before you learn how to configure your system, you should learn how to gather essential system information. For example, you should know how to find the amount of free memory, the amount of available hard drive space, how your hard drive is partitioned, and what processes are running. This chapter discusses how to retrieve this type of information from your Fedora system using simple commands and a few simple programs.
+ </div><div class="section" title="20.1. System Processes" id="s1-sysinfo-system-processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-system-processes">20.1. System Processes</h2></div></div></div><a id="id732870" class="indexterm"></a><a id="id712129" class="indexterm"></a><a id="id484136" class="indexterm"></a><div class="para">
+ The <code class="command">ps ax</code> command displays a list of current system processes, including processes owned by other users. To display the owner alongside each process, use the <code class="command">ps aux</code> command. This list is a static list; in other words, it is a snapshot of what was running when you invoked the command. If you want a constantly updated list of running processes, use <code class="command">top</code> as described below.
+ </div><div class="para">
+ The <code class="command">ps</code> output can be long. To prevent it from scrolling off the screen, you can pipe it through less:
+ </div><pre class="screen">
+<code class="command">ps aux | less</code>
+</pre><div class="para">
+ You can use the <code class="command">ps</code> command in combination with the <code class="command">grep</code> command to see if a process is running. For example, to determine if <span class="application"><strong>Emacs</strong></span> is running, use the following command:
+ </div><pre class="screen">
+<code class="command">ps ax | grep emacs</code>
+</pre><a id="id784441" class="indexterm"></a><a id="id625096" class="indexterm"></a><div class="para">
+ The <code class="command">top</code> command displays currently running processes and important information about them including their memory and CPU usage. The list is both real-time and interactive. An example of output from the <code class="command">top</code> command is provided as follows:
+ </div><pre class="screen">top - 18:11:48 up 1 min, 1 user, load average: 0.68, 0.30, 0.11
+Tasks: 122 total, 1 running, 121 sleeping, 0 stopped, 0 zombie
+Cpu(s): 0.0%us, 0.5%sy, 0.0%ni, 93.4%id, 5.7%wa, 0.2%hi, 0.2%si, 0.0
+Mem: 501924k total, 376496k used, 125428k free, 29664k buffers
+Swap: 1015800k total, 0k used, 1015800k free, 189008k cached
+
+ PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
+ 1601 root 40 0 20172 1084 920 S 0.3 0.2 0:00.08 hald-addon-sto
+ 1998 silas 40 0 14984 1160 880 R 0.3 0.2 0:00.13 top
+ 1 root 40 0 19160 1412 1156 S 0.0 0.3 0:00.96 init
+ 2 root 40 0 0 0 0 S 0.0 0.0 0:00.01 kthreadd
+ 3 root RT 0 0 0 0 S 0.0 0.0 0:00.05 migration/0
+ 4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
+ 5 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
+ 6 root RT 0 0 0 0 S 0.0 0.0 0:00.04 migration/1
+ 7 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/1
+ 8 root RT 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/1
+ 9 root 20 0 0 0 0 S 0.0 0.0 0:00.00 events/0
+ 10 root 20 0 0 0 0 S 0.0 0.0 0:00.01 events/1
+ 11 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuset
+ 12 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre><div class="para">
+ To exit <code class="command">top</code>, press the <span class="keycap"><strong>q</strong></span> key.
+ </div><div class="para">
+ <a class="xref" href="ch-Gathering_System_Information.html#interactive-top-command" title="Table 20.1. Interactive top commands">Table 20.1, “Interactive <code class="command">top</code> commands”</a> contains useful interactive commands that you can use with <code class="command">top</code>. For more information, refer to the <code class="command">top</code>(1) manual page.
+ </div><div class="table" title="Table 20.1. Interactive top commands" id="interactive-top-command"><h6>Table 20.1. Interactive <code class="command">top</code> commands</h6><div class="table-contents"><table summary="Interactive top commands" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span class="keycap"><strong>Space</strong></span>
+ </td><td>
+ Immediately refresh the display
+ </td></tr><tr><td>
+ <span class="keycap"><strong>h</strong></span>
+ </td><td>
+ Display a help screen
+ </td></tr><tr><td>
+ <span class="keycap"><strong>k</strong></span>
+ </td><td>
+ Kill a process. You are prompted for the process ID and the signal to send to it.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>n</strong></span>
+ </td><td>
+ Change the number of processes displayed. You are prompted to enter the number.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>u</strong></span>
+ </td><td>
+ Sort by user.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>M</strong></span>
+ </td><td>
+ Sort by memory usage.
+ </td></tr><tr><td>
+ <span class="keycap"><strong>P</strong></span>
+ </td><td>
+ Sort by CPU usage.
+ </td></tr></tbody></table></div></div><br class="table-break" /><a id="id651014" class="indexterm"></a><a id="id651028" class="indexterm"></a><div class="para">
+ If you prefer a graphical interface for <code class="command">top</code>, you can use the <span class="application"><strong>GNOME System Monitor</strong></span>. To start it from the desktop, select <span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> or execute <code class="command">gnome-system-monitor</code> at a shell prompt. Select the <span class="guilabel"><strong>Processes</strong></span> tab.
+ </div><div class="para">
+ The <span class="application"><strong>GNOME System Monitor</strong></span> allows you to search for a process in the list of running processes. Using the <span class="application"><strong>GNOME System Monitor</strong></span>, you can also view all processes, your processes, or active processes.
+ </div><div class="para">
+ The <span class="guimenuitem"><strong>Edit</strong></span> menu item allows you to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Stop a process.
+ </div></li><li class="listitem"><div class="para">
+ Continue or start a process.
+ </div></li><li class="listitem"><div class="para">
+ End a processes.
+ </div></li><li class="listitem"><div class="para">
+ Kill a process.
+ </div></li><li class="listitem"><div class="para">
+ Change the priority of a selected process.
+ </div></li><li class="listitem"><div class="para">
+ Edit the System Monitor preferences. These include changing the interval seconds to refresh the list and selecting process fields to display in the System Monitor window.
+ </div></li></ul></div><div class="para">
+ The <span class="guimenuitem"><strong>View</strong></span> menu item allows you to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ View only active processes.
+ </div></li><li class="listitem"><div class="para">
+ View all processes.
+ </div></li><li class="listitem"><div class="para">
+ View my processes.
+ </div></li><li class="listitem"><div class="para">
+ View process dependencies.
+ </div></li><li class="listitem"><div class="para">
+ View a memory map of a selected process.
+ </div></li><li class="listitem"><div class="para">
+ View the files opened by the selected process.
+ </div></li><li class="listitem"><div class="para">
+ Refresh the list of processes.
+ </div></li></ul></div><div class="para">
+ To stop a process, select it and click <span class="guibutton"><strong>End Process</strong></span>. Alternatively you can also stop a process by selecting it, clicking <span class="guimenuitem"><strong>Edit</strong></span> on your menu and selecting <span class="guimenuitem"><strong>Stop Process</strong></span>.
+ </div><div class="para">
+ To sort the information by a specific column, click on the name of the column. This sorts the information by the selected column in ascending order. Click on the name of the column again to toggle the sort between ascending and descending order.
+ </div><div class="figure" title="Figure 20.1. GNOME System Monitor - Processes tab" id="fig-sysinfo-processes"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/gnome-system-monitor-processes.png" align="middle" alt="GNOME System Monitor - Processes tab" /><div class="longdesc"><div class="para">
+ Processes tab of the gnome-system-monitor
+ </div></div></div></div><h6>Figure 20.1. <span class="application">GNOME System Monitor - Processes tab</span> </h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-system-monitoring.html"><strong>Prev</strong>Part IV. System Monitoring</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-sysinfo-memory-usage.html"><strong>Next</strong>20.2. Memory Usage</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.html
new file mode 100644
index 0000000..80d98aa
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Graphical_Package_Management-sec-Additional_Resources.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.4. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-PackageKit.html" title="Chapter 2. PackageKit" /><link rel="prev" href="sec-PackageKit_Architecture.html" title="2.3. PackageKit Architecture" /><link rel="next" href="ch-RPM.html" title="Chapter 3. RPM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-PackageKit_Architecture.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-RPM.htm
l"><strong>Next</strong></a></li></ul><div class="section" title="2.4. Additional Resources" id="ch-Graphical_Package_Management-sec-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="ch-Graphical_Package_Management-sec-Additional_Resources">2.4. Additional Resources</h2></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <span class="application"><strong>PackageKit</strong></span> home page — <a href="http://www.packagekit.org/index.html">http://www.packagekit.org/index.html</a> </span></dt><dd><div class="para">
+ Information about and mailing lists for <span class="application"><strong>PackageKit</strong></span>.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="application"><strong>PackageKit</strong></span> FAQ — <a href="http://www.packagekit.org/pk-faq.html">http://www.packagekit.org/pk-faq.html</a> </span></dt><dd><div class="para">
+ An informative list of Frequently Asked Questions for the <span class="application"><strong>PackageKit</strong></span> software suite.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="application"><strong>PackageKit</strong></span> Feature Matrix — <a href="http://www.packagekit.org/pk-matrix.html">http://www.packagekit.org/pk-matrix.html</a> </span></dt><dd><div class="para">
+ Cross-reference <span class="application"><strong>PackageKit</strong></span>-provided features with the long list of package manager back ends.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-PackageKit_Architecture.html"><strong>Prev</strong>2.3. PackageKit Architecture</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-RPM.html"><strong>Next</strong>Chapter 3. RPM</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Keyboard_Configuration.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Keyboard_Configuration.html
new file mode 100644
index 0000000..ea99853
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Keyboard_Configuration.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 14. Keyboard Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-sysconfig.html" title="Part III. System Configuration" /><link rel="prev" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html" title="13.2.2. Network Time Protocol Setup" /><link rel="next" href="s1-keyboard-indicator.html" title="14.2. Adding the Keyboard Layout Indicator" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec
t-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-keyboard-indicator.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 14. Keyboard Configuration" id="ch-Keyboard_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 14. Keyboard Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Keyboard_Configuration.html#s1-keyboard-layout">14.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="s1-keyboard-indicator.html">14.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="s1-keyboard-break.html">14.3. Setting Up a Typing Break</a></span></dt></dl></div><a id="id520760" class="indexterm"></a><div class="para">
+ This chapter describes how to change the keyboard layout, as well as how to add the <span class="application"><strong>Keyboard Indicator</strong></span> applet to the panel. It also covers the option to enforce a typing break, and explains both advantages and disadvantages of doing so.
+ </div><div class="section" title="14.1. Changing the Keyboard Layout" id="s1-keyboard-layout"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-keyboard-layout">14.1. Changing the Keyboard Layout</h2></div></div></div><a id="id499694" class="indexterm"></a><a id="id711038" class="indexterm"></a><a id="id679443" class="indexterm"></a><div class="para">
+ The installation program allowed you to configure a keyboard layout for your system. However, the default settings may not always suit your current needs. To configure a different keyboard layout after the installation, use the <span class="application"><strong>Keyboard Preferences</strong></span> tool.
+ </div><div class="para">
+ To open <span class="application"><strong>Keyboard Layout Preferences</strong></span>, select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Keyboard</strong></span> from the panel, and click the <span class="guilabel"><strong>Layouts</strong></span> tab.
+ </div><div class="figure" title="Figure 14.1. Keybord Layout Preferences" id="fig-keyboard-layouts-layout"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-layouts.png" alt="Keybord Layout Preferences" /><div class="longdesc"><div class="para">
+ Keyboard Layout Preferences
+ </div></div></div></div><h6>Figure 14.1. Keybord Layout Preferences</h6></div><br class="figure-break" /><div class="para">
+ You will be presented with a list of available layouts. To add a new one, click the <span class="guibutton"><strong>Add...</strong></span> button below the list, and you will be prompted to chose which layout you want to add.
+ </div><div class="figure" title="Figure 14.2. Choosing a layout" id="fig-keyboard-layouts-layout-new"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-layouts-new.png" alt="Choosing a layout" /><div class="longdesc"><div class="para">
+ Choosing a layout
+ </div></div></div></div><h6>Figure 14.2. Choosing a layout</h6></div><br class="figure-break" /><div class="para">
+ Currently, there are two ways how to chose the keyboard layout: you can either find it by the country it is associated with (the <span class="guilabel"><strong>By country</strong></span> tab), or you can select it by the language (the <span class="guilabel"><strong>By language</strong></span> tab). In either case, first select the desired country or language from the <span class="guilabel"><strong>Country</strong></span> or <span class="guilabel"><strong>Language</strong></span> pulldown menu, then specify the variant from the <span class="guilabel"><strong>Variants</strong></span> menu. The preview of the layout changes immediately. To confirm the selection, click <span class="guibutton"><strong>Add</strong></span>.
+ </div><div class="figure" title="Figure 14.3. Selecting the default layout" id="fig-keyboard-layouts-default"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-layouts-default.png" alt="Selecting the default layout" /><div class="longdesc"><div class="para">
+ Selecting the default layout
+ </div></div></div></div><h6>Figure 14.3. Selecting the default layout</h6></div><br class="figure-break" /><div class="para">
+ The layout should appear in the list. To make it the default, select the radio button next to its name. The changes take effect immediately. Note that there is a text-entry field at the bottom of the window where you can safely test your settings. Once you are satisfied, click <span class="guibutton"><strong>Close</strong></span> to close the window.
+ </div><div class="figure" title="Figure 14.4. Testing the layout" id="fig-keyboard-layouts-layout-test"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-layouts-test.png" alt="Testing the layout" /><div class="longdesc"><div class="para">
+ Testing the layout
+ </div></div></div></div><h6>Figure 14.4. Testing the layout</h6></div><br class="figure-break" /><div class="note" title="Suggestion: Disable Separate Layout for Each Window"><div class="admonition_header"><h2>Suggestion: Disable Separate Layout for Each Window</h2></div><div class="admonition"><div class="para">
+ By default, changing the keyboard layout affects the active window only. This means that if you change the layout and switch to another window, this window will use the old one, which might be confusing. To turn this unfortunate behavior off, unselect the <span class="guilabel"><strong>Separate layout for each window</strong></span> check box.
+ </div><div class="mediaobject" align="center"><img src="images/keyboard-configuration-layouts-separate.png" align="middle" /><div class="longdesc"><div class="para">
+ Disabling separate layout for each window
+ </div></div></div><div class="para">
+ Doing this has its drawbacks though, as you will no longer be able to chose the default layout by selecting the radio button as shown in <a class="xref" href="ch-Keyboard_Configuration.html#fig-keyboard-layouts-default" title="Figure 14.3. Selecting the default layout">Figure 14.3, “Selecting the default layout”</a>. To make the layout the default, simply drag it at the beginning of the list.
+ </div><div class="mediaobject" align="center"><img src="images/keyboard-configuration-layouts-prioritize.png" align="middle" /><div class="longdesc"><div class="para">
+ Changing the order of layouts
+ </div></div></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html"><strong>Prev</strong>13.2.2. Network Time Protocol Setup</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-keyboard-indicator.html"><strong>Next</strong>14.2. Adding the Keyboard Layout Indicator</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Log_Files.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Log_Files.html
new file mode 100644
index 0000000..f336812
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Log_Files.html
@@ -0,0 +1,146 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 17. Log Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-sysconfig.html" title="Part III. System Configuration" /><link rel="prev" href="s1-autotasks-additional-resources.html" title="16.3. Additional Resources" /><link rel="next" href="s1-rsyslog-performance.html" title="17.2. rsyslog Performance" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-autotasks-additional-resources.html"><strong>Prev</strong></a></li><li cl
ass="next"><a accesskey="n" href="s1-rsyslog-performance.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 17. Log Files" id="ch-Log_Files" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 17. Log Files</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Log_Files.html#s1-configuring-rsyslog">17.1. Configuring <code class="command">rsyslog</code> </a></span></dt><dt><span class="section"><a href="s1-rsyslog-performance.html">17.2. <code class="command">rsyslog</code> Performance</a></span></dt><dt><span class="section"><a href="s1-logfiles-locating.html">17.3. Locating Log Files</a></span></dt><dt><span class="section"><a href="s1-logfiles-viewing.html">17.4. Viewing Log Files</a></span></dt><dt><span class="section"><a href="s1-logfiles-adding.html">17.5. Adding a Log File</a></span></dt><dt><span class="section"><a href="s1-logfiles-examining.html">17.6. Monitoring Log Files
</a></span></dt><dt><span class="section"><a href="s1-log-files-additional-resources.html">17.7. Additional Resources</a></span></dt></dl></div><a id="id519064" class="indexterm"></a><a id="id404105" class="indexterm"></a><div class="para">
+ <em class="firstterm">Log files</em> are files that contain messages about the system, including the kernel, services, and applications running on it. There are different log files for different information. For example, there is a default system log file, a log file just for security messages, and a log file for cron tasks.
+ </div><div class="para">
+ Log files can be very useful when trying to troubleshoot a problem with the system such as trying to load a kernel driver or when looking for unauthorized log in attempts to the system. This chapter discusses where to find log files, how to view log files, and what to look for in log files.
+ </div><a id="id833858" class="indexterm"></a><a id="id448684" class="indexterm"></a><div class="para">
+ Some log files are controlled by a daemon called <code class="systemitem">rsyslogd</code>. A list of log messages maintained by <code class="systemitem">rsyslogd</code> can be found in the <code class="filename">/etc/rsyslog.conf</code> configuration file.
+ </div><div class="para">
+ <code class="command">rsyslog</code> replaced <code class="command">syslogd</code> as the default program for forwarding syslog messages over the network. <code class="command">rsyslog</code> uses the basic <code class="command">syslog</code> protocol and extends its functionality with enhanced filtering, encryption protected relaying of messages, various configuration options, or support for transportation via the <code class="systemitem">TCP</code> or <code class="systemitem">UDP</code> protocols.
+ </div><div class="section" title="17.1. Configuring rsyslog" id="s1-configuring-rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-configuring-rsyslog">17.1. Configuring <code class="command">rsyslog</code> </h2></div></div></div><div class="para">
+ The main configuration file for <code class="command">rsyslog</code> is <code class="filename">/etc/rsyslog.conf</code>. It is essentially divided in the following parts:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Modules
+ </div></li><li class="listitem"><div class="para">
+ Global directives
+ </div></li><li class="listitem"><div class="para">
+ Rules
+ </div></li><li class="listitem"><div class="para">
+ Templates
+ </div></li><li class="listitem"><div class="para">
+ Filter conditions
+ </div></li><li class="listitem"><div class="para">
+ Output channels
+ </div></li></ul></div><div class="para">
+ Each of these segments of the <code class="filename">/etc/rsyslog.conf</code> configuration file is described in the sections below.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ In your <code class="filename">/etc/rsyslog.conf</code> configuration file, any empty lines or any text following a hash sign (#) are comments and are not processed.
+ </div></div></div><div class="section" title="17.1.1. Modules" id="s2-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-modules">17.1.1. Modules</h3></div></div></div><div class="para">
+ Due to its modular design, <code class="command">rsyslog</code> offers a variety of <em class="firstterm">modules</em> which provide dynamic functionality. Note that modules can be written by third parties. Essentially, modules are comprised of various configuration directives that become available when a module is loaded. To load a module, use the following syntax:
+ </div><pre class="screen">
+$ModLoad <em class="replaceable"><code><MODULE></code></em>
+</pre><div class="para">
+ where <em class="replaceable"><code><MODULE></code></em> represents your desired module. For example, if you want to load the <code class="literal">Text File Input Module</code> (<code class="command">imfile</code> — enables <code class="command">rsyslog</code> to convert any standard text files into a syslog messages), specify the following line in your <code class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad imfile
+</pre><div class="para">
+ <code class="command">rsyslog</code> offers a number of modules which are split into these main categories:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Input Modules — Input modules gather messages from various sources. The name of an input module always starts with the <code class="literal">im</code> prefix, such as <code class="command">imfile</code>, <code class="command">imrelp</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Output Modules — Output modules process messages into different formats or perform various actions on them. The name of an output module always starts with the <code class="literal">om</code> prefix, such as <code class="command">omsnmp</code>, <code class="command">omrelp</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Filter Modules — Filter modules provide the ability to filter messages according to specified rules. The name of a filter module always starts with the <code class="literal">fm</code> prefix.
+ </div></li><li class="listitem"><div class="para">
+ Parser Modules — Parser modules use the message parsers to parse message content of any received messages. The name of a parser module always starts with the <code class="literal">pm</code> prefix, such as <code class="command">pmrfc5424</code>, <code class="command">pmrfc3164</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Message Modification Modules — Message modification modules change the content of asyslog message. The message modification modules only differ in their implementation from the output and filter modules but share the same interface.
+ </div></li><li class="listitem"><div class="para">
+ String Generator Modules — String generator modules generate strings based on the message content and strongly cooperate with the template feature provided by <code class="command">rsyslog</code>. For more information on templates, refer to . The name of a string generator module always starts with the <code class="literal">sm</code> prefix, such as <code class="command">smfile</code>, <code class="command">smtradfile</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Library Modules — Library modules provide the ability to load and handle other loadable modules. These modules are loaded automatically by <code class="command">rsyslog</code> when needed and cannot be configured by the user.
+ </div></li></ul></div><div class="para">
+ A comprehensive list of all available modules and their detailed description can be found at <a href="http://www.rsyslog.com/doc/rsyslog_conf_modules.html/">http://www.rsyslog.com/doc/rsyslog_conf_modules.html</a>
+ </div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Note that when <code class="command">rsyslog</code> loads any modules, it provides them with access to some of its functions and data. This poses a possible security threat. To minimize security risks, use trustworthy modules only.
+ </div></div></div></div><div class="section" title="17.1.2. Global Directives" id="s2-global-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-global-directives">17.1.2. Global Directives</h3></div></div></div><div class="para">
+ <em class="firstterm">Global directives</em> specify configuration options that apply to the <code class="systemitem">rsyslogd</code> daemon. All of the global directives must start with a dollar sign (<code class="literal">$</code>). Only one directive can be specified per line. The following is an example of a global directive that specifies the maximum size of the syslog message queue:
+ </div><pre class="screen">
+$MainMsgQueueSize
+</pre><div class="para">
+ The default size defined for this directive (<code class="constant">10,000</code> messages) can be overridden by specifying a different value.
+ </div><div class="para">
+ A comprehensive list of all available configuration directives and their detailed description can be found in <code class="filename">/usr/share/doc/rsyslog-4.4.2/rsyslog_conf_global.html</code> or online at <a href="http://www.rsyslog.com/doc/rsyslog_conf_global.html">http://www.rsyslog.com/doc/rsyslog_conf_global.html</a>.
+ </div></div><div class="section" title="17.1.3. Rules" id="s2-rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rules">17.1.3. Rules</h3></div></div></div><div class="para">
+ A rule specifies the cooperation of a <em class="firstterm">selector</em> with an <em class="firstterm">action</em>. To define a rule in your <code class="filename">/etc/rsyslog.conf</code> configuration file, define both, a selector and an action, on one line and separate them with one or more spaces or tabs. For more information on selectors, refer to <a class="xref" href="ch-Log_Files.html#s3-selectors" title="17.1.3.1. Selectors">Section 17.1.3.1, “Selectors”</a> and for information on actions, refer to <a class="xref" href="ch-Log_Files.html#s3-actions" title="17.1.3.2. Actions">Section 17.1.3.2, “Actions”</a>.
+ </div><div class="section" title="17.1.3.1. Selectors" id="s3-selectors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-selectors">17.1.3.1. Selectors</h4></div></div></div><div class="para">
+ Selectors filter syslog messages based on two conditions: <em class="firstterm">facility</em> and <em class="firstterm">priority</em>. The following is an example of a selector:
+ </div><pre class="screen">
+<em class="replaceable"><code><FACILITY></code></em>.<em class="replaceable"><code><PRIORITY></code></em>
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="replaceable"><code><FACILITY></code></em> specifies the subsystem that produces a specific syslog message. For example, the <code class="command">mail</code> subsystem handles all mail related syslog messages. <em class="replaceable"><code><FACILITY></code></em> can be represented by one of these keywords: <code class="command">auth</code>, <code class="command">authpriv</code>, <code class="command">cron</code>, <code class="command">daemon</code>, <code class="command">kern</code>, <code class="command">lpr</code>, <code class="command">mail</code>, <code class="command">news</code>, <code class="command">syslog</code>, <code class="command">user</code>, <code class="command">uucp</code>, and <code class="command">local0</code> through <code class="command">local7</code>.
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code><PRIORITY></code></em> specifies a priority of a syslog message. <em class="replaceable"><code><PRIORITY></code></em> can be represented by one of these keywords: <code class="command">debug</code>, <code class="command">info</code>, <code class="command">notice</code>, <code class="command">warning</code>, <code class="command">err</code>, <code class="command">crit</code>, <code class="command">alert</code>, and <code class="command">emerg</code>.
+ </div><div class="para">
+ By preceding any priority with an equal sign (<code class="literal">=</code>), you specify that only syslog messages with that priority will be selected. All other priorities will be ignored. Conversely, preceding a priority with an exclamation mark (<code class="literal">!</code>) selects all syslog messages but those with the defined priority. By not using either of these two extensions, you specify a selection of syslog messages with the defined priority and higher.
+ </div></li></ul></div><div class="para">
+ In addition to the keywords specified above, you may also use an asterisk (<code class="literal">*</code>) to define all facilities or priorities (depending on where you place the asterisk, before or after the dot). Specifying the keyword <code class="literal">none</code> serves for facilities with no given priorities.
+ </div><div class="para">
+ To define multiple facilities and priorities, simply separate them with a comma (<code class="literal">,</code>). To define multiple selectors on one line, separate them with a semi-colon (<code class="literal">;</code>).
+ </div><div class="para">
+ The following are a few examples of simple selectors:
+ </div><pre class="screen">
+kern.* # Selects all kernel syslog messages with any priority
+</pre><pre class="screen">
+mail.crit # Selects all mail syslog messages with priority <code class="command">crit</code> and higher.
+</pre><pre class="screen">
+cron.!info,!debug # Selects all cron syslog messages except those with the <code class="command">info</code> or <code class="command">debug</code> priority.
+</pre></div><div class="section" title="17.1.3.2. Actions" id="s3-actions"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-actions">17.1.3.2. Actions</h4></div></div></div><div class="para">
+ Actions specify what is to be done with the messages filtered out by the defined selector. The following are some of the actions you can define in your rule:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Syslog message placement</span></dt><dd><div class="para">
+ The majority of actions specify to which log file a syslog message is saved. This is done by specifying a file path after your already defined selector. The following is a rule comprised of a selector that selects all <span class="application"><strong>cron</strong></span> syslog messages and an action that saves them into the <code class="filename">/var/log/cron</code> log file:
+ </div><pre class="screen">cron.* /var/log/cron
+</pre><div class="para">
+ Use a dash mark (<code class="literal">-</code>) as a prefix of the file path you specified if you want to omit syncing the desired log file after every syslog message is generated.
+ </div><div class="para">
+ Your specified file path can be either static or dynamic. Static files are represented by a simple file path as was shown in the example above. Dynamic files are represented by a template and a question mark (<code class="literal">?</code>) prefix. For more information on templates, refer to <a class="xref" href="ch-Log_Files.html#s2-templates" title="17.1.4. Templates">Section 17.1.4, “Templates”</a>.
+ </div></dd><dt class="varlistentry"><span class="term">Sending syslog messages over the network</span></dt><dd><div class="para">
+ <code class="command">rsyslog</code> allows you to send and receive syslog messages over the network. This feature allows to administer syslog messages of multiple hosts on one machine. To forward syslog messages to a remote machine, use the following syntax:
+ </div><pre class="screen">@[<span class="optional">(<em class="replaceable"><code><OPTION></code></em>,<em class="replaceable"><code><MORE OPTIONS></code></em>)</span>]<em class="replaceable"><code><HOST></code></em>:[<span class="optional"><em class="replaceable"><code><PORT></code></em></span>]
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The at sign (<code class="literal">@</code>) indicates that the syslog messages are forwarded to a host using the <code class="systemitem">UDP</code> protocol. To use the <code class="systemitem">TCP</code> protocol, use two at signs with no space between them (<code class="literal">@@</code>).
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code><OPTION></code></em> and <em class="replaceable"><code><MORE OPTIONS></code></em> attributes can be replaced with an option such as <code class="command">z<em class="replaceable"><code><NUMBER></code></em></code>. This option enables <span class="application"><strong>zlib</strong></span> compression for syslog messages; the <em class="replaceable"><code><NUMBER></code></em> attribute specifies the level of compression.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code><HOST></code></em> attribute specifies the host which receives the selected syslog messages.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code><PORT></code></em> attribute specifies the host machine's port.
+ </div></li></ul></div><div class="para">
+ When specifying an <code class="systemitem">IPv6</code> address as the hoset, enclose the address in square brackets (<code class="literal">[</code>, <code class="literal">]</code>).
+ </div><div class="para">
+ The following are some examples of actions that forward syslog messages over the network (note that all actions are preceded with a selector that selects all messages with any priority):
+ </div><pre class="screen">*.* @192.168.0.1 # Forwards messages to 192.168.0.1 via the <code class="systemitem">UDP</code> protocol</pre><pre class="screen">*.* @@example.com:18 # Forwards messages to "example.com" using port 18 and the <code class="systemitem">TCP</code> protocol</pre><pre class="screen">
+*.* @(z9)[2001::1] # Compresses messages with <span class="application"><strong>zlib</strong></span> (level 9 compression)
+ # and forwards them to 2001::1 using the <code class="systemitem">UDP</code> protocol</pre></dd><dt class="varlistentry"><span class="term">Sending syslog messages to specific users</span></dt><dd><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> can send syslog messages to specific users by simply specifying a username of the user you wish to send the messages to. To specify more than one user, separate each username with a comma (<code class="literal">,</code>). To send messages to every user that is currently logged on, use an asterisk (<code class="literal">*</code>).
+ </div></dd><dt class="varlistentry"><span class="term">Discarding syslog messages</span></dt><dd><div class="para">
+ To discard your selected messages, use the tilde character (<code class="literal">~</code>). The following rule discards any cron syslog messages:
+ </div><pre class="screen">cron.* ~</pre></dd></dl></div><div class="para">
+
+ </div><div class="para">
+ Note that any action can be followed by a template that formats the message. To specify a template, suffix an action with a semicolon (<code class="literal">;</code>) and specify the name of the template.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ A template must be defined before it is used in an action.
+ </div></div></div><div class="para">
+ For more information on templates, refer to <a class="xref" href="ch-Log_Files.html#s2-templates" title="17.1.4. Templates">Section 17.1.4, “Templates”</a>.
+ </div><div class="para">
+ For more information on various <span class="application"><strong>rsyslog</strong></span> actions, refer to <code class="filename">/usr/share/doc/rsyslog-4.4.2/rsyslog_conf_actions.html</code>.
+ </div></div></div><div class="section" title="17.1.4. Templates" id="s2-templates"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-templates">17.1.4. Templates</h3></div></div></div><div class="para">
+
+ </div></div><div class="section" title="17.1.5. Filter Conditions" id="s2-filter-conditions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-filter-conditions">17.1.5. Filter Conditions</h3></div></div></div><div class="para">
+
+ </div></div><div class="section" title="17.1.6. Output Channels" id="s2-output-channels"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-output-channels">17.1.6. Output Channels</h3></div></div></div><div class="para">
+
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-autotasks-additional-resources.html"><strong>Prev</strong>16.3. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-rsyslog-performance.html"><strong>Next</strong>17.2. rsyslog Performance</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Manually_Upgrading_the_Kernel.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Manually_Upgrading_the_Kernel.html
new file mode 100644
index 0000000..e713faf
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Manually_Upgrading_the_Kernel.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 23. Manually Upgrading the Kernel</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-kernel-configuration.html" title="Part V. Kernel, Module and Driver Configuration" /><link rel="prev" href="s1-kernel-modules-additional-resources.html" title="22.8. Additional Resources" /><link rel="next" href="s1-kernel-preparing.html" title="23.2. Preparing to Upgrade" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-modules-additional-resources.html">
<strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kernel-preparing.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 23. Manually Upgrading the Kernel" id="ch-Manually_Upgrading_the_Kernel" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 23. Manually Upgrading the Kernel</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">23.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">23.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">23.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">23.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">23.5. Verifying the Initial
RAM Disk Image</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">23.6. Verifying the Boot Loader</a></span></dt></dl></div><a id="id706026" class="indexterm"></a><a id="id838169" class="indexterm"></a><a id="id837725" class="indexterm"></a><a id="id781948" class="indexterm"></a><div class="para">
+ The Fedora kernel is custom-built by the Fedora kernel team to ensure its integrity and compatibility with supported hardware. Before Red Hat releases a kernel, it must first pass a rigorous set of quality assurance tests.
+ </div><div class="para">
+ Fedora kernels are packaged in the RPM format so that they are easy to upgrade and verify using the <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span> package managers. <span class="application"><strong>PackageKit</strong></span> automatically queries the Red Hat Network servers and informs you of packages with available updates, including kernel packages.
+ </div><div class="para">
+ This chapter is therefore <span class="emphasis"><em>only</em></span> useful for users who need to manually update a kernel package using the <code class="command">rpm</code> command instead of <code class="command">yum</code>.
+ </div><a id="id569658" class="indexterm"></a><a id="id437436" class="indexterm"></a><div class="warning" title="Use Yum to Install Kernels Whenever Possible"><div class="admonition_header"><h2>Use Yum to Install Kernels Whenever Possible</h2></div><div class="admonition"><div class="para">
+ Whenever possible, use either the <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span> package manager to install a new kernel because they always <span class="emphasis"><em>install</em></span> a new kernel instead of replacing the current one, which could potentially leave your system unable to boot.
+ </div></div></div><div class="warning" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Building a custom kernel is not supported by the Red Hat Global Services Support team, and therefore is not explored in this manual.
+ </div></div></div><a id="id448198" class="indexterm"></a><div class="para">
+ For more information on installing kernel packages with <span class="application"><strong>Yum</strong></span>, refer to <a class="xref" href="ch-yum.html#sec-Updating_Packages" title="1.1.2. Updating Packages">Section 1.1.2, “Updating Packages”</a>.
+ </div><div class="section" title="23.1. Overview of Kernel Packages" id="s1-kernel-packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-packages">23.1. Overview of Kernel Packages</h2></div></div></div><a id="id523660" class="indexterm"></a><a id="id523672" class="indexterm"></a><a id="id523688" class="indexterm"></a><a id="id523703" class="indexterm"></a><a id="id523491" class="indexterm"></a><a id="id523507" class="indexterm"></a><a id="id523523" class="indexterm"></a><a id="id523539" class="indexterm"></a><a id="id799074" class="indexterm"></a><a id="id799090" class="indexterm"></a><a id="id799106" class="indexterm"></a><a id="id799122" class="indexterm"></a><a id="id799138" class="indexterm"></a><div class="para">
+ Fedora contains the following kernel packages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="package">kernel</span> — Contains the kernel for single, multicore and multiprocessor systems.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-debug</span> — Contains a kernel with numerous debugging options enabled for kernel diagnosis, at the expense of reduced performance.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-devel</span> — Contains the kernel headers and makefiles sufficient to build modules against the <span class="package">kernel</span> package.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-debug-devel</span> — Contains the development version of the kernel with numerous debugging options enabled for kernel diagnosis, at the expense of reduced performance.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-doc</span> — Documentation files from the kernel source. Various portions of the Linux kernel and the device drivers shipped with it are documented in these files. Installation of this package provides a reference to the options that can be passed to Linux kernel modules at load time.
+ </div><div class="para">
+ By default, these files are placed in the <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-headers</span> — Includes the C header files that specify the interface between the Linux kernel and user-space libraries and programs. The header files define structures and constants that are needed for building most standard programs.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-firmware</span> — Contains all of the firmware files that are required by various devices to operate.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">perf</span> — This package contains supporting scripts and documentation for the <span class="application"><strong>perf</strong></span> tool shipped in each kernel image subpackage.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-modules-additional-resources.html"><strong>Prev</strong>22.8. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kernel-preparing.html"><strong>Next</strong>23.2. Preparing to Upgrade</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Network_Configuration.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Network_Configuration.html
new file mode 100644
index 0000000..1a2145e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Network_Configuration.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 5. Network Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /><link rel="prev" href="s1-networkscripts-resources.html" title="4.6. Additional Resources" /><link rel="next" href="sec-Interacting_with_NetworkManager.html" title="5.2. Interacting with NetworkManager" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-resources.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Interacting_with_NetworkManager.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 5. Network Configuration" id="ch-Network_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 5. Network Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Network_Configuration.html#sec-The_NetworkManager_Daemon">5.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html">5.2. Interacting with NetworkManager</a></span></dt><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html">5.3. Configuring Connection Settings</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> is a dynamic network control and configuration system that attempts to keep network devices and connections up and active when they are available. <span class="application"><strong>NetworkManager</strong></span> consists of a core daemon, a GNOME Notification Area applet that provides network status information, and graphical configuration tools that can create, edit and remove connections and interfaces. <span class="application"><strong>NetworkManager</strong></span> can be used to configure the following types of connections: Ethernet, wireless, mobile broadband (such as cellular 3G), and <code class="systemitem">DSL</code> and <code class="systemitem">PPPoE</code> (Point-to-Point over Ethernet). In addition, <span class="application"><strong>NetworkManager</strong></span> allows for the configuration of network aliases, static routes, DNS information and VPN connections, as well as many connection-specifi
c parameters. Finally, <span class="application"><strong>NetworkManager</strong></span> provides a rich API via D-Bus which allows applications to query and control network configuration and state.
+ </div><div class="para">
+ Previous versions of Fedora shipped with the <span class="application"><strong>Network Administration Tool</strong></span>, which was commonly known as <code class="command">system-config-network</code> after its command line invocation. In Fedora 14, <span class="application"><strong>NetworkManager</strong></span> replaces the former <span class="application"><strong>Network Administration Tool</strong></span> while providing enhanced functionality, such as user-specific and mobile broadband configuration. It is also possible to configure the network in Fedora 14 by editing interface configuration files; refer to <a class="xref" href="ch-Network_Interfaces.html" title="Chapter 4. Network Interfaces">Chapter 4, <i>Network Interfaces</i></a> for more information.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> may be installed by default on Fedora. To ensure that it is, first run the following command as the root user:
+ </div><pre class="screen">~]# <code class="command">yum install NetworkManager</code>
+</pre><div class="section" title="5.1. The NetworkManager Daemon" id="sec-The_NetworkManager_Daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-The_NetworkManager_Daemon">5.1. The NetworkManager Daemon</h2></div></div></div><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> daemon runs with root privileges and is usually configured to start up at boot time. You can determine whether the <span class="application"><strong>NetworkManager</strong></span> daemon is running by entering this command as root:
+ </div><pre class="screen">~]# <code class="command">service NetworkManager status</code>
+NetworkManager (pid 1527) is running...
+</pre><div class="para">
+ The <code class="command">service</code> command will report <code class="computeroutput">NetworkManager is stopped</code> if the <span class="application"><strong>NetworkManager</strong></span> service is not running. To start it for the current session:
+ </div><pre class="screen">~]# <code class="command">service NetworkManager start</code>
+</pre><div class="para">
+ Run the <code class="command">chkconfig</code> command to ensure that <span class="application"><strong>NetworkManager</strong></span> starts up every time the system boots:
+ </div><pre class="screen">~]# <code class="command">chkconfig NetworkManager on</code>
+</pre><div class="para">
+ For more information on starting, stopping and managing services and runlevels, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-resources.html"><strong>Prev</strong>4.6. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Interacting_with_NetworkManager.html"><strong>Next</strong>5.2. Interacting with NetworkManager</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Network_Interfaces.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Network_Interfaces.html
new file mode 100644
index 0000000..584cc78
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Network_Interfaces.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 4. Network Interfaces</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /><link rel="prev" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /><link rel="next" href="s1-networkscripts-interfaces.html" title="4.2. Interface Configuration Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-network-related-config.html"><st
rong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-interfaces.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 4. Network Interfaces" id="ch-Network_Interfaces" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Network Interfaces</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Network_Interfaces.html#s1-networkscripts-files">4.1. Network Configuration Files</a></span></dt><dt><span class="section"><a href="s1-networkscripts-interfaces.html">4.2. Interface Configuration Files</a></span></dt><dt><span class="section"><a href="s1-networkscripts-control.html">4.3. Interface Control Scripts</a></span></dt><dt><span class="section"><a href="s1-networkscripts-static-routes.html">4.4. Configuring Static Routes</a></span></dt><dt><span class="section"><a href="s1-networkscripts-functions.html">4.5. Network Function Files</a></span></dt><dt><span
class="section"><a href="s1-networkscripts-resources.html">4.6. Additional Resources</a></span></dt></dl></div><a id="id540069" class="indexterm"></a><a id="id543820" class="indexterm"></a><div class="para">
+ Under Fedora, all network communications occur between configured software <em class="firstterm">interfaces</em> and <em class="firstterm">physical networking devices</em> connected to the system.
+ </div><div class="para">
+ The configuration files for network interfaces are located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory. The scripts used to activate and deactivate these network interfaces are also located here. Although the number and type of interface files can differ from system to system, there are three categories of files that exist in this directory:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <em class="firstterm">Interface configuration files</em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Interface control scripts</em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="firstterm">Network function files</em>
+ </div></li></ol></div><div class="para">
+ The files in each of these categories work together to enable various network devices.
+ </div><div class="para">
+ This chapter explores the relationship between these files and how they are used.
+ </div><div class="section" title="4.1. Network Configuration Files" id="s1-networkscripts-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-files">4.1. Network Configuration Files</h2></div></div></div><a id="id738799" class="indexterm"></a><div class="para">
+ Before delving into the interface configuration files, let us first itemize the primary configuration files used in network configuration. Understanding the role these files play in setting up the network stack can be helpful when customizing a Fedora system.
+ </div><div class="para">
+ The primary network configuration files are as follows:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">/etc/hosts</code> </span></dt><dd><div class="para">
+ The main purpose of this file is to resolve hostnames that cannot be resolved any other way. It can also be used to resolve hostnames on small networks with no DNS server. Regardless of the type of network the computer is on, this file should contain a line specifying the IP address of the loopback device (<code class="command">127.0.0.1</code>) as <code class="command">localhost.localdomain</code>. For more information, refer to the <code class="filename">hosts</code> man page.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/resolv.conf</code> </span></dt><dd><div class="para">
+ This file specifies the IP addresses of DNS servers and the search domain. Unless configured to do otherwise, the network initialization scripts populate this file. For more information about this file, refer to the <code class="filename">resolv.conf</code> man page.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/network</code> </span></dt><dd><div class="para">
+ This file specifies routing and host information for all network interfaces. For more information about this file and the directives it accepts, refer to <a class="xref" href="ch-The_sysconfig_Directory.html#s2-sysconfig-network" title="18.1.13. /etc/sysconfig/network">Section 18.1.13, “ <code class="filename">/etc/sysconfig/network</code> ”</a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/network-scripts/ifcfg-<em class="replaceable"><code><interface-name></code></em> </code> </span></dt><dd><div class="para">
+ For each network interface, there is a corresponding interface configuration script. Each of these files provide information specific to a particular network interface. Refer to <a class="xref" href="s1-networkscripts-interfaces.html" title="4.2. Interface Configuration Files">Section 4.2, “Interface Configuration Files”</a> for more information on this type of file and the directives it accepts.
+ </div></dd></dl></div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The <code class="filename">/etc/sysconfig/networking/</code> directory is used by the <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>) and its contents should <span class="bold bold"><strong>not</strong></span> be edited manually. Using only one method for network configuration is strongly encouraged, due to the risk of configuration deletion.
+ </div><div class="para">
+ For more information about configuring network interfaces using the <span class="application"><strong>Network Administration Tool</strong></span>, refer to <a class="xref" href="ch-Network_Configuration.html" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a>
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-network-related-config.html"><strong>Prev</strong>Part II. Network-Related Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-interfaces.html"><strong>Next</strong>4.2. Interface Configuration Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-OpenSSH.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-OpenSSH.html
new file mode 100644
index 0000000..7fe7061
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-OpenSSH.html
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 9. OpenSSH</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /><link rel="prev" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html" title="8.2.8. SSSD Configuration File Format" /><link rel="next" href="s1-ssh-configuration.html" title="9.2. An OpenSSH Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="
p" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ssh-configuration.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 9. OpenSSH" id="ch-OpenSSH" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 9. OpenSSH</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">9.1. The SSH Protocol</a></span></dt><dt><span class="section"><a href="s1-ssh-configuration.html">9.2. An OpenSSH Configuration</a></span></dt><dt><span class="section"><a href="s1-ssh-clients.html">9.3. OpenSSH Clients</a></span></dt><dt><span class="section"><a href="s1-ssh-beyondshell.html">9.4. More Than a Secure Shell</a></span></dt><dt><span class="section"><a href="s1-openssh-additional-resources.html">9.5. Additional Resources</a></span></dt></dl></div><a id="id832
738" class="indexterm"></a><div class="para">
+ <code class="systemitem">SSH</code> (Secure Shell) is a protocol which facilitates secure communications between two systems using a client/server architecture and allows users to log into server host systems remotely. Unlike other remote communication protocols, such as <code class="systemitem">FTP</code> or <code class="systemitem">Telnet</code>, SSH encrypts the login session, rendering the connection difficult for intruders to collect unencrypted passwords.
+ </div><div class="para">
+ The <span class="application"><strong>ssh</strong></span> program is designed to replace older, less secure terminal applications used to log into remote hosts, such as <code class="command">telnet</code> or <code class="command">rsh</code>. A related program called <code class="command">scp</code> replaces older programs designed to copy files between hosts, such as <code class="command">rcp</code>. Because these older applications do not encrypt passwords transmitted between the client and the server, avoid them whenever possible. Using secure methods to log into remote systems decreases the risks for both the client system and the remote host.
+ </div><div class="para">
+ Fedora includes the general OpenSSH package (<code class="filename">openssh</code>) as well as the OpenSSH server (<code class="filename">openssh-server</code>) and client (<code class="filename">openssh-clients</code>) packages. Note, the OpenSSH packages require the OpenSSL package (<code class="filename">openssl</code>) which installs several important cryptographic libraries, enabling OpenSSH to provide encrypted communications.
+ </div><div class="section" title="9.1. The SSH Protocol" id="s1-ssh-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ssh-protocol">9.1. The SSH Protocol</h2></div></div></div><div class="section" title="9.1.1. Why Use SSH?" id="s2-ssh-why"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-why">9.1.1. Why Use SSH?</h3></div></div></div><a id="id577002" class="indexterm"></a><div class="para">
+ Potential intruders have a variety of tools at their disposal enabling them to disrupt, intercept, and re-route network traffic in an effort to gain access to a system. In general terms, these threats can be categorized as follows:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Interception of communication between two systems</span></dt><dd><div class="para">
+ The attacker can be somewhere on the network between the communicating parties, copying any information passed between them. He may intercept and keep the information, or alter the information and send it on to the intended recipient.
+ </div><div class="para">
+ This attack is usually performed using a <em class="firstterm">packet sniffer</em>, a rather common network utility that captures each packet flowing through the network, and analyzes its content.
+ </div></dd><dt class="varlistentry"><span class="term">Impersonation of a particular host</span></dt><dd><div class="para">
+ Attacker's system is configured to pose as the intended recipient of a transmission. If this strategy works, the user's system remains unaware that it is communicating with the wrong host.
+ </div><div class="para">
+ This attack can be performed using a technique known as <em class="firstterm">DNS poisoning</em>, or via so-called <em class="firstterm">IP spoofing</em>. In the first case, the intruder uses a cracked DNS server to point client systems to a maliciously duplicated host. In the second case, the intruder sends falsified network packets that appear to be from a trusted host.
+ </div></dd></dl></div><div class="para">
+ Both techniques intercept potentially sensitive information and, if the interception is made for hostile reasons, the results can be disastrous. If SSH is used for remote shell login and file copying, these security threats can be greatly diminished. This is because the SSH client and server use digital signatures to verify their identity. Additionally, all communication between the client and server systems is encrypted. Attempts to spoof the identity of either side of a communication does not work, since each packet is encrypted using a key known only by the local and remote systems.
+ </div></div><div class="section" title="9.1.2. Main Features" id="s2-ssh-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-features">9.1.2. Main Features</h3></div></div></div><a id="id791561" class="indexterm"></a><a id="id791573" class="indexterm"></a><div class="para">
+ The SSH protocol provides the following safeguards:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">No one can pose as the intended server</span></dt><dd><div class="para">
+ After an initial connection, the client can verify that it is connecting to the same server it had connected to previously.
+ </div></dd><dt class="varlistentry"><span class="term">No one can capture the authentication information</span></dt><dd><div class="para">
+ The client transmits its authentication information to the server using strong, 128-bit encryption.
+ </div></dd><dt class="varlistentry"><span class="term">No one can intercept the communication</span></dt><dd><div class="para">
+ All data sent and received during a session is transferred using 128-bit encryption, making intercepted transmissions extremely difficult to decrypt and read.
+ </div></dd></dl></div><div class="para">
+ Additionally, it also offers the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">It provides secure means to use graphical applications over a network</span></dt><dd><div class="para">
+ Using a technique called <em class="firstterm">X11 forwarding</em>, the client can forward <em class="firstterm">X11</em> (<em class="firstterm">X Window System</em>) applications from the server.
+ </div></dd><dt class="varlistentry"><span class="term">It provides a way to secure otherwise insecure protocols</span></dt><dd><div class="para">
+ The SSH protocol encrypts everything it sends and receives. Using a technique called <em class="firstterm">port forwarding</em>, an SSH server can become a conduit to securing otherwise insecure protocols, like <acronym class="acronym">POP</acronym>, and increasing overall system and data security.
+ </div></dd><dt class="varlistentry"><span class="term">It can be used to create a secure channel</span></dt><dd><div class="para">
+ The OpenSSH server and client can be configured to create a tunnel similar to a virtual private network for traffic between server and client machines.
+ </div></dd><dt class="varlistentry"><span class="term">It supports the Kerberos authentication</span></dt><dd><div class="para">
+ OpenSSH servers and clients can be configured to authenticate using the <acronym class="acronym">GSSAPI</acronym> (Generic Security Services Application Program Interface) implementation of the Kerberos network authentication protocol.
+ </div></dd></dl></div></div><div class="section" title="9.1.3. Protocol Versions" id="s2-ssh-versions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-versions">9.1.3. Protocol Versions</h3></div></div></div><a id="id539537" class="indexterm"></a><a id="id539549" class="indexterm"></a><div class="para">
+ Two varieties of SSH currently exist: version 1, and newer version 2. The OpenSSH suite under Fedora uses SSH version 2, which has an enhanced key exchange algorithm not vulnerable to the known exploit in version 1. However, for compatibility reasons, the OpenSSH suite does support version 1 connections as well.
+ </div><div class="important" title="Important: Avoid Using SSH Version 1"><div class="admonition_header"><h2>Important: Avoid Using SSH Version 1</h2></div><div class="admonition"><div class="para">
+ To ensure maximum security for your connection, it is recommended that only SSH version 2-compatible servers and clients are used whenever possible.
+ </div></div></div></div><div class="section" title="9.1.4. Event Sequence of an SSH Connection" id="s2-ssh-conn"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-conn">9.1.4. Event Sequence of an SSH Connection</h3></div></div></div><a id="id490793" class="indexterm"></a><div class="para">
+ The following series of events help protect the integrity of SSH communication between two hosts.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ A cryptographic handshake is made so that the client can verify that it is communicating with the correct server.
+ </div></li><li class="listitem"><div class="para">
+ The transport layer of the connection between the client and remote host is encrypted using a symmetric cipher.
+ </div></li><li class="listitem"><div class="para">
+ The client authenticates itself to the server.
+ </div></li><li class="listitem"><div class="para">
+ The remote client interacts with the remote host over the encrypted connection.
+ </div></li></ol></div><div class="section" title="9.1.4.1. Transport Layer" id="s2-ssh-protocol-conn-transport"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-ssh-protocol-conn-transport">9.1.4.1. Transport Layer</h4></div></div></div><a id="id558607" class="indexterm"></a><div class="para">
+ The primary role of the transport layer is to facilitate safe and secure communication between the two hosts at the time of authentication and during subsequent communication. The transport layer accomplishes this by handling the encryption and decryption of data, and by providing integrity protection of data packets as they are sent and received. The transport layer also provides compression, speeding the transfer of information.
+ </div><div class="para">
+ Once an SSH client contacts a server, key information is exchanged so that the two systems can correctly construct the transport layer. The following steps occur during this exchange:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Keys are exchanged
+ </div></li><li class="listitem"><div class="para">
+ The public key encryption algorithm is determined
+ </div></li><li class="listitem"><div class="para">
+ The symmetric encryption algorithm is determined
+ </div></li><li class="listitem"><div class="para">
+ The message authentication algorithm is determined
+ </div></li><li class="listitem"><div class="para">
+ The hash algorithm is determined
+ </div></li></ul></div><div class="para">
+ During the key exchange, the server identifies itself to the client with a unique <em class="firstterm">host key</em>. If the client has never communicated with this particular server before, the server's host key is unknown to the client and it does not connect. OpenSSH gets around this problem by accepting the server's host key. This is done after the user is notified and has both accepted and verified the new host key. In subsequent connections, the server's host key is checked against the saved version on the client, providing confidence that the client is indeed communicating with the intended server. If, in the future, the host key no longer matches, the user must remove the client's saved version before a connection can occur.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ It is possible for an attacker to masquerade as an SSH server during the initial contact since the local system does not know the difference between the intended server and a false one set up by an attacker. To help prevent this, verify the integrity of a new SSH server by contacting the server administrator before connecting for the first time or in the event of a host key mismatch.
+ </div></div></div><div class="para">
+ SSH is designed to work with almost any kind of public key algorithm or encoding format. After an initial key exchange creates a hash value used for exchanges and a shared secret value, the two systems immediately begin calculating new keys and algorithms to protect authentication and future data sent over the connection.
+ </div><div class="para">
+ After a certain amount of data has been transmitted using a given key and algorithm (the exact amount depends on the SSH implementation), another key exchange occurs, generating another set of hash values and a new shared secret value. Even if an attacker is able to determine the hash and shared secret value, this information is only useful for a limited period of time.
+ </div></div><div class="section" title="9.1.4.2. Authentication" id="s2-ssh-protocol-authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-ssh-protocol-authentication">9.1.4.2. Authentication</h4></div></div></div><a id="id722520" class="indexterm"></a><div class="para">
+ Once the transport layer has constructed a secure tunnel to pass information between the two systems, the server tells the client the different authentication methods supported, such as using a private key-encoded signature or typing a password. The client then tries to authenticate itself to the server using one of these supported methods.
+ </div><div class="para">
+ SSH servers and clients can be configured to allow different types of authentication, which gives each side the optimal amount of control. The server can decide which encryption methods it supports based on its security model, and the client can choose the order of authentication methods to attempt from the available options.
+ </div></div><div class="section" title="9.1.4.3. Channels" id="s2-ssh-protocol-connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-ssh-protocol-connection">9.1.4.3. Channels</h4></div></div></div><a id="id722555" class="indexterm"></a><div class="para">
+ After a successful authentication over the SSH transport layer, multiple channels are opened via a technique called <em class="firstterm">multiplexing</em><sup>[<a id="id483177" href="#ftn.id483177" class="footnote">3</a>]</sup>. Each of these channels handles communication for different terminal sessions and for forwarded X11 sessions.
+ </div><div class="para">
+ Both clients and servers can create a new channel. Each channel is then assigned a different number on each end of the connection. When the client attempts to open a new channel, the clients sends the channel number along with the request. This information is stored by the server and is used to direct communication to that channel. This is done so that different types of sessions do not affect one another and so that when a given session ends, its channel can be closed without disrupting the primary SSH connection.
+ </div><div class="para">
+ Channels also support <em class="firstterm">flow-control</em>, which allows them to send and receive data in an orderly fashion. In this way, data is not sent over the channel until the client receives a message that the channel is open.
+ </div><div class="para">
+ The client and server negotiate the characteristics of each channel automatically, depending on the type of service the client requests and the way the user is connected to the network. This allows great flexibility in handling different types of remote connections without having to change the basic infrastructure of the protocol.
+ </div></div></div></div><div class="footnotes"><br /><hr /><div class="footnote"><p><sup>[<a id="ftn.id483177" href="#id483177" class="para">3</a>] </sup>
+ A multiplexed connection consists of several signals being sent over a shared, common medium. With SSH, different channels are sent over a common secure connection.
+ </p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"><strong>Prev</strong>8.2.8. SSSD Configuration File Format</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-ssh-configuration.html"><strong>Next</strong>9.2. An OpenSSH Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-PackageKit.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-PackageKit.html
new file mode 100644
index 0000000..55b8f7f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-PackageKit.html
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 2. PackageKit</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-pkg-management.html" title="Part I. Package Management" /><link rel="prev" href="sec-Additional_Resources.html" title="1.5. Additional Resources" /><link rel="next" href="sec-Using_Add_Remove_Software.html" title="2.2. Using Add/Remove Software" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Additional_Resources.html"><strong>Prev</strong></a></li><li class="n
ext"><a accesskey="n" href="sec-Using_Add_Remove_Software.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 2. PackageKit" id="ch-PackageKit" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. PackageKit</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">2.1. Updating Packages with Software Update</a></span></dt><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html">2.2. Using Add/Remove Software</a></span></dt><dt><span class="section"><a href="sec-PackageKit_Architecture.html">2.3. PackageKit Architecture</a></span></dt><dt><span class="section"><a href="ch-Graphical_Package_Management-sec-Additional_Resources.html">2.4. Additional Resources</a></span></dt></dl></div><a id="id418308" class="indexterm"></a><div class="para">
+ Red Hat provides <span class="application"><strong>PackageKit</strong></span> for viewing, managing, updating, installing and uninstalling packages
+ <a id="id720907" class="indexterm"></a>
+ <a id="id706708" class="indexterm"></a>
+ <a id="id721523" class="indexterm"></a>
+ <a id="id675370" class="indexterm"></a>
+ <a id="id758627" class="indexterm"></a>
+ <a id="id539173" class="indexterm"></a>
+ <a id="id837056" class="indexterm"></a>
+ <a id="id674299" class="indexterm"></a>
+ <a id="id733499" class="indexterm"></a>
+ <a id="id417143" class="indexterm"></a>
+ compatible with your system. <span class="application"><strong>PackageKit</strong></span> consists of several graphical interfaces that can be opened from the GNOME panel menu, or from the Notification Area when <span class="application"><strong>PackageKit</strong></span> alerts you that updates are available. For more information on <span class="application"><strong>PackageKit's</strong></span> architecture and available front ends, refer to <a class="xref" href="sec-PackageKit_Architecture.html" title="2.3. PackageKit Architecture">Section 2.3, “PackageKit Architecture”</a>.
+ </div><div class="section" title="2.1. Updating Packages with Software Update" id="sec-Updating_Packages_with_Software_Update"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Updating_Packages_with_Software_Update">2.1. Updating Packages with Software Update</h2></div></div></div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> displays a starburst icon in the Notification Area whenever updates are available to be installed on your system.
+ </div><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-updates_available.png" align="middle" /></div><div class="para">
+ Clicking on the notification icon opens the <span class="guilabel"><strong>Software Update</strong></span> <a id="id429482" class="indexterm"></a>
+ <a id="id429498" class="indexterm"></a>
+ window. Alternatively, you can open <span class="guilabel"><strong>Software Updates</strong></span> by clicking <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Software Update</strong></span> from the GNOME panel, or running the <code class="command">gpk-update-viewer</code> command at the shell prompt. In the <span class="guilabel"><strong>Software Updates</strong></span> window, all available updates are listed along with the names of the packages being updated (minus the <code class="filename">.rpm</code> suffix, but including the CPU architecture), a short summary of the package, and, usually, short descriptions of the changes the update provides. Any updates you do not wish to install can be de-selected here by unchecking the checkbox corresponding to the update.
+ </div><div class="figure" title="Figure 2.1. Installing updates with Software Update" id="fig-Graphical_Package_Management-software_update"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-software_update.png" align="middle" width="444" alt="Installing updates with Software Update" /><div class="longdesc"><div class="para">
+ installing 12 updates with packagekit's software update window
+ </div></div></div></div><h6>Figure 2.1. Installing updates with Software Update</h6></div><br class="figure-break" /><div class="para">
+ The updates presented in the <span class="guilabel"><strong>Software Updates</strong></span> window only represent the currently-installed packages on your system for which updates are available;
+ <a id="id708234" class="indexterm"></a>
+ <a id="id802764" class="indexterm"></a>
+ dependencies of those packages, whether they are existing packages on your system or new ones, are not shown until you click <span class="guibutton"><strong>Install Updates</strong></span>.
+ </div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> <a id="id802789" class="indexterm"></a>
+ <a id="id802805" class="indexterm"></a>
+ <a id="id802816" class="indexterm"></a>
+ utilizes the fine-grained user authentication
+ <a id="id802824" class="indexterm"></a>
+ capabilities provided by the <span class="application"><strong>PolicyKit</strong></span> toolkit whenever you request it to make changes to the system. Whenever you instruct <span class="application"><strong>PackageKit</strong></span> to update, install or remove packages, you will be prompted to enter the superuser password before changes are made to the system.
+ </div><div class="figure" title="Figure 2.2. PackageKit uses PolicyKit to authenticate" id="fig-Graphical_Package_Management-authenticate"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-authenticate.png" align="middle" alt="PackageKit uses PolicyKit to authenticate" /><div class="longdesc"><div class="para">
+ packagekit defers to policykit to provide authentication in order to make changes to the system
+ </div></div></div></div><h6>Figure 2.2. PackageKit uses PolicyKit to authenticate</h6></div><br class="figure-break" /><div class="para">
+ If you instruct <span class="application"><strong>PackageKit</strong></span> to update the <code class="filename">kernel</code> package, then it will prompt you after installation, asking you whether you want to reboot the system and thereby boot into the newly-installed kernel.
+ </div><h3>Setting the Update-Checking Interval</h3><a id="id590480" class="indexterm"></a><div class="para">
+ Right-clicking on <span class="application"><strong>PackageKit</strong></span>'s Notification Area icon and clicking <span class="guimenuitem"><strong>Preferences</strong></span> opens the <span class="guilabel"><strong>Software Update Preferences</strong></span> window, where you can define the interval at which <span class="application"><strong>PackageKit</strong></span> checks for package updates, as well as whether or not to automatically install all updates or only security updates, and how often to check for major upgrades. Leaving the <span class="guilabel"><strong>Check for updates when using mobile broadband</strong></span> box unchecked is handy for avoiding extraneous bandwidth usage when using a wireless connection on which you are charged for the amount of data you download.
+ </div><div class="figure" title="Figure 2.3. Setting PackageKit's update-checking interval" id="fig-Graphical_Package_Management-Software_Update_Preferences"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-Software_Update_Preferences.png" align="middle" alt="Setting PackageKit's update-checking interval" /><div class="longdesc"><div class="para">
+ Setting the update-checking interval for packagekit by right-clicking on the notification area applet
+ </div></div></div></div><h6>Figure 2.3. Setting PackageKit's update-checking interval</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Additional_Resources.html"><strong>Prev</strong>1.5. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_Add_Remove_Software.html"><strong>Next</strong>2.2. Using Add/Remove Software</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-RPM.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-RPM.html
new file mode 100644
index 0000000..1cefebb
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-RPM.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 3. RPM</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-pkg-management.html" title="Part I. Package Management" /><link rel="prev" href="ch-Graphical_Package_Management-sec-Additional_Resources.html" title="2.4. Additional Resources" /><link rel="next" href="s1-rpm-using.html" title="3.2. Using RPM" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Graphical_Package_Management-sec-Additional_Resources.html"><strong>Pre
v</strong></a></li><li class="next"><a accesskey="n" href="s1-rpm-using.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 3. RPM" id="ch-RPM" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 3. RPM</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-RPM.html#s1-rpm-design">3.1. RPM Design Goals</a></span></dt><dt><span class="section"><a href="s1-rpm-using.html">3.2. Using RPM</a></span></dt><dt><span class="section"><a href="s1-check-rpm-sig.html">3.3. Checking a Package's Signature</a></span></dt><dt><span class="section"><a href="s1-rpm-impressing.html">3.4. Practical and Common Examples of RPM Usage</a></span></dt><dt><span class="section"><a href="s1-rpm-additional-resources.html">3.5. Additional Resources</a></span></dt></dl></div><a id="id653908" class="indexterm"></a><a id="id653901" class="indexterm"></a><div class="para">
+ The <em class="firstterm">RPM Package Manager</em> (RPM) is an open packaging system
+ <a id="id653888" class="indexterm"></a>
+ , which runs on Fedora as well as other Linux and UNIX systems. Red Hat, Inc. and the Fedora Project encourage other vendors to use RPM for their own products. RPM is distributed under the terms of the <em class="firstterm">GPL</em> (<em class="firstterm">GNU General Public License</em>).
+ </div><div class="para">
+ The RPM Package Manager only works with packages built to work with the <span class="emphasis"><em>RPM format</em></span>. RPM is itself provided as a pre-installed <span class="package">rpm</span> package. For the end user, RPM makes system updates easy. Installing, uninstalling and upgrading RPM packages can be accomplished with short commands. RPM maintains a database of installed packages and their files, so you can invoke powerful queries and verifications on your system.
+ </div><div class="para">
+ The RPM package format has been improved for Fedora 14. RPM packages are now compressed using the XZ lossless data compression format, which has the benefit of greater compression and less CPU usage during decompression, and support multiple strong hash algorithms, such as SHA-256, for package signing and verification.
+ </div><div class="warning" title="Use Yum Instead of RPM Whenever Possible" id="warning-Use_Yum_Instead_of_RPM_Whenever_Possible"><div class="admonition_header"><h2>Use Yum Instead of RPM Whenever Possible</h2></div><div class="admonition"><div class="para">
+ For most package management tasks, the <span class="application"><strong>Yum</strong></span> package manager offers equal and often greater capabilities and utility than RPM
+ <a id="id584296" class="indexterm"></a>
+ . <span class="application"><strong>Yum</strong></span> also performs and tracks complicated system dependency resolution, and will complain and force system integrity checks if you use RPM as well to install and remove packages. For these reasons, it is highly recommended that you use <span class="application"><strong>Yum</strong></span> instead of RPM whenever possible to perform package management tasks. Refer to <a class="xref" href="ch-yum.html" title="Chapter 1. Yum">Chapter 1, <i>Yum</i></a>.
+ </div><div class="para">
+ If you prefer a graphical interface, you can use the <span class="application"><strong>PackageKit</strong></span> GUI application, which uses <span class="application"><strong>Yum</strong></span> as its back end, to manage your system's packages. Refer to <a class="xref" href="ch-PackageKit.html" title="Chapter 2. PackageKit">Chapter 2, <i>PackageKit</i></a> for details.
+ </div></div></div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When installing a package, ensure it is compatible with your operating system and processor architecture. This can usually be determined by checking the package name. Many of the following examples show RPM packages compiled for the AMD64/Intel 64 computer architectures; thus, the RPM file name ends in <code class="filename">x86_64.rpm</code>.
+ </div></div></div><div class="para">
+ During upgrades, RPM handles configuration files carefully, so that you never lose your customizations—something that you cannot accomplish with regular <code class="filename">.tar.gz</code> files.
+ </div><div class="para">
+ For the developer, RPM allows you to take software source code and package it into source and binary packages for end users.
+ <a id="id752485" class="indexterm"></a>
+ This process is quite simple and is driven from a single file and optional patches that you create. This clear delineation between <em class="firstterm">pristine</em> sources and your patches along with build instructions eases the maintenance of the package as new versions of the software are released.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Because RPM makes changes to your system, you must be logged in as root to install, remove, or upgrade an RPM package.
+ </div></div></div><div class="section" title="3.1. RPM Design Goals" id="s1-rpm-design"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-rpm-design">3.1. RPM Design Goals</h2></div></div></div><a id="id503646" class="indexterm"></a><div class="para">
+ To understand how to use RPM, it can be helpful to understand the design goals of RPM:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Upgradability
+ <a id="id503623" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ With RPM, you can upgrade individual components of your system without completely reinstalling. When you get a new release of an operating system based on RPM, such as Fedora, you do not need to reinstall a fresh copy of the operating system your machine (as you might need to with operating systems based on other packaging systems). RPM allows intelligent, fully-automated, in-place upgrades of your system. In addition, configuration files in packages are preserved across upgrades, so you do not lose your customizations. There are no special upgrade files needed to upgrade a package because the same RPM file is used to both install and upgrade the package on your system.
+ </div></dd><dt class="varlistentry"><span class="term">Powerful Querying
+ <a id="id776134" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ RPM is designed to provide powerful querying options. You can perform searches on your entire database for packages or even just certain files. You can also easily find out what package a file belongs to and from where the package came. The files an RPM package contains are in a compressed archive, with a custom binary header containing useful information about the package and its contents, allowing you to query individual packages quickly and easily.
+ </div></dd><dt class="varlistentry"><span class="term"> System Verification
+ <a id="id419971" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Another powerful RPM feature is the ability to verify packages. If you are worried that you deleted an important file for some package, you can verify the package. You are then notified of anomalies, if any—at which point you can reinstall the package, if necessary. Any configuration files that you modified are preserved during reinstallation.
+ </div></dd><dt class="varlistentry"><span class="term">Pristine Sources
+ <a id="id802970" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ A crucial design goal was to allow the use of <span class="emphasis"><em>pristine </em></span> software sources, as distributed by the original authors of the software. With RPM, you have the pristine sources along with any patches that were used, plus complete build instructions. This is an important advantage for several reasons. For instance, if a new version of a program is released, you do not necessarily have to start from scratch to get it to compile. You can look at the patch to see what you <span class="emphasis"><em>might</em></span> need to do. All the compiled-in defaults, and all of the changes that were made to get the software to build properly, are easily visible using this technique.
+ </div><div class="para">
+ The goal of keeping sources pristine may seem important only for developers, but it results in higher quality software for end users, too.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Graphical_Package_Management-sec-Additional_Resources.html"><strong>Prev</strong>2.4. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-rpm-using.html"><strong>Next</strong>3.2. Using RPM</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-The_Apache_HTTP_Server.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-The_Apache_HTTP_Server.html
new file mode 100644
index 0000000..8ca2bf9
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-The_Apache_HTTP_Server.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 11. The Apache HTTP Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /><link rel="prev" href="s2-bind-related-books.html" title="10.8.3. Related Books" /><link rel="next" href="s1-apache-running.html" title="11.2. Running the httpd Service" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-related-books.html"><strong>Prev</strong></a></li><li class="ne
xt"><a accesskey="n" href="s1-apache-running.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 11. The Apache HTTP Server" id="ch-The_Apache_HTTP_Server" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 11. The Apache HTTP Server</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-The_Apache_HTTP_Server.html#s1-apache-version2">11.1. The Apache HTTP Server 2.2</a></span></dt><dt><span class="section"><a href="s1-apache-running.html">11.2. Running the <code class="systemitem">httpd</code> Service</a></span></dt><dt><span class="section"><a href="s1-apache-editing.html">11.3. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="s1-apache-dso.html">11.4. Working with Modules</a></span></dt><dt><span class="section"><a href="s1-apache-virtualhosts.html">11.5. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="s1-apache-mod_ssl.h
tml">11.6. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="s1-apache-resources.html">11.7. Additional Resources</a></span></dt></dl></div><a id="id832749" class="indexterm"></a><a id="id802728" class="indexterm"></a><div class="para">
+ <code class="systemitem">HTTP</code> (Hypertext Transfer Protocol) server, or a <em class="firstterm">web server</em>, is a network service that serves content to a client over the web. This typically means web pages, but any other documents can be served as well.
+ </div><a id="id518608" class="indexterm"></a><div class="para">
+ This chapter focuses on the <span class="application"><strong>Apache HTTP Server 2.2</strong></span>, a robust, full-featured open source web server developed by the <a href="http://www.apache.org/">Apache Software Foundation</a>, that is included in Fedora 14. It describes the basic configuration of the <code class="systemitem">httpd</code> service, and covers advanced topics such as adding server modules, setting up virtual hosts, or configuring the secure HTTP server.
+ </div><div class="section" title="11.1. The Apache HTTP Server 2.2" id="s1-apache-version2"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-version2">11.1. The Apache HTTP Server 2.2</h2></div></div></div><div class="para">
+ There are important differences between the Apache HTTP Server 2.2 and version 2.0, and if you are upgrading from a previous release of Fedora, you will need to update the <code class="systemitem">httpd</code> service configuration accordingly. This section reviews some of the newly added features, outlines important changes, and guides you through the update of older configuration files.
+ </div><div class="section" title="11.1.1. New Features" id="s2-apache-version2-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-version2-features">11.1.1. New Features</h3></div></div></div><a id="id745324" class="indexterm"></a><div class="para">
+ The Apache HTTP Server version 2.2 introduces the following enhancements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a id="id771953" class="indexterm"></a>
+ <a id="id539626" class="indexterm"></a>
+ Improved caching modules, that is, <code class="systemitem">mod_cache</code> and <code class="systemitem">mod_disk_cache</code>.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id549910" class="indexterm"></a>
+ Support for proxy load balancing, that is, the <code class="systemitem">mod_proxy_balancer</code> module.
+ </div></li><li class="listitem"><div class="para">
+ Support for large files on 32-bit architectures, allowing the web server to handle files greater than 2GB.
+ </div></li><li class="listitem"><div class="para">
+ A new structure for authentication and authorization support, replacing the authentication modules provided in previous versions.
+ </div></li></ul></div></div><div class="section" title="11.1.2. Notable Changes" id="s2-apache-version2-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-version2-changes">11.1.2. Notable Changes</h3></div></div></div><a id="id737807" class="indexterm"></a><div class="para">
+ Since version 2.0, few changes have been made to the default <code class="systemitem">httpd</code> service configuration:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a id="id737842" class="indexterm"></a>
+ <a id="id777867" class="indexterm"></a>
+ The following modules are no longer loaded by default: <code class="systemitem">mod_cern_meta</code> and <code class="systemitem">mod_asis</code>.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id777907" class="indexterm"></a>
+ The following module is newly loaded by default: <code class="systemitem">mod_ext_filter</code>.
+ </div></li></ul></div></div><div class="section" title="11.1.3. Updating the Configuration" id="s1-apache-version2-migrating"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s1-apache-version2-migrating">11.1.3. Updating the Configuration</h3></div></div></div><a id="id546903" class="indexterm"></a><div class="para">
+ To update the configuration files from the Apache HTTP Server version 2.0, take the following steps:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Make sure all module names are correct, since they may have changed. Adjust the <code class="option">LoadModule</code> directive for each module that has been renamed.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Recompile all third party modules before attempting to load them. This typically means authentication and authorization modules.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ <a id="id546953" class="indexterm"></a>
+ If you use the <code class="systemitem">mod_userdir</code> module, make sure the <code class="option">UserDir</code> directive indicating a directory name (typically <code class="literal">public_html</code>) is provided.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ If you use the Apache HTTP Secure Server, edit the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> to enable the Secure Sockets Layer (SSL) protocol.
+ </div></li></ol></div><div class="para">
+ Note that you can check the configuration for possible errors by using the following command:
+ </div><pre class="screen">~]# <code class="command">service httpd configtest</code>
+Syntax OK</pre><div class="para">
+ For more information on upgrading the Apache HTTP Server configuration from version 2.0 to 2.2, refer to <a href="http://httpd.apache.org/docs/2.2/upgrading.html">http://httpd.apache.org/docs/2.2/upgrading.html</a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-related-books.html"><strong>Prev</strong>10.8.3. Related Books</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-running.html"><strong>Next</strong>11.2. Running the httpd Service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-The_BIND_DNS_Server.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-The_BIND_DNS_Server.html
new file mode 100644
index 0000000..f0bcea7
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-The_BIND_DNS_Server.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 10. The BIND DNS Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /><link rel="prev" href="s2-openssh-useful-websites.html" title="9.5.2. Useful Websites" /><link rel="next" href="s1-bind-namedconf.html" title="10.2. Configuring the named Service" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-openssh-useful-websites.html"><strong>Prev</strong></a></l
i><li class="next"><a accesskey="n" href="s1-bind-namedconf.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 10. The BIND DNS Server" id="ch-The_BIND_DNS_Server" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. The BIND DNS Server</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s1-bind-introduction">10.1. Introduction to DNS</a></span></dt><dt><span class="section"><a href="s1-bind-namedconf.html">10.2. Configuring the <code class="command">named</code> Service</a></span></dt><dt><span class="section"><a href="s1-bind-zone.html">10.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="s1-bind-rndc.html">10.4. Using the <code class="command">rndc</code> Utility</a></span></dt><dt><span class="section"><a href="s1-bind-dig.html">10.5. Using the <code class="command">dig</code> Utility</a></span></dt><dt><span class="section"><a
href="s1-bind-features.html">10.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="s1-bind-mistakes.html">10.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="s1-bind-additional-resources.html">10.8. Additional Resources</a></span></dt></dl></div><a id="id431507" class="indexterm"></a><a id="id700670" class="indexterm"></a><div class="para">
+ <code class="systemitem">DNS</code> (Domain Name System), also known as a <em class="firstterm">nameserver</em>, is a network system that associates hostnames with their respective IP addresses. For users, this has the advantage that they can refer to machines on the network by names that are usually easier to remember than the numerical network addresses. For system administrators, using the nameserver allows them to change the IP address for a host without ever affecting the name-based queries, or to decide which machines handle these queries.
+ </div><a id="id692708" class="indexterm"></a><div class="para">
+ This chapter covers <code class="systemitem">BIND</code> (Berkeley Internet Name Domain), the DNS server included in Fedora. It focuses on the structure of its configuration files, and describes how to administer it both locally and remotely.
+ </div><div class="section" title="10.1. Introduction to DNS" id="s1-bind-introduction"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-introduction">10.1. Introduction to DNS</h2></div></div></div><a id="id444867" class="indexterm"></a><div class="para">
+ DNS is usually implemented using one or more centralized servers that are authoritative for certain domains. When a client host requests information from a nameserver, it usually connects to port 53. The nameserver then attempts to resolve the name requested. If it does not have an authoritative answer, or does not already have the answer cached from an earlier query, it queries other nameservers, called <em class="firstterm">root nameservers</em>, to determine which nameservers are authoritative for the name in question, and then queries them to get the requested name.
+ </div><div class="section" title="10.1.1. Nameserver Zones" id="s2-bind-introduction-zones"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-introduction-zones">10.1.1. Nameserver Zones</h3></div></div></div><a id="id404228" class="indexterm"></a><a id="id816597" class="indexterm"></a><a id="id557818" class="indexterm"></a><a id="id672413" class="indexterm"></a><div class="para">
+ In a DNS server such as BIND, all information is stored in basic data elements called <em class="firstterm">resource records</em> (RR). The resource record is usually a <em class="firstterm">fully qualified domain name</em> (FQDN) of a host, and is broken down into multiple sections organized into a tree-like hierarchy. This hierarchy consists of a main trunk, primary branches, secondary branches, and so on.
+ </div><div class="example" title="Example 10.1. A simple resource record" id="example-bind-introduction-zones-rr"><h6>Example 10.1. A simple resource record</h6><div class="example-contents"><pre class="screen">bob.sales.example.com</pre></div></div><br class="example-break" /><a id="id520693" class="indexterm"></a><div class="para">
+ Each level of the hierarchy is divided by a period (that is, <code class="literal">.</code>). In <a class="xref" href="ch-The_BIND_DNS_Server.html#example-bind-introduction-zones-rr" title="Example 10.1. A simple resource record">Example 10.1, “A simple resource record”</a>, <code class="literal">com</code> defines the <em class="firstterm">top-level domain</em>, <code class="literal">example</code> its subdomain, and <code class="literal">sales</code> the subdomain of <code class="literal">example</code>. In this case, <code class="literal">bob</code> identifies a resource record that is part of the <code class="systemitem">sales.example.com</code> domain. With the exception of the part furthest to the left (that is, <code class="literal">bob</code>), each of these sections is called a <em class="firstterm">zone</em> and defines a specific <em class="firstterm">namespace</em>.
+ </div><a id="id834653" class="indexterm"></a><a id="id834669" class="indexterm"></a><div class="para">
+ Zones are defined on authoritative nameservers through the use of <em class="firstterm">zone files</em>, which contain definitions of the resource records in each zone. Zone files are stored on <em class="firstterm">primary nameservers</em> (also called <em class="firstterm">master nameservers</em>), where changes are made to the files, and <em class="firstterm">secondary nameservers</em> (also called <em class="firstterm">slave nameservers</em>), which receive zone definitions from the primary nameservers. Both primary and secondary nameservers are authoritative for the zone and look the same to clients. Depending on the configuration, any nameserver can also serve as a primary or secondary server for multiple zones at the same time.
+ </div></div><div class="section" title="10.1.2. Nameserver Types" id="s2-bind-introduction-nameservers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-introduction-nameservers">10.1.2. Nameserver Types</h3></div></div></div><div class="para">
+ There are two nameserver configuration types:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id590837" class="indexterm"></a>
+ <a id="id590853" class="indexterm"></a>
+ <a id="id590865" class="indexterm"></a>
+ <a id="id853634" class="indexterm"></a>
+ <a id="id853646" class="indexterm"></a>
+ <a id="id853662" class="indexterm"></a>
+ authoritative </span></dt><dd><div class="para">
+ Authoritative nameservers answer to resource records that are part of their zones only. This category includes both primary (master) and secondary (slave) nameservers.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id853691" class="indexterm"></a>
+ <a id="id461681" class="indexterm"></a>
+ recursive </span></dt><dd><div class="para">
+ Recursive nameservers offer resolution services, but they are not authoritative for any zone. Answers for all resolutions are cached in a memory for a fixed period of time, which is specified by the retrieved resource record.
+ </div></dd></dl></div><div class="para">
+ Although a nameserver can be both authoritative and recursive at the same time, it is recommended not to combine the configuration types. To be able to perform their work, authoritative servers should be available to all clients all the time. On the other hand, since the recursive lookup takes far more time than authoritative responses, recursive servers should be available to a restricted number of clients only, otherwise they are prone to distributed denial of service (DDoS) attacks.
+ </div></div><div class="section" title="10.1.3. BIND as a Nameserver" id="s2-bind-introduction-bind"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-introduction-bind">10.1.3. BIND as a Nameserver</h3></div></div></div><a id="id461724" class="indexterm"></a><a id="id461743" class="indexterm"></a><a id="id461761" class="indexterm"></a><a id="id732721" class="indexterm"></a><a id="id732736" class="indexterm"></a><a id="id732749" class="indexterm"></a><div class="para">
+ BIND consists of a set of DNS-related programs. It contains a monolithic nameserver called <code class="systemitem">named</code>, an administration utility called <code class="command">rndc</code>, and a debugging tool called <code class="command">dig</code>. Refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for more information on how to run a service in Fedora.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-openssh-useful-websites.html"><strong>Prev</strong>9.5.2. Useful Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-bind-namedconf.html"><strong>Next</strong>10.2. Configuring the named Service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-The_sysconfig_Directory.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-The_sysconfig_Directory.html
new file mode 100644
index 0000000..e00019a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-The_sysconfig_Directory.html
@@ -0,0 +1,332 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 18. The sysconfig Directory</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-sysconfig.html" title="Part III. System Configuration" /><link rel="prev" href="s2-log-files-useful-websites.html" title="17.7.2. Useful Websites" /><link rel="next" href="s1-sysconfig-etcsysconf-dir.html" title="18.2. Directories in the /etc/sysconfig/ Directory" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-log-files-useful-websites.html"><strong>Prev</stron
g></a></li><li class="next"><a accesskey="n" href="s1-sysconfig-etcsysconf-dir.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 18. The sysconfig Directory" id="ch-The_sysconfig_Directory" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 18. The sysconfig Directory</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s1-sysconfig-files">18.1. Files in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="s1-sysconfig-etcsysconf-dir.html">18.2. Directories in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="s1-sysconfig-additional-resources.html">18.3. Additional Resources</a></span></dt></dl></div><a id="id458349" class="indexterm"></a><a id="id719438" class="indexterm"></a><div class="para">
+ This chapter outlines some of the files and directories found in the <code class="filename">/etc/sysconfig/</code> directory, their function, and their contents. The information in this chapter is not intended to be complete, as many of these files have a variety of options that are only used in very specific or rare circumstances.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The actual content of your <code class="filename">/etc/sysconfig/</code> directory depends on the programs you have installed on your machine. To find the name of the package the configuration file belongs to, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">yum provides /etc/sysconfig/<em class="replaceable"><code>filename</code></em> </code>
+</pre><div class="para">
+ Refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><div class="section" title="18.1. Files in the /etc/sysconfig/ Directory" id="s1-sysconfig-files"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysconfig-files">18.1. Files in the <code class="filename">/etc/sysconfig/</code> Directory</h2></div></div></div><a id="id701327" class="indexterm"></a><div class="para">
+ The following sections offer descriptions of files normally found in the <code class="filename">/etc/sysconfig/</code> directory.
+ </div><div class="section" title="18.1.1. /etc/sysconfig/arpwatch" id="s2-sysconfig-arpwatch"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-arpwatch">18.1.1. <code class="filename">/etc/sysconfig/arpwatch</code> </h3></div></div></div><a id="id531213" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/arpwatch</code> file is used to pass arguments to the <code class="command">arpwatch</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">arpwatch</code> daemon. For example:
+ </div><pre class="screen">OPTIONS="-u arpwatch -e root -s 'root (Arpwatch)'"</pre></dd></dl></div></div><div class="section" title="18.1.2. /etc/sysconfig/authconfig" id="s2-sysconfig-authconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-authconfig">18.1.2. <code class="filename">/etc/sysconfig/authconfig</code> </h3></div></div></div><a id="id468899" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/authconfig</code> file sets the authorization to be used on the host. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">USEMKHOMEDIR=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) creating a home directory for a user on the first login. For example:
+ </div><pre class="screen">USEMKHOMEDIR=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEPAMACCESS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the PAM authentication. For example:
+ </div><pre class="screen">USEPAMACCESS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESSSDAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the SSSD authentication. For example:
+ </div><pre class="screen">USESSSDAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESHADOW=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) shadow passwords. For example:
+ </div><pre class="screen">USESHADOW=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEWINBIND=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using Winbind for user account configuration. For example:
+ </div><pre class="screen">USEWINBIND=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEDB=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the FAS authentication. For example:
+ </div><pre class="screen">USEDB=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEFPRINTD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the fingerprint authentication. For example:
+ </div><pre class="screen">USEFPRINTD=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">FORCESMARTCARD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) enforcing the smart card authentication. For example:
+ </div><pre class="screen">FORCESMARTCARD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PASSWDALGORITHM=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The password algorithm. The <em class="replaceable"><code>value</code></em> can be <code class="option">bigcrypt</code>, <code class="option">descrypt</code>, <code class="option">md5</code>, <code class="option">sha256</code>, or <code class="option">sha512</code>. For example:
+ </div><pre class="screen">PASSWDALGORITHM=sha512</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELDAPAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the LDAP authentication. For example:
+ </div><pre class="screen">USELDAPAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELOCAUTHORIZE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the local authorization for local users. For example:
+ </div><pre class="screen">USELOCAUTHORIZE=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USECRACKLIB=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the CrackLib. For example:
+ </div><pre class="screen">USECRACKLIB=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEWINBINDAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the Winbind authentication. For example:
+ </div><pre class="screen">USEWINBINDAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESMARTCARD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the smart card authentication. For example:
+ </div><pre class="screen">USESMARTCARD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USELDAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using LDAP for user account configuration. For example:
+ </div><pre class="screen">USELDAP=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USENIS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using NIS for user account configuration. For example:
+ </div><pre class="screen">USENIS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEKERBEROS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the Kerberos authentication. For example:
+ </div><pre class="screen">USEKERBEROS=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESYSNETAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) authenticating system accounts with network services. For example:
+ </div><pre class="screen">USESYSNETAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESMBAUTH=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the SMB authentication. For example:
+ </div><pre class="screen">USESMBAUTH=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USESSSD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using SSSD for obtaining user information. For example:
+ </div><pre class="screen">USESSSD=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USEHESIOD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the Hesoid name service. For example:
+ </div><pre class="screen">USEHESIOD=no</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="ch-Authentication_Configuration.html" title="Chapter 8. Authentication Configuration">Chapter 8, <i>Authentication Configuration</i></a> for more information on this topic.
+ </div></div><div class="section" title="18.1.3. /etc/sysconfig/autofs" id="s2-sysconfig-autofs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-autofs">18.1.3. <code class="filename">/etc/sysconfig/autofs</code> </h3></div></div></div><a id="id748097" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/autofs</code> file defines custom options for the automatic mounting of devices. This file controls the operation of the automount daemons, which automatically mount file systems when you use them and unmount them after a period of inactivity. File systems can include network file systems, CD-ROM drives, diskettes, and other media.
+ </div><div class="para">
+ By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">MASTER_MAP_NAME=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default name for the master map. For example:
+ </div><pre class="screen">MASTER_MAP_NAME="auto.master"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default mount timeout. For example:
+ </div><pre class="screen">TIMEOUT=300</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">NEGATIVE_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default negative timeout for unsuccessful mount attempts. For example:
+ </div><pre class="screen">NEGATIVE_TIMEOUT=60</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOUNT_WAIT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for a response from <code class="command">mount</code>. For example:
+ </div><pre class="screen">MOUNT_WAIT=-1</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">UMOUNT_WAIT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for a response from <code class="command">umount</code>. For example:
+ </div><pre class="screen">UMOUNT_WAIT=12</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">BROWSE_MODE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) browsing the maps. For example:
+ </div><pre class="screen">BROWSE_MODE="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOUNT_NFS_DEFAULT_PROTOCOL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default protocol to be used by <code class="command">mount.nfs</code>. For example:
+ </div><pre class="screen">MOUNT_NFS_DEFAULT_PROTOCOL=4</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">APPEND_OPTIONS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) appending the global options instead of replacing them. For example:
+ </div><pre class="screen">APPEND_OPTIONS="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LOGGING=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default logging level. The <em class="replaceable"><code>value</code></em> has to be either <code class="option">none</code>, <code class="option">verbose</code>, or <code class="option">debug</code>. For example:
+ </div><pre class="screen">LOGGING="none"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_URI=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of server URIs in the form of <code class="systemitem"><em class="replaceable"><code>protocol</code></em>://<em class="replaceable"><code>server</code></em> </code>. For example:
+ </div><pre class="screen">LDAP_URI="ldaps://ldap.example.com/"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The synchronous API calls timeout. For example:
+ </div><pre class="screen">LDAP_TIMEOUT=-1</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LDAP_NETWORK_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The network response timeout. For example:
+ </div><pre class="screen">LDAP_NETWORK_TIMEOUT=8</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SEARCH_BASE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The base Distinguished Name (DN) for the map search. For example:
+ </div><pre class="screen">SEARCH_BASE=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">AUTH_CONF_FILE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default location of the SASL authentication configuration file. For example:
+ </div><pre class="screen">AUTH_CONF_FILE="/etc/autofs_ldap_auth.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MAP_HASH_TABLE_SIZE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The hash table size for the map cache. For example:
+ </div><pre class="screen">MAP_HASH_TABLE_SIZE=1024</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">USE_MISC_DEVICE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the autofs miscellaneous device. For example:
+ </div><pre class="screen">USE_MISC_DEVICE="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the LDAP daemon. For example:
+ </div><pre class="screen">OPTIONS=""</pre></dd></dl></div></div><div class="section" title="18.1.4. /etc/sysconfig/clock" id="s2-sysconfig-clock"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-clock">18.1.4. <code class="filename">/etc/sysconfig/clock</code> </h3></div></div></div><a id="id690493" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/clock</code> file controls the interpretation of values read from the system hardware clock. It is used by the <span class="application"><strong>Date/Time Properties</strong></span> tool, and should not be edited by hand. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">ZONE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time zone file under <code class="filename">/usr/share/zoneinfo</code> that <code class="filename">/etc/localtime</code> is a copy of. For example:
+ </div><pre class="screen">ZONE="Europe/Prague"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool" title="13.1. Date/Time Properties Tool">Section 13.1, “Date/Time Properties Tool”</a> for more information on the <span class="application"><strong>Date/Time Properties</strong></span> tool and its usage.
+ </div></div><div class="section" title="18.1.5. /etc/sysconfig/dhcpd" id="s2-sysconfig-dhcpd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-dhcpd">18.1.5. <code class="filename">/etc/sysconfig/dhcpd</code> </h3></div></div></div><a id="id542502" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/dhcpd</code> file is used to pass arguments to the <code class="command">dhcpd</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">DHCPDARGS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">dhcpd</code> daemon. For example:
+ </div><pre class="screen">DHCPDARGS=</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)">Chapter 6, <i>Dynamic Host Configuration Protocol (DHCP)</i></a> for more information on DHCP and its usage.
+ </div></div><div class="section" title="18.1.6. /etc/sysconfig/firstboot" id="s2-sysconfig-firewall"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-firewall">18.1.6. <code class="filename">/etc/sysconfig/firstboot</code> </h3></div></div></div><a id="id542592" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/firstboot</code> file defines whether to run the <code class="command">firstboot</code> utility. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">RUN_FIRSTBOOT=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">YES</code>) or disable (<code class="option">NO</code>) running the <code class="command">firstboot</code> program. For example:
+ </div><pre class="screen">RUN_FIRSTBOOT=NO</pre></dd></dl></div><div class="para">
+ The first time the system boots, the <code class="command">init</code> program calls the <code class="filename">/etc/rc.d/init.d/firstboot</code> script, which looks for the <code class="filename">/etc/sysconfig/firstboot</code> file. If this file does not contain the <code class="option">RUN_FIRSTBOOT=NO</code> option, the <code class="command">firstboot</code> program is run, guiding a user through the initial configuration of the system.
+ </div><div class="note" title="Tip: You Can Run the firstboot Program Again"><div class="admonition_header"><h2>Tip: You Can Run the <code class="command">firstboot</code> Program Again</h2></div><div class="admonition"><div class="para">
+ To start the <code class="command">firstboot</code> program the next time the system boots, change the value of <code class="command">RUN_FIRSTBOOT</code> option to <code class="option">YES</code>, and type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">chkconfig firstboot on</code>
+</pre></div></div></div><div class="section" title="18.1.7. /etc/sysconfig/i18n" id="s2-sysconfig-i18n"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-i18n">18.1.7. <code class="filename">/etc/sysconfig/i18n</code> </h3></div></div></div><div class="para">
+ The <code class="filename">/etc/sysconfig/i18n</code> configuration file defines the default language, any supported languages, and the default system font. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">LANG=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default language. For example:
+ </div><pre class="screen">LANG="en_US.UTF-8"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SUPPORTED=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A colon-separated list of supported languages. For example:
+ </div><pre class="screen">SUPPORTED="en_US.UTF-8:en_US:en"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SYSFONT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default system font. For example:
+ </div><pre class="screen">SYSFONT="latarcyrheb-sun16"</pre></dd></dl></div></div><div class="section" title="18.1.8. /etc/sysconfig/init" id="s2-sysconfig-init"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-init">18.1.8. <code class="filename">/etc/sysconfig/init</code> </h3></div></div></div><a id="id559442" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/init</code> file controls how the system appears and functions during the boot process. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">BOOTUP=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The bootup style. The value has to be either <code class="option">color</code> (the standard color boot display), <code class="option">verbose</code> (an old style display which provides more information), or anything else for the new style display, but without ANSI formatting. For example:
+ </div><pre class="screen">BOOTUP=color</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RES_COL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The number of the column in which the status labels start. For example:
+ </div><pre class="screen">RES_COL=60</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MOVE_TO_COL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to move the cursor to the column specified in <code class="option">RES_COL</code> (see above). For example:
+ </div><pre class="screen">MOVE_TO_COL="echo -en \\033[${RES_COL}G"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_SUCCESS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the success color. For example:
+ </div><pre class="screen">SETCOLOR_SUCCESS="echo -en \\033[0;32m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_FAILURE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the failure color. For example:
+ </div><pre class="screen">SETCOLOR_FAILURE="echo -en \\033[0;31m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_WARNING=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the warning color. For example:
+ </div><pre class="screen">SETCOLOR_WARNING="echo -en \\033[0;33m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SETCOLOR_NORMAL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The terminal sequence to set the default color. For example:
+ </div><pre class="screen">SETCOLOR_NORMAL="echo -en \\033[0;39m"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LOGLEVEL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The initial console logging level. The <em class="replaceable"><code>value</code></em> has to be in the range from <code class="option">1</code> (kernel panics only) to <code class="option">8</code> (everything, including the debugging information). For example:
+ </div><pre class="screen">LOGLEVEL=3</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PROMPT=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the hotkey interactive startup. For example:
+ </div><pre class="screen">PROMPT=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">AUTOSWAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) probing for devices with swap signatures. For example:
+ </div><pre class="screen">AUTOSWAP=no</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ACTIVE_CONSOLES=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The list of active consoles. For example:
+ </div><pre class="screen">ACTIVE_CONSOLES=/dev/tty[1-6]</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SINGLE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The single-user mode type. The <em class="replaceable"><code>value</code></em> has to be either <code class="option">/sbin/sulogin</code> (a user will be prompted for a password to log in), or <code class="option">/sbin/sushell</code> (the user will be logged in directly). For example:
+ </div><pre class="screen">SINGLE=/sbin/sushell</pre></dd></dl></div></div><div class="section" title="18.1.9. /etc/sysconfig/ip6tables-config" id="s2-sysconfig-ip6tables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-ip6tables">18.1.9. <code class="filename">/etc/sysconfig/ip6tables-config</code> </h3></div></div></div><a id="id812429" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ip6tables-config</code> file stores information used by the kernel to set up IPv6 packet filtering at boot time or whenever the <code class="command">ip6tables</code> service is started. Note that you should not modify it unless you are familiar with <code class="command">ip6tables</code> rules. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_MODULES=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of helpers to be loaded after the firewall rules are applied. For example:
+ </div><pre class="screen">IP6TABLES_MODULES="ip_nat_ftp ip_nat_irc"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_MODULES_UNLOAD=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) module unloading when the firewall is stopped or restarted. For example:
+ </div><pre class="screen">IP6TABLES_MODULES_UNLOAD="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_ON_STOP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the current firewall rules when the firewall is stopped. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_ON_STOP="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_ON_RESTART=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the current firewall rules when the firewall is restarted. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_ON_RESTART="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_SAVE_COUNTER=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) saving the rule and chain counters. For example:
+ </div><pre class="screen">IP6TABLES_SAVE_COUNTER="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_NUMERIC=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing IP addresses and port numbers in a numeric format in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_NUMERIC="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_VERBOSE=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing information about the number of packets and bytes in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_VERBOSE="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">IP6TABLES_STATUS_LINENUMBERS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) printing line numbers in the status output. For example:
+ </div><pre class="screen">IP6TABLES_STATUS_LINENUMBERS="yes"</pre></dd></dl></div><div class="para">
+ </div><div class="note" title="Tip: Use the ip6tables Command to Create the Rules"><div class="admonition_header"><h2>Tip: Use the <code class="command">ip6tables</code> Command to Create the Rules</h2></div><div class="admonition"><div class="para">
+ You can create the rules manually using the <code class="command">ip6tables</code> command. Once created, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service ip6tables save</code>
+</pre><div class="para">
+ This will add the rules to <code class="filename">/etc/sysconfig/ip6tables</code>. Once this file exists, any firewall rules saved in it persist through a system reboot or a service restart.
+ </div></div></div></div><div class="section" title="18.1.10. /etc/sysconfig/keyboard" id="s2-sysconfig-kybd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-kybd">18.1.10. <code class="filename">/etc/sysconfig/keyboard</code> </h3></div></div></div><a id="id685310" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/keyboard</code> file controls the behavior of the keyboard. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">KEYTABLE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The name of a keytable file. The files that can be used as keytables start in the <code class="filename">/lib/kbd/keymaps/i386/</code> directory, and branch into different keyboard layouts from there, all labeled <code class="filename"><em class="replaceable"><code>value</code></em>.kmap.gz</code>. The first filename that matches the <code class="option">KEYTABLE</code> setting is used. For example:
+ </div><pre class="screen">KEYTABLE="us"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">MODEL=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard model. For example:
+ </div><pre class="screen">MODEL="pc105+inet"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">LAYOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard layout. For example:
+ </div><pre class="screen">LAYOUT="us"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">KEYBOARDTYPE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keyboard type. Allowed values are <code class="option">pc</code> (a PS/2 keyboard), or <code class="option">sun</code> (a Sun keyboard). For example:
+ </div><pre class="screen">KEYBOARDTYPE="pc"</pre></dd></dl></div></div><div class="section" title="18.1.11. /etc/sysconfig/ldap" id="s2-sysconfig-ldap"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-ldap">18.1.11. <code class="filename">/etc/sysconfig/ldap</code> </h3></div></div></div><a id="id798444" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ldap</code> file holds the basic configuration for the LDAP server. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">slapd</code> daemon. For example:
+ </div><pre class="screen">SLAPD_OPTIONS="-4"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLURPD_OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">slurpd</code> daemon. For example:
+ </div><pre class="screen">SLURPD_OPTIONS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAP=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over TCP (that is, <code class="systemitem">ldap:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAP="yes"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAPI=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over IPC (that is, <code class="systemitem">ldapi:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAPI="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_LDAPS=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) using the LDAP over TLS (that is, <code class="systemitem">ldaps:///</code>). For example:
+ </div><pre class="screen">SLAPD_LDAPS="no"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_URLS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space-separated list of URLs. For example:
+ </div><pre class="screen">SLAPD_URLS="ldapi:///var/lib/ldap_root/ldapi ldapi:/// ldaps:///"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_SHUTDOWN_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for <code class="command">slapd</code> to shut down. For example:
+ </div><pre class="screen">SLAPD_SHUTDOWN_TIMEOUT=3</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SLAPD_ULIMIT_SETTINGS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The parameters to be passed to <code class="command">ulimit</code> before the <code class="command">slapd</code> daemon is started. For example:
+ </div><pre class="screen">SLAPD_ULIMIT_SETTINGS=""</pre></dd></dl></div></div><div class="section" title="18.1.12. /etc/sysconfig/named" id="s2-sysconfig-named"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-named">18.1.12. <code class="filename">/etc/sysconfig/named</code> </h3></div></div></div><a id="id843164" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/named</code> file is used to pass arguments to the <code class="command">named</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">ROOTDIR=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The chroot environment under which the <code class="command">named</code> daemon runs. The <em class="replaceable"><code>value</code></em> has to be a full directory path. For example:
+ </div><pre class="screen">ROOTDIR="/var/named/chroot"</pre><div class="para">
+ Note that the chroot environment has to be configured first (type <code class="command">info chroot</code> at a shell prompt for more information).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">named</code>. For example:
+ </div><pre class="screen">OPTIONS="-6"</pre><div class="para">
+ Note that you should not use the <code class="option">-t</code> option. Instead, use <code class="option">ROOTDIR</code> as described above.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">KEYTAB_FILE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The keytab filename. For example:
+ </div><pre class="screen">KEYTAB_FILE="/etc/named.keytab"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="ch-The_BIND_DNS_Server.html" title="Chapter 10. The BIND DNS Server">Chapter 10, <i>The BIND DNS Server</i></a> for more information on the BIND DNS server and its configuration.
+ </div></div><div class="section" title="18.1.13. /etc/sysconfig/network" id="s2-sysconfig-network"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-network">18.1.13. <code class="filename">/etc/sysconfig/network</code> </h3></div></div></div><a id="id843338" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/network</code> file is used to specify information about the desired network configuration. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">NETWORKING=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) the networking. For example:
+ </div><pre class="screen">NETWORKING=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">HOSTNAME=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The hostname of the machine. For example:
+ </div><pre class="screen">HOSTNAME=penguin.example.com</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">GATEWAY=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The IP address of the network's gateway. For example:
+ </div><pre class="screen">GATEWAY=192.168.1.0</pre></dd></dl></div><div class="warning" title="Warning: Avoid Using Custom Init Scripts"><div class="admonition_header"><h2>Warning: Avoid Using Custom Init Scripts</h2></div><div class="admonition"><div class="para">
+ Do not use custom init scripts to configure network settings. When performing a post-boot network service restart, custom init scripts configuring network settings that are run outside of the network init script lead to unpredictable results.
+ </div></div></div></div><div class="section" title="18.1.14. /etc/sysconfig/ntpd" id="s2-sysconfig-ntpd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-ntpd">18.1.14. <code class="filename">/etc/sysconfig/ntpd</code> </h3></div></div></div><a id="id640620" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/ntpd</code> file is used to pass arguments to the <code class="command">ntpd</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">ntpd</code>. For example:
+ </div><pre class="screen">OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid -g"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Network_Time_Protocol" title="13.1.2. Network Time Protocol Properties">Section 13.1.2, “Network Time Protocol Properties”</a> or <a class="xref" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html" title="13.2.2. Network Time Protocol Setup">Section 13.2.2, “Network Time Protocol Setup”</a> for more information on how to configure the <code class="command">ntpd</code> daemon.
+ </div></div><div class="section" title="18.1.15. /etc/sysconfig/quagga" id="s2-sysconfig-quagga"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-quagga">18.1.15. <code class="filename">/etc/sysconfig/quagga</code> </h3></div></div></div><a id="id776182" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/quagga</code> file holds the basic configuration for Quagga daemons. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">QCONFDIR=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The directory with the configuration files for Quagga daemons. For example:
+ </div><pre class="screen">QCONFDIR="/etc/quagga"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">BGPD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">bgpd</code> daemon. For example:
+ </div><pre class="screen">BGPD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/bgpd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OSPF6D_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ospf6d</code> daemon. For example:
+ </div><pre class="screen">OSPF6D_OPTS="-A ::1 -f ${QCONFDIR}/ospf6d.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">OSPFD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ospfd</code> daemon. For example:
+ </div><pre class="screen">OSPFD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/ospfd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RIPD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ripd</code> daemon. For example:
+ </div><pre class="screen">RIPD_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/ripd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">RIPNGD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">ripngd</code> daemon. For example:
+ </div><pre class="screen">RIPNGD_OPTS="-A ::1 -f ${QCONFDIR}/ripngd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ZEBRA_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">zebra</code> daemon. For example:
+ </div><pre class="screen">ZEBRA_OPTS="-A 127.0.0.1 -f ${QCONFDIR}/zebra.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ISISD_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">isisd</code> daemon. For example:
+ </div><pre class="screen">ISISD_OPTS="-A ::1 -f ${QCONFDIR}/isisd.conf"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WATCH_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">watchquagga</code> daemon. For example:
+ </div><pre class="screen">WATCH_OPTS="-Az -b_ -r/sbin/service_%s_restart -s/sbin/service_%s_start -k/sbin/service_%s_stop"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WATCH_DAEMONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A space separated list of monitored daemons. For example:
+ </div><pre class="screen">WATCH_DAEMONS="zebra bgpd ospfd ospf6d ripd ripngd"</pre></dd></dl></div></div><div class="section" title="18.1.16. /etc/sysconfig/radvd" id="s2-sysconfig-radvd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-radvd">18.1.16. <code class="filename">/etc/sysconfig/radvd</code> </h3></div></div></div><a id="id469186" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/radvd</code> file is used to pass arguments to the <code class="command">radvd</code> daemon at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">OPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">radvd</code> daemon. For example:
+ </div><pre class="screen">OPTIONS="-u radvd"</pre></dd></dl></div></div><div class="section" title="18.1.17. /etc/sysconfig/samba" id="s2-sysconfig-samba"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-samba">18.1.17. <code class="filename">/etc/sysconfig/samba</code> </h3></div></div></div><a id="id485036" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/samba</code> file is used to pass arguments to the Samba daemons at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">SMBDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">smbd</code>. For example:
+ </div><pre class="screen">SMBDOPTIONS="-D"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">NMBDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">nmbd</code>. For example:
+ </div><pre class="screen">NMBDOPTIONS="-D"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">WINBINDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">winbindd</code>. For example:
+ </div><pre class="screen">WINBINDOPTIONS=""</pre></dd></dl></div></div><div class="section" title="18.1.18. /etc/sysconfig/selinux" id="s2-sysconfig-selinux"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-selinux">18.1.18. <code class="filename">/etc/sysconfig/selinux</code> </h3></div></div></div><a id="id485184" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/selinux</code> file contains the basic configuration options for SELinux. It is a symbolic link to <code class="filename">/etc/selinux/config</code>, and by default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">SELINUX=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The security policy. The <em class="replaceable"><code>value </code></em> can be either <code class="option">enforcing</code> (the security policy is always enforced), <code class="option">permissive</code> (instead of enforcing the policy, appropriate warnings are displayed), or <code class="option">disabled</code> (no policy is used). For example:
+ </div><pre class="screen">SELINUX=enforcing</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SELINUXTYPE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The protection type. The <em class="replaceable"><code>value</code></em> can be either <code class="option">targeted</code> (the targeted processes are protected), or <code class="option">mls</code> (the Multi Level Security protection). For example:
+ </div><pre class="screen">SELINUXTYPE=targeted</pre></dd></dl></div></div><div class="section" title="18.1.19. /etc/sysconfig/sendmail" id="s2-sysconfig-sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-sendmail">18.1.19. <code class="filename">/etc/sysconfig/sendmail</code> </h3></div></div></div><a id="id706525" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/sendmail</code> is used to set the default values for the <span class="application"><strong>Sendmail</strong></span> application. By default, it contains the following values:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">DAEMON=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">yes</code>) or disable (<code class="option">no</code>) running <code class="command">sendmail</code> as a daemon. For example:
+ </div><pre class="screen">DAEMON=yes</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">QUEUE=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The interval at which the messages are to be processed. For example:
+ </div><pre class="screen">QUEUE=1h</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="s2-email-mta-sendmail.html" title="12.3.2. Sendmail">Section 12.3.2, “Sendmail”</a> for more information on Sendmail and its configuration.
+ </div></div><div class="section" title="18.1.20. /etc/sysconfig/spamassassin" id="s2-sysconfig-spamd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-spamd">18.1.20. <code class="filename">/etc/sysconfig/spamassassin</code> </h3></div></div></div><a id="id740746" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/spamassassin</code> file is used to pass arguments to the <code class="command">spamd</code> daemon (a daemonized version of <span class="application"><strong>Spamassassin</strong></span>) at boot time. By default, it contains the following option:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">SPAMDOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">spamd</code> daemon. For example:
+ </div><pre class="screen">SPAMDOPTIONS="-d -c -m5 -H"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="s2-email-procmail-recipes.html#s3-email-mda-spam" title="12.4.2.6. Spam Filters">Section 12.4.2.6, “Spam Filters”</a> for more information on Spamassassin and its configuration.
+ </div></div><div class="section" title="18.1.21. /etc/sysconfig/squid" id="s2-sysconfig-squid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-squid">18.1.21. <code class="filename">/etc/sysconfig/squid</code> </h3></div></div></div><a id="id740844" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/squid</code> file is used to pass arguments to the <code class="command">squid</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">SQUID_OPTS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to the <code class="command">squid</code> daemon. For example:
+ </div><pre class="screen">SQUID_OPTS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SQUID_SHUTDOWN_TIMEOUT=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The time to wait for <code class="command">squid</code> daemon to shut down. For example:
+ </div><pre class="screen">SQUID_SHUTDOWN_TIMEOUT=100</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">SQUID_CONF=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The default configuration file. For example:
+ </div><pre class="screen">SQUID_CONF="/etc/squid/squid.conf"</pre></dd></dl></div></div><div class="section" title="18.1.22. /etc/sysconfig/system-config-users" id="s2-sysconfig-rcu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-rcu">18.1.22. <code class="filename">/etc/sysconfig/system-config-users</code> </h3></div></div></div><a id="id489369" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/system-config-users</code> file is the configuration file for the <span class="application"><strong>User Manager</strong></span> utility, and should not be edited by hand. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">FILTER=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) filtering of system users. For example:
+ </div><pre class="screen">FILTER=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ASSIGN_HIGHEST_UID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) assigning the highest available UID to newly added users. For example:
+ </div><pre class="screen">ASSIGN_HIGHEST_UID=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">ASSIGN_HIGHEST_GID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) assigning the highest available GID to newly added groups. For example:
+ </div><pre class="screen">ASSIGN_HIGHEST_GID=true</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">PREFER_SAME_UID_GID=<em class="replaceable"><code>boolean</code></em> </code> </span></dt><dd><div class="para">
+ A boolean to enable (<code class="option">true</code>) or disable (<code class="option">false</code>) using the same UID and GID for newly added users when possible. For example:
+ </div><pre class="screen">PREFER_SAME_UID_GID=true</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="Users_and_Groups.html#s1-users-configui" title="15.1. User and Group Configuration">Section 15.1, “User and Group Configuration”</a> for more information on <span class="application"><strong>User Manager</strong></span> and its usage.
+ </div></div><div class="section" title="18.1.23. /etc/sysconfig/vncservers" id="s2-sysconfig-vncservers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-vncservers">18.1.23. <code class="filename">/etc/sysconfig/vncservers</code> </h3></div></div></div><a id="id693878" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/vncservers</code> file configures the way the <em class="firstterm">Virtual Network Computing</em> (<em class="firstterm">VNC</em>) server starts up. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">VNCSERVERS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ A list of space separated <code class="option"><em class="replaceable"><code>display</code></em>:<em class="replaceable"><code>username</code></em> </code> pairs. For example:
+ </div><pre class="screen">VNCSERVERS="2:myusername"</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">VNCSERVERARGS[<em class="replaceable"><code>display</code></em>]=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional arguments to be passed to the VNC server running on the specified <em class="replaceable"><code>display</code></em>. For example:
+ </div><pre class="screen">VNCSERVERARGS[2]="-geometry 800x600 -nolisten tcp -localhost"</pre></dd></dl></div></div><div class="section" title="18.1.24. /etc/sysconfig/xinetd" id="s2-sysconfig-xinetd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-xinetd">18.1.24. <code class="filename">/etc/sysconfig/xinetd</code> </h3></div></div></div><a id="id694008" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/sysconfig/xinetd</code> file is used to pass arguments to the <code class="command">xinetd</code> daemon at boot time. By default, it contains the following options:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="option">EXTRAOPTIONS=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ Additional options to be passed to <code class="command">xinetd</code>. For example:
+ </div><pre class="screen">EXTRAOPTIONS=""</pre></dd><dt class="varlistentry"><span class="term"> <code class="option">XINETD_LANG=<em class="replaceable"><code>value</code></em> </code> </span></dt><dd><div class="para">
+ The locale information to be passed to every service started by <code class="command">xinetd</code>. Note that to remove locale information from the <code class="command">xinetd</code> environment, you can use an empty string (<code class="option">""</code>) or <code class="option">none</code>. For example:
+ </div><pre class="screen">XINETD_LANG="en_US"</pre></dd></dl></div><div class="para">
+ Refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for more information on how to configure the <code class="command">xinetd</code> services.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-log-files-useful-websites.html"><strong>Prev</strong>17.7.2. Useful Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-sysconfig-etcsysconf-dir.html"><strong>Next</strong>18.2. Directories in the /etc/sysconfig/ Directory</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Working_with_Kernel_Modules.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Working_with_Kernel_Modules.html
new file mode 100644
index 0000000..e39430a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-Working_with_Kernel_Modules.html
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 22. Working with Kernel Modules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-kernel-configuration.html" title="Part V. Kernel, Module and Driver Configuration" /><link rel="prev" href="pt-kernel-configuration.html" title="Part V. Kernel, Module and Driver Configuration" /><link rel="next" href="sec-Displaying_Information_About_a_Module.html" title="22.2. Displaying Information About a Module" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href=
"pt-kernel-configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Displaying_Information_About_a_Module.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 22. Working with Kernel Modules" id="ch-Working_with_Kernel_Modules" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 22. Working with Kernel Modules</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="sec-Displaying_Information_About_a_Module.html">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="sec-Loading_a_Module.html">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="sec-Unloading_a_Module.html">22.4. Unloading a Module</a></span></dt><dt><span class="sectio
n"><a href="sec-Setting_Module_Parameters.html">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="sec-Persistent_Module_Loading.html">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="sec-Specific_Kernel_Module_Capabilities.html">22.7. Specific Kernel Module Capabilities</a></span></dt><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">22.8. Additional Resources</a></span></dt></dl></div><a id="id464232" class="indexterm"></a><a id="id760287" class="indexterm"></a><a id="id601144" class="indexterm"></a><div class="para">
+ The Linux kernel is modular, which means it can extend its capabilities through the use of dynamically-loaded <em class="firstterm">kernel modules</em>. A Kernel module can provide:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ a device driver which adds support for new hardware; or,
+ </div></li><li class="listitem"><div class="para">
+ support for a file system such as <code class="systemitem">btrfs</code> or<code class="systemitem">NFS</code>.
+ </div></li></ul></div><div class="para">
+ Like the kernel itself, modules can take parameters that customize their behavior, though the default parameters work well in most cases. User-space tools can list the modules currently loaded into a running kernel; query all available modules for available parameters and module-specific information; and load or unload (remove) modules dynamically into or from a running kernel. Many of these utilities, which are provided by the <span class="package">module-init-tools</span> package, take module dependencies into account when performing operations so that manual dependency-tracking is rarely necessary.
+ </div><div class="para">
+ On modern systems, kernel modules are automatically loaded by various mechanisms when the conditions call for it. However, there are occasions when it is necessary to load and/or unload modules manually, such as when a module provides optional functionality, one module should be preferred over another although either could provide basic functionality, or when a module is misbehaving, among other situations.
+ </div><div class="para">
+ This chapter explains how to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ use the user-space <span class="package">module-init-tools</span> package to display, query, load and unload kernel modules and their dependencies;
+ </div></li><li class="listitem"><div class="para">
+ set module parameters both dynamically on the command line and permanently so that you can customize the behavior of your kernel modules; and,
+ </div></li><li class="listitem"><div class="para">
+ load modules at boot time.
+ </div></li></ul></div><div class="note" title="Note: Installing the module-init-tools package"><div class="admonition_header"><h2>Note: Installing the module-init-tools package</h2></div><div class="admonition"><div class="para">
+ In order to use the kernel module utilities described in this chapter, first ensure the module-init-tools package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install module-init-tools</code>
+</pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="section" title="22.1. Listing Currently-Loaded Modules" id="sec-Listing_Currently-Loaded_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</h2></div></div></div><a id="id851068" class="indexterm"></a><a id="id859059" class="indexterm"></a><a id="id859079" class="indexterm"></a><div class="para">
+ You can list all kernel modules that are currently loaded into the kernel by running the <code class="command">lsmod</code> command:
+ </div><pre class="screen">
+~]$ <code class="command">lsmod</code>
+Module Size Used by
+xfs 803635 1
+exportfs 3424 1 xfs
+vfat 8216 1
+fat 43410 1 vfat
+tun 13014 2
+fuse 54749 2
+ip6table_filter 2743 0
+ip6_tables 16558 1 ip6table_filter
+ebtable_nat 1895 0
+ebtables 15186 1 ebtable_nat
+ipt_MASQUERADE 2208 6
+iptable_nat 5420 1
+nf_nat 19059 2 ipt_MASQUERADE,iptable_nat
+rfcomm 65122 4
+ipv6 267017 33
+sco 16204 2
+bridge 45753 0
+stp 1887 1 bridge
+llc 4557 2 bridge,stp
+bnep 15121 2
+l2cap 45185 16 rfcomm,bnep
+cpufreq_ondemand 8420 2
+acpi_cpufreq 7493 1
+freq_table 3851 2 cpufreq_ondemand,acpi_cpufreq
+usb_storage 44536 1
+sha256_generic 10023 2
+aes_x86_64 7654 5
+aes_generic 27012 1 aes_x86_64
+cbc 2793 1
+dm_crypt 10930 1
+kvm_intel 40311 0
+kvm 253162 1 kvm_intel
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em>
+</pre><div class="para">
+ Each row of <code class="command">lsmod</code> output specifies:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ the name of a kernel module currently loaded in memory;
+ </div></li><li class="listitem"><div class="para">
+ the amount of memory it uses; and,
+ </div></li><li class="listitem"><div class="para">
+ the sum total of processes that are using the module and other modules which depend on it, followed by a list of the names of those modules, if there are any. Using this list, you can first unload all the modules depending the module you want to unload. For more information, refer to <a class="xref" href="sec-Unloading_a_Module.html" title="22.4. Unloading a Module">Section 22.4, “Unloading a Module”</a>.
+ </div></li></ul></div><a id="id705818" class="indexterm"></a><div class="para">
+ Finally, note that <code class="command">lsmod</code> output is less verbose and considerably easier to read than the content of the <code class="filename">/proc/modules</code> pseudo-file.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-kernel-configuration.html"><strong>Prev</strong>Part V. Kernel, Module and Driver Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Displaying_Information_About_a_Module.html"><strong>Next</strong>22.2. Displaying Information About a Module</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-abrt.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-abrt.html
new file mode 100644
index 0000000..9947ecc
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-abrt.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 21. ABRT</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-system-monitoring.html" title="Part IV. System Monitoring" /><link rel="prev" href="s1-sysinfo-additional-resources.html" title="20.5. Additional Resources" /><link rel="next" href="ch21s02.html" title="21.2. Installing and Running ABRT" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-additional-resources.html"><strong>Prev</strong></a></li><li class="ne
xt"><a accesskey="n" href="ch21s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 21. ABRT" id="ch-abrt" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. ABRT</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-abrt.html#id544620">21.1. Overview</a></span></dt><dt><span class="section"><a href="ch21s02.html">21.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="abrt-plugins.html">21.3. <span class="application"><strong>ABRT</strong></span> Plugins</a></span></dt><dt><span class="section"><a href="generating-backtrace.html">21.4. Generating Backtraces</a></span></dt><dt><span class="section"><a href="ch21s05.html">21.5. Using the Command Line Interface</a></span></dt><dt><span class="section"><a href="configuring.html">21.6. Configuring ABRT</a></span></dt><dt><span class="section"><a href="configuring-centralized-crash-collection.html">21.
7. Configuring Centralized Crash Collection</a></span></dt></dl></div><div class="section" title="21.1. Overview"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id544620">21.1. Overview</h2></div></div></div><div class="para">
+ <span class="application"><strong>ABRT</strong></span> is the <span class="application"><strong>Automatic Bug-Reporting Tool</strong></span>. <span class="application"><strong>ABRT</strong></span> consists of a daemon that runs silently in the background most of the time. It springs into action when an application crashes. It then collects the relevant crash data such as a core file if there is one, the crashing application's command line parameters, and other contextual puzzle pieces of forensic utility. Finally, <span class="application"><strong>ABRT</strong></span> is capable of reporting crash data to a relevant issue tracker, such as RHTSupport. Reporting crash data to a relevant issue tracker can be configured to happen automatically at every detected crash, or crash dumps can be stored locally, reviewed, reported, and deleted manually by a user. <span class="application"><strong>ABRT</strong></span>'s various plugins analyze crash data from applications written in
the C, C++ and Python language, as well as report crashes to relevant issue trackers.
+ </div><div class="para">
+ The <span class="application"><strong>ABRT</strong></span> package consists of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">abrtd</code>, the system service
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>abrt-applet</strong></span>, which runs in the user's Notification Area
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>abrt-gui</strong></span>, the GUI application that shows collected crash dumps and allows you to edit, report, and delete them
+ </div></li><li class="listitem"><div class="para">
+ <span class="application"><strong>abrt-cli</strong></span>, the command line interface with functionality similar to <span class="application"><strong>abrt-gui</strong></span>.
+ </div></li></ul></div><div class="para">
+ You can open the <span class="application"><strong>ABRT</strong></span> GUI application by clicking <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Automatic Bug Reporting Tool</strong></span>.
+ </div><div class="mediaobject" align="center"><img src="images/ABRT-Main_Window.png" align="middle" /><div class="caption"><div class="para">
+ Automatic Bug Reporting Tool Main Window
+ </div></div></div><div class="para">
+ A number of additional packages can be installed to provide <span class="application"><strong>ABRT</strong></span> plugins and addons. To view all the available <span class="application"><strong>ABRT</strong></span> packages, type the following command:
+<pre class="screen">
+<code class="command">~]$ yum list all | grep abrt</code>
+</pre>
+
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-additional-resources.html"><strong>Prev</strong>20.5. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch21s02.html"><strong>Next</strong>21.2. Installing and Running ABRT</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-email.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-email.html
new file mode 100644
index 0000000..76851a2
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-email.html
@@ -0,0 +1,103 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 12. Email</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /><link rel="prev" href="s2-apache-resources-web.html" title="11.7.2. Useful Websites" /><link rel="next" href="s1-email-types.html" title="12.2. Email Program Classifications" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-resources-web.html"><strong>Prev</strong></a></li><li cl
ass="next"><a accesskey="n" href="s1-email-types.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 12. Email" id="ch-email" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 12. Email</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-email.html#s1-email-protocols">12.1. Email Protocols</a></span></dt><dt><span class="section"><a href="s1-email-types.html">12.2. Email Program Classifications</a></span></dt><dt><span class="section"><a href="s1-email-mta.html">12.3. Mail Transport Agents</a></span></dt><dt><span class="section"><a href="s1-email-mda.html">12.4. Mail Delivery Agents</a></span></dt><dt><span class="section"><a href="s1-email-mua.html">12.5. Mail User Agents</a></span></dt><dt><span class="section"><a href="s1-email-additional-resources.html">12.6. Additional Resources</a></span></dt></dl></div><a id="id584396" class="indexterm"></a><div class="para">
+ <em class="firstterm">Email</em> was born in the 1960s. The mailbox was a file in a user's home directory that was readable only by that user. Primitive mail applications appended new text messages to the bottom of the file, making the user wade through the constantly growing file to find any particular message. This system was only capable of sending messages to users on the same system.
+ </div><div class="para">
+ The first network transfer of an electronic mail message file took place in 1971 when a computer engineer named Ray Tomlinson sent a test message between two machines via ARPANET—the precursor to the Internet. Communication via email soon became very popular, comprising 75 percent of ARPANET's traffic in less than two years.
+ </div><div class="para">
+ Today, email systems based on standardized network protocols have evolved into some of the most widely used services on the Internet. Fedora offers many advanced applications to serve and access email.
+ </div><div class="para">
+ This chapter reviews modern email protocols in use today, and some of the programs designed to send and receive email.
+ </div><div class="section" title="12.1. Email Protocols" id="s1-email-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-protocols">12.1. Email Protocols</h2></div></div></div><a id="id559260" class="indexterm"></a><div class="para">
+ Today, email is delivered using a client/server architecture. An email message is created using a mail client program. This program then sends the message to a server. The server then forwards the message to the recipient's email server, where the message is then supplied to the recipient's email client.
+ </div><div class="para">
+ To enable this process, a variety of standard network protocols allow different machines, often running different operating systems and using different email programs, to send and receive email.
+ </div><div class="para">
+ The following protocols discussed are the most commonly used in the transfer of email.
+ </div><div class="section" title="12.1.1. Mail Transport Protocols" id="s2-email-protocols-send"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-protocols-send">12.1.1. Mail Transport Protocols</h3></div></div></div><div class="para">
+ Mail delivery from a client application to the server, and from an originating server to the destination server, is handled by the <em class="firstterm">Simple Mail Transfer Protocol</em> (<em class="firstterm">SMTP</em>).
+ </div><div class="section" title="12.1.1.1. SMTP" id="s3-email-protocols-smtp"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-protocols-smtp">12.1.1.1. SMTP</h4></div></div></div><a id="id836064" class="indexterm"></a><div class="para">
+ The primary purpose of SMTP is to transfer email between mail servers. However, it is critical for email clients as well. To send email, the client sends the message to an outgoing mail server, which in turn contacts the destination mail server for delivery. For this reason, it is necessary to specify an SMTP server when configuring an email client.
+ </div><div class="para">
+ Under Fedora, a user can configure an SMTP server on the local machine to handle mail delivery. However, it is also possible to configure remote SMTP servers for outgoing mail.
+ </div><div class="para">
+ One important point to make about the SMTP protocol is that it does not require authentication. This allows anyone on the Internet to send email to anyone else or even to large groups of people. It is this characteristic of SMTP that makes junk email or <em class="firstterm">spam</em> possible. Imposing relay restrictions limits random users on the Internet from sending email through your SMTP server, to other servers on the internet. Servers that do not impose such restrictions are called <em class="firstterm">open relay</em> servers.
+ </div><div class="para">
+ Fedora provides the Postfix and Sendmail SMTP programs.
+ </div></div></div><div class="section" title="12.1.2. Mail Access Protocols" id="s2-email-protocols-client"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-protocols-client">12.1.2. Mail Access Protocols</h3></div></div></div><div class="para">
+ There are two primary protocols used by email client applications to retrieve email from mail servers: the <em class="firstterm">Post Office Protocol</em> (<em class="firstterm">POP</em>) and the <em class="firstterm">Internet Message Access Protocol</em> (<em class="firstterm">IMAP</em>).
+ </div><div class="section" title="12.1.2.1. POP" id="s3-email-protocols-pop"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-protocols-pop">12.1.2.1. POP</h4></div></div></div><a id="id418018" class="indexterm"></a><div class="para">
+ The default POP server under Fedora is <span class="application"><strong>Dovecot</strong></span> and is provided by the <span class="package">dovecot</span> package.
+ </div><div class="note" title="Note: Installing the dovecot package"><div class="admonition_header"><h2>Note: Installing the <span class="package">dovecot</span> package</h2></div><div class="admonition"><div class="para">
+ In order to use <span class="application"><strong>Dovecot</strong></span>, first ensure the <code class="command">dovecot</code> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install dovecot</code>
+</pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ When using a <code class="systemitem">POP</code> server, email messages are downloaded by email client applications. By default, most <code class="systemitem">POP</code> email clients are automatically configured to delete the message on the email server after it has been successfully transferred, however this setting usually can be changed.
+ </div><div class="para">
+ <code class="systemitem">POP</code> is fully compatible with important Internet messaging standards, such as <em class="firstterm">Multipurpose Internet Mail Extensions</em> (<em class="firstterm">MIME</em>), which allow for email attachments.
+ </div><div class="para">
+ <code class="systemitem">POP</code> works best for users who have one system on which to read email. It also works well for users who do not have a persistent connection to the Internet or the network containing the mail server. Unfortunately for those with slow network connections, <code class="systemitem">POP</code> requires client programs upon authentication to download the entire content of each message. This can take a long time if any messages have large attachments.
+ </div><div class="para">
+ The most current version of the standard <code class="systemitem">POP</code> protocol is <code class="systemitem">POP3</code>.
+ </div><div class="para">
+ There are, however, a variety of lesser-used <code class="systemitem">POP</code> protocol variants:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>APOP</em></span> — <code class="systemitem">POP3</code> with <code class="systemitem">MDS</code> (Monash Directory Service) authentication. An encoded hash of the user's password is sent from the email client to the server rather then sending an unencrypted password.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>KPOP</em></span> — <code class="systemitem">POP3</code> with Kerberos authentication.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>RPOP</em></span> — <code class="systemitem">POP3</code> with <code class="systemitem">RPOP</code> authentication. This uses a per-user ID, similar to a password, to authenticate POP requests. However, this ID is not encrypted, so <code class="systemitem">RPOP</code> is no more secure than standard <code class="systemitem">POP</code>.
+ </div></li></ul></div><div class="para">
+ For added security, it is possible to use <em class="firstterm">Secure Socket Layer</em> (<em class="firstterm">SSL</em>) encryption for client authentication and data transfer sessions. This can be enabled by using the <code class="command">pop3s</code> service, or by using the <code class="command">/usr/sbin/stunnel</code> application. For more information on securing email communication, refer to <a class="xref" href="s1-email-mua.html#s2-email-security" title="12.5.1. Securing Communication">Section 12.5.1, “Securing Communication”</a>.
+ </div></div><div class="section" title="12.1.2.2. IMAP" id="s3-email-protocols-imap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-protocols-imap">12.1.2.2. IMAP</h4></div></div></div><a id="id792730" class="indexterm"></a><div class="para">
+ The default <code class="systemitem">IMAP</code> server under Fedora is <span class="application"><strong>Dovecot</strong></span> and is provided by the <span class="package">dovecot</span> package. Refer to <a class="xref" href="ch-email.html#s3-email-protocols-pop" title="12.1.2.1. POP">Section 12.1.2.1, “POP”</a> for information on how to install <span class="application"><strong>Dovecot</strong></span>.
+ </div><div class="para">
+ When using an <code class="systemitem">IMAP</code> mail server, email messages remain on the server where users can read or delete them. <code class="systemitem">IMAP</code> also allows client applications to create, rename, or delete mail directories on the server to organize and store email.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code> is particularly useful for users who access their email using multiple machines. The protocol is also convenient for users connecting to the mail server via a slow connection, because only the email header information is downloaded for messages until opened, saving bandwidth. The user also has the ability to delete messages without viewing or downloading them.
+ </div><div class="para">
+ For convenience, <code class="systemitem">IMAP</code> client applications are capable of caching copies of messages locally, so the user can browse previously read messages when not directly connected to the <code class="systemitem">IMAP</code> server.
+ </div><div class="para">
+ <code class="systemitem">IMAP</code>, like <code class="systemitem">POP</code>, is fully compatible with important Internet messaging standards, such as MIME, which allow for email attachments.
+ </div><div class="para">
+ For added security, it is possible to use <code class="systemitem">SSL</code> encryption for client authentication and data transfer sessions. This can be enabled by using the <code class="command">imaps</code> service, or by using the <code class="command">/usr/sbin/stunnel</code> program. For more information on securing email communication, refer to <a class="xref" href="s1-email-mua.html#s2-email-security" title="12.5.1. Securing Communication">Section 12.5.1, “Securing Communication”</a>.
+ </div><div class="para">
+ Other free, as well as commercial, IMAP clients and servers are available, many of which extend the IMAP protocol and provide additional functionality.
+ </div></div><div class="section" title="12.1.2.3. Dovecot" id="s3-mail-server-dovecot"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-mail-server-dovecot">12.1.2.3. Dovecot</h4></div></div></div><a id="id485995" class="indexterm"></a><div class="para">
+ The <code class="command">imap-login</code> and <code class="command">pop3-login</code> processes which implement the <code class="systemitem">IMAP</code> and <code class="systemitem">POP3</code> protocols are spawned by the master <code class="systemitem">dovecot</code> daemon included in the <span class="package">dovecot</span> package. The use of <code class="systemitem">IMAP</code> and <code class="systemitem">POP</code> is configured through the <code class="filename">/etc/dovecot/dovecot.conf</code> configuration file; by default <code class="command">dovecot</code> runs <code class="systemitem">IMAP</code> and <code class="systemitem">POP3</code> together with their secure versions using <code class="systemitem">SSL</code>. To configure <code class="command">dovecot</code> to use <code class="systemitem">POP</code>, complete the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/dovecot/dovecot.conf</code> configuration file to make sure the <code class="literal">protocols</code> variable is uncommented (remove the hash sign (<code class="command">#</code>) at the beginning of the line) and contains the <code class="literal">pop3</code> argument. For example:
+ </div><pre class="screen">protocols = imap imaps pop3 pop3s
+</pre><div class="para">
+ When the <code class="literal">protocols</code> variable is left commented out, <code class="command">dovecot</code> will use the default values specified for this variable.
+ </div></li><li class="listitem"><div class="para">
+ Make that change operational for the current session by running the following command:
+ </div><pre class="screen">~]# <code class="command">service dovecot restart</code>
+</pre></li><li class="listitem"><div class="para">
+ Make that change operational after the next reboot by running the command:
+ </div><pre class="screen">~]# <code class="command">chkconfig dovecot on</code>
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Please note that <code class="command">dovecot</code> only reports that it started the <code class="systemitem">IMAP</code> server, but also starts the <code class="systemitem">POP3</code> server.
+ </div></div></div></li></ol></div><div class="para">
+ Unlike <code class="systemitem">SMTP</code>, both <code class="systemitem">IMAP</code> and <code class="systemitem">POP3</code> require connecting clients to authenticate using a username and password. By default, passwords for both protocols are passed over the network unencrypted.
+ </div><div class="para">
+ To configure <code class="systemitem">SSL</code> on <code class="command">dovecot</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/pki/dovecot/dovecot-openssl.conf</code> configuration file as you prefer. However, in a typical installation, this file does not require modification.
+ </div></li><li class="listitem"><div class="para">
+ Rename, move or delete the files <code class="filename">/etc/pki/dovecot/certs/dovecot.pem</code> and <code class="filename">/etc/pki/dovecot/private/dovecot.pem</code>.
+ </div></li><li class="listitem"><div class="para">
+ Execute the <code class="filename">/usr/libexec/dovecot/mkcert.sh</code> script which creates the <code class="command">dovecot</code> self signed certificates. These certificates are copied in the <code class="filename">/etc/pki/dovecot/certs</code> and <code class="filename">/etc/pki/dovecot/private</code> directories. To implement the changes, restart <code class="command">dovecot</code>:
+ </div><pre class="screen">~]# <code class="command">service dovecot restart</code>
+</pre></li></ul></div><div class="para">
+ More details on <code class="command">dovecot</code> can be found online at <a href="http://www.dovecot.org">http://www.dovecot.org</a>.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-resources-web.html"><strong>Prev</strong>11.7.2. Useful Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-email-types.html"><strong>Next</strong>12.2. Email Program Classifications</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-intro.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-intro.html
new file mode 100644
index 0000000..0b65814
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-intro.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Introduction</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="Acknowledgements.html" title="3. Acknowledgements" /><link rel="next" href="pt-pkg-management.html" title="Part I. Package Management" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Acknowledgements.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt-pkg-management.html"><strong>N
ext</strong></a></li></ul><div xml:lang="en-US" class="preface" title="Introduction" id="ch-intro" lang="en-US"><div class="titlepage"><div><div><h1 class="title">Introduction</h1></div></div></div><a id="id841674" class="indexterm"></a><div class="para">
+ Welcome to the <em class="citetitle">Fedora 14 Deployment Guide</em>.
+ </div><div class="para">
+ The <em class="citetitle">Deployment Guide</em> contains information on how to customize your Fedora 14 system to fit your needs. If you are looking for a comprehensive, task-oriented guide for configuring and customizing your system, this is the manual for you.
+ </div><div class="para">
+ This manual discusses many intermediate topics such as the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Installing and managing packages using the graphical <span class="application"><strong>PackageKit</strong></span> and command line <span class="application"><strong>Yum</strong></span> package managers
+ </div></li><li class="listitem"><div class="para">
+ Setting up a network—from establishing an Ethernet connection using <span class="application"><strong>NetworkManager</strong></span> to configuring channel bonding interfaces to increase server bandwidth
+ </div></li><li class="listitem"><div class="para">
+ Configuring <code class="systemitem">DHCP</code>, <span class="application"><strong>BIND</strong></span>, <span class="application"><strong>Apache</strong></span>, <span class="application"><strong>Postfix</strong></span>, <span class="application"><strong>Sendmail</strong></span> and other enterprise-class servers and software
+ </div></li><li class="listitem"><div class="para">
+ Gathering information about your system, including obtaining user-space crash data with the <span class="application"><strong>Automatic Bug Reporting Tool</strong></span>, and kernel-space crash data with <code class="systemitem">kdump</code>
+ </div></li><li class="listitem"><div class="para">
+ Easily working with kernel modules and upgrading the kernel
+ </div></li></ul></div><div class="para">
+ This manual is divided into the following main categories:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a class="xref" href="pt-pkg-management.html" title="Part I. Package Management">Part I, “Package Management”</a>
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="pt-network-related-config.html" title="Part II. Network-Related Configuration">Part II, “Network-Related Configuration”</a>
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="pt-sysconfig.html" title="Part III. System Configuration">Part III, “System Configuration”</a>
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="pt-system-monitoring.html" title="Part IV. System Monitoring">Part IV, “System Monitoring”</a>
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="pt-kernel-configuration.html" title="Part V. Kernel, Module and Driver Configuration">Part V, “Kernel, Module and Driver Configuration”</a>
+ </div></li></ul></div><div class="para">
+ This guide assumes you have a basic understanding of your Fedora system. If you need help installing Fedora, refer to the <em class="citetitle">Fedora 14 Installation Guide</em>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Acknowledgements.html"><strong>Prev</strong>3. Acknowledgements</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pt-pkg-management.html"><strong>Next</strong>Part I. Package Management</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-kdump.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-kdump.html
new file mode 100644
index 0000000..9beda5e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-kdump.html
@@ -0,0 +1,197 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 24. The kdump Crash Recovery Service</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-kernel-configuration.html" title="Part V. Kernel, Module and Driver Configuration" /><link rel="prev" href="s2-kernel-boot-loader-pseries.html" title="23.6.3. Configuring the YABOOT Boot Loader" /><link rel="next" href="s1-kdump-crash.html" title="24.2. Analyzing the Core Dump" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kernel-boot-loader-pseries.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kdump-crash.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 24. The kdump Crash Recovery Service" id="ch-kdump" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 24. The <code class="systemitem">kdump</code> Crash Recovery Service</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-kdump.html#s1-kdump-configuration">24.1. Configuring the <code class="systemitem">kdump</code> Service</a></span></dt><dt><span class="section"><a href="s1-kdump-crash.html">24.2. Analyzing the Core Dump</a></span></dt><dt><span class="section"><a href="s1-kdump-resources.html">24.3. Additional Resources</a></span></dt></dl></div><div class="para">
+ <code class="systemitem">kdump</code> is an advanced crash dumping mechanism. When enabled, the system is booted from the context of another kernel. This second kernel reserves a small amount of memory, and its only purpose is to capture the core dump image in case the system crashes. Since being able to analyze the core dump helps significantly to determine the exact cause of the system failure, it is strongly recommended to have this feature enabled.
+ </div><div class="para">
+ This chapter explains how to configure, test, and use the <code class="systemitem">kdump</code> service in Fedora, and provides a brief overview of how to analyze the resulting core dump using the <span class="application"><strong>crash</strong></span> debugging utility.
+ </div><div class="section" title="24.1. Configuring the kdump Service" id="s1-kdump-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kdump-configuration">24.1. Configuring the <code class="systemitem">kdump</code> Service</h2></div></div></div><div class="para">
+ This section covers three common means of configuring the <code class="systemitem">kdump</code> service: at the first boot, using the <span class="application"><strong>Kernel Dump Configuration</strong></span> graphical utility, and doing so manually on the command line. It also describes how to test the configuration to verify that everything works as expected.
+ </div><a id="id437267" class="indexterm"></a><div class="note" title="Note: Make Sure You Have kexec-tools Installed"><div class="admonition_header"><h2>Note: Make Sure You Have <span class="package">kexec-tools</span> Installed</h2></div><div class="admonition"><div class="para">
+ To use the <code class="systemitem">kdump</code> service, you must have the <span class="package">kexec-tools</span> package installed. Refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><div class="section" title="24.1.1. Configuring the kdump at First Boot" id="s2-kdump-configuration-firstboot"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-configuration-firstboot">24.1.1. Configuring the <code class="systemitem">kdump</code> at First Boot</h3></div></div></div><div class="para">
+ When the system boots for the first time, the <span class="application"><strong>firstboot</strong></span> application is launched to guide a user through the initial configuration of the freshly installed system. To configure <code class="systemitem">kdump</code>, navigate to the <span class="guilabel"><strong>Kdump</strong></span> section, and follow the instructions below.
+ </div><div class="important" title="Important: Make Sure the System Has Enough Memory"><div class="admonition_header"><h2>Important: Make Sure the System Has Enough Memory</h2></div><div class="admonition"><div class="para">
+ Unless the system has enough memory, this option will not be available. For the information on minimum memory requirements, refer to the <em class="citetitle">Required minimums</em> section of the <a href="http://www.redhat.com/rhel/compare/"><em class="citetitle">Red Hat Enterprise Linux</em> comparison chart</a>. Note that when the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by a user, and defaults to 128 MB.
+ </div></div></div><div class="section" title="24.1.1.1. Enabling the Service" id="s3-kdump-configuration-firstboot-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-firstboot-enable">24.1.1.1. Enabling the Service</h4></div></div></div><a id="id539921" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">kdump</code> daemon at boot time, select the <span class="guilabel"><strong>Enable kdump?</strong></span> check box. This will enable the service for runlevels <code class="literal">2</code>, <code class="literal">3</code>, <code class="literal">4</code>, and <code class="literal">5</code>, and start it for the current session. Similarly, unselecting the check box will disable it for all runlevels and stop the service immediately.
+ </div></div><div class="section" title="24.1.1.2. Configuring the Memory Usage" id="s3-kdump-configuration-firstboot-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-firstboot-memory">24.1.1.2. Configuring the Memory Usage</h4></div></div></div><a id="id843382" class="indexterm"></a><div class="para">
+ To configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel, click the up and down arrow buttons next to the <span class="guilabel"><strong>Kdump Memory</strong></span> field to increase or decrease the value. Notice that the <span class="guilabel"><strong>Usable System Memory</strong></span> field changes accordingly showing you the remaining memory that will be available to the system.
+ </div></div></div><div class="section" title="24.1.2. Using the Kernel Dump Configuration Utility" id="s2-kdump-configuration-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-configuration-gui">24.1.2. Using the <span class="application"><strong>Kernel Dump Configuration</strong></span> Utility</h3></div></div></div><a id="id822342" class="indexterm"></a><a id="id822358" class="indexterm"></a><div class="para">
+ To start the <span class="application"><strong>Kernel Dump Configuration</strong></span> utility, select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Kernel crash dumps</strong></span> from the panel, or type <code class="command">system-config-kdump</code> at a shell prompt (for example, <span class="emphasis"><em>xterm</em></span> or <span class="emphasis"><em>GNOME Terminal</em></span>). You will be presented with a window as shown in <a class="xref" href="ch-kdump.html#fig-kdump-kernel_dump_configuration" title="Figure 24.1. Basic Settings">Figure 24.1, “<span class="guilabel">Basic Settings</span>”</a>.
+ </div><div class="para">
+ The utility allows you to configure <code class="systemitem">kdump</code> as well as to enable or disable starting the service at boot time. When you are done, click <span class="guibutton"><strong>Apply</strong></span> to save the changes. The system reboot will be requested, and unless you are already authenticated, you will be prompted to enter the superuser password.
+ </div><div class="important" title="Important: Make Sure the System Has Enough Memory"><div class="admonition_header"><h2>Important: Make Sure the System Has Enough Memory</h2></div><div class="admonition"><div class="para">
+ Unless the system has enough memory, the utility will not start, and you will be presented with the following error message:
+ </div><div class="mediaobject" align="center"><img src="images/kdump-kernel_dump_configuration-not_enough_memory.png" align="middle" /><div class="longdesc"><div class="para">
+ The <span class="quote">“<span class="quote">not enough memory</span>”</span> error
+ </div></div></div><div class="para">
+ For the information on minimum memory requirements, refer to the <em class="citetitle">Required minimums</em> section of the <a href="http://www.redhat.com/rhel/compare/"><em class="citetitle">Red Hat Enterprise Linux</em> comparison chart</a>. Note that when the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by a user, and defaults to 128 MB.
+ </div></div></div><div class="section" title="24.1.2.1. Enabling the Service" id="s3-kdump-configuration-gui-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-gui-enable">24.1.2.1. Enabling the Service</h4></div></div></div><a id="id788458" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">kdump</code> daemon at boot time, click the <span class="guibutton"><strong>Apply</strong></span> button on the toolbar. This will enable the service for runlevels <code class="literal">2</code>, <code class="literal">3</code>, <code class="literal">4</code>, and <code class="literal">5</code>, and start it for the current session. Similarly, clicking the <span class="guibutton"><strong>Disable</strong></span> button will disable it for all runlevels and stop the service immediately.
+ </div><div class="para">
+ For more information on runlevels and configuring services in general, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div></div><div class="section" title="24.1.2.2. The Basic Settings Tab" id="s3-kdump-configuration-gui-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-gui-basic">24.1.2.2. The <span class="guilabel"><strong>Basic Settings</strong></span> Tab</h4></div></div></div><a id="id497784" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Basic Settings</strong></span> tab enables you to configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel. To do so, select the <span class="guilabel"><strong>Manual kdump memory settings</strong></span> radio button, and click the up and down arrow buttons next to the <span class="guilabel"><strong>New kdump Memory</strong></span> field to increase or decrease the value. Notice that the <span class="guilabel"><strong>Usable Memory</strong></span> field changes accordingly showing you the remaining memory that will be available to the system.
+ </div><div class="figure" title="Figure 24.1. Basic Settings" id="fig-kdump-kernel_dump_configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration.png" alt="Basic Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Basic Settings</strong></span>
+ </div></div></div></div><h6>Figure 24.1. <span class="guilabel">Basic Settings</span></h6></div><br class="figure-break" /></div><div class="section" title="24.1.2.3. The Target Settings Tab" id="s3-kdump-configuration-gui-target"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-gui-target">24.1.2.3. The <span class="guilabel"><strong>Target Settings</strong></span> Tab</h4></div></div></div><a id="id589998" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Target Settings</strong></span> tab enables you to specify the target location for the <code class="filename">vmcore</code> dump. It can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol.
+ </div><div class="figure" title="Figure 24.2. Target Settings" id="fig-kdump-kernel_dump_configuration-target_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-target_settings.png" alt="Target Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Target Settings</strong></span>
+ </div></div></div></div><h6>Figure 24.2. <span class="guilabel">Target Settings</span></h6></div><br class="figure-break" /><div class="para">
+ To save the dump to the local file system, select the <span class="guilabel"><strong>Local filesystem</strong></span> radio button. Optionally, you can customize the settings by choosing a different partition from the <span class="guilabel"><strong>Partition</strong></span>, and a target directory from the <span class="guilabel"><strong>Path</strong></span> pulldown lists.
+ </div><div class="para">
+ To write the dump directly to a device, select the <span class="guilabel"><strong>Raw device</strong></span> radio button, and choose the desired target device from the pulldown list next to it.
+ </div><div class="para">
+ To store the dump to a remote machine, select the <span class="guilabel"><strong>Network</strong></span> radio button. To use the NFS protocol, select the <span class="guilabel"><strong>NFS</strong></span> radio button, and fill the <span class="guilabel"><strong>Server name</strong></span> and <span class="guilabel"><strong>Path to directory</strong></span> fields. To use the SSH protocol, select the <span class="guilabel"><strong>SSH</strong></span> radio button, and fill the <span class="guilabel"><strong>Server name</strong></span>, <span class="guilabel"><strong>Path to directory</strong></span>, and <span class="guilabel"><strong>User name</strong></span> fields with the remote server address, target directory, and a valid remote user name respectively.
+ </div><div class="para">
+ Refer to <a class="xref" href="ch-OpenSSH.html" title="Chapter 9. OpenSSH">Chapter 9, <i>OpenSSH</i></a> for information on how to configure an SSH server, and how to set up a key-based authentication.
+ </div><a id="id478770" class="indexterm"></a><div class="important" title="Important: Using the hpsa Driver for a Storage"><div class="admonition_header"><h2>Important: Using the <code class="systemitem">hpsa</code> Driver for a Storage</h2></div><div class="admonition"><div class="para">
+ Due to known issue with the <code class="systemitem">hpsa</code> driver, <code class="systemitem">kdump</code> is unable to save the dump to a storage that uses this driver for HP Smart Array Controllers. If this applies to your machine, it is advised that you save the dump to a remote system using the NFS or SSH protocol instead.
+ </div></div></div></div><div class="section" title="24.1.2.4. The Filtering Settings Tab" id="s3-kdump-configuration-gui-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-gui-filtering">24.1.2.4. The <span class="guilabel"><strong>Filtering Settings</strong></span> Tab</h4></div></div></div><a id="id478837" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Filtering Settings</strong></span> tab enables you to select the filtering level for the <code class="filename">vmcore</code> dump.
+ </div><div class="figure" title="Figure 24.3. Filtering Settings" id="fig-kdump-kernel_dump_configuration-filtering_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-filtering_settings.png" alt="Filtering Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Filtering Settings</strong></span>
+ </div></div></div></div><h6>Figure 24.3. <span class="guilabel">Filtering Settings</span></h6></div><br class="figure-break" /><div class="para">
+ To exclude the <span class="guilabel"><strong>zero page</strong></span>, <span class="guilabel"><strong>cache page</strong></span>, <span class="guilabel"><strong>cache private</strong></span>, <span class="guilabel"><strong>user data</strong></span>, or <span class="guilabel"><strong>free page</strong></span> from the dump, select the check box next to the appropriate label.
+ </div></div><div class="section" title="24.1.2.5. The Expert Settings Tab" id="s3-kdump-configuration-gui-expert"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-gui-expert">24.1.2.5. The <span class="guilabel"><strong>Expert Settings</strong></span> Tab</h4></div></div></div><div class="para">
+ The <span class="guilabel"><strong>Expert Settings</strong></span> tab enables you to choose which kernel and initial RAM disk to use, as well as to customize the options that are passed to the kernel and the core collector program.
+ </div><div class="figure" title="Figure 24.4. Expert Settings" id="fig-kdump-kernel_dump_configuration-expert_settings"><div class="figure-contents"><div class="mediaobject"><img src="images/kdump-kernel_dump_configuration-expert_settings.png" alt="Expert Settings" /><div class="longdesc"><div class="para">
+ <span class="guilabel"><strong>Expert Settings</strong></span>
+ </div></div></div></div><h6>Figure 24.4. <span class="guilabel">Expert Settings</span></h6></div><br class="figure-break" /><a id="id479000" class="indexterm"></a><div class="para">
+ To use a different initial RAM disk, select the <span class="guilabel"><strong>Custom initrd</strong></span> radio button, and choose the desired RAM disk from the pulldown list next to it.
+ </div><a id="id459975" class="indexterm"></a><div class="para">
+ To capture a different kernel, select the <span class="guilabel"><strong>Custom kernel</strong></span> radio button, and choose the desired kernel image from the pulldown list on the right.
+ </div><a id="id460003" class="indexterm"></a><div class="para">
+ To adjust the list of options that are passed to the kernel at boot time, edit the content of the <span class="guilabel"><strong>Edited</strong></span> text field. Note that you can always revert your changes by clicking the <span class="guibutton"><strong>Refresh</strong></span> button.
+ </div><a id="id460036" class="indexterm"></a><div class="para">
+ To choose what steps should be taken when the kernel crash is captured, select the appropriate option from the <span class="guilabel"><strong>Default action</strong></span> pulldown list. Available options are <span class="guimenuitem"><strong>mount rootfs and run /sbin/init</strong></span> (the default action), <span class="guimenuitem"><strong>reboot</strong></span> (to reboot the system), <span class="guimenuitem"><strong>shell</strong></span> (to present a user with an interactive shell prompt), <span class="guimenuitem"><strong>halt</strong></span> (to halt the system), and <span class="guimenuitem"><strong>poweroff</strong></span> (to power the system off).
+ </div><a id="id460083" class="indexterm"></a><div class="para">
+ To customize the options that are passed to the <code class="command">makedumpfile</code> core collector, edit the <span class="guilabel"><strong>Core collector</strong></span> text field; see <a class="xref" href="ch-kdump.html#s3-kdump-configuration-cli-filtering" title="24.1.3.3. Configuring the Core Collector">Section 24.1.3.3, “Configuring the Core Collector”</a> for more information.
+ </div></div></div><div class="section" title="24.1.3. Configuring kdump on the Command Line" id="s2-kdump-configuration-cli"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-configuration-cli">24.1.3. Configuring <code class="systemitem">kdump</code> on the Command Line</h3></div></div></div><div class="para">
+ To perform actions described in this section, you have to be logged in as a superuser:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="section" title="24.1.3.1. Configuring the Memory Usage" id="s3-kdump-configuration-cli-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-cli-memory">24.1.3.1. Configuring the Memory Usage</h4></div></div></div><a id="id460158" class="indexterm"></a><div class="para">
+ To configure the amount of memory that is reserved for the <code class="systemitem">kdump</code> kernel, open the <code class="filename">/boot/grub/grub.conf</code> file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, and add the <code class="option">crashkernel=<em class="replaceable"><code><size></code></em>M</code> parameter to the list of kernel options as shown in <a class="xref" href="ch-kdump.html#ex-kdump-configuration-cli-memory-grub" title="Example 24.1. A sample /boot/grub/grub.conf file">Example 24.1, “A sample <code class="filename">/boot/grub/grub.conf</code> file”</a>.
+ </div><a id="id460211" class="indexterm"></a><a id="id460231" class="indexterm"></a><a id="id529540" class="indexterm"></a><div class="example" title="Example 24.1. A sample /boot/grub/grub.conf file" id="ex-kdump-configuration-cli-memory-grub"><h6>Example 24.1. A sample <code class="filename">/boot/grub/grub.conf</code> file</h6><div class="example-contents"><pre class="screen"># grub.conf generated by anaconda
+#
+# Note that you do not have to rerun grub after making changes to this file
+# NOTICE: You have a /boot partition. This means that
+# all kernel and initrd paths are relative to /boot/, eg.
+# root (hd0,0)
+# kernel /vmlinuz-version ro root=/dev/sda3
+# initrd /initrd
+#boot=/dev/sda
+default=0
+timeout=5
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+title Red Hat Enterprise Linux (2.6.32-54.el6.i686)
+ root (hd0,0)
+ kernel /boot/vmlinuz-2.6.32-54.el6.i686 root=/dev/sda3 ro crashkernel=128M
+ initrd /initramfs-2.6.32-54.el6.i686.img
+</pre></div></div><br class="example-break" /><div class="important" title="Important: Make Sure the System Has Enough Memory"><div class="admonition_header"><h2>Important: Make Sure the System Has Enough Memory</h2></div><div class="admonition"><div class="para">
+ When the <code class="systemitem">kdump</code> crash recovery is enabled, the minimum memory requirements increase by the amount of memory reserved for it. This value is determined by a user, and defaults to 128 MB, as lower values proved to be unreliable. For more information on minimum memory requirements for Fedora 14, refer to the <em class="citetitle">Required minimums</em> section of the <a href="http://www.redhat.com/rhel/compare/">Red Hat Enterprise Linux comparison chart</a>.
+ </div></div></div></div><div class="section" title="24.1.3.2. Configuring the Target Type" id="s3-kdump-configuration-cli-target"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-cli-target">24.1.3.2. Configuring the Target Type</h4></div></div></div><a id="id529626" class="indexterm"></a><div class="para">
+ When a kernel crash is captured, the core dump can be either stored as a file in a local file system, written directly to a device, or sent over a network using the NFS (Network File System) or SSH (Secure Shell) protocol. Note that only one of these options can be set at the moment. The default option is to store the <code class="filename">vmcore</code> file in the <code class="filename">/var/crash/</code> directory of the local file system. To change this, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, and edit the options as described below.
+ </div><div class="para">
+ To change the local directory in which the core dump is to be saved, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#path /var/crash</code> line, and replace the value with a desired directory path. Optionally, if you wish to write the file to a different partition, follow the same procedure with the <code class="literal">#ext4 /dev/sda3</code> line as well, and change both the file system type and the device (a device name, a file system label, and UUID are all supported) accordingly. For example:
+ </div><pre class="screen">ext3 /dev/sda4
+path /usr/local/cores</pre><div class="para">
+ To write the dump directly to a device, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#raw /dev/sda5</code> line, and replace the value with a desired device name. For example:
+ </div><pre class="screen">raw /dev/sdb1</pre><div class="para">
+ To store the dump to a remote machine using the NFS protocol, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#net my.server.com:/export/tmp</code> line, and replace the value with a valid hostname and directory path. For example:
+ </div><pre class="screen">net penguin.example.com:/export/cores</pre><div class="para">
+ To store the dump to a remote machine using the SSH protocol, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#net user at my.server.com</code> line, and replace the value with a valid username and hostname. For example:
+ </div><pre class="screen">net john at penguin.example.com</pre><div class="para">
+ Refer to <a class="xref" href="ch-OpenSSH.html" title="Chapter 9. OpenSSH">Chapter 9, <i>OpenSSH</i></a> for information on how to configure an SSH server, and how to set up a key-based authentication.
+ </div><a id="id529756" class="indexterm"></a><div class="important" title="Important: Using the hpsa Driver for a Storage"><div class="admonition_header"><h2>Important: Using the <code class="systemitem">hpsa</code> Driver for a Storage</h2></div><div class="admonition"><div class="para">
+ Due to known issue with the <code class="systemitem">hpsa</code> driver, <code class="systemitem">kdump</code> is unable to save the dump to a storage that uses this driver for HP Smart Array Controllers. If this applies to your machine, it is advised that you save the dump to a remote system using the NFS or SSH protocol instead.
+ </div></div></div></div><div class="section" title="24.1.3.3. Configuring the Core Collector" id="s3-kdump-configuration-cli-filtering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-cli-filtering">24.1.3.3. Configuring the Core Collector</h4></div></div></div><div class="para">
+ To reduce the size of the <code class="filename">vmcore</code> dump file, <code class="systemitem">kdump</code> allows you to specify an external application (that is, a core collector) to compress the data, and optionally leave out all irrelevant information. Currently, the only fully supported core collector is <code class="command">makedumpfile</code>.
+ </div><div class="para">
+ To enable the core collector, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#core_collector makedumpfile -c --message-level 1 -d 31</code> line, and edit the command line options as described below.
+ </div><a id="id567917" class="indexterm"></a><div class="para">
+ To enable the dump file compression, add the <code class="option">-c</code> parameter. For example:
+ </div><pre class="screen">core_collector makedumpfile -c</pre><a id="id567948" class="indexterm"></a><div class="para">
+ To remove certain pages from the dump, add the <code class="option">-d <em class="replaceable"><code>value</code></em></code> parameter, where <em class="replaceable"><code>value</code></em> is a sum of values of pages you want to omit as described in <a class="xref" href="ch-kdump.html#table-kdump-configuration-cli-filtering-makedumpfile" title="Table 24.1. Supported filtering levels">Table 24.1, “Supported filtering levels”</a>. For example, to remove both zero and free pages, use the following:
+ </div><pre class="screen">core_collector makedumpfile -d 17 -c</pre><div class="para">
+ Refer to the manual page for <code class="command">makedumpfile</code> for a complete list of available options.
+ </div><div class="table" title="Table 24.1. Supported filtering levels" id="table-kdump-configuration-cli-filtering-makedumpfile"><h6>Table 24.1. Supported filtering levels</h6><div class="table-contents"><table summary="Supported filtering levels" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">1</code>
+ </td><td>
+ Zero pages
+ </td></tr><tr><td>
+ <code class="option">2</code>
+ </td><td>
+ Cache pages
+ </td></tr><tr><td>
+ <code class="option">4</code>
+ </td><td>
+ Cache private
+ </td></tr><tr><td>
+ <code class="option">8</code>
+ </td><td>
+ User pages
+ </td></tr><tr><td>
+ <code class="option">16</code>
+ </td><td>
+ Free pages
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" title="24.1.3.4. Changing the Default Action" id="s3-kdump-configuration-cli-action"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-cli-action">24.1.3.4. Changing the Default Action</h4></div></div></div><a id="id477327" class="indexterm"></a><div class="para">
+ By default, when the kernel crash is captured, the root file system is mounted, and <code class="command">/sbin/init</code> is run. To change this behavior, open the <code class="filename">/etc/kdump.conf</code> configuration file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, remove the hash sign (<span class="quote">“<span class="quote">#</span>”</span>) from the beginning of the <code class="literal">#default shell</code> line, and replace the value with a desired action as described in <a class="xref" href="ch-kdump.html#table-kdump-configuration-cli-action-actions" title="Table 24.2. Supported actions">Table 24.2, “Supported actions”</a>. For example:
+ </div><pre class="screen">default halt</pre><div class="table" title="Table 24.2. Supported actions" id="table-kdump-configuration-cli-action-actions"><h6>Table 24.2. Supported actions</h6><div class="table-contents"><table summary="Supported actions" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">reboot</code>
+ </td><td>
+ Reboot the system, losing the core in the process.
+ </td></tr><tr><td>
+ <code class="option">halt</code>
+ </td><td>
+ After attempting to capture a core, halt the system no matter if it succeeded.
+ </td></tr><tr><td>
+ <code class="option">poweroff</code>
+ </td><td>
+ Power off the system.
+ </td></tr><tr><td>
+ <code class="option">shell</code>
+ </td><td>
+ Run the <span class="application"><strong>msh</strong></span> session from within the initramfs, allowing a user to record the core manually.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" title="24.1.3.5. Enabling the Service" id="s3-kdump-configuration-cli-enable"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-kdump-configuration-cli-enable">24.1.3.5. Enabling the Service</h4></div></div></div><a id="id477520" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">kdump</code> daemon at boot time, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">chkconfig kdump on</code></pre><div class="para">
+ This will enable the service for runlevels <code class="literal">2</code>, <code class="literal">3</code>, <code class="literal">4</code>, and <code class="literal">5</code>. Similarly, typing <code class="command">chkconfig kdump off</code> will disable it for all runlevels. To start the service in the current session, use the following command:
+ </div><a id="id584014" class="indexterm"></a><pre class="screen">~]# <code class="command">service kdump start</code>
+No kdump initial ramdisk found. [WARNING]
+Rebuilding /boot/initrd-2.6.32-54.el6.i686kdump.img
+Starting kdump: [ OK ]</pre><div class="para">
+ For more information on runlevels and configuring services in general, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div></div></div><div class="section" title="24.1.4. Testing the Configuration" id="s2-kdump-configuration-testing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-configuration-testing">24.1.4. Testing the Configuration</h3></div></div></div><a id="id584060" class="indexterm"></a><div class="warning" title="Caution: Be Careful When Using These Commands"><div class="admonition_header"><h2>Caution: Be Careful When Using These Commands</h2></div><div class="admonition"><div class="para">
+ The commands below will cause the kernel to crash. Use caution when following these steps, and by no means use them on a production machine.
+ </div></div></div><div class="para">
+ To test the configuration, reboot the system with <code class="systemitem">kdump</code> enabled, and make sure that the service is running (refer to <a class="xref" href="s1-services-running.html" title="7.3. Running the Services">Section 7.3, “Running the Services”</a> for more information on how to run a service in Fedora):
+ </div><pre class="screen">~]# <code class="command">service kdump status</code>
+Kdump is operational</pre><div class="para">
+ Then type the following commands at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">echo 1 > /proc/sys/kernel/sysrq</code>
+~]# <code class="command">echo c > /proc/sysrq-trigger</code></pre><div class="para">
+ This will force the Linux kernel to crash, and the <code class="filename"><em class="replaceable"><code>address</code></em>-<em class="replaceable"><code>YYYY-MM-DD</code></em>-<em class="replaceable"><code>HH:MM:SS</code></em>/vmcore</code> file will be copied to the location you have selected in the configuration (that is, to <code class="filename">/var/crash/</code> by default).
+ </div><div class="example" title="Example 24.2. Listing a content of /var/crash/ after a crash" id="ex-kdump-configuration-testing-vmcore"><h6>Example 24.2. Listing a content of <code class="filename">/var/crash/</code> after a crash</h6><div class="example-contents"><pre class="screen">~]# <code class="command">tree --charset=ascii /var/crash</code>
+/var/crash
+`-- 127.0.0.1-2010-08-25-08:45:02
+ `-- vmcore
+
+1 directory, 1 file</pre></div></div><br class="example-break" /></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kernel-boot-loader-pseries.html"><strong>Prev</strong>23.6.3. Configuring the YABOOT Boot Loader</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kdump-crash.html"><strong>Next</strong>24.2. Analyzing the Core Dump</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-proc.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-proc.html
new file mode 100644
index 0000000..409d547
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-proc.html
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 19. The proc File System</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-sysconfig.html" title="Part III. System Configuration" /><link rel="prev" href="s1-sysconfig-additional-resources.html" title="18.3. Additional Resources" /><link rel="next" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysconfig-additional-resources.html"><strong>Prev</stro
ng></a></li><li class="next"><a accesskey="n" href="s1-proc-topfiles.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 19. The proc File System" id="ch-proc" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. The <code class="filename">proc</code> File System</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-proc.html#s1-proc-virtual">19.1. A Virtual File System</a></span></dt><dt><span class="section"><a href="s1-proc-topfiles.html">19.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dt><span class="section"><a href="s1-proc-directories.html">19.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dt><span class="section"><a href="s1-proc-sysctl.html">19.4. Using the <code class="command">sysctl</code> Command</a></span></dt><dt><span class="section"><a href="s1-proc-additional-resources.html">19.5. Refere
nces</a></span></dt></dl></div><a id="id522543" class="indexterm"></a><a id="id549090" class="indexterm"></a><div class="para">
+ The Linux kernel has two primary functions: to control access to physical devices on the computer and to schedule when and how processes interact with these devices. The <code class="filename">/proc/</code> directory (also called the <code class="filename">proc</code> file system) contains a hierarchy of special files which represent the current state of the kernel, allowing applications and users to peer into the kernel's view of the system.
+ </div><div class="para">
+ The <code class="filename">/proc/</code> directory contains a wealth of information detailing system hardware and any running processes. In addition, some of the files within <code class="filename">/proc/</code> can be manipulated by users and applications to communicate configuration changes to the kernel.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Later versions of the 2.6 kernel have made the <code class="filename">/proc/ide/</code> and <code class="filename">/proc/pci/</code> directories obsolete. The <code class="command">/proc/ide/</code> file system is now superseded by files in <code class="command">sysfs</code>; to retrieve information on PCI devices, use <code class="command">lspci</code> instead. For more information on <code class="command">sysfs</code> or <code class="command">lspci</code>, refer to their respective <code class="command">man</code> pages.
+ </div></div></div><div class="section" title="19.1. A Virtual File System" id="s1-proc-virtual"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-proc-virtual">19.1. A Virtual File System</h2></div></div></div><a id="id748484" class="indexterm"></a><a id="id831827" class="indexterm"></a><a id="id831844" class="indexterm"></a><div class="para">
+ Linux systems store all data as <span class="emphasis"><em>files</em></span>. Most users are familiar with the two primary types of files: text and binary. But the <code class="filename">/proc/</code> directory contains another type of file called a <em class="firstterm">virtual file</em>. As such, <code class="filename">/proc/</code> is often referred to as a <em class="firstterm">virtual file system</em>.
+ </div><div class="para">
+ Virtual files have unique qualities. Most of them are listed as zero bytes in size, but can still contain a large amount of information when viewed. In addition, most of the time and date stamps on virtual files reflect the current time and date, indicative of the fact they are constantly updated.
+ </div><div class="para">
+ Virtual files such as <code class="filename">/proc/interrupts</code>, <code class="filename">/proc/meminfo</code>, <code class="filename">/proc/mounts</code>, and <code class="filename">/proc/partitions</code> provide an up-to-the-moment glimpse of the system's hardware. Others, like the <code class="filename">/proc/filesystems</code> file and the <code class="filename">/proc/sys/</code> directory provide system configuration information and interfaces.
+ </div><div class="para">
+ For organizational purposes, files containing information on a similar topic are grouped into virtual directories and sub-directories. Process directories contain information about each running process on the system.
+ </div><div class="section" title="19.1.1. Viewing Virtual Files" id="s2-proc-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-viewing">19.1.1. Viewing Virtual Files</h3></div></div></div><a id="id520144" class="indexterm"></a><a id="id520158" class="indexterm"></a><div class="para">
+ Most files within <code class="filename">/proc/</code> files operate similarly to text files, storing useful system and hardware data in human-readable text format. As such, you can use <code class="command">cat</code>, <code class="command">more</code>, or <code class="command">less</code> to view them. For example, to display information about the system's CPU, run <code class="command">cat /proc/cpuinfo</code>. This will return output similar to the following:
+ </div><pre class="screen">
+processor : 0
+vendor_id : AuthenticAMD
+cpu family : 5
+model : 9
+model name : AMD-K6(tm) 3D+
+Processor stepping : 1 cpu
+MHz : 400.919
+cache size : 256 KB
+fdiv_bug : no
+hlt_bug : no
+f00f_bug : no
+coma_bug : no
+fpu : yes
+fpu_exception : yes
+cpuid level : 1
+wp : yes
+flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr
+bogomips : 799.53
+</pre><div class="para">
+ Some files in <code class="command">/proc/</code> contain information that is not human-readable. To retrieve information from such files, use tools such as <code class="command">lspci</code>, <code class="command">apm</code>, <code class="command">free</code>, and <code class="command">top</code>.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Some of the virtual files in the <code class="filename">/proc/</code> directory are readable only by the root user.
+ </div></div></div></div><div class="section" title="19.1.2. Changing Virtual Files" id="s2-proc-change"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-change">19.1.2. Changing Virtual Files</h3></div></div></div><a id="id544530" class="indexterm"></a><a id="id544543" class="indexterm"></a><div class="para">
+ As a general rule, most virtual files within the <code class="filename">/proc/</code> directory are read-only. However, some can be used to adjust settings in the kernel. This is especially true for files in the <code class="filename">/proc/sys/</code> subdirectory.
+ </div><div class="para">
+ To change the value of a virtual file, use the following command:
+ </div><div class="para">
+ <code class="command">echo <em class="replaceable"><code>value</code></em> > /proc/<em class="replaceable"><code>file</code></em> </code>
+ </div><div class="para">
+ For example, to change the hostname on the fly, run:
+ </div><div class="para">
+ <code class="command">echo <em class="replaceable"><code>www.example.com</code></em> > /proc/sys/kernel/hostname </code>
+ </div><div class="para">
+ Other files act as binary or Boolean switches. Typing <code class="command">cat /proc/sys/net/ipv4/ip_forward</code> returns either a <code class="computeroutput">0</code> (off or false) or a <code class="computeroutput">1</code> (on or true). A <code class="computeroutput">0</code> indicates that the kernel is not forwarding network packets. To turn packet forwarding on, run <code class="command">echo 1 > /proc/sys/net/ipv4/ip_forward</code>.
+ </div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ Another command used to alter settings in the <code class="filename">/proc/sys/</code> subdirectory is <code class="command">/sbin/sysctl</code>. For more information on this command, refer to <a class="xref" href="s1-proc-sysctl.html" title="19.4. Using the sysctl Command">Section 19.4, “Using the <code class="command">sysctl</code> Command”</a>
+ </div></div></div><div class="para">
+ For a listing of some of the kernel configuration files available in the <code class="filename">/proc/sys/</code> subdirectory, refer to <a class="xref" href="s2-proc-dir-sys.html" title="19.3.9. /proc/sys/">Section 19.3.9, “ <code class="filename">/proc/sys/</code> ”</a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysconfig-additional-resources.html"><strong>Prev</strong>18.3. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-proc-topfiles.html"><strong>Next</strong>19.2. Top-level Files within the proc File System</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-yum.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-yum.html
new file mode 100644
index 0000000..0be1157
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch-yum.html
@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 1. Yum</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-pkg-management.html" title="Part I. Package Management" /><link rel="prev" href="pt-pkg-management.html" title="Part I. Package Management" /><link rel="next" href="sec-Packages_and_Package_Groups.html" title="1.2. Packages and Package Groups" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-pkg-management.html"><strong>Prev</strong></a></li><li class="next"><a
accesskey="n" href="sec-Packages_and_Package_Groups.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 1. Yum" id="ch-yum" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Yum</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages">1.1. Checking For and Updating Packages</a></span></dt><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">1.2. Packages and Package Groups</a></span></dt><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">1.3. Configuring Yum and Yum Repositories</a></span></dt><dt><span class="section"><a href="sec-Yum_Plugins.html">1.4. Yum Plugins</a></span></dt><dt><span class="section"><a href="sec-Additional_Resources.html">1.5. Additional Resources</a></span></dt></dl></div><div class="para">
+ <span class="application"><strong>Yum</strong></span> is the The Fedora Project package manager that is able to query for information about packages, fetch packages from repositories, install and uninstall packages using automatic dependency resolution, and update an entire system to the latest available packages. <span class="application"><strong>Yum</strong></span> performs automatic dependency resolution on packages you are updating, installing or removing, and thus is able to automatically determine, fetch and install all available dependent packages. <span class="application"><strong>Yum</strong></span> can be configured with new, additional repositories, or <em class="firstterm">package sources</em>, and also provides many plugins which enhance and extend its capabilities. <span class="application"><strong>Yum</strong></span> is able to perform many of the same tasks that <span class="application"><strong>RPM</strong></span> can; additionally, many of the command lin
e options are similar. <span class="application"><strong>Yum</strong></span> enables easy and simple package management on a single machine or on groups of them.
+ </div><div class="important" title="Secure Package Management with GPG-Signed Packages" id="important-Secure_Package_Management_with_GPG-Signed_Packages"><div class="admonition_header"><h2>Secure Package Management with GPG-Signed Packages</h2></div><div class="admonition"><div class="para">
+ <span class="application"><strong>Yum</strong></span> provides secure package management by enabling GPG (Gnu Privacy Guard; also known as GnuPG) signature verification on GPG-signed packages to be turned on for all package repositories (i.e. package sources), or for individual repositories. When signature verification is enabled, <span class="application"><strong>Yum</strong></span> will refuse to install any packages not GPG-signed with the correct key for that repository. This means that you can trust that the <span class="application"><strong>RPM</strong></span> packages you download and install on your system are from a trusted source, such as The Fedora Project, and were not modified during transfer. Refer to <a class="xref" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="1.3. Configuring Yum and Yum Repositories">Section 1.3, “Configuring Yum and Yum Repositories”</a> for details on enabling signature-checking with <span class="application"><stron
g>Yum</strong></span>, or <a class="xref" href="s1-check-rpm-sig.html" title="3.3. Checking a Package's Signature">Section 3.3, “Checking a Package's Signature”</a> for information on working with and verifying GPG-signed <span class="application"><strong>RPM</strong></span> packages in general.
+ </div></div></div><div class="para">
+ <span class="application"><strong>Yum</strong></span> also enables you to easily set up your own repositories of <span class="application"><strong>RPM</strong></span> packages for download and installation on other machines.
+ </div><div class="para">
+ Learning <span class="application"><strong>Yum</strong></span> is a worthwhile investment because it is often the fastest way to perform system administration tasks, and it provides capabilities beyond those provided by the <span class="application"><strong>PackageKit</strong></span> graphical package management tools. Refer to <a class="xref" href="ch-PackageKit.html" title="Chapter 2. PackageKit">Chapter 2, <i>PackageKit</i></a> for details on using <span class="application"><strong>PackageKit</strong></span>.
+ </div><div class="section" title="1.1. Checking For and Updating Packages" id="sec-Checking_For_and_Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Checking_For_and_Updating_Packages">1.1. Checking For and Updating Packages</h2></div></div></div><div class="section" title="1.1.1. Checking For Updates" id="sec-Checking_For_Updates"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Checking_For_Updates">1.1.1. Checking For Updates</h3></div></div></div><a id="id784403" class="indexterm"></a><div class="para">
+ You can use the <code class="command">yum check-update</code> command to see which installed packages on your system have updates available.
+ </div><div class="note" title="Note: Yum and Superuser Privileges" id="note-Note_Yum_and_Superuser_Privileges"><div class="admonition_header"><h2>Note: <span class="application"><strong>Yum</strong></span> and Superuser Privileges</h2></div><div class="admonition"><div class="para">
+ You must have superuser privileges in order to use <code class="command">yum</code> to install, update or remove packages on your system. All examples in this chapter assume that you have already obtained superuser privileges by using either the <code class="command">su</code> or <code class="command">sudo</code> command.
+ </div></div></div><pre class="screen">
+~]# <code class="command">yum check-update</code>
+Loaded plugins: presto, refresh-packagekit, security
+PackageKit.x86_64 0.5.3-0.1.20090915git.fc12 fedora
+PackageKit-glib.x86_64 0.5.3-0.1.20090915git.fc12 fedora
+PackageKit-yum.x86_64 0.5.3-0.1.20090915git.fc12 fedora
+PackageKit-yum-plugin.x86_64 0.5.3-0.1.20090915git.fc12 fedora
+glibc.x86_64 2.10.90-22 fedora
+glibc-common.x86_64 2.10.90-22 fedora
+kernel.x86_64 2.6.31-14.fc12 fedora
+kernel-firmware.noarch 2.6.31-14.fc12 fedora
+rpm.x86_64 4.7.1-5.fc12 fedora
+rpm-libs.x86_64 4.7.1-5.fc12 fedora
+rpm-python.x86_64 4.7.1-5.fc12 fedora
+yum.noarch 3.2.24-4.fc12 fedora
+</pre><div class="para">
+ These packages are listed as having updates available. The first package in the list is <span class="application"><strong>PackageKit</strong></span>, the graphical package manager. The first line of the above output tells us:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">PackageKit</code> — the name of the package
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">x86_64</code> — the CPU architecture the package was built for
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">0.5.3-0.1.20090915git.fc12</code> — the version of the updated package to be installed
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">fedora</code> — the repository in which the updated package is located
+ </div></li></ul></div><div class="para">
+ The output also shows us that we can update the kernel (the kernel package), <span class="application"><strong>Yum</strong></span> and <span class="application"><strong>RPM</strong></span> themselves (the <code class="filename">yum</code> and <code class="filename">rpm</code> packages), as well as their dependencies (such as the <code class="computeroutput">kernel-firmware</code>, <code class="computeroutput">rpm-libs</code> and <code class="computeroutput">rpm-python</code> packages), all using <code class="command">yum</code>.
+ </div></div><div class="section" title="1.1.2. Updating Packages" id="sec-Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Updating_Packages">1.1.2. Updating Packages</h3></div></div></div><a id="id832064" class="indexterm"></a><div class="para">
+ You can choose to update a single package, multiple packages, or all packages at once. If any dependencies of the package (or packages) you update have updates available themselves, then they are updated too. To update a single package
+ <a id="id832082" class="indexterm"></a>
+ , enter <code class="command">yum update <package_name></code>:
+ </div><pre class="screen">
+~]# <code class="command">yum update glibc</code>
+Loaded plugins: presto, refresh-packagekit, security
+Setting up Install Process
+Resolving Dependencies
+--> Running transaction check
+--> Processing Dependency: glibc = 2.10.90-21 for package: glibc-common-2.10.90-21.x86_64
+---> Package glibc.x86_64 0:2.10.90-22 set to be updated
+--> Running transaction check
+---> Package glibc-common.x86_64 0:2.10.90-22 set to be updated
+--> Finished Dependency Resolution
+Dependencies Resolved
+======================================================================
+ Package Arch Version Repository Size
+======================================================================
+Updating:
+ glibc x86_64 2.10.90-22 fedora 2.7 M
+Updating for dependencies:
+ glibc-common x86_64 2.10.90-22 fedora 6.0 M
+Transaction Summary
+======================================================================
+Install 0 Package(s)
+Upgrade 2 Package(s)
+Total download size: 8.7 M
+Is this ok [y/N]:
+</pre><div class="para">
+ This output contains several items of interest:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <code class="computeroutput">Loaded plugins: presto, refresh-packagekit, security</code> — <code class="command">yum</code> always informs you which <span class="application"><strong>Yum</strong></span> plugins are installed and enabled. Here, <code class="command">yum</code> is using the <span class="application"><strong>presto</strong></span>, <span class="application"><strong>refresh-packagekit</strong></span> and <span class="application"><strong>security</strong></span> plugins. Refer to <a class="xref" href="sec-Yum_Plugins.html" title="1.4. Yum Plugins">Section 1.4, “Yum Plugins”</a> for general information on <span class="application"><strong>Yum</strong></span> plugins, or to <a class="xref" href="sec-Plugin_Descriptions.html" title="1.4.3. Plugin Descriptions">Section 1.4.3, “Plugin Descriptions”</a> for descriptions of specific plugins.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">kernel.x86_64</code> — you can download and install new kernels safely with <code class="command">yum</code>.
+ </div><div class="important" title="Important: Updating and Installing Kernels with Yum" id="important-Important-Updating_and_Installing_Kernels_with_Yum"><div class="admonition_header"><h2>Important: Updating and Installing Kernels with Yum</h2></div><div class="admonition"><div class="para">
+ <code class="command">yum</code> always <span class="strong strong"><strong>install</strong></span>s a new kernel in the same sense that <span class="application"><strong>RPM</strong></span> <span class="emphasis"><em>installs</em></span> a new kernel when you use the command <code class="command">rpm -i kernel</code>. Therefore, you do not need to worry about the distinction between <span class="emphasis"><em>installing</em></span> and <span class="emphasis"><em>upgrading</em></span> a kernel package when you use <code class="command">yum</code>: it will do the right thing, regardless of whether you are using the <code class="command">yum update</code> or <code class="command">yum install</code> command.
+ </div><div class="para">
+ When using <span class="application"><strong>RPM</strong></span>, on the other hand, it is important to use the <code class="command">rpm -i kernel</code> command (which installs a new kernel) instead of <code class="command">rpm -u kernel</code> (which <span class="emphasis"><em>replaces</em></span> the current kernel). Refer to <a class="xref" href="sec-Installing_and_Upgrading.html" title="3.2.2. Installing and Upgrading">Section 3.2.2, “Installing and Upgrading”</a> for more information on installing/updating kernels with <span class="application"><strong>RPM</strong></span>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="command">yum</code> presents the update information and then prompts you as to whether you want it to perform the update; <code class="command">yum</code> runs interactively by default. If you already know which transactions <code class="command">yum</code> plans to perform, you can use the <code class="option">-y</code> option to automatically answer <code class="command">yes</code> to any questions <code class="command">yum</code> may ask (in which case it runs non-interactively). However, you should always examine which changes <code class="command">yum</code> plans to make to the system so that you can easily troubleshoot any problems that might arise.
+ </div><div class="para">
+ If a transaction does go awry, you can view <span class="application"><strong>Yum</strong></span>'s log of transactions by entering <code class="command">cat /var/log/yum.log</code> at the shell prompt. The most recent transactions are listed at the end of the log file.
+ </div></li></ol></div><h4>Updating All Packages and Their Dependencies</h4><a id="id633580" class="indexterm"></a><div class="para">
+ To update all packages and their dependencies, simply enter <code class="command">yum update</code> (without any arguments):
+ </div><div class="example" title="Example 1.1. Updating all packages at once" id="ex-Updating_all_packages_at_once"><h6>Example 1.1. Updating all packages at once</h6><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum update</code>
+</pre></div></div><br class="example-break" /></div><div class="section" title="1.1.3. Updating Security-Related Packages" id="sec-Updating_Security-Related_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Updating_Security-Related_Packages">1.1.3. Updating Security-Related Packages</h3></div></div></div><a id="id785052" class="indexterm"></a><a id="id785064" class="indexterm"></a><div class="para">
+ Discovering which packages have security updates available and then updating those packages quickly and easily is important. <span class="application"><strong>Yum</strong></span> provides the
+ <a id="id785083" class="indexterm"></a>
+ plugin for this purpose. The <span class="application"><strong>security</strong></span> plugin extends the <code class="command">yum</code> command with a set of highly-useful security-centric commands, subcommands and options. Refer to <a class="xref" href="sec-Plugin_Descriptions.html#bh-security_yum-plugin-security" title="1.4.3. security (yum-plugin-security)">Section 1.4.3, “security (yum-plugin-security)”</a> for specific information.
+ </div></div><div class="section" title="1.1.4. Preserving Configuration File Changes" id="sec-Preserving_Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Preserving_Configuration_File_Changes">1.1.4. Preserving Configuration File Changes</h3></div></div></div><a id="id785119" class="indexterm"></a><div class="para">
+ You will inevitably make changes to the configuration files installed by packages as you use your Fedora system. <span class="application"><strong>RPM</strong></span>, which <span class="application"><strong>Yum</strong></span> uses to perform changes to the system, provides a mechanism for ensuring their integrity. Refer to <a class="xref" href="sec-Installing_and_Upgrading.html" title="3.2.2. Installing and Upgrading">Section 3.2.2, “Installing and Upgrading”</a> for details on how to manage changes to configuration files across package upgrades.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-pkg-management.html"><strong>Prev</strong>Part I. Package Management</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Packages_and_Package_Groups.html"><strong>Next</strong>1.2. Packages and Package Groups</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch06s02s03.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch06s02s03.html
new file mode 100644
index 0000000..840de1c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch06s02s03.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2.3. Starting and Stopping the Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-dhcp-configuring-server.html" title="6.2. Configuring a DHCP Server" /><link rel="prev" href="lease-database.html" title="6.2.2. Lease Database" /><link rel="next" href="dhcp-relay-agent.html" title="6.2.4. DHCP Relay Agent" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="lease-database.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="dhcp
-relay-agent.html"><strong>Next</strong></a></li></ul><div class="section" title="6.2.3. Starting and Stopping the Server"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id544179">6.2.3. Starting and Stopping the Server</h3></div></div></div><a id="id544185" class="indexterm"></a><a id="id834990" class="indexterm"></a><a id="id835004" class="indexterm"></a><a id="id835021" class="indexterm"></a><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When the DHCP server is started for the first time, it fails unless the <code class="filename">dhcpd.leases</code> file exists. Use the command <code class="command">touch /var/lib/dhcpd/dhcpd.leases</code> to create the file if it does not exist.
+ </div><div class="para">
+ If the same server is also running BIND as a DNS server, this step is not necessary, as starting the <code class="command">named</code> service automatically checks for a <code class="filename">dhcpd.leases</code> file.
+ </div></div></div><div class="para">
+ To start the DHCP service, use the command <code class="command">/sbin/service dhcpd start</code>. To stop the DHCP server, use the command <code class="command">/sbin/service dhcpd stop</code>.
+ </div><div class="para">
+ By default, the DHCP service does not start at boot time. To configure the daemon to start automatically at boot time, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div><a id="id835082" class="indexterm"></a><a id="id505993" class="indexterm"></a><div class="para">
+ If more than one network interface is attached to the system, but the DHCP server should only be started on one of the interfaces, configure the DHCP server to start only on that device. In <code class="filename">/etc/sysconfig/dhcpd</code>, add the name of the interface to the list of <code class="command">DHCPDARGS</code>:
+ </div><pre class="screen">
+# Command line options here
+DHCPDARGS=eth0
+</pre><div class="para">
+ This is useful for a firewall machine with two network cards. One network card can be configured as a DHCP client to retrieve an IP address to the Internet. The other network card can be used as a DHCP server for the internal network behind the firewall. Specifying only the network card connected to the internal network makes the system more secure because users can not connect to the daemon via the Internet.
+ </div><div class="para">
+ Other command line options that can be specified in <code class="filename">/etc/sysconfig/dhcpd</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-p <em class="replaceable"><code><portnum></code></em> </code> — Specifies the UDP port number on which <code class="command">dhcpd</code> should listen. The default is port 67. The DHCP server transmits responses to the DHCP clients at a port number one greater than the UDP port specified. For example, if the default port 67 is used, the server listens on port 67 for requests and responses to the client on port 68. If a port is specified here and the DHCP relay agent is used, the same port on which the DHCP relay agent should listen must be specified. Refer to <a class="xref" href="dhcp-relay-agent.html" title="6.2.4. DHCP Relay Agent">Section 6.2.4, “DHCP Relay Agent”</a> for details.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-f</code> — Runs the daemon as a foreground process. This is mostly used for debugging.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-d</code> — Logs the DHCP server daemon to the standard error descriptor. This is mostly used for debugging. If this is not specified, the log is written to <code class="filename">/var/log/messages</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-cf <em class="replaceable"><code><filename></code></em> </code> — Specifies the location of the configuration file. The default location is <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-lf <em class="replaceable"><code><filename></code></em> </code> — Specifies the location of the lease database file. If a lease database file already exists, it is very important that the same file be used every time the DHCP server is started. It is strongly recommended that this option only be used for debugging purposes on non-production machines. The default location is <code class="filename">/var/lib/dhcpd/dhcpd.leases</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-q</code> — Do not print the entire copyright message when starting the daemon.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="lease-database.html"><strong>Prev</strong>6.2.2. Lease Database</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="dhcp-relay-agent.html"><strong>Next</strong>6.2.4. DHCP Relay Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s02.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s02.html
new file mode 100644
index 0000000..3d23672
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s02.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.2. Installing and Running ABRT</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-abrt.html" title="Chapter 21. ABRT" /><link rel="prev" href="ch-abrt.html" title="Chapter 21. ABRT" /><link rel="next" href="abrt-plugins.html" title="21.3. ABRT Plugins" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-abrt.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="abrt-plugins.html"><strong>Next</strong></a></li></ul><div cla
ss="section" title="21.2. Installing and Running ABRT"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id1770668">21.2. Installing and Running ABRT</h2></div></div></div><div class="para">
+ By default, <span class="application"><strong>ABRT</strong></span> should be installed on your system, the <code class="systemitem">abrtd</code> daemon configured to run at boot time, and <span class="application"><strong>abrt-applet</strong></span> to run in the Notification Area of your desktop session.
+ </div><div class="note" title="Note: Installing the ABRT packages"><div class="admonition_header"><h2>Note: Installing the <span class="application"><strong>ABRT</strong></span> packages</h2></div><div class="admonition"><div class="para">
+ In order to use <span class="application"><strong>ABRT</strong></span>, first ensure the <code class="command">abrt-desktop</code> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install abrt-desktop</code>
+</pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ <span class="application"><strong>ABRT</strong></span> is typically configured to start up at boot time. You can check that the <code class="systemitem">abrtd</code> daemon is running by running the following command, as root:
+ </div><pre class="screen">~]# <code class="command">service abrtd status</code>
+abrt (pid 1559) is running...</pre><div class="para">
+ If you receive <code class="computeroutput">abrt is stopped</code>, you can start the <code class="systemitem">abrtd</code> service by running, as root:
+ </div><pre class="screen">~]# <code class="command">service abrtd start</code>
+Starting abrt daemon: [ OK ]</pre><div class="para">
+ You can ensure that the <code class="systemitem">abrtd</code> service initializes at startup time by running the following command, as root:
+ </div><pre class="screen">~]# <code class="command">chkconfig abrtd on</code>
+</pre><div class="para">
+ <span class="application"><strong>ABRT</strong></span>'s applet can be started by hand by running the <code class="command">abrt-applet</code> program as a normal user when logged into your desktop session, or by arranging for it to be started when the GUI session is initialized. For example, on the GNOME desktop, this can be configured in <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Startup Applications</strong></span>.
+ </div><div class="mediaobject" align="center"><img src="images/ABRT-Notification_Area_alarm_icon.png" align="middle" width="29" /><div class="caption"><div class="para">
+ The ABRT alarm icon
+ </div></div></div><div class="para">
+ When a crash is detected and saved, a broadcast <code class="systemitem">D-Bus</code> message is sent about this crash. If <code class="command">abrt-applet</code> is running, it receives this message and displays a red alarm icon in the Notification Area. You can open the GUI application by clicking on this icon.
+ </div><div class="para">
+ Alternatively, you can open the <span class="application"><strong>ABRT</strong></span> GUI application by clicking <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Automatic Bug Reporting Tool</strong></span>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-abrt.html"><strong>Prev</strong>Chapter 21. ABRT</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="abrt-plugins.html"><strong>Next</strong>21.3. ABRT Plugins</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s05.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s05.html
new file mode 100644
index 0000000..c879595
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s05.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.5. Using the Command Line Interface</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-abrt.html" title="Chapter 21. ABRT" /><link rel="prev" href="generating-backtrace.html" title="21.4. Generating Backtraces" /><link rel="next" href="ch21s05s02.html" title="21.5.2. Reporting Crashes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="generating-backtrace.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch21s05s02.html"><stro
ng>Next</strong></a></li></ul><div class="section" title="21.5. Using the Command Line Interface"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id840565">21.5. Using the Command Line Interface</h2></div></div></div><div class="para">
+ Crashes detected by <span class="application"><strong>ABRT</strong></span> can be viewed, reported, and deleted using the command line interface.
+ </div><div class="section" title="21.5.1. Viewing Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id840579">21.5.1. Viewing Crashes</h3></div></div></div><div class="para">
+ To get a list of all crashes, simply enter <code class="command">abrt-cli --list</code> or <code class="command">abrt-cli -l</code>:
+ </div><pre class="screen">
+~]$ <code class="command">abrt-cli --list</code>
+0.
+ UID : 500
+ UUID : 784b06666020e9f43718d99bf2649f19b4f251a9
+ Package : bash-4.1.2-3.el6
+ Executable : /bin/bash
+ Crash Time : Tue 20 Jul 2010 03:22:52 PM CEST
+ Crash Count: 2
+1.
+ UID : 500
+ UUID : 48007b98d65cca4530d99a564379e2609169239d
+ Package : coreutils-8.4-9.el6
+ Executable : /bin/sleep
+ Crash Time : Tue 20 Jul 2010 03:22:00 PM CEST
+ Crash Count: 1
+</pre><div class="para">
+ This output contains basic information for every crash. The <code class="computeroutput">UID:</code> field shows the ID of the user which ran the program that caused the crash. The <code class="computeroutput">Package</code> field shows the name and version of the Fedora package that contains the program, and the <code class="computeroutput">Executable</code> field shows the location of the binary or script that crashed. The <code class="computeroutput">Crash Count</code> field indicates how many times the same crash happened.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="generating-backtrace.html"><strong>Prev</strong>21.4. Generating Backtraces</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch21s05s02.html"><strong>Next</strong>21.5.2. Reporting Crashes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s05s02.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s05s02.html
new file mode 100644
index 0000000..da0a60a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s05s02.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.5.2. Reporting Crashes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch21s05.html" title="21.5. Using the Command Line Interface" /><link rel="prev" href="ch21s05.html" title="21.5. Using the Command Line Interface" /><link rel="next" href="ch21s05s03.html" title="21.5.3. Deleting Crashes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s05.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch21s05s03.html">
<strong>Next</strong></a></li></ul><div class="section" title="21.5.2. Reporting Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id840630">21.5.2. Reporting Crashes</h3></div></div></div><div class="para">
+ To report a certain crash, enter <code class="command">abrt-cli --report <em class="replaceable"><code><UUID></code></em></code> or <code class="command">abrt-cli --r <em class="replaceable"><code><UUID></code></em></code>, where <code class="varname">UUID</code> is a Universally Unique Identifier of a crash from the list of crashes; to view this list, execute the <code class="command">abrt-cli --list</code> command. You do not need to remember the exact <code class="varname">UUID</code>; either use a mouse to copy and paste it, or enter a unique prefix and press <span class="keycap"><strong><ENTER></strong></span>.
+ </div><pre class="screen">
+~]$ <code class="command">abrt-cli --report 480</code>
+ <span class="keycap"><strong><ENTER></strong></span>
+>> Starting report creation...
+</pre><div class="para">
+ <span class="application"><strong>ABRT</strong></span> analyzes the crash and creates a report about it. This might take a while. When the report is ready, <code class="command">abrt-cli</code> opens a text editor with the content of the report. You can see what is being reported, and you can fill in instructions on how to reproduce the crash and other comments. You should also check the backtrace, because the backtrace might be sent to a public server and viewed by anyone, depending on the plugin settings.
+ </div><div class="note" title="Preferred Text Editor"><div class="admonition_header"><h2>Preferred Text Editor</h2></div><div class="admonition"><div class="para">
+ You can choose which text editor is used to check the reports. <code class="command">abrt-cli</code> uses the editor defined in the <code class="envar">ABRT_EDITOR</code> environment variable. If the variable is not defined, it checks the <code class="envar">VISUAL</code> and <code class="envar">EDITOR</code> variables. If none of these variables is set, <code class="command">vi</code> is used. You can set the preferred editor in your <code class="filename">.bashrc</code> configuration file. For example, if you prefer GNU Emacs, add the following line to the file:
+ </div><pre class="screen">
+export <code class="varname">VISUAL</code>=<strong class="userinput"><code>emacs</code></strong></pre></div></div><div class="para">
+ When you are done with the report, save your changes and close the editor. You will be asked which of the enabled <span class="application"><strong>ABRT</strong></span> plugins you want to use to send the report. Respond <span class="keycap"><strong>Y</strong></span> to send the report using your desired plugin or <span class="keycap"><strong>N</strong></span> to skip a plugin you wish not to use.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s05.html"><strong>Prev</strong>21.5. Using the Command Line Interface</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch21s05s03.html"><strong>Next</strong>21.5.3. Deleting Crashes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s05s03.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s05s03.html
new file mode 100644
index 0000000..192518c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ch21s05s03.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.5.3. Deleting Crashes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch21s05.html" title="21.5. Using the Command Line Interface" /><link rel="prev" href="ch21s05s02.html" title="21.5.2. Reporting Crashes" /><link rel="next" href="configuring.html" title="21.6. Configuring ABRT" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s05s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="configuring.html"><strong
>Next</strong></a></li></ul><div class="section" title="21.5.3. Deleting Crashes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id549181">21.5.3. Deleting Crashes</h3></div></div></div><div class="para">
+ If you know that you do not want to report a certain crash dump, you can delete it from the crash list. To delete a certain crash dump, enter the command: <code class="command">abrt-cli --delete <em class="replaceable"><code><UUID></code></em> </code>.
+ </div><div class="para">
+ Note that <span class="application"><strong>ABRT</strong></span> performs a detection of duplicate crashes by comparing new crashes with all locally saved crashes. For a repeating crash, <span class="application"><strong>ABRT</strong></span> requires you to act upon it only once. However, if you delete the crash dump of that crash, the next time this specific crash occurs, <span class="application"><strong>ABRT</strong></span> will treat it as a new crash: <span class="application"><strong>ABRT</strong></span> will alert you about it, prompt you to fill in a description, and report it. This can be redundant, therefore, deleting a crash is not advisable.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s05s02.html"><strong>Prev</strong>21.5.2. Reporting Crashes</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="configuring.html"><strong>Next</strong>21.6. Configuring ABRT</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-Date_and_Time_Configuration.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-Date_and_Time_Configuration.html
new file mode 100644
index 0000000..7169755
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-Date_and_Time_Configuration.html
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 13. Date and Time Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pt-sysconfig.html" title="Part III. System Configuration" /><link rel="prev" href="pt-sysconfig.html" title="Part III. System Configuration" /><link rel="next" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html" title="13.2. Command Line Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-sysconfig.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" title="Chapter 13. Date and Time Configuration" id="chap-Date_and_Time_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 13. Date and Time Configuration</h2></div></div></div><div class="toc"><dl><dt><span class="section"><a href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool">13.1. Date/Time Properties Tool</a></span></dt><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html">13.2. Command Line Configuration</a></span></dt></dl></div><div class="para">
+ This chapter covers setting the system date and time in Fedora, both manually and using the Network Time Protocol (<abbr class="abbrev">NTP</abbr>), as well as setting the adequate time zone. Two methods are covered: setting the date and time using the <span class="application"><strong>Date/Time Properties</strong></span> tool, and doing so on the command line.
+ </div><div class="section" title="13.1. Date/Time Properties Tool" id="sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool">13.1. Date/Time Properties Tool</h2></div></div></div><div class="para">
+ The <span class="application"><strong>Date/Time Properties</strong></span> tool allows the user to change the system date and time, to configure the time zone used by the system, and to set up the Network Time Protocol daemon to synchronize the system clock with a time server. Note that to use this application, you must be running the <span class="emphasis"><em>X Window System</em></span>.
+ </div><a id="id697727" class="indexterm"></a><div class="para">
+ To start the tool, select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Date & Time</strong></span> from the panel, or type the <code class="command">system-config-date</code> command at a shell prompt (e.g., <span class="emphasis"><em>xterm</em></span> or <span class="emphasis"><em>GNOME Terminal</em></span>). Unless you are already authenticated, you will be prompted to enter the superuser password.
+ </div><div class="figure" title="Figure 13.1. Authentication Query" id="figu-Date_and_Time_Configuration-Authentication"><div class="figure-contents"><div class="mediaobject"><img src="images/date-and-time-authentication.png" alt="Authentication Query" /></div></div><h6>Figure 13.1. Authentication Query</h6></div><br class="figure-break" /><div class="section" title="13.1.1. Date and Time Properties" id="sect-Date_and_Time_Configuration-Date_and_Time"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Date_and_Time_Configuration-Date_and_Time">13.1.1. Date and Time Properties</h3></div></div></div><a id="id823586" class="indexterm"></a><a id="id437446" class="indexterm"></a><div class="para">
+ As shown in <a class="xref" href="chap-Date_and_Time_Configuration.html#figu-Date_and_Time_Configuration-Date_and_Time" title="Figure 13.2. Date and Time Properties">Figure 13.2, “Date and Time Properties”</a>, the <span class="application"><strong>Date/Time Properties</strong></span> tool is divided into two separate tabs. The tab containing the configuration of the current date and time is shown by default.
+ </div><div class="figure" title="Figure 13.2. Date and Time Properties" id="figu-Date_and_Time_Configuration-Date_and_Time"><div class="figure-contents"><div class="mediaobject"><img src="images/date-and-time-date_and_time.png" alt="Date and Time Properties" /><div class="longdesc"><div class="para">
+ Date and Time Properties
+ </div></div></div></div><h6>Figure 13.2. Date and Time Properties</h6></div><br class="figure-break" /><div class="para">
+ To set up your system manually, follow these steps:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ <span class="emphasis"><em>Change the current date.</em></span> Use the arrows to the left and right of the month and year to change the month and year respectively. Then click inside the calendar to select the day of the month.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ <span class="emphasis"><em>Change the current time.</em></span> Use the up and down arrow buttons beside the <span class="guilabel"><strong>Hour</strong></span>, <span class="guilabel"><strong>Minute</strong></span>, and <span class="guilabel"><strong>Second</strong></span>, or replace the values directly.
+ </div></li></ol></div><div class="para">
+ Click the <span class="guibutton"><strong>OK</strong></span> button to apply the changes and exit the application.
+ </div></div><div class="section" title="13.1.2. Network Time Protocol Properties" id="sect-Date_and_Time_Configuration-Network_Time_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Date_and_Time_Configuration-Network_Time_Protocol">13.1.2. Network Time Protocol Properties</h3></div></div></div><a id="id527391" class="indexterm"></a><a id="id527404" class="indexterm"></a><a id="id527418" class="indexterm"></a><a id="id527431" class="indexterm"></a><a id="id497631" class="indexterm"></a><div class="para">
+ If you prefer an automatic setup, select the checkbox labeled <span class="guilabel"><strong>Synchronize date and time over the network</strong></span> instead. This will display the list of available NTP servers as shown in <a class="xref" href="chap-Date_and_Time_Configuration.html#figu-Date_and_Time_Configuration-Network_Time_Protocol" title="Figure 13.3. Network Time Protocol Properties">Figure 13.3, “Network Time Protocol Properties”</a>.
+ </div><div class="figure" title="Figure 13.3. Network Time Protocol Properties" id="figu-Date_and_Time_Configuration-Network_Time_Protocol"><div class="figure-contents"><div class="mediaobject"><img src="images/date-and-time-network_time_protocol.png" alt="Network Time Protocol Properties" /><div class="longdesc"><div class="para">
+ Network Time Protocol Properties
+ </div></div></div></div><h6>Figure 13.3. Network Time Protocol Properties</h6></div><br class="figure-break" /><div class="para">
+ Here you can choose one of the predefined servers, edit a predefined server by clicking the <span class="guibutton"><strong>Edit</strong></span> button, or add a new server name by clicking <span class="guibutton"><strong>Add</strong></span>. In the <span class="guilabel"><strong>Advanced Options</strong></span>, you can also select whether you want to synchronize the system clock before starting the service, and if you wish to use a local time source.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Your system does not start synchronizing with the NTP server until you click the <span class="guibutton"><strong>OK</strong></span> button at the bottom of the window to confirm your changes.
+ </div></div></div><div class="para">
+ Click the <span class="guibutton"><strong>OK</strong></span> button to apply any changes made to the date and time settings and exit the application.
+ </div></div><div class="section" title="13.1.3. Time Zone Properties" id="sect-Date_and_Time_Configuration-Time_Zone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Date_and_Time_Configuration-Time_Zone">13.1.3. Time Zone Properties</h3></div></div></div><a id="id690150" class="indexterm"></a><div class="para">
+ To configure the system time zone, click the <span class="guilabel"><strong>Time Zone</strong></span> tab as shown in <a class="xref" href="chap-Date_and_Time_Configuration.html#figu-Date_and_Time_Configuration-Time_Zone" title="Figure 13.4. Time Zone Properties">Figure 13.4, “Time Zone Properties”</a>.
+ </div><div class="figure" title="Figure 13.4. Time Zone Properties" id="figu-Date_and_Time_Configuration-Time_Zone"><div class="figure-contents"><div class="mediaobject"><img src="images/date-and-time-time_zone.png" alt="Time Zone Properties" /><div class="longdesc"><div class="para">
+ Time Zone Properties
+ </div></div></div></div><h6>Figure 13.4. Time Zone Properties</h6></div><br class="figure-break" /><div class="para">
+ There are two common approaches to the time zone selection:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Using the interactive map.</em></span> Click “zoom in” and “zoom out” buttons next to the map, or click on the map itself to zoom into the selected region. Then choose the city specific to your time zone. A red <span class="guilabel"><strong>X</strong></span> appears and the time zone selection changes in the list below the map.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Use the list below the map.</em></span> To make the selection easier, cities and countries are grouped within their specific continents. Note that non-geographic time zones have also been added to address needs in the scientific community.
+ </div></li></ol></div><div class="para">
+ If your system clock is set to use <acronym class="acronym">UTC</acronym>, select the <span class="guibutton"><strong>System clock uses UTC</strong></span> option. UTC stands for the <em class="firstterm">Universal Time, Coordinated</em>, also known as <em class="firstterm">Greenwich Mean Time</em> (<acronym class="acronym">GMT</acronym>). Other time zones are determined by adding or subtracting from the UTC time.
+ </div><div class="para">
+ Click <span class="guibutton"><strong>OK</strong></span> to apply the changes and exit the program.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pt-sysconfig.html"><strong>Prev</strong>Part III. System Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"><strong>Next</strong>13.2. Command Line Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Domains.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Domains.html
new file mode 100644
index 0000000..d9fbba8
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Domains.html
@@ -0,0 +1,269 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.5. Configuring Domains</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Configuring_Services.html" title="8.2.4. Configuring Services" /><link rel="next" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html" title="8.2.6. Setting Up Kerberos Authentication" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li c
lass="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Configuring_Services.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>Next</strong></a></li></ul><div class="section" title="8.2.5. Configuring Domains" id="chap-SSSD_User_Guide-Configuring_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="chap-SSSD_User_Guide-Configuring_Domains">8.2.5. Configuring Domains</h3></div></div></div><div class="para">
+ A domain is a database of user information. SSSD can use more than one domain at the same time, but at least one must be configured for SSSD to start. Using SSSD domains, it is possible to use several LDAP servers providing several unique namespaces. You can specify not only where users' identity information is stored, but how users authenticate against each of the specified domains.
+ </div><div class="para">
+ SSSD supports the following identity and authentication combinations:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a class="link" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain" title="8.2.5.2. Configuring an LDAP Domain">LDAP/LDAP</a>
+ </div><div class="para">
+ This combination uses an LDAP back end as both the identity and authentication provider.
+ </div></li><li class="listitem"><div class="para">
+ <a class="link" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html" title="8.2.6. Setting Up Kerberos Authentication">LDAP/KRB5</a>
+ </div><div class="para">
+ This combination uses an LDAP back end as the identity provider, and uses Kerberos to provide authentication.
+ </div></li><li class="listitem"><div class="para">
+ proxy
+ </div><div class="para">
+ Specifying a proxy identity or authentication provider uses an existing NSS library or customized PAM stack, but takes advantage of the SSSD caching mechanism.
+ </div></li></ul></div>
+
+ </div><div class="para">
+ The following example assumes that SSSD is correctly configured and FOO is one of the domains in the <code class="literal">[sssd]</code> section. This example shows only the configuration of Kerberos authentication; it does not include any identity provider.
+ </div><pre class="screen">[domain/FOO]
+auth_provider = krb5
+krb5_kdcip = 192.168.1.1
+krb5_realm = EXAMPLE.COM</pre><div class="section" title="8.2.5.1. Domain Configuration Options" id="sect-SSSD_User_Guide-Configuring_Domains-Domain_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Domain_Configuration_Options">8.2.5.1. Domain Configuration Options</h4></div></div></div><div class="para">
+ You can add new domain configurations to the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> sections of the <code class="filename">/etc/sssd/sssd.conf</code> file, and then add the list of domains to the <em class="parameter"><code>domains</code></em> attribute of the <code class="literal">[sssd]</code> section, in the order you want them to be queried.
+ </div><div class="section" title="8.2.5.1.1. General Domain Configuration Options" id="sect-SSSD_User_Guide-Domain_Configuration_Options-General_Domain_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Domain_Configuration_Options-General_Domain_Configuration_Options">8.2.5.1.1. General Domain Configuration Options</h5></div></div></div><div class="para">
+ You can use the following configuration options in a domain configuration section:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">min_id,max_id <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the UID and GID limits for the domain. If a domain contains entries that are outside these limits, they are ignored.
+ </div><div class="para">
+ The default value for <code class="option">min_id</code> is <code class="literal">1</code>; the default value for <code class="option">max_id</code> is <code class="literal">0</code> (unbounded).
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If <code class="option">min_id</code> is unspecified, it defaults to <code class="literal">1</code> for any back end. This default was chosen to provide compatibility with existing systems and to ease any migration attempts. LDAP administrators should be aware that granting identities in this range may conflict with users in the local <code class="filename">/etc/passwd</code> file. To avoid these conflicts, <code class="option">min_id</code> should be set to <code class="literal">1000</code> or higher wherever possible.
+ </div><div class="para">
+ The <code class="option">min_id</code> option determines the minimum acceptable value for both UID and GID numbers. Accounts with either UID or GID values below the <code class="option">min_id</code> value are filtered out and not made available on the client.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">enumerate <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not to enumerate (list) the users and groups of a domain.
+ </div><div class="para">
+ Enumeration means that the entire set of available users and groups on the remote source is cached on the local machine. When enumeration is disabled, users and groups are only cached as they are requested. For performance reasons, it is recommended that you disable enumeration for domains with many users and groups.
+ </div><div class="para">
+ The default value for this parameter is <code class="literal">FALSE</code>. Set this value to <code class="literal">TRUE</code> to enable enumeration of users and groups of a domain.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the timeout in seconds for this particular domain.
+ </div><div class="para">
+ This is used to ensure that the backend process is alive and capable of answering requests. The default value for this parameter is <code class="literal">10</code> seconds. Raising this timeout might prove useful for slower back ends, such as distant LDAP servers.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If you set <code class="option">timeout = 0</code>, SSSD reverts to the default value; you cannot force a timeout value of zero, because this would force the <code class="systemitem">sssd</code> daemon into a loop.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">cache_credentials <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not to store user credentials in the local SSSD domain database cache.
+ </div><div class="para">
+ The default value for this parameter is <code class="literal">FALSE</code>. You should set this value to <code class="literal">TRUE</code> for domains other than local if you want to enable offline authentication.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">id_provider <span class="type">(string)</span> </code>
+ </div><div class="para">
+ Specifies the data provider identity back end to use for this domain. Currently supported identity back ends are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ proxy — Support a legacy <code class="systemitem">NSS</code> provider (for example, <span class="package">nss_nis</span>).
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ SSSD needs to know which legacy NSS library to load in order to start successfully. If you set <code class="option">id_provider</code> to <code class="literal">proxy</code>, ensure that you also specify a value for <code class="option">proxy_lib_name</code>. Refer to <a class="xref" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain" title="8.2.5.4. Configuring a Proxy Domain">Section 8.2.5.4, “Configuring a Proxy Domain”</a> for information on this attribute.
+ </div></div></div></li><li class="listitem"><div class="para">
+ local — <code class="systemitem">SSSD</code> internal local provider.
+ </div></li><li class="listitem"><div class="para">
+ ldap — <code class="systemitem">LDAP</code> provider.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_cache_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long the domain's data provider should cache positive cache hits (that is, queries for valid database entries) before asking the database again.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">use_fully_qualified_names <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ Specifies whether or not requests to this domain require fully-qualified domain names.
+ </div><div class="para">
+ If set to <code class="literal">TRUE</code>, all requests to this domain must use fully-qualified domain names. It also means that the output from the request displays the fully-qualified name.
+ </div><div class="para">
+ The ability to restrict requests in this way means that if you know you have multiple domains with conflicting usernames, then there is no doubt about which username the query will resolve.
+ </div><div class="para">
+ Consider the following examples, in which the IPA domain database contains a user named <code class="systemitem">ipauser01</code>, and the <em class="parameter"><code>use_fully_qualified_names</code></em> attribute is set to <code class="literal">TRUE</code>:
+ </div><pre class="screen">
+<code class="command"># getent passwd ipauser01</code>
+[no output]
+<code class="command"># getent passwd ipauser01 at IPA</code>
+ipauser01 at IPA:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+</pre><div class="para">
+ In the following examples, using the same IPA domain and user, the <em class="parameter"><code>use_fully_qualified_names</code></em> attribute is set to <code class="literal">FALSE</code>:
+ </div><pre class="screen">
+<code class="command"># getent passwd ipauser01</code>
+ipauser01:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+<code class="command"># getent passwd ipauser01 at IPA</code>
+ipauser01:x:937315651:937315651:ipauser01:/home/ipauser01:/bin/sh
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If <em class="parameter"><code>use_fully_qualified_names</code></em> is set to <code class="literal">FALSE</code>, you can continue to use the fully-qualified name in your requests, but only the simplified version is displayed in the output.
+ </div><div class="para">
+ SSSD can only parse <code class="systemitem">name at domain</code>, not <code class="systemitem">name at realm</code>. You can, however, use the same name for both your domain and your realm.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">auth_provider <span class="type">(string)</span> </code>
+ </div><div class="para">
+ The authentication provider used for the domain. The default value for this option is the value of <code class="option">id_provider</code> if it is set and can handle authentication requests.
+ </div><div class="para">
+ Currently supported authentication providers are:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ ldap — for native LDAP authentication. Refer to the sssd-ldap(5) manual page for more information on configuring LDAP.
+ </div></li><li class="listitem"><div class="para">
+ krb5 — for Kerberos authentication. Refer to the sssd-krb5(5) manual page for more information on configuring Kerberos.
+ </div></li><li class="listitem"><div class="para">
+ proxy — for relaying authentication to some other PAM target.
+ </div></li><li class="listitem"><div class="para">
+ none — explicitly disables authentication.
+ </div></li></ul></div>
+
+ </div></li></ul></div></div><div class="section" title="8.2.5.1.2. Proxy Configuration Options" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Proxy_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Proxy_Configuration_Options">8.2.5.1.2. Proxy Configuration Options</h5></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">proxy_pam_target</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">auth_provider</code> option is set to <code class="literal">proxy</code>, and specifies the target to which <acronym class="acronym">PAM</acronym> must proxy.
+ </div><div class="para">
+ This option has no default value. If proxy authentication is required, you need to specify your own <acronym class="acronym">PAM</acronym> target. This corresponds to a file containing <acronym class="acronym">PAM</acronym> stack information in the system's default <acronym class="acronym">PAM</acronym> configuration directory. On Fedora-based systems, this is the <code class="filename">/etc/pam.d/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">proxy_lib_name</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">id_provider</code> option is set to <code class="literal">proxy</code>, and specifies which existing NSS library to proxy identity requests through.
+ </div><div class="para">
+ This option has no default value. You need to manually specify an existing library to take advantage of this option. For example, set this value to <code class="literal">nis</code> to use the existing <code class="filename">libnss_nis.so</code> file.
+ </div></li></ul></div></div></div><div class="section" title="8.2.5.2. Configuring an LDAP Domain" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">8.2.5.2. Configuring an LDAP Domain</h4></div></div></div><a id="id527468" class="indexterm"></a><div class="para">
+ An LDAP domain is one where the <code class="option">id_provider</code> option is set to <code class="literal">ldap</code> (<code class="option">id_provider = ldap</code>). Such a domain requires a running LDAP server against which to authenticate. This can be an open source LDAP server such as OpenLDAP or Microsoft Active Directory. SSSD currently supports Microsoft Active Directory 2003 (+Services For UNIX) and Active Directory 2008 (+Subsystem for UNIX-based applications). In all cases, the client configuration is stored in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-How_to_Authenticate_Against_an_LDAP_Server"><h5 class="formalpara">How to Authenticate Against an LDAP Server</h5>
+ SSSD does not support authentication over an unencrypted channel. Consequently, if you want to authenticate against an LDAP server, either <code class="systemitem">TLS/SSL</code>, <code class="systemitem">LDAPS</code>, or <code class="systemitem">LDAP+GSSAPI</code> is required. If the LDAP server is used only as an identity provider, an encrypted channel is not needed.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file to reflect the following example:
+ </div><pre class="screen"># A native LDAP domain
+[domain/LDAP]
+enumerate = false
+cache_credentials = TRUE
+
+id_provider = ldap
+auth_provider = ldap
+ldap_schema = rfc2307
+chpass_provider = ldap
+
+ldap_uri = ldap://ldap.mydomain.org
+ldap_search_base = dc=mydomain,dc=org
+tls_reqcert = demand
+ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
+</pre><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-Selecting_an_LDAP_Schema"><h5 class="formalpara">Selecting an LDAP Schema</h5><a id="id455281" class="indexterm"></a>
+ You can set the <em class="parameter"><code>ldap_schema</code></em> attribute to either <code class="literal">rfc2307</code> or <code class="literal">rfc2307bis</code>. These schema define how groups in <acronym class="acronym">LDAP</acronym> are specified. In <em class="citetitle">RFC 2307</em>, group objects use a multi-valued attribute, <em class="parameter"><code>memberuid</code></em>, which lists the names of the users that belong to that group. In <em class="citetitle">RFC 2307bis</em>, instead of the <em class="parameter"><code>memberuid</code></em>, group objects use the <em class="parameter"><code>member</code></em> attribute. Rather than just the name of the user, this attribute contains the full Distinguished Name (DN) of another object in the LDAP database. This means that groups can have other groups as members. That is, it adds support for nested groups.
+ </div><div class="para">
+ SSSD assumes that your LDAP server is using <em class="citetitle">RFC 2307</em>. If your LDAP server is using <em class="citetitle">RFC 2307bis</em>, and you do not update the <code class="filename">/etc/sssd/sssd.conf</code> file accordingly, this can impact how your users and groups are displayed. It also means that some groups will not be available and network resources may be inaccessible even though you have permissions to use them.
+ </div><div class="para">
+ For example, when using <em class="citetitle">RFC 2307bis</em> and you have configured both primary and secondary groups, or are using nested groups, you can use the <code class="command">id</code> command to display these groups:
+ </div><pre class="screen">[f12server at ipaserver ~]$ id
+uid=500(f12server) gid=500(f12server) groups=500(f12server),510(f12tester)
+</pre><div class="para">
+ If instead you have configured your client to use <em class="citetitle">RFC 2307</em> then only the primary group is displayed.
+ </div><div class="para">
+ Changes to this setting only affect how SSSD determines the groups to which a user belongs; there is no negative effect on the actual user data. If you do not know the correct value for this attribute, consult your System Administrator.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Configuring_a_Native_LDAP_Domain-Specifying_Timeout_Values"><h5 class="formalpara">Specifying Timeout Values</h5><a id="id760113" class="indexterm"></a>
+ SSSD supports a number of timeout values that apply when configuring an <acronym class="acronym">LDAP</acronym> domain. These are described below.
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">ldap_search_timeout (integer)</code> — Specifies the timeout (in seconds) that <acronym class="acronym">LDAP</acronym> searches are allowed to run before they are cancelled and cached results are returned (and offline mode is entered). If not specified:
+ </div><div class="para">
+ Defaults to five when <code class="option">enumerate</code> = <code class="literal">False</code>
+ </div><div class="para">
+ Defaults to 30 when <code class="option">enumerate</code> = <code class="literal">True</code>. This option is forced to a minimum of 30 in this case.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This option is subject to change in future versions of SSSD, where it may be replaced by a series of timeouts for specific look-up types.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">ldap_network_timeout (integer)</code> — Specifies the timeout (in seconds) after which the <code class="function">poll(2)</code>/<code class="function">select(2)</code> following a <code class="function">connect(2)</code> returns in case of no activity.
+ </div><div class="para">
+ If not specified, defaults to five.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">ldap_opt_timeout (integer)</code> — Specifies the timeout (in seconds) after which calls to synchronous <acronym class="acronym">LDAP</acronym> APIs will abort if no response is received. This option also controls the timeout when communicating with the KDC in case of a SASL bind.
+ </div><div class="para">
+ If not specified, defaults to five.
+ </div></li></ul></div>
+
+ </div></div><div class="section" title="8.2.5.3. Configuring a Microsoft Active Directory Domain" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain">8.2.5.3. Configuring a Microsoft Active Directory Domain</h4></div></div></div><a id="id834167" class="indexterm"></a><div class="para">
+ You can configure SSSD to use Microsoft Active Directory as an LDAP back end, providing both identity and authentication services. If you are using Active Directory 2003, SSSD requires that you install Windows Services for UNIX (SFU) on the machine where Active Directory is installed. If instead you are using Active Directory 2008, you need to install the Subsystem for UNIX-based Applications (SUA) on the Active Directory machine.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ SFU is not supported on 64-bit operating systems. Refer to <a href="http://support.microsoft.com/kb/920751">http://support.microsoft.com/kb/920751</a> for more information about which Windows systems can provide a suitable platform for an SSSD LDAP back end.
+ </div></div></div><div class="section" title="8.2.5.3.1. Configuring Active Directory 2003 as an LDAP Back End" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2003"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2003">8.2.5.3.1. Configuring Active Directory 2003 as an LDAP Back End</h5></div></div></div><div class="para">
+ The example <code class="filename">/etc/sssd/sssd.conf</code> file that ships with SSSD contains the following sample configuration for Active Directory 2003:
+ </div><pre class="screen"># Example LDAP domain where the LDAP server is an Active Directory 2003 server.
+
+[domain/AD]
+description = LDAP domain with AD server
+enumerate = false
+min_id = 1000
+;
+id_provider = ldap
+auth_provider = ldap
+ldap_uri = ldap://your.ad.server.com
+ldap_schema = rfc2307bis
+ldap_search_base = dc=example,dc=com
+ldap_default_bind_dn = cn=Administrator,cn=Users,dc=example,dc=com
+ldap_default_authtok_type = password
+ldap_default_authtok = YOUR_PASSWORD
+ldap_user_object_class = person
+ldap_user_name = msSFU30Name
+ldap_user_uid_number = msSFU30UidNumber
+ldap_user_gid_number = msSFU30GidNumber
+ldap_user_home_directory = msSFU30HomeDirectory
+ldap_user_shell = msSFU30LoginShell
+ldap_user_principal = userPrincipalName
+ldap_group_object_class = group
+ldap_group_name = msSFU30Name
+ldap_group_gid_number = msSFU30GidNumber</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This configuration is specific to Windows Active Directory 2003. Refer to <a class="xref" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008" title="8.2.5.3.2. Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends">Section 8.2.5.3.2, “Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends”</a> for information on how to configure Active Directory 2003 R2 and Active Directory 2008.
+ </div></div></div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The above configuration assumes that the certificates are stored in the default location (that is, in <code class="filename">/etc/openldap/cacerts</code>) and that the <code class="function">c_rehash</code> function has been used to create the appropriate symlinks.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="id549708">More Information</h5>
+ Refer to the <em class="citetitle">sssd-ldap(5)</em> manual page for a full description of all the options that apply to <acronym class="acronym">LDAP</acronym> domains.
+ </div></div><div class="section" title="8.2.5.3.2. Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain-Configuring_AD_2008">8.2.5.3.2. Configuring Active Directory 2003 R2 and 2008 as LDAP Back Ends</h5></div></div></div><div class="para">
+ The configuration of <code class="filename">/etc/sssd/sssd.conf</code> to support Active Directory 2003 R2 or Active Directory 2008 as a back end is similar to that for AD 2003. The following example configuration highlights the necessary changes.
+ </div><pre class="screen"># Example LDAP domain where the LDAP server is an Active Directory 2003 R2 or an Active Directory 2008 server.
+
+[domain/AD]
+description = LDAP domain with AD server
+; debug_level = 9
+enumerate = false
+
+id_provider = ldap
+auth_provider = ldap
+chpass_provider = ldap
+
+ldap_uri = ldap://your.ad.server.com
+ldap_tls_cacertdir = /etc/openldap/cacerts
+ldap_tls_cacert = /etc/openldap/cacerts/test.cer
+ldap_search_base = dc=example,dc=com
+ldap_default_bind_dn = cn=Administrator,cn=Users,dc=example,dc=com
+ldap_default_authtok_type = password
+ldap_default_authtok = YOUR_PASSWORD
+ldap_pwd_policy = none
+ldap_user_object_class = user
+ldap_group_object_class = group</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The above configuration assumes that the certificates are stored in the default location (that is, in <code class="filename">/etc/openldap/cacerts</code>) and that the <code class="function">c_rehash</code> function has been used to create the appropriate symlinks.
+ </div></div></div></div></div><div class="section" title="8.2.5.4. Configuring a Proxy Domain" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">8.2.5.4. Configuring a Proxy Domain</h4></div></div></div><a id="id526920" class="indexterm"></a><div class="para">
+ SSSD currently only supports LDAP and Kerberos as authentication providers. If you prefer to use SSSD (for example, to take advantage of its caching functionality), but SSSD does not support your authentication method, you can set up a proxy authentication provider. This could be the case if you use fingerprint scanners or smart cards as part of your authentication process.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">proxy_pam_target</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">auth_provider</code> option is set to <code class="literal">proxy</code>, and specifies the proxy target that <acronym class="acronym">PAM</acronym> proxies to.
+ </div><div class="para">
+ This option has no default value. If proxy authentication is required, you need to specify your own <acronym class="acronym">PAM</acronym> target. This corresponds to a file containing <acronym class="acronym">PAM</acronym> stack information in the system's default <acronym class="acronym">PAM</acronym> configuration directory. On Fedora—based systems, this is the <code class="filename">/etc/pam.d/</code> directory.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Ensure that your proxy PAM stack does <span class="emphasis"><em>not</em></span> recursively include <code class="filename">pam_sss.so</code>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="option">proxy_lib_name</code> <span class="type">(string)</span>
+ </div><div class="para">
+ This option is only used when the <code class="option">id_provider</code> option is set to <code class="literal">proxy</code>, and specifies which existing NSS library to proxy identity requests through.
+ </div><div class="para">
+ This option has no default value. You need to manually specify an existing library to take advantage of this option. For example, set this value to <code class="literal">nis</code> to use the existing <code class="filename">libnss_nis.so</code> file.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Configuring_Services.html"><strong>Prev</strong>8.2.4. Configuring Services</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>Next</strong>8.2.6. Setting Up Kerberos Authentication</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Services.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Services.html
new file mode 100644
index 0000000..302fa57
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Configuring_Services.html
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.4. Configuring Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html" title="8.2.3. Setting Up SSSD" /><link rel="next" href="chap-SSSD_User_Guide-Configuring_Domains.html" title="8.2.5. Configuring Domains" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-
Setting_Up_SSSD.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Configuring_Domains.html"><strong>Next</strong></a></li></ul><div class="section" title="8.2.4. Configuring Services" id="chap-SSSD_User_Guide-Configuring_Services"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="chap-SSSD_User_Guide-Configuring_Services">8.2.4. Configuring Services</h3></div></div></div><div class="para">
+ Individual pieces of SSSD functionality are provided by special SSSD services that are started and stopped together with SSSD. The services provided by SSSD have their own configuration sections. The <code class="literal">[sssd]</code> section also lists the services that are active and should be started when <code class="systemitem">sssd</code> starts within the <code class="command">services</code> directive.
+ </div><div class="para">
+ SSSD currently provides several services:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">NSS</code> — An NSS provider service that answers NSS requests from the <code class="systemitem">sssd_nss</code> module.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">PAM</code> — A PAM provider service that manages a PAM conversation through the <code class="systemitem">sssd_pam</code> PAM module.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">monitor</code> — A special service that monitors all other SSSD services, and starts or restarts them as needed. Its options are specified in the <code class="literal">[sssd]</code> section of the <code class="filename">/etc/sssd/sssd.conf</code> configuration file.
+ </div></li></ul></div><div class="section" title="8.2.4.1. Configuration Options" id="sect-SSSD_User_Guide-Configuring_Services-Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Configuring_Services-Configuration_Options">8.2.4.1. Configuration Options</h4></div></div></div><div class="para">
+ The following sections cover the most important SSSD configuration options. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page that ships with SSSD for information on all the available configuration options.
+ </div><div class="section" title="8.2.4.1.1. General Configuration Options" id="sect-SSSD_User_Guide-Configuration_Options-General_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuration_Options-General_Configuration_Options">8.2.4.1.1. General Configuration Options</h5></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">debug_level <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Sets the debug level for a particular service. This is a per-service setting (that is, it can appear in any of the <code class="literal">[service/<NAME>]</code> sections in the SSSD configuration file).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">reconnection_retries <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ In the event of a data provider crash or restart, this specifies the number of times that a service should attempt to reconnect.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If a <code class="systemitem">DNS</code> lookup fails to return an <code class="systemitem">IPv4</code> address for a hostname, SSSD attempts to look up an <code class="systemitem">IPv6</code> address before returning a failure. Note that this only ensures that the async resolver identifies the correct address; there is currently a bug in the LDAP code that prevents SSSD from connecting to an LDAP server over IPv6. This is being investigated separately.
+ </div></div></div></li></ul></div></div><div class="section" title="8.2.4.1.2. NSS Configuration Options" id="sect-SSSD_User_Guide-Configuration_Options-NSS_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuration_Options-NSS_Configuration_Options">8.2.4.1.2. NSS Configuration Options</h5></div></div></div><div class="para">
+ Use the following options to configure the <code class="systemitem">Name Service Switch (NSS)</code> service. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for full details about each option.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">enum_cache_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long (in seconds) <span class="package">sssd_nss</span> should cache enumerations (requests for information about all users).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_cache_nowait_percentage <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long <span class="package">sssd_nss</span> should return cached entries before initiating an out-of-band cache refresh (<code class="literal">0</code> disables this feature).
+ </div><div class="para">
+ You can configure the entry cache to automatically update entries in the background if they are requested beyond a percentage of the <code class="option">entry_cache_timeout</code> value for the domain.
+ </div><div class="para">
+ Valid values for this option are <code class="literal">0-99</code>, and represent a percentage of the <code class="option">entry_cache_timeout</code> value for each domain.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">entry_negative_timeout <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies for how long (in seconds) <span class="package">sssd_nss</span> should cache negative cache hits (that is, queries for invalid database entries, such as nonexistent ones) before asking the back end again.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">filter_users, filter_groups <span class="type">(string)</span> </code>
+ </div><div class="para">
+ Exclude certain users from being fetched from the sss NSS database. This is particularly useful for system accounts such as <code class="systemitem">root</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">filter_users_in_groups <span class="type">(Boolean)</span> </code>
+ </div><div class="para">
+ If set to <code class="literal">TRUE</code>, specifies that users listed in the <code class="option">filter_users</code> list do not appear in group memberships when performing group lookups. If set to <code class="literal">FALSE</code>, group lookups return all users that are members of that group. If not specified, defaults to <code class="literal">TRUE</code>.
+ </div></li></ul></div></div><div class="section" title="8.2.4.1.3. PAM Configuration Options" id="sect-SSSD_User_Guide-Configuration_Options-PAM_Configuration_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuration_Options-PAM_Configuration_Options">8.2.4.1.3. PAM Configuration Options</h5></div></div></div><div class="para">
+ Use the following options to configure the <code class="systemitem">Pluggable Authentication Module (<acronym class="acronym">PAM</acronym>)</code> service.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">offline_credentials_expiration <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ If the authentication provider is offline, specifies for how long to allow cached log-ins (in days). This value is measured from the last successful online log-in. If not specified, defaults to <code class="literal">0</code> (no limit).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">offline_failed_login_attempts <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ If the authentication provider is offline, specifies how many failed log in attempts are allowed. If not specified, defaults to <code class="literal">0</code> (no limit).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">offline_failed_login_delay <span class="type">(integer)</span> </code>
+ </div><div class="para">
+ Specifies the time in minutes after the value of <code class="option">offline_failed_login_attempts</code> has been reached before a new log in attempt is possible.
+ </div><div class="para">
+ If set to <code class="literal">0</code>, the user cannot authenticate offline if the value of <code class="option">offline_failed_login_attempts</code> has been reached. Only a successful online authentication can re-enable offline authentication. If not specified, defaults to <code class="literal">5</code>.
+ </div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html"><strong>Prev</strong>8.2.3. Setting Up SSSD</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Configuring_Domains.html"><strong>Next</strong>8.2.5. Configuring Domains</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Introduction.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Introduction.html
new file mode 100644
index 0000000..36a2be3
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Introduction.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2. The System Security Services Daemon (SSSD)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Authentication_Configuration.html" title="Chapter 8. Authentication Configuration" /><link rel="prev" href="ch-Authentication_Configuration.html" title="Chapter 8. Authentication Configuration" /><link rel="next" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html" title="8.2.2. SSSD Features" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Authenticatio
n_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="8.2. The System Security Services Daemon (SSSD)" id="chap-SSSD_User_Guide-Introduction" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="chap-SSSD_User_Guide-Introduction">8.2. The System Security Services Daemon (SSSD)</h2></div></div></div><div class="para">
+ This section provides an introduction to the <em class="firstterm">System Security Services Daemon (SSSD)</em>, the main features that it provides, and discusses the requirements and any limitations of a typical SSSD deployment.
+ </div><div class="para">
+ This section also describes how to configure SSSD, and how to use the features that it provides. It provides information on the types of services that it supports and how to configure them, and introduces and describes the most important configuration options. Sample configuration files are also provided to help you optimize your deployment.
+ </div><div class="section" title="8.2.1. What is SSSD?" id="sect-SSSD_User_Guide-Introduction-What_is_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-SSSD_User_Guide-Introduction-What_is_SSSD">8.2.1. What is SSSD?</h3></div></div></div><div class="para">
+ The System Security Services Daemon (SSSD) is a service which provides access to different identity and authentication providers. You can configure SSSD to use a native LDAP domain (that is, an LDAP identity provider with LDAP authentication), or an LDAP identity provider with Kerberos authentication. It provides an NSS and PAM interface to the system, and a pluggable back-end system to connect to multiple different account sources.
+ </div><div class="para">
+ SSSD is also extensible; you can configure it to use new identity sources and authentication mechanisms should they arise. In addition, SSSD is fully IPv6-compatible, provided that it is built against <span class="package">c-ares 1.7.1</span> or later and <span class="package">krb5-libs 1.8.1</span> or later.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Authentication_Configuration.html"><strong>Prev</strong>Chapter 8. Authentication Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html"><strong>Next</strong>8.2.2. SSSD Features</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html
new file mode 100644
index 0000000..5948da5
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Setting_Up_SSSD.html
@@ -0,0 +1,185 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.3. Setting Up SSSD</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html" title="8.2.2. SSSD Features" /><link rel="next" href="chap-SSSD_User_Guide-Configuring_Services.html" title="8.2.4. Configuring Services" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_
User_Guide-Introduction-SSSD_Features.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Configuring_Services.html"><strong>Next</strong></a></li></ul><div class="section" title="8.2.3. Setting Up SSSD" id="chap-SSSD_User_Guide-Setting_Up_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="chap-SSSD_User_Guide-Setting_Up_SSSD">8.2.3. Setting Up SSSD</h3></div></div></div><div class="para">
+ This section describes how to install SSSD, how to run the service, and how to configure it for each type of supported information provider.
+ </div><div class="section" title="8.2.3.1. Installing SSSD" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Installing_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Installing_SSSD">8.2.3.1. Installing SSSD</h4></div></div></div><div class="para">
+ Run the following command to install SSSD and any dependencies, including the SSSD client:
+ </div><div class="para">
+ <code class="command"># yum install sssd</code>
+ </div><div class="para">
+ SSSD requires very few dependencies and should install very quickly, depending on the speed of your network connection.
+ </div><div class="section" title="8.2.3.1.1. Upgrading from a Previous Version" id="sect-SSSD_User_Guide-Installing_SSSD-Upgrading_from_a_Previous_Version"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Installing_SSSD-Upgrading_from_a_Previous_Version">8.2.3.1.1. Upgrading from a Previous Version</h5></div></div></div><div class="formalpara" id="form-SSSD_User_Guide-Upgrading_from_a_Previous_Version-Upgrading_Using_RPM_Packages"><h5 class="formalpara">Upgrading Using RPM Packages</h5>
+ If you are upgrading using RPM packages, the script will run automatically when you upgrade to the new version. This will upgrade the <code class="filename">/etc/sssd/sssd.conf</code> file to the new format, and copy the existing version to <code class="filename">/etc/sssd/sssd.conf.bak</code>.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Upgrading_from_a_Previous_Version-Upgrading_Manually"><h5 class="formalpara">Upgrading Manually</h5>
+ It may be necessary to run the upgrade script manually, either because you built SSSD from source files, or because you are using a platform that does not support the use of RPM packages. The synopsis for the script is as follows:
+ </div><div class="cmdsynopsis"><p><code class="command">upgrade_config.py</code> [
+ -f INFILE
+ ] [
+ -o OUTFILE
+ ] [
+ -verbose
+ ] [
+ --no-backup
+ ]</p></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>-f INFILE</code></em> — the configuration file to upgrade. If not specified, this defaults to <code class="filename">/etc/sssd/sssd.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>-o OUTFILE</code></em> — the name of the upgraded configuration file. If not specified, this defaults to <code class="filename">/etc/sssd/sssd.conf</code>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>-verbose</code></em> — produce more verbose output during the upgrade process
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>--no-backup</code></em> — do not produce a back-up file. If not specified, this defaults to <code class="filename"><em class="parameter"><code>INFILE</code></em>.bak</code>
+ </div></li></ul></div></div><div class="section" title="8.2.3.1.2. Starting and Stopping SSSD" id="sect-SSSD_User_Guide-Installing_SSSD-Starting_and_Stopping_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Installing_SSSD-Starting_and_Stopping_SSSD">8.2.3.1.2. Starting and Stopping SSSD</h5></div></div></div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Before you start SSSD for the first time, you need to configure at least one domain. Refer to <a class="xref" href="chap-SSSD_User_Guide-Configuring_Domains.html" title="8.2.5. Configuring Domains">Section 8.2.5, “Configuring Domains”</a> for information on how to configure an SSSD domain.
+ </div></div></div><div class="para">
+ You can use either the <code class="command">service</code> command or the <code class="filename">/etc/init.d/sssd</code> script to control SSSD. For example, run the following command to start <code class="systemitem">sssd</code>:
+ </div><div class="para">
+ <code class="command"># service sssd start</code>
+ </div><div class="para">
+ By default, SSSD is configured not to start automatically. There are two ways to change this behavior; if you use the Authentication Configuration tool to configure SSSD, it will reconfigure the default behavior so that SSSD starts when the machine boots. Alternatively, you can use the <code class="command">chkconfig</code> command, as follows:
+ </div><div class="para">
+ <code class="command"># chkconfig sssd on</code>
+ </div></div></div><div class="section" title="8.2.3.2. Configuring SSSD" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Configuring_SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Setting_Up_SSSD-Configuring_SSSD">8.2.3.2. Configuring SSSD</h4></div></div></div><div class="para">
+ The global configuration of SSSD is stored in the <code class="filename">/etc/sssd/sssd.conf</code> file. This file consists of various sections, each of which contains a number of key/value pairs. Some keys accept multiple values; use commas to separate multiple values for such keys. This configuration file uses data types of <span class="type">string</span> (no quotes required), <span class="type">integer</span> and <span class="type">Boolean</span> (with values of <code class="literal">TRUE</code> or <code class="literal">FALSE</code>). Comments are indicated by either a hash sign (#) or a semicolon (;) in the first column. The following example illustrates some of this syntax:
+ </div><pre class="programlisting">[section]
+# Keys with single values
+key1 = value
+key2 = val2
+
+# Keys with multiple values
+key10 = val10,val11
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ You can use the <em class="parameter"><code>-c</code></em> (or <em class="parameter"><code>--config</code></em>) parameter on the command line to specify a different configuration file for SSSD.
+ </div></div></div><div class="para">
+ The format of the configuration file is described in <a class="xref" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html" title="8.2.8. SSSD Configuration File Format">Section 8.2.8, “SSSD Configuration File Format”</a>
+ </div><div class="para">
+ Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more information on global SSSD configuration options.
+ </div><div class="section" title="8.2.3.2.1. Configuring NSS" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS">8.2.3.2.1. Configuring NSS</h5></div></div></div><div class="para">
+ SSSD provides a new NSS module, <code class="systemitem">sssd_nss</code>, so that you can configure your system to use SSSD to retrieve user information. Edit the <code class="filename">/etc/nsswitch.conf</code> file for your system to use the <code class="systemitem">sss</code> name database. For example:
+ </div><pre class="programlisting">passwd: files sss
+group: files sss
+</pre></div><div class="section" title="8.2.3.2.2. Configuring PAM" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM">8.2.3.2.2. Configuring PAM</h5></div></div></div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Use extreme care when changing your PAM configuration. A mistake in the PAM configuration file can lock you out of the system completely. Always back up your configuration files before performing any changes, and keep a session open so that you can revert any changes you make should the need arise.
+ </div></div></div><div class="para">
+ To enable your system to use SSSD for PAM, you need to edit the default PAM configuration file. On Fedora—based systems, this is the <code class="filename">/etc/pam.d/system-auth</code> file. Edit this file to reflect the following example, and then restart <code class="systemitem">sssd</code>:
+ </div><pre class="programlisting">#%PAM-1.0
+# This file is auto-generated.
+# User changes will be destroyed the next time authconfig is run.
+auth required pam_env.so
+auth sufficient pam_unix.so nullok try_first_pass
+auth requisite pam_succeed_if.so uid >= 500 quiet
+auth sufficient pam_sss.so use_first_pass
+auth required pam_deny.so
+
+account required pam_unix.so broken_shadow
+account sufficient pam_localuser.so
+account sufficient pam_succeed_if.so uid < 500 quiet
+account [default=bad success=ok user_unknown=ignore] pam_sss.so
+account required pam_permit.so
+
+password requisite pam_cracklib.so try_first_pass retry=3
+password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok
+password sufficient pam_sss.so use_authtok
+password required pam_deny.so
+
+session required pam_mkhomedir.so umask=0022 skel=/etc/skel/
+session optional pam_keyinit.so revoke
+session required pam_limits.so
+session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid
+session sufficient pam_sss.so
+session required pam_unix.so
+</pre><div class="section" title="8.2.3.2.2.1. Using Custom Home Directories with SSSD"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="id771914">8.2.3.2.2.1. Using Custom Home Directories with SSSD</h6></div></div></div><div class="para">
+ If your LDAP users have home directories that are not in <code class="filename">/home</code>, and if your system is configured to create home directories the first time your users log in, then these directories will be created with the wrong permissions. For example, instead of a typical home directory such as <code class="filename">/home/<username></code>, your users might have home directories that include their locale, such as <code class="filename">/home/<locale>/<username></code>. If this is true for your system, the following steps need to be taken (preemptively):
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Apply the correct SELinux context and permissions from the <code class="filename">/home</code> directory to the home directory that you use on your system. In the example above, the following command would achieve this result (replace the directory names with those that apply to your system):
+<pre class="screen"># semanage fcontext -a -e /home /home/locale</pre>
+
+ </div></li><li class="listitem"><div class="para">
+ Ensure the <span class="package">oddjob-mkhomedir</span> package is installed on your system and then re-run the Authentication Configuration tool.
+ </div><div class="para">
+ This package provides the <code class="systemitem">pam_oddjob_mkhomedir.so</code> library, which the Authentication Configuration tool will then use to create your custom home directories. You need to use this library to create your home directories, and not the default <code class="systemitem">pam_mkhomedir.so</code> library, because the latter cannot create SELinux labels.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The Authentication Configuration tool will automatically use the <code class="systemitem">pam_oddjob_mkhomedir.so</code> library if it is available. Otherwise, it will default to using <code class="systemitem">pam_mkhomedir.so</code>.
+ </div></div></div></li></ol></div><div class="para">
+ If the preceding steps were not performed before the custom home directories were created, you can use the following commands to correct the permissions and SELinux contexts (again, replace the directory names with those that apply to your system):
+<pre class="screen"># semanage fcontext -a -e /home /home/locale
+# restorecon -R -v /home/locale</pre>
+
+ </div></div><div class="section" title="8.2.3.2.2.2. Using "include" Statements in PAM Configurations" id="form-SSSD_User_Guide-Configuring_PAM-Using_include_Statements_in_PAM_Configurations"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="form-SSSD_User_Guide-Configuring_PAM-Using_include_Statements_in_PAM_Configurations">8.2.3.2.2.2. Using "include" Statements in PAM Configurations</h6></div></div></div><div class="para">
+ Recent PAM implementations allow you to use <code class="literal">include</code> statements in PAM configurations. For example:
+ </div><pre class="programlisting">...
+session include system-auth
+session optional pam_console.so
+...
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ In the preceding example, if a <em class="parameter"><code>sufficient</code></em> condition from <code class="filename">system-auth</code> returns <span class="returnvalue">PAM_SUCCESS</span>, <code class="filename">pam_console.so</code> will not be executed.
+ </div></div></div></div></div><div class="section" title="8.2.3.2.3. Configuring Access Control"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id587380">8.2.3.2.3. Configuring Access Control</h5></div></div></div><a id="id689872" class="indexterm"></a><div class="para">
+ SSSD provides a rudimentary access control mechanism, offering two solutions based on the value of the <code class="option">access_provider</code> option in the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> section in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="section" title="8.2.3.2.3.1. The Simple Access Provider"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="id699848">8.2.3.2.3.1. The Simple Access Provider</h6></div></div></div><div class="para">
+ The first of these solutions is known as the <em class="firstterm">Simple Access Provider</em>, and is based on the implementation of access or deny lists of usernames. To enable the Simple Access Provider, you need to set the <code class="option">access_provider</code> option to <code class="literal">simple</code>, and then add usernames as a comma-separated list to either the <code class="option">simple_allow_users</code> or <code class="option">simple_deny_users</code> options.
+ </div><div class="formalpara"><h5 class="formalpara" id="id490115">Using the Simple Access Provider</h5>
+ By using the Simple Access Provider, you can continue to support a number of network logins to maintain common network accounts on company or department laptops, but you might want to restrict the use of a particular laptop to one or two users. This means that even if a different user authenticated successfully against the same authentication provider, the Simple Access Provider would prevent that user from gaining access.
+ </div><div class="para">
+ The following example demonstrates the use of the Simple Access Provider to grant access to two users. This example assumes that SSSD is correctly configured and <code class="systemitem">example.com</code> is one of the domains specified in the <code class="literal">[sssd]</code> section, and only shows the Simple Access Provider-specific options.
+ </div><pre class="screen">[domain/example.com]
+access_provider = simple
+simple_allow_users = user1, user2</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The Local ID provider does not support <code class="option">simple</code> as an access provider.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="id807850">Access Control Rules</h5><a id="id1768455" class="indexterm"></a>
+ The Simple Access Provider adheres to the following three rules to determine which users should or should not be granted access:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If both lists are empty, access is granted.
+ </div></li><li class="listitem"><div class="para">
+ If <code class="option">simple_allow_users</code> is set, only users from this list are allowed access. This setting supersedes the <code class="option">simple_deny_users</code> list (which would be redundant).
+ </div></li><li class="listitem"><div class="para">
+ If the <code class="option">simple_allow_users</code> list is empty, users are allowed access unless they appear in the <code class="option">simple_deny_users</code> list.
+ </div></li></ul></div>
+ <div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Defining both <code class="option">simple_allow_users</code> and <code class="option">simple_deny_users</code> is a configuration error. If this occurs, SSSD will output an error to the <code class="filename">/var/log/sssd/sssd_default.log</code> log file when loading the back end, but continue to start normally. Future versions of SSSD will output an error and fail to start.
+ </div></div></div>
+
+ </div></div><div class="section" title="8.2.3.2.3.2. The LDAP Access Provider"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="id699756">8.2.3.2.3.2. The LDAP Access Provider</h6></div></div></div><div class="para">
+ The second access control solution uses the LDAP server itself as the access provider (<code class="option">access_provider=ldap</code>) and the associated filter option (<code class="option">ldap_access_filter</code>) to specify which users are granted access to the specified host. Note that these two options are codependent; if you use LDAP as your access provider then you must specify a value for the <code class="option">ldap_access_filter</code> option, otherwise all users will be denied access. If you are not using LDAP as your access provider, then the <code class="option">ldap_access_filter</code> option has no effect.
+ </div><div class="formalpara"><h5 class="formalpara" id="id1229220">Using the LDAP Access Provider</h5>
+ The following example demonstrates the use of the LDAP Access Provider to grant access to members of the "allowedusers" group in LDAP. This example assumes that SSSD is correctly configured and <code class="systemitem">example.com</code> is one of the domains specified in the <code class="literal">[sssd]</code> section, and only shows the LDAP Access Provider-specific options.
+ </div><pre class="screen">[domain/example.com]
+access_provider = ldap
+ldap_access_filter = memberOf=cn=allowedusers,ou=Groups,dc=example,dc=com</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Offline caching for this feature is limited to determining whether or not the user's last online login attempt was successful. If they were granted access during their last login, they will continue to be granted access while offline, and vice-versa.
+ </div></div></div><div class="para">
+ Refer to the <em class="citetitle">sssd-ldap</em> manual page for more information about using the LDAP Access Provider.
+ </div></div></div><div class="section" title="8.2.3.2.4. Configuring Failover" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover">8.2.3.2.4. Configuring Failover</h5></div></div></div><div class="para">
+ The failover feature allows back ends to automatically switch to a different server if the primary server fails. These servers are entered as a case-insensitive, comma-separated list in the <code class="literal">[domain/<<em class="replaceable"><code>NAME</code></em>>]</code> sections of the <code class="filename">/etc/sssd/sssd.conf</code> file, and listed in order of preference. This list can contain any number of servers.
+ </div><div class="para">
+ For example, if you have configured a native LDAP domain, you could specify the following as your <em class="parameter"><code>ldap_uri</code></em> values:
+ </div><pre class="screen">ldap_uri = ldap://ldap0.mydomain.org, ldap://ldap1.mydomain.org, ldap://ldap2.mydomain.org</pre><div class="para">
+ In this configuration, <code class="uri">ldap://ldap0.mydomain.org</code> functions as the primary server. If this server fails, the SSSD failover mechanism first attempts to connect to <code class="uri">ldap1.mydomain.org</code>, and if that server is unavailable, it then attempts to connect to <code class="uri">ldap2.mydomain.org</code>.
+ </div><div class="para">
+ If the parameter that specifies which server to connect to for the specific domain (for example, <em class="parameter"><code>ldap_uri</code></em>, <em class="parameter"><code>krb5_kdcip</code></em>, …) is not specified, the back end defaults to using <em class="replaceable"><code>Use service discovery</code></em>. Refer to <a class="xref" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover" title="8.2.3.2.4.1. Using SRV Records with Failover">Section 8.2.3.2.4.1, “Using SRV Records with Failover”</a> for more information on service discovery.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Do not use multiple <em class="parameter"><code>ldap_uri</code></em> parameters to specify your failover servers. The failover servers must be entered as a comma-separated list of values for a single <em class="parameter"><code>ldap_uri</code></em> parameter. If you enter multiple <em class="parameter"><code>ldap_uri</code></em> parameters, SSSD only recognizes the last entry.
+ </div><div class="para">
+ Future versions of SSSD will throw an error upon receiving additional <em class="parameter"><code>ldap_uri</code></em> entries.
+ </div></div></div><div class="section" title="8.2.3.2.4.1. Using SRV Records with Failover" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover">8.2.3.2.4.1. Using SRV Records with Failover</h6></div></div></div><div class="para">
+ SSSD also supports the use of SRV records in its failover configuration. This means that you can specify a server that is later resolved into a list of specific servers using SRV requests. The <em class="parameter"><code>priority</code></em> and <em class="parameter"><code>weight</code></em> attributes of SRV records provide further opportunity for specifying which servers should be contacted first in the event that the primary server fails.
+ </div><div class="para">
+ For every service with which you want to use service discovery, you need to add a special DNS record to your DNS server using the following form:
+ </div><pre class="screen">_<em class="replaceable"><code>service</code></em>._<em class="replaceable"><code>protocol</code></em>._<em class="replaceable"><code>domain TTL priority weight port hostname</code></em></pre><div class="para">
+ A typical configuration would contain multiple such records, each with a different priority (for failover) and different weights (for load balancing).
+ </div><div class="para">
+ The client then makes an SRV DNS query to retrieve a list of host names, their priorities, and weights. These queries are of the form _<em class="replaceable"><code>service</code></em>._<em class="replaceable"><code>protocol</code></em>._<em class="replaceable"><code>domain</code></em>, for example, <code class="literal">_ldap._tcp._redhat.com</code>. The client then sorts this list according to the priorities and weights, and connects to the first server in this sorted list.
+ </div><div class="para">
+ For more information on SRV records, refer to <a href="http://tools.ietf.org/html/rfc2782">RFC 2782</a>.
+ </div></div><div class="section" title="8.2.3.2.4.2. How the Failover Mechanism Works" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-How_the_Failover_Mechanism_Works"><div class="titlepage"><div><div keep-together.within-column="always"><h6 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-How_the_Failover_Mechanism_Works">8.2.3.2.4.2. How the Failover Mechanism Works</h6></div></div></div><div class="para">
+ The failover mechanism distinguishes between machines and services. The back end first tries to resolve the hostname of a given machine; if this resolution attempt fails, the machine is considered offline. No further attempts are made to connect to this machine for any other service. If the resolution attempt succeeds, the back end tries to connect to a service on this machine. If the service connection attempt fails, then only this particular service is considered offline and the back end automatically switches over to the next service. The machine is still considered online and might still be tried for another service.
+ </div><div class="para">
+ The failover mechanism does not handle DNS A records with multiple IP addresses; instead it only uses the first address. DNS round-robin cannot be used for failover. Further, providing multiple A records does not provide failover. Only the first A record is used, and if a lookup attempt on the first record fails then the system attempts no further lookups. To find multiple servers with a single request, and thus implementing failover, SSSD relies on SRV resource records, as explained in <a class="xref" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_Failover-Using_SRV_Records_with_Failover" title="8.2.3.2.4.1. Using SRV Records with Failover">Section 8.2.3.2.4.1, “Using SRV Records with Failover”</a>.
+ </div><div class="para">
+ Further connection attempts are made to machines or services marked as offline after a specified period of time; this is currently hard coded to 30 seconds. If there are no more machines to try, the back end as a whole switches to offline mode, and then attempts to reconnect every 30 seconds.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html"><strong>Prev</strong>8.2.2. SSSD Features</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Configuring_Services.html"><strong>Next</strong>8.2.4. Configuring Services</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Troubleshooting.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Troubleshooting.html
new file mode 100644
index 0000000..c10c82a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/chap-SSSD_User_Guide-Troubleshooting.html
@@ -0,0 +1,122 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.7. Troubleshooting</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html" title="8.2.6. Setting Up Kerberos Authentication" /><link rel="next" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html" title="8.2.8. SSSD Configuration File Format" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="D
ocumentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"><strong>Next</strong></a></li></ul><div class="section" title="8.2.7. Troubleshooting" id="chap-SSSD_User_Guide-Troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="chap-SSSD_User_Guide-Troubleshooting">8.2.7. Troubleshooting</h3></div></div></div><div class="para">
+ This section lists some of the issues you may encounter when implementing SSSD, the possible causes of these issues, and how to resolve them. If you find further issues that are not covered here, refer to the <em class="citetitle">We Need Feedback</em> section in the <em class="citetitle">Preface</em> for information on how to file a bug report.
+ </div><div class="section" title="8.2.7.1. Using SSSD Log Files" id="sect-SSSD_User_Guide-Troubleshooting-Using_SSSD_Log_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Troubleshooting-Using_SSSD_Log_Files">8.2.7.1. Using SSSD Log Files</h4></div></div></div><div class="para">
+ SSSD uses a number of log files to report information about its operation, and this information can help to resolve issues in the event of SSSD failure or unexpected behavior. The default location for these log files on Fedora—based systems is the <code class="filename">/var/log/sssd/</code> directory.
+ </div><div class="para">
+ SSSD produces a log file for each back end (that is, one log file for each domain specified in the <code class="filename">/etc/sssd/sssd.conf</code> file), as well as an <code class="filename">sssd_pam.log</code> and an <code class="filename">sssd_nss.log</code> file. This level of granularity can help you to quickly isolate and resolve any errors or issues you might experience with SSSD.
+ </div><div class="para">
+ You should also examine the <code class="filename">/var/log/secure</code> file, which logs authentication failures and the reason for the failure. For example, if you see <span class="errortext">Reason 4: System Error</span> reported against any failure, you should increase the debug level of the log files.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Using_SSSD_Log_Files-Producing_More_Verbose_Log_Files"><h5 class="formalpara">Producing More Verbose Log Files</h5>
+ If you are unable to identify and resolve any problems with SSSD after inspection of the default log files, you can configure SSSD to produce more verbose files. You can set the <code class="option">debug_level</code> option in the <code class="filename">/etc/sssd/sssd.conf</code> for the domain that is causing concern, and then restart SSSD. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more information on how to set the <code class="option">debug_level</code> for a specific domain.
+ </div><div class="para">
+ All log files include timestamps on debug messages by default. This can make it easier to understand any errors that may occur, why they occurred, and how to address them. If necessary, you can disable these timestamps by setting the appropriate parameter to <code class="literal">FALSE</code> in the <code class="filename">/etc/sssd/sssd.conf</code> file:
+ </div><pre class="screen">--debug-timestamps=FALSE
+</pre></div><div class="section" title="8.2.7.2. Problems with SSSD Configuration" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Configuration">8.2.7.2. Problems with SSSD Configuration</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ SSSD fails to start
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ SSSD requires at least one properly configured domain before the service will start. Without such a domain, you might see the following error message when trying to start SSSD with the following command:
+ </div><div class="para">
+ <code class="command"># sssd -d4</code>
+ </div><pre class="screen">[sssd] [ldb] (3): server_sort:Unable to register control with rootdse!
+
+[sssd] [confdb_get_domains] (0): No domains configured, fatal error!
+[sssd] [get_monitor_config] (0): No domains configured.
+</pre><div class="para">
+ You can ignore the <span class="errortext">"Unable to register control with rootdse!"</span> message, as it is erroneous. The other messages, however, indicate that SSSD is unable to locate any properly configured domains.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file and ensure you have at least one properly configured domain, and then try to start SSSD.
+ </div></li><li class="listitem"><div class="para">
+ SSSD requires at least one available service provider before it will start. With no available service providers, you might see the following error message when trying to start SSSD with the following command:
+ </div><div class="para">
+ <code class="command"># sssd -d4</code>
+ </div><pre class="screen">[sssd] [ldb] (3): server_sort:Unable to register control with rootdse!
+
+[sssd] [get_monitor_config] (0): No services configured!
+</pre><div class="para">
+ You can ignore the <span class="errortext">"Unable to register control with rootdse!"</span> message, as it is erroneous. The other message, however, indicates that SSSD is unable to locate any available service providers.
+ </div><div class="para">
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file and ensure you have at least one available service providers, and then try to start SSSD.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ SSSD requires that service providers be configured as a comma-separated list in a single <em class="parameter"><code>services</code></em> entry in the <code class="filename">/etc/sssd/sssd.conf</code> file. If services are listed in multiple entries, only the last entry is recognized by SSSD.
+ </div></div></div></li><li class="listitem"><div class="para">
+ Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for more options that might assist in troubleshooting issues with SSSD.
+ </div></li></ul></div></li></ul></div></div><div class="section" title="8.2.7.3. Problems with SSSD Service Configuration" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Service_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Service_Configuration">8.2.7.3. Problems with SSSD Service Configuration</h4></div></div></div><div class="section" title="8.2.7.3.1. Problems with NSS" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_NSS"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_NSS">8.2.7.3.1. Problems with NSS</h5></div></div></div><div class="para">
+ This section describes some common problems with <code class="systemitem">NSS</code>, their symptoms, and how to resolve them.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">NSS</code> fails to return user information
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Ensure that NSS is running
+ </div><div class="para">
+ <code class="command"># service sssd status</code>
+ </div><div class="para">
+ This command should return results similar to the following:
+ </div><pre class="screen">sssd (pid 21762) is running...
+</pre></li><li class="listitem"><div class="para">
+ Ensure that you have correctly configured the <code class="literal">[nss]</code> section of the <code class="filename">/etc/sssd/sssd.conf</code> file. For example, ensure that you have not misconfigured the <em class="parameter"><code>filter_users</code></em> or <em class="parameter"><code>filter_groups</code></em> attributes. Refer to the <em class="citetitle">NSS configuration options</em> section of the <em class="citetitle">sssd.conf(5)</em> manual page for information on how to configure these attributes.
+ </div></li><li class="listitem"><div class="para">
+ Ensure that you have included <code class="systemitem">nss</code> in the list of services that <code class="systemitem">sssd</code> should start
+ </div></li><li class="listitem"><div class="para">
+ Ensure that you have correctly configured the <code class="filename">/etc/nsswitch.conf</code> file. Refer to the section <a class="xref" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#sect-SSSD_User_Guide-Configuring_SSSD-Configuring_NSS" title="8.2.3.2.1. Configuring NSS">Section 8.2.3.2.1, “Configuring NSS”</a> for information on how to correctly configure this file.
+ </div></li></ul></div></li></ul></div></div><div class="section" title="8.2.7.3.2. Problems with PAM" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_PAM"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Problems_with_SSSD_Service_Configuration-Problems_with_PAM">8.2.7.3.2. Problems with PAM</h5></div></div></div><div class="para">
+ This section describes some common problems with <code class="systemitem">PAM</code>, their symptoms, and how to resolve them.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Setting the password for the local SSSD user prompts twice for the password
+ </div><div class="para">
+ When attempting to change a local SSSD user's password, you might see output similar to the following:
+ </div><pre class="screen">[root at clientF11 tmp]# passwd user1000
+Changing password for user user1000.
+New password:
+Retype new password:
+New Password:
+Reenter new Password:
+passwd: all authentication tokens updated successfully.
+</pre><div class="para">
+ This is the result of an incorrect PAM configuration. Refer to <a class="xref" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#sect-SSSD_User_Guide-Configuring_SSSD-Configuring_PAM" title="8.2.3.2.2. Configuring PAM">Section 8.2.3.2.2, “Configuring PAM”</a>, and ensure that the <em class="parameter"><code>use_authtok</code></em> option is correctly configured in your <code class="filename">/etc/pam.d/system-auth</code> file.
+ </div></li></ul></div></div><div class="section" title="8.2.7.3.3. Problems with NFS and NSCD"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id476883">8.2.7.3.3. Problems with NFS and NSCD</h5></div></div></div><div class="para">
+ SSSD is not designed to be used with the <code class="systemitem">nscd</code> daemon, and will likely generate warnings in the SSSD log files. Even though SSSD does not directly conflict with <code class="systemitem">nscd</code>, the use of both at the same time can result in unexpected behavior (specifically with how long entries are being cached).
+ </div><div class="para">
+ If you are using Network Manager to manage your network connections, it may take several minutes for the network interface to come up. During this time, various services will attempt to start. If these services start before the network is up (that is, the DNS servers cannot yet be reached) they will fail to identify the forward or reverse DNS entries they might need. These services will be reading an incorrect or possibly empty <code class="filename">resolv.conf</code> file. This file is typically only read once, and so any changes made to this file are not automatically applied.
+ </div><div class="para">
+ This can result in the failure of some system services, and in particular can cause NFS locking to fail on the machine where the <code class="systemitem">nscd</code> service is running, unless that service is manually restarted.
+ </div><div class="para">
+ One method of working around this problem is to enable caching for <em class="parameter"><code>hosts</code></em> and <em class="parameter"><code>services</code></em> in the <code class="filename">/etc/nscd.conf</code> file, and to rely on the SSSD cache for the <em class="parameter"><code>passwd</code></em> and <em class="parameter"><code>group</code></em> entries. With <code class="systemitem">nscd</code> answering <em class="parameter"><code>hosts</code></em> and <em class="parameter"><code>services</code></em> requests, these entries would have been cached and returned by <code class="systemitem">nscd</code> during the boot process.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Later versions of SSSD should negate any need for NSCD.
+ </div></div></div></div></div><div class="section" title="8.2.7.4. Problems with SSSD Domain Configuration" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Domain_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Troubleshooting-Problems_with_SSSD_Domain_Configuration">8.2.7.4. Problems with SSSD Domain Configuration</h4></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ NSS returns incorrect user information
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If your search for user information returns incorrect data, ensure that you do not have conflicting usernames in separate domains. If you use multiple domains, it is recommended that you set the <em class="parameter"><code>use_fully_qualified_domains</code></em> attribute to <code class="literal">TRUE</code> in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div></li></ul></div>
+
+ </div></li></ul></div></div><div class="section" title="8.2.7.5. Additional Resources" id="sect-SSSD_User_Guide-Troubleshooting-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-Troubleshooting-Additional_Resources">8.2.7.5. Additional Resources</h4></div></div></div><div class="section" title="8.2.7.5.1. Manual Pages" id="sect-SSSD_User_Guide-Additional_Resources-Manual_Pages"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Additional_Resources-Manual_Pages">8.2.7.5.1. Manual Pages</h5></div></div></div><div class="para">
+ SSSD ships with a number of manual pages, all of which provide additional information about specific aspects of SSSD, such as configuration files, commands, and available options. SSSD currently provides the following manual pages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">sssd.conf(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-ipa(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-krb5(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd-ldap(5)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd(8)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sssd_krb5_locator_plugin(8)</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">pam_sss(8)</code>
+ </div></li></ul></div><div class="para">
+ You should refer to these manual pages for detailed information about all aspects of SSSD, its configuration, and associated tools and commands.
+ </div></div><div class="section" title="8.2.7.5.2. Mailing Lists" id="sect-SSSD_User_Guide-Additional_Resources-Mailing_Lists"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="sect-SSSD_User_Guide-Additional_Resources-Mailing_Lists">8.2.7.5.2. Mailing Lists</h5></div></div></div><div class="para">
+ You can subscribe to the SSSD mailing list to follow and become involved in the development of SSSD, or to ask questions about any issues you may be experiencing with your SSSD deployment.
+ </div><div class="para">
+ Visit <a href="https://fedorahosted.org/mailman/listinfo/sssd-devel">https://fedorahosted.org/mailman/listinfo/sssd-devel</a> to subscribe to this mailing list.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html"><strong>Prev</strong>8.2.6. Setting Up Kerberos Authentication</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html"><strong>Next</strong>8.2.8. SSSD Configuration File Format</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/configuring-centralized-crash-collection.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/configuring-centralized-crash-collection.html
new file mode 100644
index 0000000..92f3967
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/configuring-centralized-crash-collection.html
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.7. Configuring Centralized Crash Collection</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-abrt.html" title="Chapter 21. ABRT" /><link rel="prev" href="configuring.html" title="21.6. Configuring ABRT" /><link rel="next" href="testing-upload-method.html" title="21.7.2. Testing the Upload Method" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="configuring.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="testing-upload-method.html
"><strong>Next</strong></a></li></ul><div class="section" title="21.7. Configuring Centralized Crash Collection" id="configuring-centralized-crash-collection"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="configuring-centralized-crash-collection">21.7. Configuring Centralized Crash Collection</h2></div></div></div><div class="para">
+ You can set up <span class="application"><strong>ABRT</strong></span> so that crash reports are collected from multiple systems and sent to a dedicated system for further processing. This is useful when an administrator does not want to log into hundreds of systems and manually check for crashes found by <span class="application"><strong>ABRT</strong></span>. In order to use this method, you need to install the <span class="application"><strong>abrt-plugin-reportuploader</strong></span> plugin (<code class="command">yum install abrt-plugin-reportuploader</code>).
+ </div><div class="para">
+ The steps to configure <span class="application"><strong>ABRT</strong></span>'s centralized crash collection are:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Complete the following steps on a dedicated system ("server system"):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Create a directory to which you want the crash reports to be uploaded to. Usually, <code class="filename">/var/spool/abrt-upload/</code> is used (the rest of the document assumes you are using <code class="filename">/var/spool/abrt-upload/</code>). Make sure this directory is writable by the <code class="systemitem">abrt</code> user.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ When the <span class="package">abrt-desktop</span> package is installed, it creates a new system user and and a group, both named <code class="systemitem">abrt</code>. This user is used by the <code class="systemitem">abrtd</code> daemon for various things, for example, as the owner:group of <code class="filename">/var/spool/abrt/*</code> directories.
+ </div></div></div></li><li class="listitem"><div class="para">
+ In the <code class="filename">/etc/abrt/abrt.conf</code> configuration file, set the <code class="varname">WatchCrashdumpArchiveDir</code> directive to the following:
+<pre class="screen">
+WatchCrashdumpArchiveDir = /var/spool/abrt-upload/
+</pre>
+
+ </div></li><li class="listitem"><div class="para">
+ Determine your preferred upload mechanism; for example, <code class="systemitem">FTP</code> or <code class="systemitem">SCP</code>. For more information on how to configure <code class="systemitem">SCP</code>, refer to <a class="xref" href="s2-ssh-clients-scp.html" title="9.3.2. Using the scp Utility">Section 9.3.2, “Using the <code class="command">scp</code> Utility”</a>.
+ </div><div class="para">
+ For security reasons, make sure that uploads can only be performed by a specific user and with a password. The rest of the document assumes that the username used for uploads is <code class="systemitem">USERNAME</code> and the password is <code class="literal">PASSWORD</code>. If you do not already have a suitable username which can be used to perform uploads under, you may use the <code class="systemitem">abrt</code> user which already exists on every system where <span class="application"><strong>ABRT</strong></span> is installed.
+ </div><div class="para">
+ It is advisable to check whether your upload method works. For more information, refer to <a class="xref" href="testing-upload-method.html" title="21.7.2. Testing the Upload Method">Section 21.7.2, “Testing the Upload Method”</a>.
+ </div></li><li class="listitem"><div class="para">
+ It is advisable to check and modify the following parameters if needed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="parameter"><code>MaxCrashReportsSize</code></em> directive (in <code class="filename">/etc/abrt/abrt.conf</code>) needs to be set to a larger value if the expected volume of crash data is larger than the default <code class="constant">1000</code> MB.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="parameter"><code>ProcessUnpackaged</code></em> directive (in <code class="filename">/etc/abrt/abrt.conf</code>) needs to be set to <em class="replaceable"><code>yes</code></em> and the <em class="parameter"><code>BacktraceRemotes</code></em> (in <code class="filename">/etc/abrt/plugins/CCpp.conf</code>) needs to be set to <em class="replaceable"><code>no</code></em> if the client system and the server system have significantly different sets of installed packages.
+ </div></li></ul></div></li></ul></div></li><li class="listitem"><div class="para">
+ Complete the following steps on every client system which will use the central management method:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Modify the <code class="filename">/etc/abrt/plugins/ReportUploader.conf</code> configuration file so that the <span class="application"><strong>ReportUploader</strong></span> plugin knows where to copy the saved crash reports in the following way:
+<pre class="screen">
+Enabled = yes
+Upload = yes
+URL = ftp://USERNAME:PASSWORD@SERVERNAME/var/spool/abrt-upload/
+</pre>
+
+ </div></li><li class="listitem"><div class="para">
+ To automatically send the crash reports to the server system immediately after the crash occurs, is detected, and saved, set the <code class="varname">[ ActionsAndReporters ]</code> directive in the <code class="filename">/etc/abrt/abrt.conf</code> configuration file to the following:
+<pre class="screen">
+ActionsAndReporters = ReportUploader
+</pre>
+
+ </div></li><li class="listitem"><div class="para">
+ # Alternatively, if user interaction is required before the crash dump is sent to the server system, set the <em class="parameter"><code>ReportUploader</code></em> to be a reporter plugin for a specific crash type in the <code class="literal">[ AnalyzerActionsAndReporters ]</code> section of the <code class="filename">/etc/abrt/abrt.conf</code> configuration file. The user will be required to run <span class="application"><strong>abrt-cli</strong></span> or <span class="application"><strong>abrt-gui</strong></span> and instruct the <code class="systemitem">abrtd</code> daemon to report the crash and send it to the server system. For example, if you want all crash types to use this method, edit the <code class="literal">[ AnalyzerActionsAndReporters ]</code> section in your <code class="filename">/etc/abrt/abrt.conf</code> configuration file in the following way:
+ </div><pre class="screen">
+Kerneloops = ReportUploader
+CCpp = ReportUploader
+Python = ReportUploader
+</pre></li></ul></div></li></ol></div><div class="section" title="21.7.1. Testing ABRT's Crash Detection"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id677483">21.7.1. Testing ABRT's Crash Detection</h3></div></div></div><div class="para">
+ After completing all the steps of the configuration process, the basic setup is finished. To test that this setup works properly use the <code class="command">kill -s SEGV <em class="replaceable"><code>PID</code></em> </code> command to terminate a process on a client system. For example, start a <code class="systemitem">sleep</code> process and terminate it with the <code class="command">kill</code> command in the following way:
+<pre class="screen">
+~]$ sleep 100 &
+[1] 2823
+~]$ kill -s SEGV 2823
+</pre>
+ <span class="application"><strong>ABRT</strong></span> should detect a crash shortly after executing the <code class="command">kill</code> command. Check that the crash was detected by <span class="application"><strong>ABRT</strong></span> on the client system (this can be checked by examining the appropriate syslog file, by running the <code class="command">abrt-cli --list --full</code> command, or by examining the crash dump created in the <code class="filename">/var/spool/abrt</code> directory), copied to the server system, unpacked on the server system and can be seen and acted upon using <code class="command">abrt-cli</code> or <code class="command">abrt-gui</code> on the server system.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="configuring.html"><strong>Prev</strong>21.6. Configuring ABRT</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="testing-upload-method.html"><strong>Next</strong>21.7.2. Testing the Upload Method</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/configuring-plugins-in-the-gui.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/configuring-plugins-in-the-gui.html
new file mode 100644
index 0000000..c520908
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/configuring-plugins-in-the-gui.html
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.3.3. Plugin Configuration in the GUI</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="abrt-plugins.html" title="21.3. ABRT Plugins" /><link rel="prev" href="reporter-plugins.html" title="21.3.2. Reporter Plugins" /><link rel="next" href="generating-backtrace.html" title="21.4. Generating Backtraces" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="reporter-plugins.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="generating-bac
ktrace.html"><strong>Next</strong></a></li></ul><div class="section" title="21.3.3. Plugin Configuration in the GUI" id="configuring-plugins-in-the-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="configuring-plugins-in-the-gui">21.3.3. Plugin Configuration in the GUI</h3></div></div></div><div class="para">
+ You can override the system-wide plugin configuration in the <code class="filename">/etc/abrt/plugins/*.conf</code> configuration files on a per-user basis. Each of the plugins specified in section <a class="xref" href="reporter-plugins.html" title="21.3.2. Reporter Plugins">Section 21.3.2, “Reporter Plugins”</a> can be configured in the <span class="application"><strong>ABRT</strong></span> GUI application. Open the plugins window by clicking <span class="guimenu"><strong>Edit</strong></span> → <span class="guisubmenu"><strong>Plugins</strong></span>. This window shows a list of all installed plugins. You can also view each of the plugins' details by selecting one and expanding <span class="guimenu"><strong>Plugin Details</strong></span>. When you select one of the configurable plugins, you can click the <span class="guibutton"><strong>Configure plugin</strong></span> button and you will be able to configure your desired plugin. If you change any of the plugins'
parameters, they are saved in the Gnome keyring and will be used in the future GUI sessions.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ All of the <code class="filename">/etc/abrt/plugins/*.conf</code> configuration files are world readable and are meant to be used as global settings. Thus, it is not advisable to store usernames, passwords or any other sensitive data in them. The per-user settings (set in the GUI application and readable by the owner of $HOME only) are stored in the Gnome keyring or can be stored in a text file in <code class="filename">$HOME/.abrt/*.conf</code> for use in <code class="command">abrt-cli</code>.
+ </div></div></div><div class="mediaobject" align="center"><img src="images/ABRT-plugins.png" align="middle" width="444" /><div class="caption"><div class="para">
+ ABRT Plugins
+ </div></div></div><div class="para">
+ The following is a list of all configuration options available for each configurable plugin in the <span class="application"><strong>ABRT</strong></span> GUI application.
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">RHTSupport</span></dt><dd><div class="para">
+ In the <span class="guilabel"><strong>RHTSupport plugin configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>RHTSupport URL</strong></span> — Specifies the RHTSupport URL where crash dumps are sent (by default, set to <a href="https://api.access.redhat.com/rs">https://api.access.redhat.com/rs</a>).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Login</strong></span> — User login which is used to log into RHTSupport and create a RHTSupport database entry for a reported crash.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Password</strong></span> — Password used to log into RHTSupport.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>SSL verify</strong></span> option is checked, the <code class="systemitem">SSL</code> protocol is used when sending the data over the network.
+ </div></dd><dt class="varlistentry"><span class="term">MailX</span></dt><dd><div class="para">
+ In the <span class="guilabel"><strong>MailX plugin configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Subject</strong></span> — A string that appears in the <code class="literal">Subject</code> field of a crash report email sent by <span class="application"><strong>mailx</strong></span> (by default, set to <code class="literal">"[abrt] crash report"</code>).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Your Email</strong></span> — A string that appears in the <code class="literal">From</code> field of a crash report email.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Recipient's Email</strong></span> — Email address of the recipient of a crash report email.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Send Binary Data</strong></span> option is checked, the crash report email will also contain all binary files associated with the crash in an attachment. The core dump file is also sent as an attachment.
+ </div></dd><dt class="varlistentry"><span class="term">ReportUploader</span></dt><dd><div class="para">
+ In the <span class="guilabel"><strong>ReportUploader plugin configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Customer</strong></span> — Specifies customer's identification.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Ticket</strong></span> — Specifies the Ticket ID number in a specific issue tracker that collects crash reports.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>URL</strong></span> — Specifies the URL of the issue tracker used to collect crash reports.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Retry count</strong></span> — Specifies the number of retries should an upload fail.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Retry delay</strong></span> — Specifies the number or seconds between two retries.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Use encryption</strong></span> option is checked, the crash report sent to the issue tracker is encrypted.
+ </div><div class="para">
+ When the <span class="guilabel"><strong>Upload</strong></span> option is checked, all crash reports are uploaded to the specified issue tracker. If the option is unchecked, all crash reports are saved locally.
+ </div></dd><dt class="varlistentry"><span class="term">Bugzilla</span></dt><dd><div class="para">
+ In the <span class="guilabel"><strong>Bugzilla plugin configuration</strong></span>, you can configure the following parameters:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Bugzilla URL</strong></span> — Specifies the Bugzilla URL where crash dumps are sent (by default, set to <a href="https://bugzilla.redhat.com">https://bugzilla.redhat.com</a>).
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Login (email)</strong></span> — User login which is used to log into Bugzilla and create a Bugzilla database entry for a reported crash.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Password</strong></span> — Password used to log into Bugzilla.
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>SSL verify</strong></span> option is checked, the <code class="systemitem">SSL</code> protocol is used when sending the data over the network.
+ </div></dd><dt class="varlistentry"><span class="term">Logger</span></dt><dd><div class="para">
+ In the <span class="guilabel"><strong>Logger plugin configuration</strong></span>, you can configure the following parameter:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Logger file</strong></span> — Specifies a file into which the crash reports are saved (by default, set to <code class="filename">/var/log/abrt.log</code>).
+ </div></li></ul></div><div class="para">
+ When the <span class="guilabel"><strong>Append new logs</strong></span> option is checked, the Logger plugin will append new crash reports to the log file specified in the <span class="guilabel"><strong>Logger file</strong></span> option. When unchecked, the new crash report always replaces the previous one.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="reporter-plugins.html"><strong>Prev</strong>21.3.2. Reporter Plugins</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="generating-backtrace.html"><strong>Next</strong>21.4. Generating Backtraces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/configuring.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/configuring.html
new file mode 100644
index 0000000..ffa044f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/configuring.html
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.6. Configuring ABRT</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-abrt.html" title="Chapter 21. ABRT" /><link rel="prev" href="ch21s05s03.html" title="21.5.3. Deleting Crashes" /><link rel="next" href="configuring-centralized-crash-collection.html" title="21.7. Configuring Centralized Crash Collection" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s05s03.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n"
href="configuring-centralized-crash-collection.html"><strong>Next</strong></a></li></ul><div class="section" title="21.6. Configuring ABRT" id="configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="configuring">21.6. Configuring ABRT</h2></div></div></div><div class="para">
+ <span class="application"><strong>ABRT</strong></span>'s main configuration file is <code class="filename">/etc/abrt/abrt.conf</code>. <span class="application"><strong>ABRT</strong></span> plugins can be configured through their config files, located in the <code class="filename">/etc/abrt/plugins/</code> directory.
+ </div><div class="para">
+ After changing and saving the <code class="filename">abrt.conf</code> configuration file, you must restart the <code class="systemitem">abrtd</code> daemon—as root—for the new settings to take effect:
+ </div><pre class="screen">~]# <code class="command">service abrtd restart</code>
+</pre><div class="para">
+ The following configuration directives are currently supported in <code class="filename">/etc/abrt/abrt.conf</code>.
+ </div><div class="variablelist" title="[ Common ] Section Directives"><h6>[ Common ] Section Directives</h6><dl><dt class="varlistentry"><span class="term">OpenGPGCheck = <em class="replaceable"><code><yes/no></code></em> </span></dt><dd><div class="para">
+ Setting the <code class="computeroutput">OpenGPGCheck</code> directive to <strong class="userinput"><code>yes</code></strong> (the default setting) tells <span class="application"><strong>ABRT</strong></span> to <span class="emphasis"><em>only</em></span> analyze and handle crashes in applications provided by packages which are signed by the GPG keys whose locations are listed in the <code class="filename">/etc/abrt/gpg_keys</code> file. Setting <em class="parameter"><code>OpenGPGCheck</code></em> to <strong class="userinput"><code>no</code></strong> tells <span class="application"><strong>ABRT</strong></span> to catch crashes in all programs.
+ </div></dd><dt class="varlistentry"><span class="term">BlackList = nspluginwrapper, valgrind, strace, avant-window-navigator, [<span class="optional"><em class="replaceable"><code><additional_packages></code></em> </span>] </span></dt><dd><div class="para">
+ Crashes in packages and binaries listed after the <em class="parameter"><code>BlackList</code></em> directive will not be handled by <span class="application"><strong>ABRT</strong></span>. If you want <span class="application"><strong>ABRT</strong></span> to ignore other packages and binaries, list them here separated by commas.
+ </div></dd><dt class="varlistentry"><span class="term">ProcessUnpackaged = <em class="replaceable"><code><yes/no></code></em> </span></dt><dd><div class="para">
+ This directive tells <span class="application"><strong>ABRT</strong></span> whether to process crashes in executables that do not belong to any package.
+ </div></dd><dt class="varlistentry"><span class="term">BlackListedPaths = <code class="filename">/usr/share/doc/*</code>, <code class="filename">*/example*</code> </span></dt><dd><div class="para">
+ Crashes in executables in these paths will be ignored by <span class="application"><strong>ABRT</strong></span>.
+ </div></dd><dt class="varlistentry"><span class="term">Database = SQLite3</span></dt><dd><div class="para">
+ This directive instructs <span class="application"><strong>ABRT</strong></span> to store its crash data in the <span class="application"><strong>SQLite3</strong></span> database. Other databases are not currently supported. However, <span class="application"><strong>ABRT</strong></span>'s plugin architecture allows for future support for alternative databases.
+ </div></dd><dt class="varlistentry"><span class="term">#WatchCrashdumpArchiveDir = /var/spool/abrt-upload/</span></dt><dd><div class="para">
+ This directive is commented out by default. Enable (uncomment) it if you want <code class="systemitem">abrtd</code> to auto-unpack crashdump tarballs which appear in the specified directory — in this case <code class="filename">/var/spool/abrt-upload/</code> — (for example, uploaded via <code class="systemitem">ftp</code>, <code class="systemitem">scp</code>, etc.). You must ensure that whatever directory you specify in this directive exists and is writable for <code class="systemitem">abrtd</code>. <code class="systemitem">abrtd</code> will not create it automatically.
+ </div></dd><dt class="varlistentry"><span class="term">MaxCrashReportsSize = <em class="replaceable"><code><size_in_megabytes></code></em> </span></dt><dd><div class="para">
+ This option sets the amount of storage space, in megabytes, used by <span class="application"><strong>ABRT</strong></span> to store all crash information from all users. The default setting is <code class="constant">1000</code> MB. Once the quota specified here has been met, <span class="application"><strong>ABRT</strong></span> will continue catching crashes, and in order to make room for the new crash dumps, it will delete the oldest and largest ones.
+ </div></dd><dt class="varlistentry"><span class="term">ActionsAndReporters = SOSreport, [<span class="optional"><em class="replaceable"><code><additional_plugins></code></em> </span>] </span></dt><dd><div class="para">
+ This option tells <span class="application"><strong>ABRT</strong></span> to run the specified plugin(s) immediately after a crash is detected and saved. For example, the <strong class="userinput"><code>SOSreport</code></strong> plugin runs the <code class="systemitem">sosreport</code> tool which adds the data collected by it to the created crash dump. You can turn this behavior off by commenting out this line. For further fine-tuning, you can add <strong class="userinput"><code>SOSreport</code></strong> (or any other specified plugin) to either the <em class="parameter"><code>CCpp</code></em> or <em class="parameter"><code>Python</code></em> options to make <span class="application"><strong>ABRT</strong></span> run <code class="command">sosreport</code> (or any other specified plugin) after any C and C++ or Python applications crash, respectively. For more information on various Action and Reporter plugins, refer to <a class="xref" href="abrt-plugins.html" title="21.3.
ABRT Plugins">Section 21.3, “ <span class="application"><strong>ABRT</strong></span> Plugins”</a>
+ </div></dd></dl></div><div class="variablelist" title="[ AnalyzerActionsAndReporters ] Section Directives"><h6>[ AnalyzerActionsAndReporters ] Section Directives</h6><div class="para">
+ This section allows you to associate certain analyzer actions and reporter actions to run when <span class="application"><strong>ABRT</strong></span> catches kernel oopses or crashes in C, C++ or Python programs. The actions and reporters specified in any of the directives below will run only if you run <code class="command">abrt-gui</code> or <code class="command">abrt-cli</code> and report the crash that occurred. If you do not specify any actions and reporters in these directives, you will not be able to report a crash via <code class="command">abrt-gui</code> or <code class="command">abrt-cli</code>. The order of actions and reporters is important. Commenting out a directive, will cause <span class="application"><strong>ABRT</strong></span> not to catch the crashes associated with that directive. For example, commenting out the Kerneloops line will cause <span class="application"><strong>ABRT</strong></span> not to catch kernel oopses.
+ </div><dl><dt class="varlistentry"><span class="term">Kerneloops = RHTSupport, Logger</span></dt><dd><div class="para">
+ This directive specifies that, for kernel oopses, both the RHTSupport and Logger reporters will be run.
+ </div></dd><dt class="varlistentry"><span class="term">CCpp = RHTSupport, Logger</span></dt><dd><div class="para">
+ This directive specifies that, when C or C++ program crashes occur, both the RHTSupport and Logger reporters will be run.
+ </div></dd><dt class="varlistentry"><span class="term">Python = RHTSupport, Logger</span></dt><dd><div class="para">
+ This directive specifies that, when Python program crashes occur, both the RHTSupport and Logger reporters will be run.
+ </div></dd></dl></div><div class="para">
+ Each of these destinations' details can be specified in the corresponding <code class="filename">plugins/*.conf</code> file. For example, <code class="filename">plugins/RHTSupport.conf</code> specifies which RHTSupport URL to use (set to <a href="https://api.access.redhat.com/rs">https://api.access.redhat.com/rs</a> by default), the user's login name, password for logging in to the RHTSupport site, etc. All these options can also be configured through the <code class="command">abrt-gui</code> application (for more information on plugin configuration refer to <a class="xref" href="abrt-plugins.html" title="21.3. ABRT Plugins">Section 21.3, “ <span class="application"><strong>ABRT</strong></span> Plugins”</a>).
+ </div><div class="variablelist" title="[ Cron ] Section Directives"><h6>[ Cron ] Section Directives</h6><dl><dt class="varlistentry"><span class="term"> <em class="replaceable"><code><time></code></em> = <em class="replaceable"><code><action_to_run></code></em> </span></dt><dd><div class="para">
+ The <code class="computeroutput">[ Cron ]</code> section of <code class="filename">abrt.conf</code> allows you to specify the exact time, or elapsed amount of time between, when <span class="application"><strong>ABRT</strong></span> should run a certain action, such as scanning for kernel oopses or performing file transfers. You can list further actions to run by appending them to the end of this section.
+ </div><div class="example" title="Example 21.1. [ Cron ] section of /etc/abrt/abrt.conf" id="ex-_Cron__section_of__etc_abrt_abrt.conf"><h6>Example 21.1. [ Cron ] section of /etc/abrt/abrt.conf</h6><div class="example-contents"><pre class="screen"># Which Action plugins to run repeatedly
+[ Cron ]
+# h:m - at h:m
+# s - every s seconds
+120 = KerneloopsScanner
+#02:00 = FileTransfer</pre></div></div><br class="example-break" /><div class="para">
+ The format for an entry is either <strong class="userinput"><code><time_in_seconds> = <em class="replaceable"><code><action_to_run></code></em> </code></strong> or <strong class="userinput"><code><hh:mm> = <action_to_run> </code></strong>, where <strong class="userinput"><code>hh</code></strong> (hour) is in the range <code class="constant">00-23</code> (all hours less than 10 should be zero-filled, i.e. preceded by a <code class="constant">0</code>), and <strong class="userinput"><code>mm</code></strong> (minute) is <code class="constant">00-59</code>, zero-filled likewise.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch21s05s03.html"><strong>Prev</strong>21.5.3. Deleting Crashes</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="configuring-centralized-crash-collection.html"><strong>Next</strong>21.7. Configuring Centralized Crash Collection</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/dhcp-relay-agent.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/dhcp-relay-agent.html
new file mode 100644
index 0000000..8d3c66b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/dhcp-relay-agent.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2.4. DHCP Relay Agent</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-dhcp-configuring-server.html" title="6.2. Configuring a DHCP Server" /><link rel="prev" href="ch06s02s03.html" title="6.2.3. Starting and Stopping the Server" /><link rel="next" href="s1-dhcp-configuring-client.html" title="6.3. Configuring a DHCP Client" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s02s03.html"><strong>Prev</strong></a></li><li class="next">
<a accesskey="n" href="s1-dhcp-configuring-client.html"><strong>Next</strong></a></li></ul><div class="section" title="6.2.4. DHCP Relay Agent" id="dhcp-relay-agent"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="dhcp-relay-agent">6.2.4. DHCP Relay Agent</h3></div></div></div><a id="id542819" class="indexterm"></a><a id="id542832" class="indexterm"></a><a id="id542846" class="indexterm"></a><div class="para">
+ The DHCP Relay Agent (<code class="command">dhcrelay</code>) allows for the relay of DHCP and BOOTP requests from a subnet with no DHCP server on it to one or more DHCP servers on other subnets.
+ </div><div class="para">
+ When a DHCP client requests information, the DHCP Relay Agent forwards the request to the list of DHCP servers specified when the DHCP Relay Agent is started. When a DHCP server returns a reply, the reply is broadcast or unicast on the network that sent the original request.
+ </div><div class="para">
+ The DHCP Relay Agent listens for DHCP requests on all interfaces unless the interfaces are specified in <code class="filename">/etc/sysconfig/dhcrelay</code> with the <code class="computeroutput">INTERFACES</code> directive.
+ </div><div class="para">
+ To start the DHCP Relay Agent, use the command <code class="command">service dhcrelay start</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch06s02s03.html"><strong>Prev</strong>6.2.3. Starting and Stopping the Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-dhcp-configuring-client.html"><strong>Next</strong>6.3. Configuring a DHCP Client</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/generating-backtrace.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/generating-backtrace.html
new file mode 100644
index 0000000..fe46011
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/generating-backtrace.html
@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.4. Generating Backtraces</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-abrt.html" title="Chapter 21. ABRT" /><link rel="prev" href="configuring-plugins-in-the-gui.html" title="21.3.3. Plugin Configuration in the GUI" /><link rel="next" href="ch21s05.html" title="21.5. Using the Command Line Interface" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="configuring-plugins-in-the-gui.html"><strong>Prev</strong></a></li><li class="next"><a
accesskey="n" href="ch21s05.html"><strong>Next</strong></a></li></ul><div class="section" title="21.4. Generating Backtraces" id="generating-backtrace"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="generating-backtrace">21.4. Generating Backtraces</h2></div></div></div><div class="para">
+ In order to analyze a reported crash, developers need as much detail about the crash as possible. A <em class="firstterm">stack backtrace</em> is an important source of information when a crash in a binary program (caught by the <code class="command">CCpp</code> analyzer plugin) occurs.
+ </div><div class="para">
+ <span class="application"><strong>ABRT</strong></span> is configured to generate a backtrace whenever a crash is reported through the <span class="application"><strong>ABRT</strong></span> GUI application or the <span class="application"><strong>ABRT</strong></span> command line interface.
+ </div><div class="para">
+ <span class="application"><strong>ABRT</strong></span> completes the following steps to generate a backtrace:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ It examines the core dump (which consists of the recorded contents of the memory of an application at a specific time), which is saved in the crash dump directory. From this file, <span class="application"><strong>ABRT</strong></span> extracts the information about the crashed binary program and information about every loaded dynamic library.
+ </div></li><li class="listitem"><div class="para">
+ It queries <span class="application"><strong>Yum</strong></span> to determine which <span class="package">debuginfo</span> packages correspond to all the files extracted from the crash dump. This is the first potentially slow operation. <span class="application"><strong>Yum</strong></span> may need to refresh the <em class="parameter"><code>filelists</code></em> of various repositories in order to find the correct package names. This process may take a few minutes.
+ </div></li><li class="listitem"><div class="para">
+ It downloads the needed <span class="package">debuginfo</span> packages, and extracts and saves the <code class="command">debuginfo</code> files. In order to speed up future backtrace generation, <code class="command">debuginfo</code> files are cached in the <code class="filename">/var/cache/abrt-di</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ It generates a backtrace using <span class="application"><strong>GDB</strong></span> (the GNU Debugger) and saves it into the crash dump directory.
+ </div></li></ul></div><div class="para">
+ You can change the following backtrace generation parameters in the <code class="filename">/etc/abrt/plugins/CCpp.conf</code> file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">Backtrace = <em class="replaceable"><code><yes/no></code></em></code> — Enables/Disables backtrace generation.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">BacktraceRemotes = <em class="replaceable"><code><yes/no></code></em></code> — For more information about this parameter, refer to <a class="xref" href="configuring-centralized-crash-collection.html" title="21.7. Configuring Centralized Crash Collection">Section 21.7, “Configuring Centralized Crash Collection”</a>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">InstallDebugInfo = <em class="replaceable"><code><yes/no></code></em></code> — Enables/Disables the installation of <span class="package">debuginfo</span> packages (useful if your network is not available or it is firewalled).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ReadonlyLocalDebugInfoDirs = /path1:/path2:...</code> — Specifies the paths of local repositories (available, for example, through a network mount) that contain pre-downloaded <span class="package">debuginfo</span> packages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">DebugInfoCacheMB = <code class="constant">4000</code></code> — Specifies the maximum size of the cached <span class="package">debuginfo</span> packages in the <code class="filename">/var/cache/abrt-di</code> directory.
+ </div></li></ul></div><div class="section" title="21.4.1. Troubleshooting Backtrace Generation" id="troubleshooting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="troubleshooting">21.4.1. Troubleshooting Backtrace Generation</h3></div></div></div><div class="para">
+ In some cases, a long delay in the <span class="application"><strong>ABRT</strong></span> GUI application occurs after choosing a crash and pressing the <span class="guibutton"><strong>Report</strong></span> button. In this case, open the <span class="guibutton"><strong>Details</strong></span> in the <span class="guilabel"><strong>Generating backtrace</strong></span> window and examine the messages.
+ </div><div class="para">
+ The following is a typical output seen in the <span class="guilabel"><strong>Generating backtrace</strong></span> window:
+ </div><pre class="screen">
+Starting the debuginfo installation
+Getting list of build IDs
+12 missing debuginfos, getting package list from cache
+12 missing debuginfos, getting package list from repositories
+Downloading 7 packages
+Download 1/7: acl-debuginfo-2.2.49-6.fc13.x86_64
+Unpacking: acl-debuginfo-2.2.49-6.fc13.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/3d/e20df1db609bd9313b1dc440796004f95911fd.debug
+Download 2/7: firefox-debuginfo-3.6.7-1.fc13.x86_64
+Unpacking: firefox-debuginfo-3.6.7-1.fc13.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/3d/b29c9308cb276431ce8854a2d88cf83518afc6.debug
+Caching debuginfo:
+usr/lib/debug/.build-id/a3/86884285365c8288e4e761ec034fafaa1daee1.debug
+⋮
+Download 7/7: zlib-debuginfo-1.2.3-23.fc12.x86_64
+Unpacking: zlib-debuginfo-1.2.3-23.fc12.x86_64.rpm
+Caching debuginfo:
+usr/lib/debug/.build-id/f7/933750da80f555321576e72b375caf7a3cc075.debug
+All needed debuginfos are present
+Generating backtrace
+</pre><div class="para">
+ This process is performed by the <span class="application"><strong>/usr/bin/abrt-debuginfo-install</strong></span> shell script. This script uses a temporary directory (e.g. <code class="filename">/var/run/abrt/tmp-29177-1283344373</code>) for its operations. Normally, this directory is removed when <span class="application"><strong>abrt-debuginfo-install</strong></span> exits.
+ </div><div class="para">
+ If the <span class="package">debuginfo</span> installation hangs, or is unable to download anything, you may debug the problem by editing the <span class="application"><strong>abrt-debuginfo-install</strong></span> script. Change the following parameters:
+ </div><pre class="screen">
+debug=false
+keep_tmp=false
+</pre><div class="para">
+ at the top of the script to:
+ </div><pre class="screen">
+debug=true
+keep_tmp=true
+</pre><div class="para">
+ The first parameter instructs <span class="application"><strong>abrt-debuginfo-install</strong></span> to be verbose, the second parameter instructs <span class="application"><strong>abrt-debuginfo-install</strong></span> to not delete the <code class="filename">/var/run/abrt/tmp-NNN-NNN</code> directory. You can examine the log files in this directory, they may contain useful error messages.
+ </div><div class="para">
+ <span class="application"><strong>abrt-debuginfo-install</strong></span> uses <span class="application"><strong>yum</strong></span> and <span class="application"><strong>yumdownloader</strong></span> to handle the <span class="package">debuginfo</span> packages. In order to quickly check that your <span class="application"><strong>yum</strong></span> configuration does not cause any problems which prevent <span class="application"><strong>abrt-debuginfo-install</strong></span> from working properly, change to the <code class="filename">/tmp</code> directory and run the following commands, as root:
+ </div><pre class="screen">
+tmp]# yum --enablerepo=*debuginfo* --quiet provides /usr/bin/true
+tmp]# yumdownloader --enablerepo=*debuginfo* --quiet coreutils
+</pre><div class="para">
+ Both of these commands should complete successfully, with no error messages. The second command should download the <code class="filename">coreutils-*.rpm</code> file. If any error messages appear, check your <span class="application"><strong>yum</strong></span> configuration files in the <code class="filename">/etc/yum.repos.d/*</code> directory and the <code class="filename">/etc/yum/*</code> directory. If any of these commands hang, check that you do not have another instance of <span class="application"><strong>yum</strong></span> running, and that your network connection is working properly.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="configuring-plugins-in-the-gui.html"><strong>Prev</strong>21.3.3. Plugin Configuration in the GUI</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch21s05.html"><strong>Next</strong>21.5. Using the Command Line Interface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ABRT-Main_Window.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ABRT-Main_Window.png
new file mode 100644
index 0000000..a3a4b0f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ABRT-Main_Window.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png
new file mode 100644
index 0000000..4d3ef28
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ABRT-Notification_Area_alarm_icon.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ABRT-plugins.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ABRT-plugins.png
new file mode 100644
index 0000000..88c1947
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ABRT-plugins.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-Authentication.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-Authentication.png
new file mode 100644
index 0000000..f6ba344
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-Authentication.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-Options.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-Options.png
new file mode 100644
index 0000000..4cdea6e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-Options.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-SSSD_Settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-SSSD_Settings.png
new file mode 100644
index 0000000..ed54c8c
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-SSSD_Settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-User_Information.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-User_Information.png
new file mode 100644
index 0000000..f15c4c0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Authentication_Configuration-authconfig-User_Information.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Change_Runtime_Boolean.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Change_Runtime_Boolean.png
new file mode 100644
index 0000000..307fb1d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Change_Runtime_Boolean.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/FirefoxWithKerberosSSO.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/FirefoxWithKerberosSSO.png
new file mode 100644
index 0000000..20fca1e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/FirefoxWithKerberosSSO.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-Software_Log_Viewer.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-Software_Log_Viewer.png
new file mode 100644
index 0000000..b65257d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-Software_Log_Viewer.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-Software_Update_Preferences.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-Software_Update_Preferences.png
new file mode 100644
index 0000000..200c773
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-Software_Update_Preferences.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-add_remove_software.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-add_remove_software.png
new file mode 100644
index 0000000..ceca3e0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-add_remove_software.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-additional_updates.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-additional_updates.png
new file mode 100644
index 0000000..a4998b9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-additional_updates.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-authenticate.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-authenticate.png
new file mode 100644
index 0000000..5276c79
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-authenticate.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-filters-only_available.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-filters-only_available.png
new file mode 100644
index 0000000..62848c3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-filters-only_available.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-filters-only_end_user.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-filters-only_end_user.png
new file mode 100644
index 0000000..eee440c
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-filters-only_end_user.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-htop.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-htop.png
new file mode 100644
index 0000000..c5a7357
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-htop.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-install.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-install.png
new file mode 100644
index 0000000..9a0d4c4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-install.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-installing_a_package_group.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-installing_a_package_group.png
new file mode 100644
index 0000000..e5035a9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-installing_a_package_group.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-removal_in_progress.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-removal_in_progress.png
new file mode 100644
index 0000000..c439981
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-removal_in_progress.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-remove.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-remove.png
new file mode 100644
index 0000000..0131330
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-remove.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-removing_a_package.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-removing_a_package.png
new file mode 100644
index 0000000..e6043a9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-removing_a_package.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-software_update.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-software_update.png
new file mode 100644
index 0000000..e181637
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-software_update.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-updates_available.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-updates_available.png
new file mode 100644
index 0000000..3a0128a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Graphical_Package_Management-updates_available.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Load_New_Policy.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Load_New_Policy.png
new file mode 100644
index 0000000..cd98e04
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Load_New_Policy.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png
new file mode 100644
index 0000000..e5c7782
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-All_applet_states.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png
new file mode 100644
index 0000000..218ef23
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Available_to_all_users.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Connect_automatically.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Connect_automatically.png
new file mode 100644
index 0000000..7be39e5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Connect_automatically.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-IPv4_Settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-IPv4_Settings.png
new file mode 100644
index 0000000..f7d08b6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-IPv4_Settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-Wired.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-Wired.png
new file mode 100644
index 0000000..c2333ff
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Edit_System_eth0-Wired.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png
new file mode 100644
index 0000000..60dee58
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Editing_Wired_Connection_1.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png
new file mode 100644
index 0000000..d26d73a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Editing_Wireless_Connection_1.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Addresses.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Addresses.png
new file mode 100644
index 0000000..4c7cdce
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Addresses.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DHCP_Client_ID.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DHCP_Client_ID.png
new file mode 100644
index 0000000..377c12e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DHCP_Client_ID.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DNS_Servers.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DNS_Servers.png
new file mode 100644
index 0000000..b237513
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-DNS_Servers.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Method.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Method.png
new file mode 100644
index 0000000..f8a34ec
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Method.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Routes.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Routes.png
new file mode 100644
index 0000000..b19e4dd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Routes.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Search_domains.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Search_domains.png
new file mode 100644
index 0000000..fd07c37
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings-Search_domains.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings.png
new file mode 100644
index 0000000..0189e20
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-IPv4_Settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png
new file mode 100644
index 0000000..de27930
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Network_Connections.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-System_eth0-Routes.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-System_eth0-Routes.png
new file mode 100644
index 0000000..d7cbd30
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-System_eth0-Routes.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png
new file mode 100644
index 0000000..56baee0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Wireless_Auto_Connections_List.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png
new file mode 100644
index 0000000..be2b3f3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-Wireless_authentication_required.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-applet_states.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-applet_states.png
new file mode 100644
index 0000000..9b7b776
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-applet_states.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png
new file mode 100644
index 0000000..7c979c8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-left-click_menu.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png
new file mode 100644
index 0000000..cacaf1a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM-right-click_menu.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png
new file mode 100644
index 0000000..2f4c41b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Network_Configuration-NM_applet-signal_strength_75.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/PS2port.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/PS2port.png
new file mode 100644
index 0000000..c1ef70b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/PS2port.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/SCLogin.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/SCLogin.png
new file mode 100644
index 0000000..5bdef58
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/SCLogin.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/SCLoginEnrollment.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/SCLoginEnrollment.png
new file mode 100644
index 0000000..2809b32
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/SCLoginEnrollment.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/SELinux_Decision_Process.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/SELinux_Decision_Process.png
new file mode 100644
index 0000000..acd0883
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/SELinux_Decision_Process.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Screenshot-1.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Screenshot-1.png
new file mode 100644
index 0000000..ab08c32
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Screenshot-1.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Screenshot-2.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Screenshot-2.png
new file mode 100644
index 0000000..fb95149
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Screenshot-2.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Users_Groups-Create_New_User.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Users_Groups-Create_New_User.png
new file mode 100644
index 0000000..8b8a6c1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Users_Groups-Create_New_User.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Users_Groups-User_Manager.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Users_Groups-User_Manager.png
new file mode 100644
index 0000000..c314821
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/Users_Groups-User_Manager.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-01.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-01.png
new file mode 100644
index 0000000..5d3952e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-01.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-02.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-02.png
new file mode 100644
index 0000000..5f0bb11
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-02.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-03.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-03.png
new file mode 100644
index 0000000..ff0eb87
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-03.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-04.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-04.png
new file mode 100644
index 0000000..1de182b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-04.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-05.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-05.png
new file mode 100644
index 0000000..4f2fa66
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-05.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-06.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-06.png
new file mode 100644
index 0000000..35bf2f3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-06.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-07.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-07.png
new file mode 100644
index 0000000..4da6ddf
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apache-mod_ssl-genkey-07.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apol-DIF.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apol-DIF.png
new file mode 100644
index 0000000..f8bcb41
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apol-DIF.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apol-TE-rule-search.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apol-TE-rule-search.png
new file mode 100644
index 0000000..1a063ed
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apol-TE-rule-search.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apol-plain.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apol-plain.png
new file mode 100644
index 0000000..a7415e8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/apol-plain.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/arrow.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/arrow.png
new file mode 100644
index 0000000..e4cc965
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/arrow.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/auth-panel.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/auth-panel.png
new file mode 100644
index 0000000..6335d2f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/auth-panel.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig-auth.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig-auth.png
new file mode 100644
index 0000000..c219198
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig-auth.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig-options.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig-options.png
new file mode 100644
index 0000000..5ed80b8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig-options.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig-user-info.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig-user-info.png
new file mode 100644
index 0000000..97b8689
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig-user-info.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig_LDAP_kerb.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig_LDAP_kerb.png
new file mode 100644
index 0000000..0da191d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig_LDAP_kerb.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig_advanced.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig_advanced.png
new file mode 100644
index 0000000..1fa30ce
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authconfig_advanced.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authentication_configuration.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authentication_configuration.png
new file mode 100644
index 0000000..ea48230
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authentication_configuration.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authicon.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authicon.png
new file mode 100644
index 0000000..e397b63
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/authicon.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/bugworkflow_new4.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/bugworkflow_new4.png
new file mode 100644
index 0000000..29151dd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/bugworkflow_new4.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/bugworkflow_old8.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/bugworkflow_old8.png
new file mode 100644
index 0000000..64025b2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/bugworkflow_old8.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-authentication.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-authentication.png
new file mode 100644
index 0000000..2e84f56
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-authentication.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-ntsysv.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-ntsysv.png
new file mode 100644
index 0000000..70bc146
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-ntsysv.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_configuration.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_configuration.png
new file mode 100644
index 0000000..ea3a46b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_configuration.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_disabled.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_disabled.png
new file mode 100644
index 0000000..3dceb52
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_disabled.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_enabled.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_enabled.png
new file mode 100644
index 0000000..dec0092
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_enabled.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_running.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_running.png
new file mode 100644
index 0000000..c2d1ca0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_running.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_selected.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_selected.png
new file mode 100644
index 0000000..13d5262
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_selected.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_stopped.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_stopped.png
new file mode 100644
index 0000000..bd9e1a8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_stopped.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_unknown.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_unknown.png
new file mode 100644
index 0000000..94dc930
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_unknown.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_wrong.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_wrong.png
new file mode 100644
index 0000000..f59ef68
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/controlling-access-to-services-service_wrong.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-authentication.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-authentication.png
new file mode 100644
index 0000000..97bd72d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-authentication.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-date_and_time.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-date_and_time.png
new file mode 100644
index 0000000..0c5c375
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-date_and_time.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-network_time_protocol.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-network_time_protocol.png
new file mode 100644
index 0000000..dac02af
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-network_time_protocol.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-time_zone.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-time_zone.png
new file mode 100644
index 0000000..33f305b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/date-and-time-time_zone.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/devicemngr.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/devicemngr.png
new file mode 100644
index 0000000..9709a00
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/devicemngr.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/display-dualhead.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/display-dualhead.png
new file mode 100644
index 0000000..8e5ddc6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/display-dualhead.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/display-hardware.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/display-hardware.png
new file mode 100644
index 0000000..1afbfb8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/display-hardware.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/display-settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/display-settings.png
new file mode 100644
index 0000000..dff2b43
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/display-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/flask-arch.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/flask-arch.png
new file mode 100644
index 0000000..3b560a4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/flask-arch.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/flow-diagram.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/flow-diagram.png
new file mode 100644
index 0000000..e693600
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/flow-diagram.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-print-manager-list.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-print-manager-list.png
new file mode 100644
index 0000000..b217335
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-print-manager-list.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-print-manager.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-print-manager.png
new file mode 100644
index 0000000..61c6aee
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-print-manager.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-print-queue.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-print-queue.png
new file mode 100644
index 0000000..0fb401b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-print-queue.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-system-monitor-filesystems.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-system-monitor-filesystems.png
new file mode 100644
index 0000000..78544f6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-system-monitor-filesystems.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-system-monitor-memory.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-system-monitor-memory.png
new file mode 100644
index 0000000..adddecb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-system-monitor-memory.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-system-monitor-processes.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-system-monitor-processes.png
new file mode 100644
index 0000000..a423370
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/gnome-system-monitor-processes.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/group-new.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/group-new.png
new file mode 100644
index 0000000..a9ad250
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/group-new.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/group-properties.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/group-properties.png
new file mode 100644
index 0000000..2fd40e4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/group-properties.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-directories-add.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-directories-add.png
new file mode 100644
index 0000000..6ae3fa1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-directories-add.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-directories.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-directories.png
new file mode 100644
index 0000000..3f9a08a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-directories.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-environment.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-environment.png
new file mode 100644
index 0000000..01e7b3f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-environment.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-general-options.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-general-options.png
new file mode 100644
index 0000000..a6be6ef
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-general-options.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-listen.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-listen.png
new file mode 100644
index 0000000..dc8d3fb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-listen.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-logging.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-logging.png
new file mode 100644
index 0000000..adc3abc
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-logging.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-main.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-main.png
new file mode 100644
index 0000000..a081a27
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-main.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-server.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-server.png
new file mode 100644
index 0000000..3cdb10f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-server.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-siteconfig.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-siteconfig.png
new file mode 100644
index 0000000..3b9d2f3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-siteconfig.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-tuning.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-tuning.png
new file mode 100644
index 0000000..4013cb9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-tuning.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-virtualhosts-ssl.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-virtualhosts-ssl.png
new file mode 100644
index 0000000..1e5a82b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-virtualhosts-ssl.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-virtualhosts.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-virtualhosts.png
new file mode 100644
index 0000000..9817274
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/httpd-virtualhosts.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/hwbrowser.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/hwbrowser.png
new file mode 100644
index 0000000..d3a44d8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/hwbrowser.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/icon-greencheck-pkgs.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/icon-greencheck-pkgs.png
new file mode 100644
index 0000000..961ba23
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/icon-greencheck-pkgs.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/icon-install-prep.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/icon-install-prep.png
new file mode 100644
index 0000000..877f768
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/icon-install-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/icon-removal-prep.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/icon-removal-prep.png
new file mode 100644
index 0000000..da5833e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/icon-removal-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/image_needed.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/image_needed.png
new file mode 100644
index 0000000..9c179f0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/image_needed.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/individual-pkgs.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/individual-pkgs.png
new file mode 100644
index 0000000..ce1b35d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/individual-pkgs.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/install-depend-prep.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/install-depend-prep.png
new file mode 100644
index 0000000..270046d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/install-depend-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/install-prep.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/install-prep.png
new file mode 100644
index 0000000..ffb480b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/install-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png
new file mode 100644
index 0000000..190a06c
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-expert_settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png
new file mode 100644
index 0000000..24638bf
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-filtering_settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png
new file mode 100644
index 0000000..031750e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-not_enough_memory.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png
new file mode 100644
index 0000000..a5cb44a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration-target_settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration.png
new file mode 100644
index 0000000..e2099b1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/kdump-kernel_dump_configuration.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-applet-addition.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-applet-addition.png
new file mode 100644
index 0000000..c3398d9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-applet-addition.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-applet-observation.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-applet-observation.png
new file mode 100644
index 0000000..fd74dd6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-applet-observation.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-applet-selection.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-applet-selection.png
new file mode 100644
index 0000000..1896a2e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-applet-selection.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-break-take.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-break-take.png
new file mode 100644
index 0000000..94a8ee2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-break-take.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-break.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-break.png
new file mode 100644
index 0000000..23c127f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-break.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-default.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-default.png
new file mode 100644
index 0000000..87143db
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-default.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-new.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-new.png
new file mode 100644
index 0000000..2976104
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-new.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-prioritize.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-prioritize.png
new file mode 100644
index 0000000..69d8c31
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-prioritize.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-separate.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-separate.png
new file mode 100644
index 0000000..7b2c9e1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-separate.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-test.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-test.png
new file mode 100644
index 0000000..3b2c6ef
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts-test.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts.png
new file mode 100644
index 0000000..82fc603
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/keyboard-configuration-layouts.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvg.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvg.png
new file mode 100644
index 0000000..c7a6719
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvg.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-auto-config.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-auto-config.png
new file mode 100644
index 0000000..bb8d7e4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-auto-config.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main1.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main1.png
new file mode 100644
index 0000000..b31935d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main1.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main10.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main10.png
new file mode 100644
index 0000000..d69338d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main10.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main12.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main12.png
new file mode 100644
index 0000000..e52b865
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main12.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main13.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main13.png
new file mode 100644
index 0000000..5dfb234
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main13.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main14.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main14.png
new file mode 100644
index 0000000..29679e9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main14.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main15.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main15.png
new file mode 100644
index 0000000..aaf3437
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main15.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main16.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main16.png
new file mode 100644
index 0000000..c621f91
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main16.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main17.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main17.png
new file mode 100644
index 0000000..3592633
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main17.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main18.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main18.png
new file mode 100644
index 0000000..b249b29
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main18.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main2.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main2.png
new file mode 100644
index 0000000..262b114
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main2.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main21.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main21.png
new file mode 100644
index 0000000..00bd4f9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main21.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main23.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main23.png
new file mode 100644
index 0000000..9b44669
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main23.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main26.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main26.png
new file mode 100644
index 0000000..bb6bff0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main26.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main27.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main27.png
new file mode 100644
index 0000000..6948d82
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main27.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main28.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main28.png
new file mode 100644
index 0000000..fc8707d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main28.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main3.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main3.png
new file mode 100644
index 0000000..9d219c4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main3.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main30.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main30.png
new file mode 100644
index 0000000..6a7c34b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main30.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main31.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main31.png
new file mode 100644
index 0000000..5d35af5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main31.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main32.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main32.png
new file mode 100644
index 0000000..84b6b88
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main32.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main33.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main33.png
new file mode 100644
index 0000000..cda6747
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main33.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main34.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main34.png
new file mode 100644
index 0000000..9e5fe58
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main34.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main36.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main36.png
new file mode 100644
index 0000000..9c71571
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main36.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main7.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main7.png
new file mode 100644
index 0000000..7c9f09a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-main7.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-boot.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-boot.png
new file mode 100644
index 0000000..6a0b6bc
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-boot.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-done.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-done.png
new file mode 100644
index 0000000..8735895
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-done.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-free.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-free.png
new file mode 100644
index 0000000..27ce579
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-free.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-lv.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-lv.png
new file mode 100644
index 0000000..2a39b2e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-lv.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-lvdone.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-lvdone.png
new file mode 100644
index 0000000..7a9f89b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-lvdone.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-postboot.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-postboot.png
new file mode 100644
index 0000000..30a65e5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-postboot.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-pv01.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-pv01.png
new file mode 100644
index 0000000..ea16714
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-pv01.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-pvdone.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-pvdone.png
new file mode 100644
index 0000000..872e47d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-pvdone.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-vg.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-vg.png
new file mode 100644
index 0000000..b6ec9af
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm-manual-vg.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm/lvg.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm/lvg.svg
new file mode 100644
index 0000000..f564769
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm/lvg.svg
@@ -0,0 +1,684 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/"
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://web.resource.org/cc/"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ id="svg2"
+ sodipodi:version="0.32"
+ inkscape:version="0.45+devel"
+ width="500"
+ height="262"
+ version="1.0"
+ sodipodi:docbase="/home/andy/Desktop"
+ sodipodi:docname="lvg.svg"
+ inkscape:export-filename="/home/andy/Build/RedHat/Deployment_Guide/en-US/images/lvmintro/lvg.png"
+ inkscape:export-xdpi="90"
+ inkscape:export-ydpi="90"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ sodipodi:modified="true">
+ <metadata
+ id="metadata7">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <defs
+ id="defs5">
+ <linearGradient
+ id="linearGradient3987">
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:0"
+ offset="0"
+ id="stop3989" />
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:1"
+ offset="1"
+ id="stop3991" />
+ </linearGradient>
+ <radialGradient
+ cx="265"
+ cy="789.56696"
+ r="265"
+ fx="265"
+ fy="789.56696"
+ id="radialGradient4023"
+ xlink:href="#linearGradient3987"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.886887,0,0,1.602074,-235.025,-437.5826)" />
+ <pattern
+ patternUnits="userSpaceOnUse"
+ width="32"
+ height="32"
+ id="white-spots"
+ patternTransform="matrix(0.375,0,0,0.375,379,400)">
+ <g
+ inkscape:label="#g3035"
+ id="white-spot"
+ transform="translate(-484.3997,-513.505)">
+ <path
+ sodipodi:nodetypes="czzzz"
+ d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z "
+ id="path3033"
+ style="opacity:0.3;fill:white" />
+ </g>
+ </pattern>
+ <pattern
+ xlink:href="#white-spots"
+ id="pattern4015"
+ patternTransform="matrix(0.375,0,0,0.375,379,437.7952)" />
+ <pattern
+ xlink:href="#pattern4015"
+ id="pattern4062"
+ patternTransform="matrix(0.3975,0,0,0.644084,0.7397418,648.83735)" />
+ <marker
+ inkscape:stockid="TriangleOutM"
+ orient="auto"
+ refY="0"
+ refX="0"
+ id="TriangleOutM"
+ style="overflow:visible">
+ <path
+ id="path3238"
+ d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z "
+ style="fill:#5c5c4f;fill-rule:evenodd;stroke-width:1pt;marker-start:none"
+ transform="scale(0.4,0.4)" />
+ </marker>
+ <linearGradient
+ x1="200.7363"
+ y1="100.4028"
+ x2="211.99519"
+ y2="89.143997"
+ id="XMLID_3298_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#bfbfbf;stop-opacity:1"
+ offset="0"
+ id="stop20103" />
+ <stop
+ style="stop-color:#f2f2f2;stop-opacity:1"
+ offset="1"
+ id="stop20105" />
+ <a:midPointStop
+ style="stop-color:#BFBFBF"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#BFBFBF"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#F2F2F2"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="200.7363"
+ y1="100.4028"
+ x2="211.99519"
+ y2="89.143997"
+ id="linearGradient36592"
+ xlink:href="#XMLID_3298_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="181.2925"
+ y1="110.8481"
+ x2="192.6369"
+ y2="99.5037"
+ id="XMLID_3297_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0"
+ id="stop20096" />
+ <stop
+ style="stop-color:#ccc;stop-opacity:1"
+ offset="1"
+ id="stop20098" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#CCCCCC"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="181.2925"
+ y1="110.8481"
+ x2="192.6369"
+ y2="99.5037"
+ id="linearGradient36595"
+ xlink:href="#XMLID_3297_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="211.77589"
+ y1="105.7749"
+ x2="212.6619"
+ y2="108.2092"
+ id="XMLID_3296_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#0f6124;stop-opacity:1"
+ offset="0"
+ id="stop20087" />
+ <stop
+ style="stop-color:#219630;stop-opacity:1"
+ offset="1"
+ id="stop20089" />
+ <a:midPointStop
+ style="stop-color:#0F6124"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#0F6124"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#219630"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="211.77589"
+ y1="105.7749"
+ x2="212.6619"
+ y2="108.2092"
+ id="linearGradient36677"
+ xlink:href="#XMLID_3296_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="208.9834"
+ y1="116.8296"
+ x2="200.0811"
+ y2="96.834602"
+ id="XMLID_3295_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#b2b2b2;stop-opacity:1"
+ offset="0"
+ id="stop20076" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0.5"
+ id="stop20078" />
+ <stop
+ style="stop-color:white;stop-opacity:1"
+ offset="1"
+ id="stop20080" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="208.9834"
+ y1="116.8296"
+ x2="200.0811"
+ y2="96.834602"
+ id="linearGradient36604"
+ xlink:href="#XMLID_3295_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="195.5264"
+ y1="97.911102"
+ x2="213.5213"
+ y2="115.9061"
+ id="XMLID_3294_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#ccc;stop-opacity:1"
+ offset="0"
+ id="stop20069" />
+ <stop
+ style="stop-color:white;stop-opacity:1"
+ offset="1"
+ id="stop20071" />
+ <a:midPointStop
+ style="stop-color:#CCCCCC"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#CCCCCC"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="195.5264"
+ y1="97.911102"
+ x2="213.5213"
+ y2="115.9061"
+ id="linearGradient36607"
+ xlink:href="#XMLID_3294_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="186.1938"
+ y1="109.1343"
+ x2="206.6881"
+ y2="88.639999"
+ id="XMLID_3293_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#b2b2b2;stop-opacity:1"
+ offset="0"
+ id="stop20056" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0.16850001"
+ id="stop20058" />
+ <stop
+ style="stop-color:white;stop-opacity:1"
+ offset="0.23029999"
+ id="stop20060" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0.2809"
+ id="stop20062" />
+ <stop
+ style="stop-color:#c2c2c2;stop-opacity:1"
+ offset="0.5"
+ id="stop20064" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.1685" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.2303" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.2809" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#C2C2C2"
+ offset="0.5" />
+ </linearGradient>
+ <linearGradient
+ x1="186.1938"
+ y1="109.1343"
+ x2="206.6881"
+ y2="88.639999"
+ id="linearGradient36610"
+ xlink:href="#XMLID_3293_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2888,-113.1415)" />
+ <linearGradient
+ x1="184.8569"
+ y1="112.2676"
+ x2="211.94099"
+ y2="89.541397"
+ id="XMLID_3292_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#b2b2b2;stop-opacity:1"
+ offset="0"
+ id="stop20043" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0.16850001"
+ id="stop20045" />
+ <stop
+ style="stop-color:white;stop-opacity:1"
+ offset="0.23029999"
+ id="stop20047" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="0.2809"
+ id="stop20049" />
+ <stop
+ style="stop-color:#ccc;stop-opacity:1"
+ offset="1"
+ id="stop20051" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#B2B2B2"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.1685" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.2303" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.2809" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#CCCCCC"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="184.8569"
+ y1="112.2676"
+ x2="211.94099"
+ y2="89.541397"
+ id="linearGradient36613"
+ xlink:href="#XMLID_3292_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.341664,0,0,1.309319,-245.2887,-113.1416)" />
+ </defs>
+ <sodipodi:namedview
+ inkscape:window-height="680"
+ inkscape:window-width="1067"
+ inkscape:pageshadow="0"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base"
+ inkscape:zoom="1"
+ inkscape:cx="254.22455"
+ inkscape:cy="51.82077"
+ inkscape:window-x="1763"
+ inkscape:window-y="162"
+ inkscape:current-layer="svg2" />
+ <g
+ transform="matrix(0.9433962,0,0,0.5822222,0,-350.70864)"
+ id="background">
+ <rect
+ width="530"
+ height="450"
+ rx="21.200001"
+ ry="34.351147"
+ x="0"
+ y="602.36218"
+ style="fill:#e3dcc0"
+ id="rect1933" />
+ <rect
+ width="530"
+ height="450"
+ rx="21.200001"
+ ry="34.351147"
+ x="0"
+ y="602.36218"
+ style="fill:url(#pattern4062);fill-opacity:1"
+ id="rect3092" />
+ <rect
+ width="530"
+ height="450"
+ rx="21.200001"
+ ry="34.351147"
+ x="0"
+ y="602.36218"
+ style="fill:url(#radialGradient4023);fill-opacity:1"
+ id="rect3985" />
+ </g>
+ <g
+ transform="matrix(1.13733,0,0,1.13733,42.68492,14.4921)"
+ id="g36679">
+ <path
+ d="M 14.068171,35.701824 L -2.3269574,19.911437 C -2.487957,19.728132 -2.5818734,19.479362 -2.5818734,19.178218 L -2.5818734,10.379595 C -2.5818734,9.62019 -1.9512916,8.847691 -1.1597102,8.651294 L 26.652975,1.9344875 C 27.135974,1.8166488 27.55189,1.9475807 27.806806,2.2356309 L 44.175102,17.986738 C 44.362933,18.222415 44.45685,18.458093 44.45685,18.746143 L 44.45685,27.544767 C 44.45685,28.304172 43.826268,29.07667 43.034687,29.273068 L 15.222002,35.989874 C 14.739003,36.09462 14.323087,35.976781 14.068171,35.701824 z "
+ style="fill:url(#linearGradient36613);stroke:#000000;stroke-width:2.66666627;stroke-miterlimit:3.86369991;stroke-dasharray:none"
+ id="path20053" />
+ <path
+ d="M 14.068181,35.701818 L -2.3269553,19.911433 C -2.4879549,19.728128 -2.5818714,19.479358 -2.5818714,19.178215 L -2.5818714,10.379592 C -2.5818714,9.620187 -1.9512893,8.847689 -1.1597074,8.651291 L 26.65299,1.9344862 C 27.135989,1.8166475 27.551905,1.9475794 27.806821,2.2356295 L 44.215373,18.039107 L 14.068181,35.701818 z "
+ style="fill:url(#linearGradient36610);fill-rule:evenodd"
+ id="path20066" />
+ <path
+ d="M 15.208595,24.41549 L 43.021293,17.698684 C 43.799458,17.51538 44.443456,17.973641 44.443456,18.733046 L 44.443456,27.531669 C 44.443456,28.291073 43.812874,29.063572 43.021293,29.259969 L 15.208595,35.976775 C 14.43043,36.173173 13.786431,35.701818 13.786431,34.942413 L 13.786431,26.143791 C 13.786431,25.384386 14.417014,24.611888 15.208595,24.41549 z "
+ style="fill:url(#linearGradient36607);fill-rule:evenodd"
+ id="path20073" />
+ <path
+ d="M 42.216294,17.318982 C 43.571375,16.965466 44.443456,17.620125 44.443456,19.021096 L 44.443456,27.37455 C 44.443456,28.369633 43.665291,29.286156 42.71271,29.521833 L 16.080677,36.146986 C 15.356179,36.317198 13.853514,36.330291 13.853514,34.628177 L 13.853514,26.091418 C 13.853514,25.096336 14.631679,24.179812 15.584261,23.944135 L 42.216294,17.318982 z M 15.114678,34.981693 C 15.195178,34.981693 15.342762,34.981693 15.570844,34.92932 L 42.216294,28.304167 C 42.752959,28.173235 43.182292,27.610228 43.182292,27.165059 L 43.182292,18.811605 C 43.182292,18.615207 43.182292,18.536648 43.155458,18.471182 C 43.074959,18.471182 42.927376,18.484276 42.71271,18.536648 L 16.06726,25.174895 C 15.530595,25.305827 15.101262,25.868834 15.101262,26.314002 L 15.101262,34.850761 L 15.114678,34.981693 z "
+ style="fill:url(#linearGradient36604)"
+ id="path20082" />
+ <path
+ d="M 38.258384,26.104508 L 40.606297,25.567688 C 42.108961,25.227265 42.108961,27.42692 40.606297,27.767343 L 38.258384,28.304164 C 36.755721,28.65768 36.755721,26.444931 38.258384,26.104508 z "
+ style="fill:url(#linearGradient36677)"
+ id="path20091" />
+ <line
+ stroke-miterlimit="3.8637"
+ x1="38.177872"
+ y1="27.047226"
+ x2="40.431877"
+ y2="26.523495"
+ id="line20093"
+ style="fill:none;stroke:#7cc771;stroke-width:1.14049983;stroke-linecap:round;stroke-miterlimit:3.86369991" />
+ <path
+ d="M -1.5085401,19.361519 L 12.605766,32.533266 L 12.538684,28.160142 C 10.096854,29.286156 -1.5085401,16.598856 -1.5085401,16.598856 L -1.5085401,19.361519 z "
+ style="fill:url(#linearGradient36595);fill-rule:evenodd"
+ id="path20100" />
+ <path
+ d="M 26.89449,3.1390595 L 41.089296,16.402459 L 26.559074,20.251856 C 16.30741,10.968786 18.530549,3.9770231 23.62083,3.9770231 L 26.89449,3.1390595 z "
+ style="fill:url(#linearGradient36592);fill-rule:evenodd"
+ id="path20107" />
+ </g>
+ <use
+ id="use2083"
+ xlink:href="#g36679"
+ y="0"
+ x="0"
+ transform="translate(112,-5.8601806e-6)"
+ width="1"
+ height="1" />
+ <use
+ x="0"
+ y="0"
+ xlink:href="#g36679"
+ id="use2081"
+ transform="translate(236,-5.8601806e-6)"
+ width="500"
+ height="300" />
+ <path
+ sodipodi:nodetypes="cscs"
+ id="path7807"
+ d="M 334.65058,40.941748 L 381.51004,40.941748 C 396.59751,40.941748 404.00181,48.635068 404.00181,64.474428 C 404.00181,64.474428 404.00181,80.068835 404.00181,87.623995"
+ style="fill:none;fill-opacity:0.75;fill-rule:evenodd;stroke:#5c5c4f;stroke-width:1.99999976;stroke-linecap:butt;stroke-linejoin:miter;marker-mid:none;marker-end:url(#TriangleOutM);stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1" />
+ <path
+ style="fill:none;fill-opacity:0.75;fill-rule:evenodd;stroke:#5c5c4f;stroke-width:1.99999976;stroke-linecap:butt;stroke-linejoin:miter;marker-mid:none;marker-end:url(#TriangleOutM);stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ d="M 70.023795,58.110466 C 70.023795,58.110466 70.023795,80.775945 70.023795,88.331105"
+ id="path2203"
+ sodipodi:nodetypes="cs" />
+ <use
+ id="use2209"
+ xlink:href="#path2203"
+ y="0"
+ x="0"
+ transform="translate(113.8442,4.1398194e-6)"
+ width="1"
+ height="1" />
+ <use
+ x="0"
+ y="0"
+ xlink:href="#path2203"
+ id="use2207"
+ transform="translate(230.8704,4.1398194e-6)"
+ width="500"
+ height="300" />
+ <use
+ x="0"
+ y="0"
+ xlink:href="#path2203"
+ id="use2213"
+ transform="translate(114.1978,98.64135)"
+ width="500"
+ height="300" />
+ <use
+ height="300"
+ width="500"
+ transform="matrix(0.965926,-0.258819,0.258819,0.965926,8.0694501,120.38211)"
+ id="use2211"
+ xlink:href="#path2203"
+ y="0"
+ x="0" />
+ <use
+ x="0"
+ y="0"
+ xlink:href="#path2203"
+ id="use2215"
+ transform="matrix(-0.965926,-0.258819,-0.258819,0.965926,358.87684,120.38211)"
+ width="500"
+ height="300" />
+ <use
+ height="300"
+ width="500"
+ transform="translate(367.723,-28.72283)"
+ id="use2225"
+ xlink:href="#rect2217"
+ y="0"
+ x="0" />
+ <g
+ id="g2365"
+ transform="translate(-4.50223,-28.72283)">
+ <rect
+ ry="10"
+ rx="10"
+ y="129.88016"
+ x="15.849242"
+ height="50.91169"
+ width="110.30865"
+ id="rect2217"
+ style="fill:#5c5c4f" />
+ <g
+ transform="translate(-11.80981,18.26833)"
+ id="g2070"
+ style="fill:#ffffff">
+ <text
+ id="text2032"
+ y="132.30888"
+ x="34"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ xml:space="preserve"><tspan
+ y="132.30888"
+ x="34"
+ id="tspan2034"
+ sodipodi:role="line">Physical Volume</tspan></text>
+ <text
+ id="text2052"
+ y="148.54446"
+ x="59.29908"
+ style="font-size:12px;fill:#e3dcc0;font-family:Interstate-Bold"
+ xml:space="preserve"><tspan
+ y="148.54446"
+ x="59.29908"
+ id="tspan2054"
+ sodipodi:role="line"
+ style="font-size:14px;fill:#e3dcc0">100 GB</tspan></text>
+ </g>
+ </g>
+ <use
+ id="use2375"
+ xlink:href="#g2365"
+ y="0"
+ x="0"
+ transform="translate(117.3797,4.1398194e-6)"
+ width="1"
+ height="1" />
+ <use
+ x="0"
+ y="0"
+ xlink:href="#g2365"
+ id="use2373"
+ transform="translate(236.1737,4.1398194e-6)"
+ width="500"
+ height="300" />
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#ffffff;font-family:Interstate-Bold"
+ x="439.05899"
+ y="121.56151"
+ id="text2377"
+ sodipodi:linespacing="125%"><tspan
+ sodipodi:role="line"
+ id="tspan2379"
+ x="439.05899"
+ y="121.56151">/boot</tspan></text>
+ <text
+ xml:space="preserve"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#e3dcc0;font-family:Interstate-Bold"
+ x="438.24738"
+ y="137.79706"
+ id="text2381"
+ sodipodi:linespacing="125%"><tspan
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#e3dcc0;font-family:Interstate-Bold"
+ sodipodi:role="line"
+ id="tspan2383"
+ x="438.24738"
+ y="137.79706">100 MB (ext3)</tspan></text>
+ <g
+ id="g2401"
+ transform="translate(3.983051,-7.5096324)">
+ <rect
+ style="fill:#5c5c4f"
+ id="rect2227"
+ width="245.30865"
+ height="50.91169"
+ x="56.86396"
+ y="207.92432"
+ rx="10"
+ ry="10" />
+ <text
+ sodipodi:linespacing="125%"
+ id="text2389"
+ y="230.8945"
+ x="178.03696"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#ffffff;font-family:Interstate-Bold"
+ xml:space="preserve"><tspan
+ y="230.8945"
+ x="178.03696"
+ id="tspan2391"
+ sodipodi:role="line">Logical Volume Group</tspan></text>
+ <text
+ sodipodi:linespacing="125%"
+ id="text2393"
+ y="247.13007"
+ x="179.57793"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#e3dcc0;font-family:Interstate-Bold"
+ xml:space="preserve"><tspan
+ y="247.13007"
+ x="179.57793"
+ id="tspan2395"
+ sodipodi:role="line"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#e3dcc0;font-family:Interstate-Bold">(100 GB x3) - 100 MB</tspan></text>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm/lvols.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm/lvols.svg
new file mode 100644
index 0000000..a2c6a8f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvm/lvols.svg
@@ -0,0 +1,286 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="385"
+ height="189.99998"
+ id="svg2">
+ <defs
+ id="defs5">
+ <linearGradient
+ id="linearGradient3987">
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:0"
+ offset="0"
+ id="stop3989" />
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:1"
+ offset="1"
+ id="stop3991" />
+ </linearGradient>
+ <radialGradient
+ cx="265"
+ cy="789.56696"
+ r="265"
+ fx="265"
+ fy="789.56696"
+ id="radialGradient4023"
+ xlink:href="#linearGradient3987"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.886887,0,0,1.602074,-235.025,-437.5826)" />
+ <pattern
+ patternTransform="matrix(0.375,0,0,0.375,379,400)"
+ id="white-spots"
+ height="32"
+ width="32"
+ patternUnits="userSpaceOnUse">
+ <g
+ transform="translate(-484.3997,-513.505)"
+ id="white-spot"
+ inkscape:label="#g3035">
+ <path
+ style="opacity:0.3;fill:white"
+ id="path3033"
+ d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z "
+ sodipodi:nodetypes="czzzz" />
+ </g>
+ </pattern>
+ <pattern
+ patternTransform="matrix(0.375,0,0,0.375,379,437.7952)"
+ id="pattern4015"
+ xlink:href="#white-spots" />
+ <pattern
+ patternTransform="matrix(0.5162337,0,0,0.8881579,0.9607077,666.44901)"
+ id="pattern4062"
+ xlink:href="#pattern4015" />
+ <marker
+ refX="0"
+ refY="0"
+ orient="auto"
+ style="overflow:visible"
+ id="TriangleOutM">
+ <path
+ d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z "
+ transform="scale(0.4,0.4)"
+ style="fill:#5c5c4f;fill-rule:evenodd;stroke-width:1pt;marker-start:none"
+ id="path3238" />
+ </marker>
+ </defs>
+ <g
+ transform="matrix(0.7264151,0,0,0.4222222,0,-254.33069)"
+ id="background">
+ <rect
+ width="530"
+ height="450"
+ rx="27.532467"
+ ry="47.368423"
+ x="0"
+ y="602.36218"
+ style="fill:#e3dcc0"
+ id="rect1933" />
+ <rect
+ width="530"
+ height="450"
+ rx="27.532467"
+ ry="47.368423"
+ x="0"
+ y="602.36218"
+ style="fill:url(#pattern4062);fill-opacity:1"
+ id="rect3092" />
+ <rect
+ width="530"
+ height="450"
+ rx="27.532467"
+ ry="47.368423"
+ x="0"
+ y="602.36218"
+ style="fill:url(#radialGradient4023);fill-opacity:1"
+ id="rect3985" />
+ </g>
+ <path
+ d="M 105.47946,31.115562 L 95.96315,31.115562 C 80.875678,31.115562 73.471383,38.808874 73.471383,54.648239 L 73.471383,101.86887"
+ style="fill:none;fill-opacity:0.75;fill-rule:evenodd;stroke:#5c5c4f;stroke-width:1.99999976;stroke-linecap:butt;stroke-linejoin:miter;marker-mid:none;marker-end:url(#TriangleOutM);stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path7807" />
+ <use
+ transform="matrix(-1,0,0,1,388.2247,-4.1430667e-8)"
+ id="use2006"
+ x="0"
+ y="0"
+ width="406"
+ height="198"
+ xlink:href="#path7807" />
+ <path
+ d="M 194.0339,65.254841 L 194.0339,101.86887"
+ style="fill:none;fill-opacity:0.75;fill-rule:evenodd;stroke:#5c5c4f;stroke-width:1.99999976;stroke-linecap:butt;stroke-linejoin:miter;marker-mid:none;marker-end:url(#TriangleOutM);stroke-miterlimit:4;stroke-dasharray:none;stroke-opacity:1"
+ id="path2008" />
+ <g
+ transform="translate(-7.657627,-6.4864229)"
+ id="g2126">
+ <rect
+ width="115"
+ height="60"
+ rx="10"
+ ry="10"
+ x="19.948734"
+ y="115.77461"
+ style="fill:#5c5c4f"
+ id="rect2068" />
+ <g
+ transform="translate(-1.438859,0)"
+ style="fill:#ffffff"
+ id="g2070">
+ <text
+ x="34"
+ y="132.30888"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2032"
+ xml:space="preserve"><tspan
+ x="34"
+ y="132.30888"
+ id="tspan2034">Logical Volume</tspan></text>
+ <text
+ x="59.758186"
+ y="147.5739"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2044"
+ xml:space="preserve"><tspan
+ x="59.758186"
+ y="147.5739"
+ id="tspan2046">/home</tspan></text>
+ <text
+ x="59.29908"
+ y="164.54446"
+ style="font-size:12px;fill:#e3dcc0;font-family:Interstate-Bold"
+ id="text2052"
+ xml:space="preserve"><tspan
+ x="59.29908"
+ y="164.54446"
+ style="font-size:14px;fill:#e3dcc0"
+ id="tspan2054">200 GB</tspan></text>
+ </g>
+ </g>
+ <g
+ transform="translate(-7.657627,-6.4864229)"
+ id="g2117">
+ <use
+ transform="translate(124.2428,0)"
+ style="fill:#5c5c4f"
+ id="use2080"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#rect2068" />
+ <g
+ transform="translate(-5.196065,0)"
+ style="fill:#ffffff"
+ id="g2082">
+ <use
+ transform="translate(128,0)"
+ style="fill:#ffffff"
+ id="use2038"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#text2032" />
+ <text
+ x="204.0676"
+ y="148.44991"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2048"
+ xml:space="preserve"><tspan
+ x="204.0676"
+ y="148.44991"
+ id="tspan2050">/</tspan></text>
+ <text
+ x="192.11157"
+ y="164.54446"
+ style="font-size:12px;fill:#e3dcc0;font-family:Interstate-Bold"
+ id="text2060"
+ xml:space="preserve"><tspan
+ x="192.11157"
+ y="164.54446"
+ style="font-size:14px;fill:#e3dcc0"
+ id="tspan2062">20 GB</tspan></text>
+ </g>
+ </g>
+ <g
+ transform="translate(-7.657627,-6.4864229)"
+ id="g2109">
+ <use
+ transform="translate(248.1945,0)"
+ style="fill:#5c5c4f"
+ id="use2078"
+ x="0"
+ y="0"
+ width="406"
+ height="198"
+ xlink:href="#rect2068" />
+ <g
+ style="fill:#ffffff"
+ id="g2089">
+ <text
+ x="292.99136"
+ y="134.13889"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2040"
+ xml:space="preserve"><tspan
+ x="292.99136"
+ y="134.13889"
+ id="tspan2042">Free Space</tspan></text>
+ <text
+ x="304.35623"
+ y="164.54446"
+ style="font-size:12px;fill:#e3dcc0;font-family:Interstate-Bold"
+ id="text2056"
+ xml:space="preserve"><tspan
+ x="304.35623"
+ y="164.54446"
+ style="font-size:14px;fill:#e3dcc0"
+ id="tspan2058">80 GB</tspan></text>
+ </g>
+ </g>
+ <g
+ transform="translate(-7.657627,-6.4864229)"
+ id="g2101">
+ <rect
+ width="171.15254"
+ height="50.482662"
+ rx="10"
+ ry="10"
+ x="116.11526"
+ y="16.779661"
+ style="fill:#5c5c4f"
+ id="rect1885" />
+ <g
+ transform="translate(-1.047109,0)"
+ style="fill:#ffffff"
+ id="g2095">
+ <text
+ x="139.23997"
+ y="34"
+ style="font-size:12px;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2028"
+ xml:space="preserve"><tspan
+ x="139.23997"
+ y="34"
+ id="tspan2030">Logical Volume Group</tspan></text>
+ <text
+ x="140.57306"
+ y="57.064232"
+ style="font-size:12px;fill:#e3dcc0;font-family:Interstate-Bold"
+ id="text2064"
+ xml:space="preserve"><tspan
+ x="140.57306"
+ y="57.064232"
+ style="font-size:14px;fill:#e3dcc0"
+ id="tspan2066">(100 GB x3) -100MB</tspan></text>
+ </g>
+ </g>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvols.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvols.png
new file mode 100644
index 0000000..dae912b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/lvols.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/mouseconfig.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/mouseconfig.png
new file mode 100644
index 0000000..52c513b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/mouseconfig.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/n-t-n-ipsec-diagram.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/n-t-n-ipsec-diagram.png
new file mode 100644
index 0000000..281afd6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/n-t-n-ipsec-diagram.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/n-to-n-ipsec-local.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/n-to-n-ipsec-local.png
new file mode 100644
index 0000000..ee306da
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/n-to-n-ipsec-local.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/n-to-n-ipsec-remote.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/n-to-n-ipsec-remote.png
new file mode 100644
index 0000000..48e5beb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/n-to-n-ipsec-remote.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-aliases.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-aliases.png
new file mode 100644
index 0000000..19bb5c0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-aliases.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-dns.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-dns.png
new file mode 100644
index 0000000..e91e5bd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-dns.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-ethernet-settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-ethernet-settings.png
new file mode 100644
index 0000000..0909194
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-ethernet-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-ethernet.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-ethernet.png
new file mode 100644
index 0000000..ec60e62
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-ethernet.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-home-profile.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-home-profile.png
new file mode 100644
index 0000000..39974eb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-home-profile.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-hosts.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-hosts.png
new file mode 100644
index 0000000..2605b7d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-hosts.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-isdn-settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-isdn-settings.png
new file mode 100644
index 0000000..3e1d01d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-isdn-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-isdn.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-isdn.png
new file mode 100644
index 0000000..afa4f42
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-isdn.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-modem-settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-modem-settings.png
new file mode 100644
index 0000000..195df2d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-modem-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-modem.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-modem.png
new file mode 100644
index 0000000..7e10037
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-modem.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-office-profile.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-office-profile.png
new file mode 100644
index 0000000..06f87ec
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-office-profile.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tokenring-settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tokenring-settings.png
new file mode 100644
index 0000000..e66bfc1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tokenring-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tokenring.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tokenring.png
new file mode 100644
index 0000000..36ea52a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tokenring.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tonline1.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tonline1.png
new file mode 100644
index 0000000..4fe97dd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tonline1.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tonlineAcctsetup.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tonlineAcctsetup.png
new file mode 100644
index 0000000..3735a96
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tonlineAcctsetup.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tonlineProvidertab.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tonlineProvidertab.png
new file mode 100644
index 0000000..bcdd369
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-tonlineProvidertab.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-wireless-settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-wireless-settings.png
new file mode 100644
index 0000000..7642a10
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-wireless-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-wireless.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-wireless.png
new file mode 100644
index 0000000..95b7955
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-wireless.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-xdsl-selectdevicetype.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-xdsl-selectdevicetype.png
new file mode 100644
index 0000000..c5d7e1d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-xdsl-selectdevicetype.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-xdsl-settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-xdsl-settings.png
new file mode 100644
index 0000000..fb58da0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-xdsl-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-xdsl.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-xdsl.png
new file mode 100644
index 0000000..1705dae
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat-xdsl.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat.png
new file mode 100644
index 0000000..8a00403
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/neat.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-add.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-add.png
new file mode 100644
index 0000000..2b70a3f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-add.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-general-options.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-general-options.png
new file mode 100644
index 0000000..21bab60
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-general-options.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-server-settings.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-server-settings.png
new file mode 100644
index 0000000..e2f63bd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-server-settings.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-user-access.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-user-access.png
new file mode 100644
index 0000000..5192e64
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/nfs-user-access.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/oprof-start-config.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/oprof-start-config.png
new file mode 100644
index 0000000..32bd5e1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/oprof-start-config.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/oprof-start-setup.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/oprof-start-setup.png
new file mode 100644
index 0000000..06d8719
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/oprof-start-setup.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/originals/Graphical_Package_Management-software_update.xcf b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/originals/Graphical_Package_Management-software_update.xcf
new file mode 100644
index 0000000..0406f95
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/originals/Graphical_Package_Management-software_update.xcf differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/package-selections.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/package-selections.png
new file mode 100644
index 0000000..f9e1ea8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/package-selections.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/pam-icon.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/pam-icon.png
new file mode 100644
index 0000000..4db6046
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/pam-icon.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/print-manager-menu.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/print-manager-menu.png
new file mode 100644
index 0000000..e0625e3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/print-manager-menu.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-add-printer.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-add-printer.png
new file mode 100644
index 0000000..43cc6a2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-add-printer.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config1.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config1.png
new file mode 100644
index 0000000..0e95984
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config1.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config2.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config2.png
new file mode 100644
index 0000000..94a625d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config2.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config3.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config3.png
new file mode 100644
index 0000000..59ba05c
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config3.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config4.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config4.png
new file mode 100644
index 0000000..c4ebdf5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config4.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config5.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config5.png
new file mode 100644
index 0000000..e1b16bb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-config5.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-default-icon.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-default-icon.png
new file mode 100644
index 0000000..da8bfaf
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-default-icon.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-edit.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-edit.png
new file mode 100644
index 0000000..69b148d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-edit.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-ipp.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-ipp.png
new file mode 100644
index 0000000..19029d7
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-ipp.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-jetdirect.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-jetdirect.png
new file mode 100644
index 0000000..aa77195
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-jetdirect.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-local.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-local.png
new file mode 100644
index 0000000..0805ca5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-local.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-lpd.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-lpd.png
new file mode 100644
index 0000000..d9afe31
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-lpd.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-main.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-main.png
new file mode 100644
index 0000000..9bdfdb4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-main.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-ncp.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-ncp.png
new file mode 100644
index 0000000..6a475f0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-ncp.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-queue-name.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-queue-name.png
new file mode 100644
index 0000000..dc3d9a2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-queue-name.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-select-model.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-select-model.png
new file mode 100644
index 0000000..105bd16
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-select-model.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-sharing-general.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-sharing-general.png
new file mode 100644
index 0000000..495c934
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-sharing-general.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-sharing-hosts.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-sharing-hosts.png
new file mode 100644
index 0000000..a470ffa
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-sharing-hosts.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-sharing-queue.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-sharing-queue.png
new file mode 100644
index 0000000..fef0e03
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-sharing-queue.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-smb.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-smb.png
new file mode 100644
index 0000000..c03aec7
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-smb.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-test-page.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-test-page.png
new file mode 100644
index 0000000..41092e5
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printconf-test-page.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printer-notification-icon.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printer-notification-icon.png
new file mode 100644
index 0000000..001bb42
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/printer-notification-icon.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-boot-error.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-boot-error.png
new file mode 100644
index 0000000..68df6f2
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-boot-error.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-final.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-final.png
new file mode 100644
index 0000000..ffc3c63
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-final.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-free.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-free.png
new file mode 100644
index 0000000..3b98e20
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-free.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-lvm-final.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-lvm-final.png
new file mode 100644
index 0000000..859a2f3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-lvm-final.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-mntpt.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-mntpt.png
new file mode 100644
index 0000000..4a8a8fd
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-mntpt.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-add.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-add.png
new file mode 100644
index 0000000..ed278ac
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-add.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-bootready.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-bootready.png
new file mode 100644
index 0000000..898162a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-bootready.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-opt.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-opt.png
new file mode 100644
index 0000000..8e99e92
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-opt.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-opt2.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-opt2.png
new file mode 100644
index 0000000..746b901
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/raid-manual-part-opt2.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-config-packages.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-config-packages.png
new file mode 100644
index 0000000..598ea42
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-config-packages.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-config-users.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-config-users.png
new file mode 100644
index 0000000..ad3d581
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-config-users.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-filter-enable.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-filter-enable.png
new file mode 100644
index 0000000..3c0c2f0
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-filter-enable.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-filter-sample.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-filter-sample.png
new file mode 100644
index 0000000..7d349d6
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-filter-sample.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-filters.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-filters.png
new file mode 100644
index 0000000..3c91d0d
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-filters.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-logviewer-add.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-logviewer-add.png
new file mode 100644
index 0000000..07962eb
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-logviewer-add.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-logviewer-monitoring.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-logviewer-monitoring.png
new file mode 100644
index 0000000..01e826b
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-logviewer-monitoring.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-logviewer.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-logviewer.png
new file mode 100644
index 0000000..b24be71
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-logviewer.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-optional-packages.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-optional-packages.png
new file mode 100644
index 0000000..6f78f03
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/redhat-optional-packages.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/registering.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/registering.png
new file mode 100644
index 0000000..2d823b4
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/registering.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/relevant-errata.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/relevant-errata.png
new file mode 100644
index 0000000..0c22605
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/relevant-errata.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/removal-prep.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/removal-prep.png
new file mode 100644
index 0000000..c187553
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/removal-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/remove-depend-prep.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/remove-depend-prep.png
new file mode 100644
index 0000000..24ddd0a
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/remove-depend-prep.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/rh-securitylevel.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/rh-securitylevel.png
new file mode 100644
index 0000000..8775cc8
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/rh-securitylevel.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/rhl-common/networkconfig/n-t-n-ipsec-diagram.svg b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/rhl-common/networkconfig/n-t-n-ipsec-diagram.svg
new file mode 100644
index 0000000..c420f0c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/rhl-common/networkconfig/n-t-n-ipsec-diagram.svg
@@ -0,0 +1,658 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!-- Created with Inkscape (http://www.inkscape.org/) -->
+<svg
+ xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/"
+ xmlns:dc="http://purl.org/dc/elements/1.1/"
+ xmlns:cc="http://web.resource.org/cc/"
+ xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns="http://www.w3.org/2000/svg"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
+ xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
+ version="1.0"
+ width="600"
+ height="185.99998"
+ id="svg2580"
+ sodipodi:version="0.32"
+ inkscape:version="0.44+devel"
+ sodipodi:docname="n-t-n-ipsec-diagram.svg"
+ sodipodi:docbase="/home/andy/Build/RedHat/Deployment_Guide/en-US/images/rhl-common/networkconfig"
+ inkscape:output_extension="org.inkscape.output.svg.inkscape"
+ sodipodi:modified="TRUE"
+ inkscape:export-filename="/home/andy/Build/RedHat/Deployment_Guide/en-US/images/rhl-common/networkconfig/n-t-n-ipsec-diagram.png"
+ inkscape:export-xdpi="90"
+ inkscape:export-ydpi="90">
+ <metadata
+ id="metadata109">
+ <rdf:RDF>
+ <cc:Work
+ rdf:about="">
+ <dc:format>image/svg+xml</dc:format>
+ <dc:type
+ rdf:resource="http://purl.org/dc/dcmitype/StillImage" />
+ </cc:Work>
+ </rdf:RDF>
+ </metadata>
+ <sodipodi:namedview
+ inkscape:window-height="480"
+ inkscape:window-width="640"
+ inkscape:pageshadow="0"
+ inkscape:pageopacity="0.0"
+ guidetolerance="10.0"
+ gridtolerance="10.0"
+ objecttolerance="10.0"
+ borderopacity="1.0"
+ bordercolor="#666666"
+ pagecolor="#ffffff"
+ id="base" />
+ <defs
+ id="defs3">
+ <radialGradient
+ cx="603.19"
+ cy="230.77"
+ r="1.67"
+ fx="603.19"
+ fy="230.77"
+ id="x5010_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.1,0,0,1.1,-54.33,-75.4)">
+ <stop
+ style="stop-color:#c9ffc9;stop-opacity:1"
+ offset="0"
+ id="stop29201" />
+ <stop
+ style="stop-color:#23a11f;stop-opacity:1"
+ offset="1"
+ id="stop29203" />
+ <a:midPointStop
+ style="stop-color:#C9FFC9"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#C9FFC9"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#23A11F"
+ offset="1" />
+ </radialGradient>
+ <linearGradient
+ x1="601.48999"
+ y1="170.16"
+ x2="613.84003"
+ y2="170.16"
+ id="x5002_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#d9d9d9;stop-opacity:1"
+ offset="0"
+ id="stop29134" />
+ <stop
+ style="stop-color:#ffffff;stop-opacity:1"
+ offset="0.2"
+ id="stop29136" />
+ <stop
+ style="stop-color:#999999;stop-opacity:1"
+ offset="1"
+ id="stop29138" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.20" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#999999"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="592.20001"
+ y1="156.45"
+ x2="609.98999"
+ y2="174.23"
+ id="x5004_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)">
+ <stop
+ style="stop-color:#d9d9d9;stop-opacity:1"
+ offset="0"
+ id="stop29157" />
+ <stop
+ style="stop-color:#ffffff;stop-opacity:1"
+ offset="1"
+ id="stop29159" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="592.31"
+ y1="162.60001"
+ x2="609.32001"
+ y2="145.59"
+ id="x5003_"
+ gradientUnits="userSpaceOnUse">
+ <stop
+ style="stop-color:#f2f2f2;stop-opacity:1"
+ offset="0"
+ id="stop29143" />
+ <stop
+ style="stop-color:#e5e5e5;stop-opacity:1"
+ offset="1"
+ id="stop29145" />
+ <a:midPointStop
+ style="stop-color:#F2F2F2"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#F2F2F2"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#E5E5E5"
+ offset="1" />
+ </linearGradient>
+ <linearGradient
+ x1="592.20001"
+ y1="156.45"
+ x2="609.98999"
+ y2="174.24001"
+ id="x5000_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)">
+ <stop
+ style="stop-color:#d9d9d9;stop-opacity:1"
+ offset="0"
+ id="stop29124" />
+ <stop
+ style="stop-color:#ffffff;stop-opacity:1"
+ offset="1"
+ id="stop29126" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0" />
+ <a:midPointStop
+ style="stop-color:#D9D9D9"
+ offset="0.5" />
+ <a:midPointStop
+ style="stop-color:#FFFFFF"
+ offset="1" />
+ </linearGradient>
+ <pattern
+ xlink:href="#pattern4396"
+ id="pattern4704"
+ patternTransform="matrix(0.4660769,0,0,0.4386606,446.32365,760.68863)" />
+ <pattern
+ xlink:href="#pattern4315"
+ id="pattern4396"
+ patternTransform="matrix(0.361895,0,0,0.361895,41.1944,774.2561)" />
+ <pattern
+ xlink:href="#pattern4038"
+ id="pattern4315"
+ patternTransform="matrix(0.361895,0,0,0.361895,253.6944,752.2561)" />
+ <pattern
+ xlink:href="#pattern4015"
+ id="pattern4062"
+ patternTransform="matrix(0.33125,0,0,0.9072579,0.6164534,667.82716)" />
+ <linearGradient
+ id="linearGradient4054">
+ <stop
+ style="stop-color:#a70000;stop-opacity:0"
+ offset="0"
+ id="stop4056" />
+ <stop
+ style="stop-color:#a70000;stop-opacity:1"
+ offset="1"
+ id="stop4058" />
+ </linearGradient>
+ <pattern
+ patternUnits="userSpaceOnUse"
+ width="32"
+ height="32"
+ id="black-spots"
+ patternTransform="matrix(0.455007,0,0,0.455007,20.99995,116)">
+ <g
+ inkscape:label="#g3039"
+ id="black-spot"
+ transform="translate(-448.3997,-513.505)">
+ <path
+ style="opacity:0.1;fill:black"
+ id="path2961"
+ d="M 473.39967,529.50504 C 473.39967,534.47304 469.36767,538.50504 464.39967,538.50504 C 459.43167,538.50504 455.39967,534.47304 455.39967,529.50504 C 455.39967,524.53704 459.43167,520.50504 464.39967,520.50504 C 469.36767,520.50504 473.39967,524.53704 473.39967,529.50504 z "
+ sodipodi:nodetypes="czzzz" />
+ </g>
+ </pattern>
+ <pattern
+ xlink:href="#black-spots"
+ id="pattern4038"
+ patternTransform="matrix(0.361895,0,0,0.361895,-33.80556,922.2561)" />
+ <pattern
+ xlink:href="#white-spots"
+ id="pattern4015"
+ patternTransform="matrix(0.375,0,0,0.375,379,437.7952)" />
+ <linearGradient
+ id="linearGradient3987">
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:0"
+ offset="0"
+ id="stop3989" />
+ <stop
+ style="stop-color:#e3dcc0;stop-opacity:1"
+ offset="1"
+ id="stop3991" />
+ </linearGradient>
+ <pattern
+ patternUnits="userSpaceOnUse"
+ width="32"
+ height="32"
+ id="white-spots"
+ patternTransform="matrix(0.375,0,0,0.375,379,400)">
+ <g
+ inkscape:label="#g3035"
+ id="white-spot"
+ transform="translate(-484.3997,-513.505)">
+ <path
+ sodipodi:nodetypes="czzzz"
+ d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z "
+ id="path3033"
+ style="opacity:0.3;fill:white" />
+ </g>
+ </pattern>
+ <radialGradient
+ cx="265"
+ cy="789.56696"
+ r="265"
+ fx="265"
+ fy="789.56696"
+ id="radialGradient4023"
+ xlink:href="#linearGradient3987"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.886887,0,0,1.602074,-235.025,-437.5826)" />
+ <radialGradient
+ cx="710"
+ cy="668.36218"
+ r="75"
+ fx="710"
+ fy="668.36218"
+ id="radialGradient4393"
+ xlink:href="#linearGradient4054"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.522104,0,0,1.217683,-946.194,60.5088)" />
+ <linearGradient
+ x1="592.20001"
+ y1="156.45"
+ x2="609.98999"
+ y2="174.24001"
+ id="linearGradient2554"
+ xlink:href="#x5000_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
+ <linearGradient
+ x1="592.31"
+ y1="162.60001"
+ x2="609.32001"
+ y2="145.59"
+ id="linearGradient2556"
+ xlink:href="#x5003_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
+ <linearGradient
+ x1="592.20001"
+ y1="156.45"
+ x2="609.98999"
+ y2="174.23"
+ id="linearGradient2558"
+ xlink:href="#x5004_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
+ <linearGradient
+ x1="601.48999"
+ y1="170.16"
+ x2="613.84003"
+ y2="170.16"
+ id="linearGradient2560"
+ xlink:href="#x5002_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
+ <linearGradient
+ x1="592.31"
+ y1="162.60001"
+ x2="609.32001"
+ y2="145.59"
+ id="linearGradient2562"
+ xlink:href="#x5003_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" />
+ <radialGradient
+ cx="603.19"
+ cy="230.77"
+ r="1.67"
+ fx="603.19"
+ fy="230.77"
+ id="radialGradient2564"
+ xlink:href="#x5010_"
+ gradientUnits="userSpaceOnUse"
+ gradientTransform="matrix(1.23,0,0,1.23,-709.93,-245.02)" />
+ </defs>
+ <g
+ transform="translate(-8.5872532,-710.1876)"
+ id="layer1">
+ <g
+ transform="matrix(1.1320755,0,0,0.4133333,8.5872532,461.21125)"
+ id="background">
+ <rect
+ width="530"
+ height="450"
+ rx="17.666664"
+ ry="48.387093"
+ x="0"
+ y="602.36218"
+ style="fill:#e3dcc0"
+ id="rect1933" />
+ <rect
+ width="530"
+ height="450"
+ rx="17.666664"
+ ry="48.387093"
+ x="0"
+ y="602.36218"
+ style="fill:url(#pattern4062);fill-opacity:1"
+ id="rect3092" />
+ <rect
+ width="530"
+ height="450"
+ rx="17.666664"
+ ry="48.387093"
+ x="0"
+ y="602.36218"
+ style="fill:url(#radialGradient4023);fill-opacity:1"
+ id="rect3985" />
+ </g>
+ <g
+ transform="translate(248,0)"
+ id="g4070" />
+ <path
+ d="M 129.40054,237.86797 L 472.39401,237.86797"
+ transform="translate(0,602.3622)"
+ style="fill:none;stroke:#5c5c4f;stroke-width:2"
+ id="path3199" />
+ <text
+ x="-753.05115"
+ y="587.36591"
+ transform="matrix(0,-1,1,0,0,0)"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#c8c5ac;font-family:Interstate-Bold"
+ id="text3222"
+ xml:space="preserve"><tspan
+ x="-753.05115"
+ y="587.36591"
+ id="tspan3224">#4592</tspan></text>
+ <path
+ d="M 181.40054,840.23017 C 181.40054,778.65551 260.02962,738.50013 310.35665,840.23017 C 363.5259,739.1693 427.39402,778.43988 427.39402,840.23017"
+ style="fill:none;stroke:#5c5c4f;stroke-width:2"
+ id="path3248" />
+ <g
+ transform="translate(218.38333,751.3446)"
+ id="computer">
+ <path
+ d="M 10.98,7.35 L 10.98,31.17 L 24.76,45.05 C 24.76,45.05 28.25,45.27 31.9,44.16 C 35.55,43.05 36.95,41.49 36.95,41.49 L 36.95,17.46 L 23.59,4.07 L 10.98,7.35 z "
+ style="fill:url(#linearGradient2554)"
+ id="path4802" />
+ <path
+ d="M 36.18,16.79 L 23.61,3.9 L 10.61,7.23 L 24.81,21.11 C 24.81,21.11 28.44,21 31.76,20.11 C 35.07,19.22 37.03,17.66 37.03,17.66 L 36.18,16.79 z "
+ style="fill:url(#linearGradient2556)"
+ id="path4804" />
+ <path
+ d="M 10.98,7.35 L 10.98,31.17 L 24.76,45.05 C 24.76,45.05 28.25,45.27 31.9,44.16 C 35.55,43.05 36.95,41.49 36.95,41.49 L 36.95,17.46 L 23.59,4.07 L 10.98,7.35 z "
+ style="fill:none;stroke:#000000;stroke-width:1.92999995;stroke-linecap:round;stroke-linejoin:round"
+ id="path4806" />
+ <path
+ d="M 10.98,7.35 L 10.98,31.17 L 24.76,45.05 C 24.76,45.05 28.25,45.27 31.9,44.16 C 35.55,43.05 36.95,41.49 36.95,41.49 L 36.95,17.46 L 23.59,4.07 L 10.98,7.35 z "
+ style="fill:url(#linearGradient2558)"
+ id="path4808" />
+ <path
+ d="M 24.52,14.7 L 37,17.81 L 37,41.59 C 33.22,44.88 29.67,44.95 24.7,45 L 24.52,14.7 z "
+ style="fill:url(#linearGradient2560)"
+ id="path4810" />
+ <path
+ d="M 23.58,4.02 L 11.03,7.42 L 24.81,21.11 C 24.81,21.11 28.44,21 31.76,20.11 C 35.07,19.22 37.03,17.66 37.03,17.66 L 23.58,4.02 z "
+ style="fill:url(#linearGradient2562)"
+ id="path4812" />
+ <path
+ d="M 11.27,7.58 L 24.82,21.12 C 24.82,21.12 28.03,21.33 31.68,20.35 C 35.18,19.41 36.83,17.71 36.83,17.71"
+ style="fill:none;stroke:#ffffff;stroke-width:0.47999999;stroke-linecap:round"
+ id="path4814" />
+ <path
+ d="M 24.74,21.3 L 24.74,44.76"
+ style="fill:none;stroke:#ffffff;stroke-width:0.47999999;stroke-linecap:round"
+ id="path4816" />
+ <path
+ d="M 27.44,23.79 C 30.4,23.66 33.22,22.96 35.54,21.38 C 35.75,21.91 35.7,23.06 35.54,23.36 C 35.45,23.45 34.62,23.99 33.18,24.54 C 31.77,25.07 29.77,25.62 27.47,25.68 C 27.19,25.22 27.27,24.04 27.44,23.79 z "
+ style="fill:#808080"
+ id="path4818" />
+ <path
+ d="M 35.53,23.38 L 27.44,25.56 C 27.45,25.6 27.45,25.66 27.47,25.69 C 29.78,25.63 31.78,25.07 33.19,24.53 C 34.63,23.98 35.44,23.46 35.53,23.38 z "
+ style="fill:#b2b2b2"
+ id="path4820" />
+ <path
+ d="M 27.44,27.28 C 30.4,27.16 33.22,26.46 35.54,24.88 C 35.75,25.4 35.7,26.56 35.54,26.86 C 35.45,26.95 34.62,27.49 33.18,28.03 C 31.77,28.57 29.77,29.12 27.47,29.18 C 27.19,28.72 27.27,27.54 27.44,27.28 z "
+ style="fill:#808080"
+ id="path4822" />
+ <path
+ d="M 35.53,26.87 L 27.44,29.06 C 27.45,29.1 27.45,29.16 27.47,29.19 C 29.78,29.13 31.78,28.57 33.19,28.03 C 34.63,27.48 35.44,26.96 35.53,26.87 z "
+ style="fill:#b2b2b2"
+ id="path4824" />
+ <path
+ d="M 27.21,42.71 L 27.21,31.52 C 27.21,31.52 29,31.51 31.85,30.69 C 34.68,29.87 35.58,29.02 35.58,29.02 L 35.58,40.05 C 35.58,40.05 34.21,41.19 31.54,41.98 C 28.88,42.76 27.21,42.71 27.21,42.71 z "
+ style="fill:none;stroke:#b2b2b2;stroke-width:0.47999999;stroke-linecap:round;stroke-linejoin:round"
+ id="path4826" />
+ <path
+ d="M 31.68,37.72 C 32.29,37.54 32.79,37.95 32.79,38.62 C 32.79,39.29 32.29,39.97 31.68,40.15 C 31.07,40.33 30.58,39.93 30.58,39.27 C 30.58,38.58 31.07,37.9 31.68,37.72 z "
+ style="fill:url(#radialGradient2564);stroke:#328e36;stroke-width:0.44"
+ id="path4828" />
+ </g>
+ <use
+ transform="translate(131.19729,-4)"
+ id="use3219"
+ x="0"
+ y="0"
+ width="530"
+ height="450"
+ xlink:href="#computer" />
+ <use
+ transform="translate(-59.201614,63)"
+ id="use3189"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#computer" />
+ <use
+ transform="translate(190.39892,56)"
+ id="use3187"
+ x="0"
+ y="0"
+ width="530"
+ height="450"
+ xlink:href="#computer" />
+ <path
+ d="M 139,831.8622 C 143.432,831.8622 147,835.4302 147,839.8622 C 147,844.2942 143.432,847.8622 139,847.8622 C 134.568,847.8622 131,844.2942 131,839.8622 C 131,835.4302 134.568,831.8622 139,831.8622 z "
+ style="fill:#5c5c4f"
+ id="rect3250" />
+ <use
+ transform="translate(340,0)"
+ id="use3255"
+ x="0"
+ y="0"
+ width="530"
+ height="450"
+ xlink:href="#rect3250" />
+ <use
+ transform="translate(456.57438,0)"
+ id="use3236"
+ x="0"
+ y="0"
+ width="530"
+ height="450"
+ xlink:href="#g3226" />
+ <g
+ id="g3226">
+ <g
+ transform="matrix(0.7764706,0,0,0.825,-24.775496,114.51338)"
+ id="redbox">
+ <rect
+ width="150"
+ height="120"
+ rx="12.878788"
+ ry="12.121212"
+ x="59.5"
+ y="814.36218"
+ style="fill:#a70000"
+ id="rect2056" />
+ <rect
+ width="150"
+ height="120"
+ rx="12.878788"
+ ry="12.121212"
+ x="59.5"
+ y="814.36218"
+ style="fill:url(#pattern4704);fill-opacity:1"
+ id="rect4036" />
+ <rect
+ width="150"
+ height="120"
+ rx="12.878788"
+ ry="12.121212"
+ x="59.5"
+ y="814.36218"
+ style="fill:url(#radialGradient4393);fill-opacity:1"
+ id="rect4052" />
+ </g>
+ <g
+ transform="translate(14,-3.5)"
+ id="g3201">
+ <use
+ transform="translate(28,11)"
+ id="use3197"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#use3191" />
+ <use
+ transform="matrix(0.8136403,0,0,0.8136403,-134.27293,193.59903)"
+ id="use3191"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#computer" />
+ <use
+ transform="translate(-26,13)"
+ id="use3195"
+ x="0"
+ y="0"
+ width="1"
+ height="1"
+ xlink:href="#use3191" />
+ </g>
+ </g>
+ <text
+ x="79.673676"
+ y="869.12421"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;font-family:Interstate-Bold"
+ id="text3206"
+ xml:space="preserve"><tspan
+ x="79.673676"
+ y="869.12421"
+ id="tspan3208"><tspan
+ style="fill:#e3dcc0"
+ id="tspan3214">192.168</tspan><tspan
+ style="fill:#ffffff;font-family:Interstate-Black"
+ id="tspan3210">.1.0</tspan><tspan
+ style="fill:#e3dcc0"
+ id="tspan3216">/24</tspan></tspan></text>
+ <text
+ x="536.24792"
+ y="869.12421"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;font-family:Interstate-Bold"
+ id="text3238"
+ xml:space="preserve"
+ sodipodi:linespacing="125%"><tspan
+ x="536.24792"
+ y="869.12421"
+ id="tspan3240"><tspan
+ style="fill:#e3dcc0"
+ id="tspan3242">192.168</tspan><tspan
+ style="fill:#ffffff;font-family:Interstate-Black"
+ id="tspan3244">.2.0</tspan><tspan
+ style="fill:#e3dcc0"
+ id="tspan3246">/24</tspan></tspan></text>
+ </g>
+ <g
+ transform="translate(72.359706,94.597376)"
+ id="g5942">
+ <path
+ d="M 227.11741,-2.304662 C 218.61044,-2.304662 211.08086,1.861868 206.4667,8.285438 C 195.39058,8.321638 186.41172,17.32208 186.41169,28.40664 C 172.14009,28.40664 172.14966,48.52785 185.94835,48.52785 C 189.32794,48.52785 192.29548,46.79837 194.05642,44.19252 C 200.67358,49.26756 208.83789,49.60772 216.16326,46.04579 C 223.4569,49.52596 232.72939,49.18683 238.60105,45.78104 C 244.88316,49.59798 253.32269,49.74361 259.1119,45.00919 C 260.85648,47.99903 264.57749,48.52785 268.28642,48.52785 C 273.83988,48.52785 278.34705,44.02069 278.34703,38.46723 C 277.87274,30.86628 270.94669,26.89599 264.14967,29.26709 C 263.09801,22.48659 258.00258,17.05277 251.37537,15.56615 C 248.16502,5.206798 238.52748,-2.304662 227.11741,-2.304662 z "
+ style="fill:#5c5c4f"
+ id="path3769" />
+ <text
+ x="225.04935"
+ y="31.033188"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#ffffff;font-family:Interstate-Bold"
+ id="text2388"
+ xml:space="preserve"><tspan
+ x="225.04935"
+ y="31.033188"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#ffffff;font-family:Interstate-Bold"
+ id="tspan2390">Internet</tspan></text>
+ </g>
+ <text
+ x="232.42056"
+ y="33.855572"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#000000;font-family:Interstate-Bold"
+ id="text2431"
+ xml:space="preserve"><tspan
+ x="232.42056"
+ y="33.855572"
+ style="fill:#000000"
+ id="tspan2433">ipsec0</tspan></text>
+ <text
+ x="363.21115"
+ y="33.855572"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#000000;font-family:Interstate-Bold"
+ id="text2443"
+ xml:space="preserve"><tspan
+ x="363.21115"
+ y="33.855572"
+ style="fill:#000000"
+ id="tspan2445">ipsec1</tspan></text>
+ <text
+ x="178.05638"
+ y="160.83585"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#000000;font-family:Interstate-Bold"
+ id="text2447"
+ xml:space="preserve"><tspan
+ x="178.05638"
+ y="160.83585"
+ style="fill:#000000"
+ id="tspan2449">gateway0</tspan></text>
+ <text
+ x="427.51163"
+ y="160.83585"
+ style="font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;text-align:center;line-height:125%;writing-mode:lr-tb;text-anchor:middle;fill:#000000;font-family:Interstate-Bold"
+ id="text2451"
+ xml:space="preserve"><tspan
+ x="427.51163"
+ y="160.83585"
+ style="fill:#000000"
+ id="tspan2453">gateway1</tspan></text>
+</svg>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-basic.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-basic.png
new file mode 100644
index 0000000..8efc8f9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-basic.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-create-share.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-create-share.png
new file mode 100644
index 0000000..7dee83e
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-create-share.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-security.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-security.png
new file mode 100644
index 0000000..a219bc7
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-security.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-users.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-users.png
new file mode 100644
index 0000000..e9a1747
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba-users.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba.png
new file mode 100644
index 0000000..df9e9a3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/s-c-samba.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/samba-nautilus-machines.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/samba-nautilus-machines.png
new file mode 100644
index 0000000..cdf3062
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/samba-nautilus-machines.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/samba-nautilus.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/samba-nautilus.png
new file mode 100644
index 0000000..f97da4f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/samba-nautilus.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-Edit-filter.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-Edit-filter.png
new file mode 100644
index 0000000..f1260e3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-Edit-filter.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-Query-policy.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-Query-policy.png
new file mode 100644
index 0000000..fed4f51
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-Query-policy.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-Select-target-type-filtering.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-Select-target-type-filtering.png
new file mode 100644
index 0000000..58f2737
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-Select-target-type-filtering.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-View-filtering.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-View-filtering.png
new file mode 100644
index 0000000..492c483
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-View-filtering.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-plain.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-plain.png
new file mode 100644
index 0000000..4b21882
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/seaudit-plain.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/sec-ipsec-host2host.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/sec-ipsec-host2host.png
new file mode 100644
index 0000000..2661e1f
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/sec-ipsec-host2host.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/security-intro-to-mls.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/security-intro-to-mls.png
new file mode 100644
index 0000000..2e0fa95
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/security-intro-to-mls.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/security-mls-data-flow.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/security-mls-data-flow.png
new file mode 100644
index 0000000..a2ecd24
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/security-mls-data-flow.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/serialport.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/serialport.png
new file mode 100644
index 0000000..a283eae
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/serialport.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/serv-config.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/serv-config.png
new file mode 100644
index 0000000..f0ca0b3
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/serv-config.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-passphrase-prompt.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-passphrase-prompt.png
new file mode 100644
index 0000000..420a5b1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-passphrase-prompt.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-startup-applications-add.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-startup-applications-add.png
new file mode 100644
index 0000000..0e8ccde
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-startup-applications-add.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-startup-applications-check.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-startup-applications-check.png
new file mode 100644
index 0000000..bd8e824
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-startup-applications-check.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-startup-applications.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-startup-applications.png
new file mode 100644
index 0000000..27dedc7
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/ssh-startup-applications.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/switchmail-gui.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/switchmail-gui.png
new file mode 100644
index 0000000..09688a1
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/switchmail-gui.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/system-config-nfs.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/system-config-nfs.png
new file mode 100644
index 0000000..b5f1979
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/system-config-nfs.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/tcp_wrap_diagram.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/tcp_wrap_diagram.png
new file mode 100644
index 0000000..38ee5ea
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/tcp_wrap_diagram.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/usbport.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/usbport.png
new file mode 100644
index 0000000..d2e5525
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/usbport.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user-new.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user-new.png
new file mode 100644
index 0000000..29bef28
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user-new.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user-properties.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user-properties.png
new file mode 100644
index 0000000..97179d9
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user-properties.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user_pass_groups.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user_pass_groups.png
new file mode 100644
index 0000000..2d50e83
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user_pass_groups.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user_pass_info.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user_pass_info.png
new file mode 100644
index 0000000..5eaedfe
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/user_pass_info.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/images/your-rhn.png b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/your-rhn.png
new file mode 100644
index 0000000..31a03ed
Binary files /dev/null and b/public_html/en-US/Fedora/14/html/Deployment_Guide/images/your-rhn.png differ
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/index.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/index.html
new file mode 100644
index 0000000..f4a02eb
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/index.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Deployment Guide</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><meta name="description" content="The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14." /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="next" href="pr01.html" title="Preface" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pr01.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="book" title="Deployment Guide" id="id633908" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-al
ign="center"><span class="productname">Fedora</span> <span class="productnumber">14</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="id633908" class="title">Deployment Guide</h1></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h2 class="subtitle">Deployment, configuration and administration of Fedora 14</h2></div><p class="edition">Edition 1.0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ <span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
+
+ </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="en-US" class="authorgroup" lang="en-US"><div class="author"><h3 class="author"><span class="firstname">Douglas</span> <span class="surname">Silas</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:dhensley at redhat.com">dhensley at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Martin</span> <span class="surname">Prpič</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mprpic at redhat.com">mprpic at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Florian</span> <span class="surname">Nadge</span>
</h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:fnadge at redhat.com">fnadge at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Jaromír</span> <span class="surname">Hradílek</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:jhradile at redhat.com">jhradile at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="surname">Ha</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">David</span> <span class="surname">O'Brien</span></h3><div class="affiliation"><sp
an class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Michael</span> <span class="surname">Hideo</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div></div><div class="author"><h3 class="author"><span class="firstname">Don</span> <span class="surname">Domingo</span></h3><div class="affiliation"><span class="orgname">Red Hat, Inc.</span> <span class="orgdiv">Engineering Content Services</span></div></div></div></div><hr /><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="id834536" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2010 Red Hat, Inc. and others.
+ </div><div class="para">
+ The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
+ </div><div class="para">
+ Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
+ </div><div class="para">
+ Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
+ </div><div class="para">
+ For guidelines on the permitted uses of the Fedora trademarks, refer to <a href="https://fedoraproject.org/wiki/Legal:Trademark_guidelines">https://fedoraproject.org/wiki/Legal:Trademark_guidelines</a>.
+ </div><div class="para">
+ <span class="trademark">Linux</span>® is the registered trademark of Linus Torvalds in the United States and other countries.
+ </div><div class="para">
+ <span class="trademark">Java</span>® is a registered trademark of Oracle and/or its affiliates.
+ </div><div class="para">
+ <span class="trademark">XFS</span>® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
+ </div><div class="para">
+ <span class="trademark">MySQL</span>® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
+ </div><div class="para">
+ All other trademarks are the property of their respective owners.
+ </div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract" title="Abstract"><h6>Abstract</h6><div class="para">
+ The <em class="citetitle">Deployment Guide</em> documents relevant information regarding the deployment, configuration and administration of Fedora 14.
+ </div></div></div></div><hr /></div><div class="toc"><dl><dt><span class="preface"><a href="pr01.html">Preface</a></span></dt><dd><dl><dt><span class="section"><a href="pr01.html#id698112">1. Document Conventions</a></span></dt><dt><span class="section"><a href="sect-RedHat-We_Need_Feedback.html">2. We Need Feedback!</a></span></dt><dt><span class="section"><a href="Acknowledgements.html">3. Acknowledgements</a></span></dt></dl></dd><dt><span class="preface"><a href="ch-intro.html">Introduction</a></span></dt><dt><span class="part"><a href="pt-pkg-management.html">I. Package Management</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-yum.html">1. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages">1.1. Checking For and Updating Packages</a></span></dt><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">1.2. Packages and Package Groups</a></span></dt><dt><span class="section"><a h
ref="sec-Configuring_Yum_and_Yum_Repositories.html">1.3. Configuring Yum and Yum Repositories</a></span></dt><dt><span class="section"><a href="sec-Yum_Plugins.html">1.4. Yum Plugins</a></span></dt><dt><span class="section"><a href="sec-Additional_Resources.html">1.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-PackageKit.html">2. PackageKit</a></span></dt><dd><dl><dt><span class="section"><a href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">2.1. Updating Packages with Software Update</a></span></dt><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html">2.2. Using Add/Remove Software</a></span></dt><dt><span class="section"><a href="sec-PackageKit_Architecture.html">2.3. PackageKit Architecture</a></span></dt><dt><span class="section"><a href="ch-Graphical_Package_Management-sec-Additional_Resources.html">2.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-RPM.html
">3. RPM</a></span></dt><dd><dl><dt><span class="section"><a href="ch-RPM.html#s1-rpm-design">3.1. RPM Design Goals</a></span></dt><dt><span class="section"><a href="s1-rpm-using.html">3.2. Using RPM</a></span></dt><dt><span class="section"><a href="s1-check-rpm-sig.html">3.3. Checking a Package's Signature</a></span></dt><dt><span class="section"><a href="s1-rpm-impressing.html">3.4. Practical and Common Examples of RPM Usage</a></span></dt><dt><span class="section"><a href="s1-rpm-additional-resources.html">3.5. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt-network-related-config.html">II. Network-Related Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Network_Interfaces.html">4. Network Interfaces</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Network_Interfaces.html#s1-networkscripts-files">4.1. Network Configuration Files</a></span></dt><dt><span class="section"><a href="s1-networkscri
pts-interfaces.html">4.2. Interface Configuration Files</a></span></dt><dt><span class="section"><a href="s1-networkscripts-control.html">4.3. Interface Control Scripts</a></span></dt><dt><span class="section"><a href="s1-networkscripts-static-routes.html">4.4. Configuring Static Routes</a></span></dt><dt><span class="section"><a href="s1-networkscripts-functions.html">4.5. Network Function Files</a></span></dt><dt><span class="section"><a href="s1-networkscripts-resources.html">4.6. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Network_Configuration.html">5. Network Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Network_Configuration.html#sec-The_NetworkManager_Daemon">5.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html">5.2. Interacting with NetworkManager</a></span></dt><dt><span class="section"><a href="sec-Configuring_Connection_Setting
s.html">5.3. Configuring Connection Settings</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html">6. Dynamic Host Configuration Protocol (DHCP)</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html#s1-dhcp-why">6.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-server.html">6.2. Configuring a DHCP Server</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-client.html">6.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="sect-Configuring_a_Multihomed_DHCP_Server.html">6.4. Configuring a Multihomed DHCP Server</a></span></dt><dt><span class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">6.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="s1-dhcp-additional-resources.html">6.6. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch
-Controlling_Access_to_Services.html">7. Controlling Access to Services</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Controlling_Access_to_Services.html#s1-services-runlevels">7.1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="s1-services-configuring.html">7.2. Configuring the Services</a></span></dt><dt><span class="section"><a href="s1-services-running.html">7.3. Running the Services</a></span></dt><dt><span class="section"><a href="s1-services-additional-resources.html">7.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Authentication_Configuration.html">8. Authentication Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool">8.1. The Authentication Configuration Tool</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html">8.2. The System Security Servi
ces Daemon (SSSD)</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-OpenSSH.html">9. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">9.1. The SSH Protocol</a></span></dt><dt><span class="section"><a href="s1-ssh-configuration.html">9.2. An OpenSSH Configuration</a></span></dt><dt><span class="section"><a href="s1-ssh-clients.html">9.3. OpenSSH Clients</a></span></dt><dt><span class="section"><a href="s1-ssh-beyondshell.html">9.4. More Than a Secure Shell</a></span></dt><dt><span class="section"><a href="s1-openssh-additional-resources.html">9.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-The_BIND_DNS_Server.html">10. The BIND DNS Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s1-bind-introduction">10.1. Introduction to DNS</a></span></dt><dt><span class="section"><a href="s1-bind-namedconf.html">10.2. Configuring the <code cla
ss="command">named</code> Service</a></span></dt><dt><span class="section"><a href="s1-bind-zone.html">10.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="s1-bind-rndc.html">10.4. Using the <code class="command">rndc</code> Utility</a></span></dt><dt><span class="section"><a href="s1-bind-dig.html">10.5. Using the <code class="command">dig</code> Utility</a></span></dt><dt><span class="section"><a href="s1-bind-features.html">10.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="s1-bind-mistakes.html">10.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a href="s1-bind-additional-resources.html">10.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-The_Apache_HTTP_Server.html">11. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_Apache_HTTP_Server.html#s1-apache-version2">11.1. The Apache HTTP Server 2.2</a></span></dt><dt><span cl
ass="section"><a href="s1-apache-running.html">11.2. Running the <code class="systemitem">httpd</code> Service</a></span></dt><dt><span class="section"><a href="s1-apache-editing.html">11.3. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="s1-apache-dso.html">11.4. Working with Modules</a></span></dt><dt><span class="section"><a href="s1-apache-virtualhosts.html">11.5. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="s1-apache-mod_ssl.html">11.6. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="s1-apache-resources.html">11.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-email.html">12. Email</a></span></dt><dd><dl><dt><span class="section"><a href="ch-email.html#s1-email-protocols">12.1. Email Protocols</a></span></dt><dt><span class="section"><a href="s1-email-types.html">12.2. Email Program Classifications</a></span></dt><dt><span class="section"><a h
ref="s1-email-mta.html">12.3. Mail Transport Agents</a></span></dt><dt><span class="section"><a href="s1-email-mda.html">12.4. Mail Delivery Agents</a></span></dt><dt><span class="section"><a href="s1-email-mua.html">12.5. Mail User Agents</a></span></dt><dt><span class="section"><a href="s1-email-additional-resources.html">12.6. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt-sysconfig.html">III. System Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="chap-Date_and_Time_Configuration.html">13. Date and Time Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool">13.1. Date/Time Properties Tool</a></span></dt><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html">13.2. Command Line Configuration</a></span></dt></dl></dd><dt><span class="chapter"><a
href="ch-Keyboard_Configuration.html">14. Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Keyboard_Configuration.html#s1-keyboard-layout">14.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="s1-keyboard-indicator.html">14.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="s1-keyboard-break.html">14.3. Setting Up a Typing Break</a></span></dt></dl></dd><dt><span class="chapter"><a href="Users_and_Groups.html">15. Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="Users_and_Groups.html#s1-users-configui">15.1. User and Group Configuration</a></span></dt><dt><span class="section"><a href="s1-users-tools.html">15.2. User and Group Management Tools</a></span></dt><dt><span class="section"><a href="s1-users-groups-standard-users.html">15.3. Standard Users</a></span></dt><dt><span class="section"><a href="s1-users-groups-standard-groups.html">15.4. Stan
dard Groups</a></span></dt><dt><span class="section"><a href="s1-users-groups-private-groups.html">15.5. User Private Groups</a></span></dt><dt><span class="section"><a href="s1-users-groups-shadow-utilities.html">15.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="s1-users-groups-additional-resources.html">15.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Automated_Tasks.html">16. Automated Tasks</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Automated_Tasks.html#s1-autotasks-cron-anacron">16.1. Cron and Anacron</a></span></dt><dt><span class="section"><a href="s1-autotasks-at-batch.html">16.2. At and Batch</a></span></dt><dt><span class="section"><a href="s1-autotasks-additional-resources.html">16.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Log_Files.html">17. Log Files</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Log_Files.html#s1-configuri
ng-rsyslog">17.1. Configuring <code class="command">rsyslog</code> </a></span></dt><dt><span class="section"><a href="s1-rsyslog-performance.html">17.2. <code class="command">rsyslog</code> Performance</a></span></dt><dt><span class="section"><a href="s1-logfiles-locating.html">17.3. Locating Log Files</a></span></dt><dt><span class="section"><a href="s1-logfiles-viewing.html">17.4. Viewing Log Files</a></span></dt><dt><span class="section"><a href="s1-logfiles-adding.html">17.5. Adding a Log File</a></span></dt><dt><span class="section"><a href="s1-logfiles-examining.html">17.6. Monitoring Log Files</a></span></dt><dt><span class="section"><a href="s1-log-files-additional-resources.html">17.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-The_sysconfig_Directory.html">18. The sysconfig Directory</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s1-sysconfig-files">18.1. Files in the <code class="f
ilename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="s1-sysconfig-etcsysconf-dir.html">18.2. Directories in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="s1-sysconfig-additional-resources.html">18.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-proc.html">19. The <code class="filename">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-proc.html#s1-proc-virtual">19.1. A Virtual File System</a></span></dt><dt><span class="section"><a href="s1-proc-topfiles.html">19.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dt><span class="section"><a href="s1-proc-directories.html">19.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dt><span class="section"><a href="s1-proc-sysctl.html">19.4. Using the <code class="command">sysctl</code> Comma
nd</a></span></dt><dt><span class="section"><a href="s1-proc-additional-resources.html">19.5. References</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt-system-monitoring.html">IV. System Monitoring</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Gathering_System_Information.html">20. Gathering System Information</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">20.1. System Processes</a></span></dt><dt><span class="section"><a href="s1-sysinfo-memory-usage.html">20.2. Memory Usage</a></span></dt><dt><span class="section"><a href="s1-sysinfo-filesystems.html">20.3. File Systems</a></span></dt><dt><span class="section"><a href="s1-sysinfo-hardware.html">20.4. Hardware</a></span></dt><dt><span class="section"><a href="s1-sysinfo-additional-resources.html">20.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-abrt.html">21. ABRT</a></s
pan></dt><dd><dl><dt><span class="section"><a href="ch-abrt.html#id544620">21.1. Overview</a></span></dt><dt><span class="section"><a href="ch21s02.html">21.2. Installing and Running ABRT</a></span></dt><dt><span class="section"><a href="abrt-plugins.html">21.3. <span class="application"><strong>ABRT</strong></span> Plugins</a></span></dt><dt><span class="section"><a href="generating-backtrace.html">21.4. Generating Backtraces</a></span></dt><dt><span class="section"><a href="ch21s05.html">21.5. Using the Command Line Interface</a></span></dt><dt><span class="section"><a href="configuring.html">21.6. Configuring ABRT</a></span></dt><dt><span class="section"><a href="configuring-centralized-crash-collection.html">21.7. Configuring Centralized Crash Collection</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="pt-kernel-configuration.html">V. Kernel, Module and Driver Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Working_with_Kerne
l_Modules.html">22. Working with Kernel Modules</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="sec-Displaying_Information_About_a_Module.html">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="sec-Loading_a_Module.html">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="sec-Unloading_a_Module.html">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="sec-Setting_Module_Parameters.html">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="sec-Persistent_Module_Loading.html">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="sec-Specific_Kernel_Module_Capabilities.html">22.7. Specific Kernel Module Capabilities</a></span></dt><dt><span class="section"><a href="
s1-kernel-modules-additional-resources.html">22.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Manually_Upgrading_the_Kernel.html">23. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">23.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">23.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">23.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">23.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">23.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">23.6. Verifying the Boot Loader</a></span></dt></dl></dd><dt><span class="chapter"><a hre
f="ch-kdump.html">24. The <code class="systemitem">kdump</code> Crash Recovery Service</a></span></dt><dd><dl><dt><span class="section"><a href="ch-kdump.html#s1-kdump-configuration">24.1. Configuring the <code class="systemitem">kdump</code> Service</a></span></dt><dt><span class="section"><a href="s1-kdump-crash.html">24.2. Analyzing the Core Dump</a></span></dt><dt><span class="section"><a href="s1-kdump-resources.html">24.3. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="app-Revision_History.html">A. Revision History</a></span></dt><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div></div><ul class="docnav"><li class="previous"></li><li class="next"><a accesskey="n" href="pr01.html"><strong>Next</strong>Preface</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/ix01.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/ix01.html
new file mode 100644
index 0000000..a4f8fe4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/ix01.html
@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Index</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="app-Revision_History.html" title="Appendix A. Revision History" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="app-Revision_History.html"><strong>Prev</strong></a></li><li class="next"></li></ul><div class="index" title="Index" id="id853503"><div class="titlepage"><div><div><h2 class="title">Index</h2></div>
</div></div><div class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt> .fetchmailrc , <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration">Fetchmail Configuration Options</a></dt><dd><dl><dt>server options, <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-server">Server Options</a></dt><dt>user options, <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-fetchmail-configuration-user">User Options</a></dt></dl></dd><dt>.htaccess, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dd><dl><dt>(see also Apache HTTP Server)</dt></dl></dd><dt>.htpasswd, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dd><dl><dt>(see also Apache HTTP Server)</dt></dl></dd><dt> .procmailrc , <a class="indexterm" href="s1-email-mda.html#s2-email-procmail-configu
ration">Procmail Configuration</a></dt><dt> /dev/shm , <a class="indexterm" href="s1-sysinfo-filesystems.html">File Systems</a></dt><dt>/etc/named.conf (see BIND)</dt><dt> /etc/sysconfig/ directory (see sysconfig directory)</dt><dt> /etc/sysconfig/dhcpd , <a class="indexterm" href="ch06s02s03.html">Starting and Stopping the Server</a></dt><dt> /proc/ directory, <a class="indexterm" href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">Installed Documentation</a> (see proc file system)</dt><dt> /var/spool/anacron , <a class="indexterm" href="ch-Automated_Tasks.html#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt><dt> /var/spool/cron , <a class="indexterm" href="ch-Automated_Tasks.html#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>Access Control</dt><dd><dl><dt>configuring in SSSD, <a class="indexterm" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#id587380">Configuring Access Control
</a></dt><dt>in SSSD, rules, <a class="indexterm" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html#id699848">The Simple Access Provider</a></dt></dl></dd><dt>adding</dt><dd><dl><dt>group, <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt><dt>user, <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>anacron, <a class="indexterm" href="ch-Automated_Tasks.html#s1-autotasks-cron-anacron">Cron and Anacron</a></dt><dd><dl><dt>anacron configuration file, <a class="indexterm" href="ch-Automated_Tasks.html#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt><dt>user-defined tasks, <a class="indexterm" href="ch-Automated_Tasks.html#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt></dl></dd><dt> anacrontab , <a class="indexterm" href="ch-Automated_Tasks.html#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt><dt>Apache HTTP Server</dt><dd><d
l><dt>additional resources</dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-apache-resources.html#s2-apache-resources-installed">Installed Documentation</a></dt><dt>useful websites, <a class="indexterm" href="s2-apache-resources-web.html">Useful Websites</a></dt></dl></dd><dt>checking configuration, <a class="indexterm" href="s1-apache-editing.html">Editing the Configuration Files</a></dt><dt>checking status, <a class="indexterm" href="s3-apache-running-status.html">Checking the Service Status</a></dt><dt>directives</dt><dd><dl><dt><Directory>, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt><IfDefine>, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt><IfModule>, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt><L
ocation>, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt><Proxy>, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt><VirtualHost>, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AccessFileName, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Action, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddDescription, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddEncoding, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddHandler, <a class="inde
xterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddIcon, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddIconByEncoding, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddIconByType, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddLanguage, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>AddType, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Alias, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Allow, <a class="indexterm" href="s1-apache-editing.html#s2-apache-htt
pdconf-directives">Common httpd.conf Directives</a></dt><dt>AllowOverride, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>BrowserMatch, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheDefaultExpire, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheDisable, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheEnable, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheLastModifiedFactor, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheMaxExpire, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-dire
ctives">Common httpd.conf Directives</a></dt><dt>CacheNegotiatedDocs, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CacheRoot, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>CustomLog, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>DefaultIcon, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>DefaultType, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Deny, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>DirectoryIndex, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives<
/a></dt><dt>DocumentRoot, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ErrorDocument, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ErrorLog, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ExtendedStatus, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Group, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>HeaderName, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>HostnameLookups, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Include, <a class="indext
erm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>IndexIgnore, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>IndexOptions, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>KeepAlive, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>KeepAliveTimeout, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>LanguagePriority, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Listen, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>LoadModule, <a class="indexterm" href="s1-apache-editing.html#
s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>LogFormat, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>LogLevel, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>MaxClients, <a class="indexterm" href="s2-apache-mpm-common.html">Common Multi-Processing Module Directives</a></dt><dt>MaxKeepAliveRequests, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>MaxSpareServers, <a class="indexterm" href="s2-apache-mpm-common.html">Common Multi-Processing Module Directives</a></dt><dt>MaxSpareThreads, <a class="indexterm" href="s2-apache-mpm-common.html">Common Multi-Processing Module Directives</a></dt><dt>MinSpareServers, <a class="indexterm" href="s2-apache-mpm-common.html">Common Multi-Processing Module Directives</a></dt><dt>MinSpareT
hreads, <a class="indexterm" href="s2-apache-mpm-common.html">Common Multi-Processing Module Directives</a></dt><dt>NameVirtualHost, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Options, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Order, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>PidFile, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ProxyRequests, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ReadmeName, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Redirect, <a class="indexterm" href="s1-apache-editing.html#s2-apa
che-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ScriptAlias, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ServerAdmin, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ServerName, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ServerRoot, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ServerSignature, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ServerTokens, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>SetEnvIf, <a class="indexterm" href="s2-apache-sslconf-common.html">Common ssl.conf Directives</a></dt>
<dt>StartServers, <a class="indexterm" href="s2-apache-mpm-common.html">Common Multi-Processing Module Directives</a></dt><dt>SuexecUserGroup, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>ThreadsPerChild, <a class="indexterm" href="s2-apache-mpm-common.html">Common Multi-Processing Module Directives</a></dt><dt>Timeout, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>TypesConfig, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>UseCanonicalName, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>User, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>UserDir, <a class="indexterm" href="s1-apache-editing.html#s
2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/httpd/, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/etc/httpd/conf.d/, <a class="indexterm" href="s1-apache-editing.html">Editing the Configuration Files</a>, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/usr/lib/httpd/modules/, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a>, <a class="indexterm" href="s1-apache-dso.html">Working with Modules</a></dt><dt>/usr/lib64/httpd/modules/, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a>, <a class="indexterm" href="s1-apache-dso.html">Working with Modules</a></dt><dt>/var/cache/mod_proxy/, <a class="indexterm" href="s1-apache-editing.
html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/var/www/cgi-bin/, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/var/www/html/, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/var/www/icons/, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>~/public_html/, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt></dl></dd><dt>files</dt><dd><dl><dt>.htaccess, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>.htpasswd, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/etc/httpd/conf.d/ssl.conf, <a class="indexterm" hr
ef="s2-apache-sslconf-common.html">Common ssl.conf Directives</a>, <a class="indexterm" href="s2-apache-mod_ssl-enabling.html">Enabling the mod_ssl Module</a></dt><dt>/etc/httpd/conf/httpd.conf, <a class="indexterm" href="s1-apache-editing.html">Editing the Configuration Files</a>, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a>, <a class="indexterm" href="s2-apache-mpm-common.html">Common Multi-Processing Module Directives</a></dt><dt>/etc/httpd/logs/access_log, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/etc/httpd/logs/error_log, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/etc/httpd/run/httpd.pid, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/etc/mime.types, <a class="index
term" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt></dl></dd><dt>modules</dt><dd><dl><dt>developing, <a class="indexterm" href="s2-apache-dso-writing.html">Writing a Module</a></dt><dt>loading, <a class="indexterm" href="s1-apache-dso.html#s2-apache-dso-loading">Loading a Module</a></dt><dt>mod_asis, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s2-apache-version2-changes">Notable Changes</a></dt><dt>mod_cache, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s2-apache-version2-features">New Features</a></dt><dt>mod_cern_meta, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s2-apache-version2-changes">Notable Changes</a></dt><dt>mod_disk_cache, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s2-apache-version2-features">New Features</a></dt><dt>mod_ext_filter, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s2-apache-version2-changes">Notable Changes</a></dt><dt>mod_proxy_
balancer, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s2-apache-version2-features">New Features</a></dt><dt>mod_rewrite, <a class="indexterm" href="s1-apache-editing.html#s2-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>mod_ssl, <a class="indexterm" href="s1-apache-mod_ssl.html">Setting Up an SSL Server</a></dt><dt>mod_userdir, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s1-apache-version2-migrating">Updating the Configuration</a></dt></dl></dd><dt>restarting, <a class="indexterm" href="s3-apache-running-restarting.html">Restarting the Service</a></dt><dt>SSL server</dt><dd><dl><dt>certificate, <a class="indexterm" href="s1-apache-mod_ssl.html#s2-apache-mod_ssl-certificates">An Overview of Certificates and Security</a>, <a class="indexterm" href="s2-apache-mod_ssl-keypair.html">Using an Existing Key and Certificate</a>, <a class="indexterm" href="s2-apache-mod_ssl-genkey.html">Generating a New Key and Certificate</a></dt><d
t>certificate authority, <a class="indexterm" href="s1-apache-mod_ssl.html#s2-apache-mod_ssl-certificates">An Overview of Certificates and Security</a></dt><dt>private key, <a class="indexterm" href="s1-apache-mod_ssl.html#s2-apache-mod_ssl-certificates">An Overview of Certificates and Security</a>, <a class="indexterm" href="s2-apache-mod_ssl-keypair.html">Using an Existing Key and Certificate</a>, <a class="indexterm" href="s2-apache-mod_ssl-genkey.html">Generating a New Key and Certificate</a></dt><dt>public key, <a class="indexterm" href="s1-apache-mod_ssl.html#s2-apache-mod_ssl-certificates">An Overview of Certificates and Security</a></dt></dl></dd><dt>starting, <a class="indexterm" href="s1-apache-running.html#s2-apache-running-starting">Starting the Service</a></dt><dt>stopping, <a class="indexterm" href="s2-apache-running-stopping.html">Stopping the Service</a></dt><dt>version 2.2</dt><dd><dl><dt>changes, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s2-
apache-version2-changes">Notable Changes</a></dt><dt>features, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s2-apache-version2-features">New Features</a></dt><dt>updating from version 2.0, <a class="indexterm" href="ch-The_Apache_HTTP_Server.html#s1-apache-version2-migrating">Updating the Configuration</a></dt></dl></dd><dt>virtual host, <a class="indexterm" href="s1-apache-virtualhosts.html">Setting Up Virtual Hosts</a></dt></dl></dd><dt> at , <a class="indexterm" href="s1-autotasks-at-batch.html">At and Batch</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-autotasks-additional-resources.html">Additional Resources</a></dt></dl></dd><dt> authconfig (see Authentication Configuration Tool )</dt><dd><dl><dt> commands , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Command_Line_Version">Command Line Version</a></dt></dl></dd><dt>authentication</dt><dd><dl><dt> Authentication Confi
guration Tool , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool">The Authentication Configuration Tool</a></dt><dt> using fingerprint support , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">Advanced Options</a></dt><dt> using smart card authentication , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Advanced_Options">Advanced Options</a></dt></dl></dd><dt> Authentication Configuration Tool </dt><dd><dl><dt> and Kerberos authentication , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt><dt> and LDAP , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentic
ation</a></dt><dt> and NIS , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt><dt> and NIS authentication , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt><dt> and Winbind , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt><dt> and Winbind authentication , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool-Identity_and_Authentication">Identity & Authentication</a></dt></dl></dd><dt>authoritative nameserver (see BIND)</dt><dt>Automated Tasks, <a class="indexterm" href="ch-Automated_Tasks.html">Automated Tasks</a></dt></dl></div><div class="indexdi
v"><h3>B</h3><dl><dt> batch , <a class="indexterm" href="s1-autotasks-at-batch.html">At and Batch</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-autotasks-additional-resources.html">Additional Resources</a></dt></dl></dd><dt>Berkeley Internet Name Domain (see BIND)</dt><dt>BIND</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-bind-additional-resources.html#s2-bind-installed-docs">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="s2-bind-related-books.html">Related Books</a></dt><dt>useful websites, <a class="indexterm" href="s2-bind-useful-websites.html">Useful Websites</a></dt></dl></dd><dt>common mistakes, <a class="indexterm" href="s1-bind-mistakes.html">Common Mistakes to Avoid</a></dt><dt>configuration</dt><dd><dl><dt>acl statement, <a class="indexterm" href="s1-bind-namedconf.html#s2-bind-namedconf-state">Common Statement Types</a></dt><dt>comment tags, <a cl
ass="indexterm" href="s2-bind-namedconf-comm.html">Comment Tags</a></dt><dt>controls statement, <a class="indexterm" href="s2-bind-namedconf-state-other.html">Other Statement Types</a></dt><dt>include statement, <a class="indexterm" href="s1-bind-namedconf.html#s2-bind-namedconf-state">Common Statement Types</a></dt><dt>key statement, <a class="indexterm" href="s2-bind-namedconf-state-other.html">Other Statement Types</a></dt><dt>logging statement, <a class="indexterm" href="s2-bind-namedconf-state-other.html">Other Statement Types</a></dt><dt>options statement, <a class="indexterm" href="s1-bind-namedconf.html#s2-bind-namedconf-state">Common Statement Types</a></dt><dt>server statement, <a class="indexterm" href="s2-bind-namedconf-state-other.html">Other Statement Types</a></dt><dt>trusted-keys statement, <a class="indexterm" href="s2-bind-namedconf-state-other.html">Other Statement Types</a></dt><dt>view statement, <a class="indexterm" href="s2-bind-namedconf-state-other.h
tml">Other Statement Types</a></dt><dt>zone statement, <a class="indexterm" href="s1-bind-namedconf.html#s2-bind-namedconf-state">Common Statement Types</a></dt></dl></dd><dt>directories</dt><dd><dl><dt>/etc/named/, <a class="indexterm" href="s1-bind-namedconf.html">Configuring the named Service</a></dt><dt>/var/named/, <a class="indexterm" href="s1-bind-zone.html">Editing Zone Files</a></dt><dt>/var/named/data/, <a class="indexterm" href="s1-bind-zone.html">Editing Zone Files</a></dt><dt>/var/named/dynamic/, <a class="indexterm" href="s1-bind-zone.html">Editing Zone Files</a></dt><dt>/var/named/slaves/, <a class="indexterm" href="s1-bind-zone.html">Editing Zone Files</a></dt></dl></dd><dt>features</dt><dd><dl><dt>Automatic Zone Transfer (AXFR), <a class="indexterm" href="s2-bind-features-ixfr.html">Incremental Zone Transfers (IXFR)</a></dt><dt>DNS Security Extensions (DNSSEC), <a class="indexterm" href="s2-bind-features-dnssec.html">DNS Security Extensions (DNSSEC)</a></dt>
<dt>Incremental Zone Transfer (IXFR), <a class="indexterm" href="s2-bind-features-ixfr.html">Incremental Zone Transfers (IXFR)</a></dt><dt>Internet Protocol version 6 (IPv6), <a class="indexterm" href="s2-bind-features-ipv6.html">Internet Protocol version 6 (IPv6)</a></dt><dt>multiple views, <a class="indexterm" href="s1-bind-features.html#s2-bind-features-views">Multiple Views</a></dt><dt>Transaction SIGnature (TSIG), <a class="indexterm" href="s2-bind-features-tsig.html">Transaction SIGnatures (TSIG)</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/etc/named.conf, <a class="indexterm" href="s1-bind-namedconf.html">Configuring the named Service</a>, <a class="indexterm" href="s1-bind-rndc.html#s2-bind-rndc-configuration">Configuring the Utility</a></dt><dt>/etc/rndc.conf, <a class="indexterm" href="s1-bind-rndc.html#s2-bind-rndc-configuration">Configuring the Utility</a></dt><dt>/etc/rndc.key, <a class="indexterm" href="s1-bind-rndc.html#s2-bind-rndc-configuration">Configuring
the Utility</a></dt></dl></dd><dt>resource record, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-zones">Nameserver Zones</a></dt><dt>types</dt><dd><dl><dt>authoritative nameserver, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">Nameserver Types</a></dt><dt>primary (master) nameserver, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-zones">Nameserver Zones</a>, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">Nameserver Types</a></dt><dt>recursive nameserver, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">Nameserver Types</a></dt><dt>secondary (slave) nameserver, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-zones">Nameserver Zones</a>, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-nameservers">Nameserver Types</a></dt></dl></dd><dt>utili
ties</dt><dd><dl><dt>dig, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="s1-bind-dig.html">Using the dig Utility</a>, <a class="indexterm" href="s2-bind-features-dnssec.html">DNS Security Extensions (DNSSEC)</a></dt><dt>named, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="s1-bind-namedconf.html">Configuring the named Service</a></dt><dt>rndc, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-bind">BIND as a Nameserver</a>, <a class="indexterm" href="s1-bind-rndc.html">Using the rndc Utility</a></dt></dl></dd><dt>zones</dt><dd><dl><dt>$INCLUDE directive, <a class="indexterm" href="s1-bind-zone.html#s2-bind-zone-directives">Common Directives</a></dt><dt>$ORIGIN directive, <a class="indexterm" href="s1-bind-zone.html#s2-bind-zone-directives">Common Directives</a></dt><dt>$TTL di
rective, <a class="indexterm" href="s1-bind-zone.html#s2-bind-zone-directives">Common Directives</a></dt><dt>A (Address) resource record, <a class="indexterm" href="s3-bind-zone-rr.html">Common Resource Records</a></dt><dt>CNAME (Canonical Name) resource record, <a class="indexterm" href="s3-bind-zone-rr.html">Common Resource Records</a></dt><dt>comment tags, <a class="indexterm" href="s2-bind-zone-comm.html">Comment Tags</a></dt><dt>description, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-zones">Nameserver Zones</a></dt><dt>example usage, <a class="indexterm" href="s2-bind-zone-examples.html#s3-bind-zone-examples-basic">A Simple Zone File</a>, <a class="indexterm" href="s2-bind-zone-examples.html#s2-bind-configuration-zone-reverse">A Reverse Name Resolution Zone File</a></dt><dt>MX (Mail Exchange) resource record, <a class="indexterm" href="s3-bind-zone-rr.html">Common Resource Records</a></dt><dt>NS (Nameserver) resource record, <a class="in
dexterm" href="s3-bind-zone-rr.html">Common Resource Records</a></dt><dt>PTR (Pointer) resource record, <a class="indexterm" href="s3-bind-zone-rr.html">Common Resource Records</a></dt><dt>SOA (Start of Authority) resource record, <a class="indexterm" href="s3-bind-zone-rr.html">Common Resource Records</a></dt></dl></dd></dl></dd><dt>block devices, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt><dd><dl><dt>(see also /proc/devices )</dt><dt>definition of, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt></dl></dd><dt>bonding (see channel bonding)</dt><dt>boot loader</dt><dd><dl><dt>verifying, <a class="indexterm" href="s1-kernel-boot-loader.html">Verifying the Boot Loader</a></dt></dl></dd><dt>boot media, <a class="indexterm" href="s1-kernel-preparing.html">Preparing to Upgrade</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt>ch-email .fetchmailrc </dt><dd><dl><dt>global options, <a class="indexterm" href="s2-email-
mta-fetchmail.html#s3-email-mda-fetchmail-configuration-global">Global Options</a></dt></dl></dd><dt> chage command</dt><dd><dl><dt>forcing password expiration with, <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>channel bonding</dt><dd><dl><dt>configuration, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt><dt>description, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt><dt>interface</dt><dd><dl><dt>configuration of, <a class="indexterm" href="s2-networkscripts-interfaces-chan.html">Channel Bonding Interfaces</a></dt></dl></dd><dt>parameters to bonded interfaces, <a class="indexterm" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>channel bonding interface (see kernel module)</dt><dt>character devices, <a class="indexterm" href="s2-proc-devices.html"> /proc/dev
ices </a></dt><dd><dl><dt>(see also /proc/devices )</dt><dt>definition of, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt></dl></dd><dt> chkconfig (see services configuration)</dt><dt>Configuration File Changes, <a class="indexterm" href="ch-yum.html#sec-Preserving_Configuration_File_Changes">Preserving Configuration File Changes</a></dt><dt>crash</dt><dd><dl><dt>analyzing the dump</dt><dd><dl><dt>message buffer, <a class="indexterm" href="s1-kdump-crash.html#s2-kdump-crash-log">Displaying the Message Buffer</a></dt><dt>open files, <a class="indexterm" href="s2-kdump-crash-files.html">Displaying Open Files</a></dt><dt>processes, <a class="indexterm" href="s2-kdump-crash-processes.html">Displaying a Process Status</a></dt><dt>stack trace, <a class="indexterm" href="s2-kdump-crash-backtrace.html">Displaying a Backtrace</a></dt><dt>virtual memory, <a class="indexterm" href="s2-kdump-crash-memory.html">Displaying Virtual Memory Information</a></dt></d
l></dd><dt>opening the dump image, <a class="indexterm" href="s1-kdump-crash.html">Analyzing the Core Dump</a></dt><dt>system requirements, <a class="indexterm" href="s1-kdump-crash.html">Analyzing the Core Dump</a></dt></dl></dd><dt>Cron, <a class="indexterm" href="ch-Automated_Tasks.html">Automated Tasks</a></dt><dt> cron , <a class="indexterm" href="ch-Automated_Tasks.html#s1-autotasks-cron-anacron">Cron and Anacron</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-autotasks-additional-resources.html">Additional Resources</a></dt><dt>cron configuration file, <a class="indexterm" href="ch-Automated_Tasks.html#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt><dt>user-defined tasks, <a class="indexterm" href="ch-Automated_Tasks.html#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></dd><dt> crontab , <a class="indexterm" href="ch-Automated_Tasks.html#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></div><div class="indexd
iv"><h3>D</h3><dl><dt> date (see date configuration)</dt><dt>date configuration</dt><dd><dl><dt> date , <a class="indexterm" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">Date and Time Setup</a></dt><dt> system-config-date , <a class="indexterm" href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">Date and Time Properties</a></dt></dl></dd><dt>deleting cache files</dt><dd><dl><dt>in SSSD, <a class="indexterm" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html#sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">Support for Multiple Domains</a></dt></dl></dd><dt>Denial of Service attack, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-net"> /proc/sys/net/ </a></dt><dd><dl><dt>(see also /proc/sys/net/ directory)</dt><dt>definition of, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-net"> /proc/s
ys/net/ </a></dt></dl></dd><dt> df , <a class="indexterm" href="s1-sysinfo-filesystems.html">File Systems</a></dt><dt>DHCP, <a class="indexterm" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html">Dynamic Host Configuration Protocol (DHCP)</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-dhcp-additional-resources.html">Additional Resources</a></dt><dt>client configuration, <a class="indexterm" href="s1-dhcp-configuring-client.html">Configuring a DHCP Client</a></dt><dt>command line options, <a class="indexterm" href="ch06s02s03.html">Starting and Stopping the Server</a></dt><dt>connecting to, <a class="indexterm" href="s1-dhcp-configuring-client.html">Configuring a DHCP Client</a></dt><dt>dhcpd.conf, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt> dhcpd.leases , <a class="indexterm" href="ch06s02s03.html">Starting and Stopping the Server</a></dt><dt>dhcpd6.conf, <a class="indexterm" href="s1-d
hcp_for_ipv6_dhcpv6.html">DHCP for IPv6 (DHCPv6)</a></dt><dt>DHCPv6, <a class="indexterm" href="s1-dhcp_for_ipv6_dhcpv6.html">DHCP for IPv6 (DHCPv6)</a></dt><dt> dhcrelay , <a class="indexterm" href="dhcp-relay-agent.html">DHCP Relay Agent</a></dt><dt>global parameters, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>group, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>options, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>reasons for using, <a class="indexterm" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html#s1-dhcp-why">Why Use DHCP?</a></dt><dt>Relay Agent, <a class="indexterm" href="dhcp-relay-agent.html">DHCP Relay Agent</a></dt><dt>server configuration, <a class="indexterm" href="s1-dhcp-configuring-server.html">Configuring a DHCP Server</a></dt><dt> shared-network , <a class="indexterm" href="s1
-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>starting the server, <a class="indexterm" href="ch06s02s03.html">Starting and Stopping the Server</a></dt><dt>stopping the server, <a class="indexterm" href="ch06s02s03.html">Starting and Stopping the Server</a></dt><dt>subnet, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">Configuration File</a></dt></dl></dd><dt>dhcpd.conf, <a class="indexterm" href="s1-dhcp-configuring-server.html#config-file">Configuration File</a></dt><dt>dhcpd.leases, <a class="indexterm" href="ch06s02s03.html">Starting and Stopping the Server</a></dt><dt> dhcrelay , <a class="indexterm" href="dhcp-relay-agent.html">DHCP Relay Agent</a></dt><dt>dig (see BIND)</dt><dt>DNS</dt><dd><dl><dt>definition, <a class="indexterm" href="ch-The_BIND_DNS_Server.html">The BIND DNS Server</a></dt><dd><dl><dt>(see also BIND)</dt></dl></dd></dl></dd><dt>documentation</dt><dd><dl><dt>finding installed, <a class="indexterm"
href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt></dl></dd><dt>DoS attack (see Denial of Service attack)</dt><dt>drivers (see kernel module)</dt><dt>DSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt> du , <a class="indexterm" href="s1-sysinfo-filesystems.html">File Systems</a></dt><dt>Dynamic Host Configuration Protocol (see DHCP)</dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>email</dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-email-additional-resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-email-additional-resources.html#s2-email-installed-docs">Installed Documentation</a></dt><dt>related books, <a class="indexterm" href="s2-email-related-books.html">Related Books</a></dt><dt>useful websites, <a class="indexterm" href
="s2-email-useful-websites.html">Useful Websites</a></dt></dl></dd><dt>Fetchmail, <a class="indexterm" href="s2-email-mta-fetchmail.html">Fetchmail</a></dt><dt>history of, <a class="indexterm" href="ch-email.html">Email</a></dt><dt>mail server</dt><dd><dl><dt>Dovecot, <a class="indexterm" href="ch-email.html#s3-mail-server-dovecot">Dovecot</a></dt></dl></dd><dt>Postfix, <a class="indexterm" href="s1-email-mta.html#s2-email-mta-postfix">Postfix</a></dt><dt>Procmail, <a class="indexterm" href="s1-email-mda.html">Mail Delivery Agents</a></dt><dt>program classifications, <a class="indexterm" href="s1-email-types.html">Email Program Classifications</a></dt><dt>protocols, <a class="indexterm" href="ch-email.html#s1-email-protocols">Email Protocols</a></dt><dd><dl><dt>IMAP, <a class="indexterm" href="ch-email.html#s3-email-protocols-imap">IMAP</a></dt><dt>POP, <a class="indexterm" href="ch-email.html#s3-email-protocols-pop">POP</a></dt><dt>SMTP, <a class="indexterm" href="ch-email.
html#s3-email-protocols-smtp">SMTP</a></dt></dl></dd><dt>security, <a class="indexterm" href="s1-email-mua.html#s2-email-security">Securing Communication</a></dt><dd><dl><dt>clients, <a class="indexterm" href="s1-email-mua.html#s3-email-security-clients">Secure Email Clients</a></dt><dt>servers, <a class="indexterm" href="s1-email-mua.html#s3-email-security-servers">Securing Email Client Communications</a></dt></dl></dd><dt>Sendmail, <a class="indexterm" href="s2-email-mta-sendmail.html">Sendmail</a></dt><dt>spam</dt><dd><dl><dt>filtering out, <a class="indexterm" href="s2-email-procmail-recipes.html#s3-email-mda-spam">Spam Filters</a></dt></dl></dd><dt>types</dt><dd><dl><dt>Mail Delivery Agent, <a class="indexterm" href="s2-email-types-mda.html">Mail Delivery Agent</a></dt><dt>Mail Transport Agent, <a class="indexterm" href="s1-email-types.html#s2-email-types-mta">Mail Transport Agent</a></dt><dt>Mail User Agent, <a class="indexterm" href="s2-email-types-mua.html">Mail User
Agent</a></dt></dl></dd></dl></dd><dt>epoch, <a class="indexterm" href="s2-proc-stat.html"> /proc/stat </a></dt><dd><dl><dt>(see also /proc/stat )</dt><dt>definition of, <a class="indexterm" href="s2-proc-stat.html"> /proc/stat </a></dt></dl></dd><dt>Ethernet (see network)</dt><dt> exec-shield </dt><dd><dl><dt>enabling, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt>introducing, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt></dl></dd><dt>execution domains, <a class="indexterm" href="s2-proc-execdomains.html"> /proc/execdomains </a></dt><dd><dl><dt>(see also /proc/execdomains )</dt><dt>definition of, <a class="indexterm" href="s2-proc-execdomains.html"> /proc/execdomains </a></dt></dl></dd><dt>expiration of password, forcing, <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl>
<dt>Fedora installation media</dt><dd><dl><dt>installable packages, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding RPM Packages</a></dt></dl></dd><dt>feedback</dt><dd><dl><dt>contact information for this manual, <a class="indexterm" href="sect-RedHat-We_Need_Feedback.html">We Need Feedback!</a></dt></dl></dd><dt>Fetchmail, <a class="indexterm" href="s2-email-mta-fetchmail.html">Fetchmail</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-email-additional-resources.html">Additional Resources</a></dt><dt>command options, <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-commands">Fetchmail Command Options</a></dt><dd><dl><dt>informational, <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-commands-info">Informational or Debugging Options</a></dt><dt>special, <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-commands-special">Special Options</a></dt></d
l></dd><dt>configuration options, <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration">Fetchmail Configuration Options</a></dt><dd><dl><dt>global options, <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-global">Global Options</a></dt><dt>server options, <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-mda-fetchmail-configuration-server">Server Options</a></dt><dt>user options, <a class="indexterm" href="s2-email-mta-fetchmail.html#s3-email-fetchmail-configuration-user">User Options</a></dt></dl></dd></dl></dd><dt>file system</dt><dd><dl><dt>virtual (see proc file system)</dt></dl></dd><dt>file systems, <a class="indexterm" href="s1-sysinfo-filesystems.html">File Systems</a></dt><dt>files, proc file system</dt><dd><dl><dt>changing, <a class="indexterm" href="ch-proc.html#s2-proc-change">Changing Virtual Files</a>, <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl
Command</a></dt><dt>viewing, <a class="indexterm" href="ch-proc.html#s2-proc-viewing">Viewing Virtual Files</a>, <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</a></dt></dl></dd><dt>FQDN (see fully qualified domain name)</dt><dt>frame buffer device, <a class="indexterm" href="s2-proc-fb.html"> /proc/fb </a></dt><dd><dl><dt>(see also /proc/fb )</dt></dl></dd><dt> free , <a class="indexterm" href="s1-sysinfo-memory-usage.html">Memory Usage</a></dt><dt>fully qualified domain name, <a class="indexterm" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-zones">Nameserver Zones</a></dt></dl></div><div class="indexdiv"><h3>G</h3><dl><dt> GNOME System Monitor , <a class="indexterm" href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">System Processes</a></dt><dt> gnome-system-log (see Log File Viewer )</dt><dt> gnome-system-monitor , <a class="indexterm" href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">Syste
m Processes</a></dt><dt>GnuPG</dt><dd><dl><dt>checking RPM package signatures, <a class="indexterm" href="s1-check-rpm-sig.html">Checking a Package's Signature</a></dt></dl></dd><dt>group confi/sbin/nologinguration</dt><dd><dl><dt>adding groups, <a class="indexterm" href="Users_and_Groups.html#s2-redhat-config-users-group-new">Adding a New Group</a></dt></dl></dd><dt>group configuration</dt><dd><dl><dt>filtering list of groups, <a class="indexterm" href="Users_and_Groups.html#s1-users-configui">User and Group Configuration</a></dt><dt> groupadd , <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt><dt>modify users in groups, <a class="indexterm" href="Users_and_Groups.html#s2-redhat-config-users-group-properties">Modifying Group Properties</a></dt><dt>modifying group properties, <a class="indexterm" href="Users_and_Groups.html#s2-redhat-config-users-group-properties">Modifying Group Properties</a></dt><dt>viewing list of group
s, <a class="indexterm" href="Users_and_Groups.html#s1-users-configui">User and Group Configuration</a></dt></dl></dd><dt>groups (see group configuration)</dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-users-groups-additional-resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">Installed Documentation</a></dt></dl></dd><dt>GID, <a class="indexterm" href="Users_and_Groups.html">Users and Groups</a></dt><dt>introducing, <a class="indexterm" href="Users_and_Groups.html">Users and Groups</a></dt><dt>shared directories, <a class="indexterm" href="s1-users-groups-private-groups.html#s2-users-groups-rationale">Group Directories</a></dt><dt>standard, <a class="indexterm" href="s1-users-groups-standard-groups.html">Standard Groups</a></dt><dt>tools for management of</dt><dd><dl><dt> groupadd , <a class="indexterm" href="s1-users-tools.h
tml">User and Group Management Tools</a>, <a class="indexterm" href="s1-users-groups-private-groups.html">User Private Groups</a></dt><dt> system-config-users , <a class="indexterm" href="s1-users-groups-private-groups.html">User Private Groups</a></dt><dt> User Manager , <a class="indexterm" href="s1-users-tools.html">User and Group Management Tools</a></dt></dl></dd><dt>user private, <a class="indexterm" href="s1-users-groups-private-groups.html">User Private Groups</a></dt></dl></dd><dt>GRUB boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Configuring the GRUB Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Configuring the GRUB Boot Loader</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hardware</dt><dd><dl><dt>viewing, <a class="indexterm" href="s1-sysinfo-hardware.html">Hardware</a></dt></dl></dd><dt
> Hardware Browser , <a class="indexterm" href="s1-sysinfo-hardware.html">Hardware</a></dt><dt>HTTP server (see Apache HTTP Server)</dt><dt>httpd (see Apache HTTP Server)</dt><dt>hugepages</dt><dd><dl><dt>configuration of, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-vm"> /proc/sys/vm/ </a></dt></dl></dd><dt> hwbrowser , <a class="indexterm" href="s1-sysinfo-hardware.html">Hardware</a></dt></dl></div><div class="indexdiv"><h3>I</h3><dl><dt> ifdown , <a class="indexterm" href="s1-networkscripts-control.html">Interface Control Scripts</a></dt><dt> ifup , <a class="indexterm" href="s1-networkscripts-control.html">Interface Control Scripts</a></dt><dt>information</dt><dd><dl><dt>about your system, <a class="indexterm" href="ch-Gathering_System_Information.html">Gathering System Information</a></dt></dl></dd><dt>initial RAM disk image</dt><dd><dl><dt>verifying, <a class="indexterm" href="sec-Verifying_the_Initial_RAM_Disk_Image.html">Verifying the Initial RAM Disk
Image</a></dt><dd><dl><dt>IBM eServer System i, <a class="indexterm" href="sec-Verifying_the_Initial_RAM_Disk_Image.html">Verifying the Initial RAM Disk Image</a></dt></dl></dd></dl></dd><dt>initial RPM repositories</dt><dd><dl><dt>installable packages, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding RPM Packages</a></dt></dl></dd><dt> insmod , <a class="indexterm" href="sec-Loading_a_Module.html">Loading a Module</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt>installing package groups</dt><dd><dl><dt>installing package groups with PackageKit, <a class="indexterm" href="sec-Installing_and_Removing_Package_Groups.html">Installing and Removing Package Groups</a></dt></dl></dd><dt>installing the kernel, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the Kernel</a></dt><dt>introduction, <a class="indexterm" href="ch-intro.html">Introduction</a></dt></dl></div><div class="indexdiv"><h3>K</h3><dl><dt>kdump<
/dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installed documents, <a class="indexterm" href="s1-kdump-resources.html#s2-kdump-resources-installed">Installed Documentation</a></dt><dt>manual pages, <a class="indexterm" href="s1-kdump-resources.html#s2-kdump-resources-installed">Installed Documentation</a></dt><dt>websites, <a class="indexterm" href="s2-kdump-resources-online.html">Useful Websites</a></dt></dl></dd><dt>analyzing the dump (see crash)</dt><dt>configuring the service</dt><dd><dl><dt>default action, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-action">Changing the Default Action</a></dt><dt>dump image compression, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-filtering">Configuring the Core Collector</a></
dt><dt>filtering level, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-gui-filtering">The Filtering Settings Tab</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-filtering">Configuring the Core Collector</a></dt><dt>initial RAM disk, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>kernel image, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>kernel options, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-gui-expert">The Expert Settings Tab</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>memory usage, <a c
lass="indexterm" href="ch-kdump.html#s3-kdump-configuration-firstboot-memory">Configuring the Memory Usage</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-gui-basic">The Basic Settings Tab</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-memory">Configuring the Memory Usage</a></dt><dt>target location, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-gui-target">The Target Settings Tab</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-target">Configuring the Target Type</a></dt></dl></dd><dt>enabling the service, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-firstboot-enable">Enabling the Service</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-gui-enable">Enabling the Service</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-enable">Enabling the Service</a></dt><dt>known issues</dt><dd><dl><dt>hpsa driver, <a class="indexterm" href=
"ch-kdump.html#s3-kdump-configuration-gui-target">The Target Settings Tab</a>, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-target">Configuring the Target Type</a></dt></dl></dd><dt>running the service, <a class="indexterm" href="ch-kdump.html#s3-kdump-configuration-cli-enable">Enabling the Service</a></dt><dt>system requirements, <a class="indexterm" href="ch-kdump.html#s1-kdump-configuration">Configuring the kdump Service</a></dt><dt>testing the configuration, <a class="indexterm" href="ch-kdump.html#s2-kdump-configuration-testing">Testing the Configuration</a></dt></dl></dd><dt>kernel</dt><dd><dl><dt>downloading, <a class="indexterm" href="s1-kernel-download.html">Downloading the Upgraded Kernel</a></dt><dt>installing kernel packages, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the Kernel</a></dt><dt>kernel packages, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview
of Kernel Packages</a></dt><dt>package, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the Kernel</a></dt><dt>performing kernel upgrade, <a class="indexterm" href="s1-kernel-perform-upgrade.html">Performing the Upgrade</a></dt><dt>RPM package, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the Kernel</a></dt><dt>upgrade kernel available, <a class="indexterm" href="s1-kernel-download.html">Downloading the Upgraded Kernel</a></dt><dd><dl><dt>Security Errata, <a class="indexterm" href="s1-kernel-download.html">Downloading the Upgraded Kernel</a></dt><dt>via Red Hat network, <a class="indexterm" href="s1-kernel-download.html">Downloading the Upgraded Kernel</a></dt></dl></dd><dt>upgrading</dt><dd><dl><dt>preparing, <a class="indexterm" href="s1-kernel-preparing.html">Preparing to Upgrade</a></dt><dt>working boot media, <a class="indexterm" href="s1-kernel-preparing.html">Preparing to Upgrade</a></dt></d
l></dd><dt>upgrading the kernel, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the Kernel</a></dt></dl></dd><dt>Kernel Dump Configuration (see kdump)</dt><dt>kernel module</dt><dd><dl><dt>bonding module, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt><dd><dl><dt>description, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt><dt>parameters to bonded interfaces, <a class="indexterm" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt></dl></dd><dt>definition, <a class="indexterm" href="ch-Working_with_Kernel_Modules.html">Working with Kernel Modules</a></dt><dt>directories</dt><dd><dl><dt> /etc/sysconfig/modules/ , <a class="indexterm" href="sec-Persistent_Module_Loading.html">Persistent Module Loading</a></dt><dt> /lib/modules/<kernel_version>/kernel/drivers/ , <a class="indexterm" href="sec-Loading_a_M
odule.html">Loading a Module</a></dt></dl></dd><dt>Ethernet module</dt><dd><dl><dt>supporting multiple cards, <a class="indexterm" href="sec-Specific_Kernel_Module_Capabilities.html#sec-Using_Multiple_Ethernet_Cards">Using Multiple Ethernet Cards</a></dt></dl></dd><dt>files</dt><dd><dl><dt> /proc/modules , <a class="indexterm" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt></dl></dd><dt>listing</dt><dd><dl><dt>currently loaded modules, <a class="indexterm" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt><dt>module information, <a class="indexterm" href="sec-Displaying_Information_About_a_Module.html">Displaying Information About a Module</a></dt></dl></dd><dt>loading</dt><dd><dl><dt>at the boot time, <a class="indexterm" href="sec-Persistent_Module_Loading.html">Persistent Module Loading</a></dt><dt>for the current session, <a cla
ss="indexterm" href="sec-Loading_a_Module.html">Loading a Module</a></dt></dl></dd><dt>module parameters</dt><dd><dl><dt>bonding module parameters, <a class="indexterm" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives">Bonding Module Directives</a></dt><dt>supplying, <a class="indexterm" href="sec-Setting_Module_Parameters.html">Setting Module Parameters</a></dt></dl></dd><dt>unloading, <a class="indexterm" href="sec-Unloading_a_Module.html">Unloading a Module</a></dt><dt>utilities</dt><dd><dl><dt> insmod , <a class="indexterm" href="sec-Loading_a_Module.html">Loading a Module</a></dt><dt> lsmod , <a class="indexterm" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt><dt> modinfo , <a class="indexterm" href="sec-Displaying_Information_About_a_Module.html">Displaying Information About a Module</a></dt><dt> modprobe , <a class="indexterm" href="sec-Loading_a_Module.html">Loading a Module</
a>, <a class="indexterm" href="sec-Unloading_a_Module.html">Unloading a Module</a></dt><dt> rmmod , <a class="indexterm" href="sec-Unloading_a_Module.html">Unloading a Module</a></dt></dl></dd></dl></dd><dt>kernel package</dt><dd><dl><dt>kernel</dt><dd><dl><dt>for single,multicore and multiprocessor systems, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-devel</dt><dd><dl><dt>kernel headers and makefiles, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-doc</dt><dd><dl><dt> documentation files, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-firmware</dt><dd><dl><dt> firmware files, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a><
/dt></dl></dd><dt>kernel-headers</dt><dd><dl><dt> C header files files, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>perf</dt><dd><dl><dt>firmware files, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd></dl></dd><dt>kernel upgrading</dt><dd><dl><dt>preparing, <a class="indexterm" href="s1-kernel-preparing.html">Preparing to Upgrade</a></dt></dl></dd><dt>keyboard configuration, <a class="indexterm" href="ch-Keyboard_Configuration.html">Keyboard Configuration</a></dt><dd><dl><dt>Keyboard Indicator applet, <a class="indexterm" href="s1-keyboard-indicator.html">Adding the Keyboard Layout Indicator</a></dt><dt>Keyboard Preferences utility, <a class="indexterm" href="ch-Keyboard_Configuration.html#s1-keyboard-layout">Changing the Keyboard Layout</a></dt><dt>layout, <a class="indexterm" href="ch-Keyboard_Configu
ration.html#s1-keyboard-layout">Changing the Keyboard Layout</a></dt><dt>typing break, <a class="indexterm" href="s1-keyboard-break.html">Setting Up a Typing Break</a></dt></dl></dd><dt>Keyboard Indicator (see keyboard configuration)</dt><dt>Keyboard Preferences (see keyboard configuration)</dt></dl></div><div class="indexdiv"><h3>L</h3><dl><dt> Log File Viewer </dt><dd><dl><dt>filtering, <a class="indexterm" href="s1-logfiles-viewing.html">Viewing Log Files</a></dt><dt>monitoring, <a class="indexterm" href="s1-logfiles-examining.html">Monitoring Log Files</a></dt><dt>searching, <a class="indexterm" href="s1-logfiles-viewing.html">Viewing Log Files</a></dt></dl></dd><dt>log files, <a class="indexterm" href="ch-Log_Files.html">Log Files</a></dt><dd><dl><dt>(see also Log Viewer )</dt><dt>additional resources</dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-log-files-additional-resources.html#s2-log-files-installed-docs">Installed Documentation</a></dt><d
t>useful websites, <a class="indexterm" href="s2-log-files-useful-websites.html">Useful Websites</a></dt></dl></dd><dt>description, <a class="indexterm" href="ch-Log_Files.html">Log Files</a></dt><dt>locating, <a class="indexterm" href="s1-logfiles-locating.html">Locating Log Files</a></dt><dt>monitoring, <a class="indexterm" href="s1-logfiles-examining.html">Monitoring Log Files</a></dt><dt>rotating, <a class="indexterm" href="s1-logfiles-locating.html">Locating Log Files</a></dt><dt> rsyslod daemon , <a class="indexterm" href="ch-Log_Files.html">Log Files</a></dt><dt>viewing, <a class="indexterm" href="s1-logfiles-viewing.html">Viewing Log Files</a></dt></dl></dd><dt> Log Viewer </dt><dd><dl><dt>refresh rate, <a class="indexterm" href="s1-logfiles-viewing.html">Viewing Log Files</a></dt></dl></dd><dt> logrotate , <a class="indexterm" href="s1-logfiles-locating.html">Locating Log Files</a></dt><dt> lsmod , <a class="indexterm" href="ch-Working_with_Kernel_Modules.html#sec-L
isting_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt> lspci , <a class="indexterm" href="s2-proc-pci.html"> /proc/bus/pci </a>, <a class="indexterm" href="s1-sysinfo-hardware.html">Hardware</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>Mail Delivery Agent (see email)</dt><dt>Mail Transport Agent (see email) (see MTA)</dt><dt> Mail Transport Agent Switcher , <a class="indexterm" href="s2-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt><dt>Mail User Agent, <a class="indexterm" href="s2-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a> (see email)</dt><dt>MDA (see Mail Delivery Agent)</dt><dt>memory usage, <a class="indexterm" href="s1-sysinfo-memory-usage.html">Memory Usage</a></dt><dt> modinfo , <a class="indexterm" href="sec-Displaying_Information_About_a_Module.html">Displaying Information About a Module</a></dt><dd><dl><dt>(see also kernel modu
le)</dt></dl></dd><dt> modprobe , <a class="indexterm" href="sec-Loading_a_Module.html">Loading a Module</a>, <a class="indexterm" href="sec-Unloading_a_Module.html">Unloading a Module</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt>module (see kernel module)</dt><dt>module parameters (see kernel module)</dt><dt>MTA (see Mail Transport Agent)</dt><dd><dl><dt>setting default, <a class="indexterm" href="s2-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt><dt>switching with Mail Transport Agent Switcher , <a class="indexterm" href="s2-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt></dl></dd><dt>MUA, <a class="indexterm" href="s2-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a> (see Mail User Agent)</dt><dt>Multihomed DHCP</dt><dd><dl><dt>host configuration, <a class="indexterm" href="sect-Configuring_a_Multihomed_DHCP_Server.html#sect-dns_Host_Configuration">Host Configuration</a></dt><dt>server c
onfiguration, <a class="indexterm" href="sect-Configuring_a_Multihomed_DHCP_Server.html">Configuring a Multihomed DHCP Server</a></dt></dl></dd><dt>multiple domains</dt><dd><dl><dt>specifying in SSSD, <a class="indexterm" href="sect-SSSD_User_Guide-Introduction-SSSD_Features.html#sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">Support for Multiple Domains</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>N</h3><dl><dt>named (see BIND)</dt><dt>nameserver (see DNS)</dt><dt>network</dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-networkscripts-resources.html">Additional Resources</a></dt><dt>commands</dt><dd><dl><dt> /sbin/ifdown , <a class="indexterm" href="s1-networkscripts-control.html">Interface Control Scripts</a></dt><dt> /sbin/ifup , <a class="indexterm" href="s1-networkscripts-control.html">Interface Control Scripts</a></dt><dt> /sbin/service network , <a class="indexterm" href="s1-networkscripts-control.html">Interface Control
Scripts</a></dt></dl></dd><dt>configuration, <a class="indexterm" href="s1-networkscripts-interfaces.html">Interface Configuration Files</a></dt><dt>configuration files, <a class="indexterm" href="ch-Network_Interfaces.html#s1-networkscripts-files">Network Configuration Files</a></dt><dt>functions, <a class="indexterm" href="s1-networkscripts-functions.html">Network Function Files</a></dt><dt>interface configuration files, <a class="indexterm" href="s1-networkscripts-interfaces.html">Interface Configuration Files</a></dt><dt>interfaces</dt><dd><dl><dt>alias, <a class="indexterm" href="s2-networkscripts-interfaces-alias.html">Alias and Clone Files</a></dt><dt>channel bonding, <a class="indexterm" href="s2-networkscripts-interfaces-chan.html">Channel Bonding Interfaces</a></dt><dt>clone, <a class="indexterm" href="s2-networkscripts-interfaces-alias.html">Alias and Clone Files</a></dt><dt>dialup, <a class="indexterm" href="s2-networkscripts-interfaces-ppp0.html">Dialup Interfac
es</a></dt><dt>Ethernet, <a class="indexterm" href="s1-networkscripts-interfaces.html#s2-networkscripts-interfaces-eth0">Ethernet Interfaces</a></dt></dl></dd><dt>scripts, <a class="indexterm" href="ch-Network_Interfaces.html">Network Interfaces</a></dt></dl></dd><dt>Network Time Protocol (see NTP)</dt><dt>NIC</dt><dd><dl><dt>binding into single channel, <a class="indexterm" href="sec-Using_Channel_Bonding.html">Using Channel Bonding</a></dt></dl></dd><dt>NTP</dt><dd><dl><dt>configuring, <a class="indexterm" href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Network_Time_Protocol">Network Time Protocol Properties</a>, <a class="indexterm" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Network Time Protocol Setup</a></dt><dt> ntpd , <a class="indexterm" href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Network_Time_Protocol">Network Time Protocol Properties</a>, <a class="index
term" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Network Time Protocol Setup</a></dt><dt> ntpdate , <a class="indexterm" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Network Time Protocol Setup</a></dt></dl></dd><dt> ntpd (see NTP)</dt><dt> ntpdate (see NTP)</dt><dt> ntsysv (see services configuration)</dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>OpenSSH, <a class="indexterm" href="ch-OpenSSH.html">OpenSSH</a>, <a class="indexterm" href="ch-OpenSSH.html#s2-ssh-features">Main Features</a></dt><dd><dl><dt>(see also SSH)</dt><dt>additional resources, <a class="indexterm" href="s1-openssh-additional-resources.html">Additional Resources</a></dt><dt>client, <a class="indexterm" href="s1-ssh-clients.html">OpenSSH Clients</a></dt><dd><dl><dt> scp , <a class="indexterm" href="s2-ssh-clients-scp.html">Using the scp Utility</a></dt><dt> sftp , <a class="indexterm" href="s2-s
sh-clients-sftp.html">Using the sftp Utility</a></dt><dt> ssh , <a class="indexterm" href="s1-ssh-clients.html#s2-ssh-clients-ssh">Using the ssh Utility</a></dt></dl></dd><dt>DSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>RSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>RSA Version 1 keys</dt><dd><dl><dt>generating, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>server, <a class="indexterm" href="s2-ssh-configuration-sshd.html">Starting an OpenSSH Server</a></dt><dd><dl><dt>starting, <a class="indexterm" href="s2-ssh-configuration-sshd.html">Starting an OpenSSH Server</a></dt><dt>stopping, <a class="indexterm"
href="s2-ssh-configuration-sshd.html">Starting an OpenSSH Server</a></dt></dl></dd><dt> ssh-add , <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">Configuring ssh-agent</a></dt><dt> ssh-agent , <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">Configuring ssh-agent</a></dt><dt>ssh-keygen</dt><dd><dl><dt>DSA, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt><dt>RSA, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt><dt>RSA Version 1, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>using key-based authentication, <a class="indexterm" href="s2-ssh-configuration-keypairs.html">Using a Key-Based Authentication</a></dt></
dl></dd><dt>OpenSSL</dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-openssh-additional-resources.html">Additional Resources</a></dt><dt>SSL (see SSL)</dt><dt>TLS (see TLS)</dt></dl></dd><dt>OS/400 boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="s2-kernel-boot-loader-iseries.html">Configuring the OS/400® Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="s2-kernel-boot-loader-iseries.html">Configuring the OS/400® Boot Loader</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>package</dt><dd><dl><dt>kernel RPM, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the Kernel</a></dt></dl></dd><dt>PackageKit, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dd><dl><dt>adding and removing, <a class="indexterm" href="sec-Using_Add_Remove_Software.html">Using Add/Remove Software</a></dt><dt>architecture, <a class="indexterm" href="sec-PackageKit_Architec
ture.html">PackageKit Architecture</a></dt><dt>installing and removing package groups, <a class="indexterm" href="sec-Installing_and_Removing_Package_Groups.html">Installing and Removing Package Groups</a></dt><dt>installing packages , <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>managing packages , <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>PolicyKit</dt><dd><dl><dt>authentication, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>uninstalling packages , <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>updating packages , <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>viewing packages , <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>viewing transaction log, <a class="indexterm" href="sec-Viewing_the_Transaction_Log.html">Viewing the Transaction Log</a></dt><
/dl></dd><dt>packages</dt><dd><dl><dt>adding and removing with PackageKit, <a class="indexterm" href="sec-Using_Add_Remove_Software.html">Using Add/Remove Software</a></dt><dt>dependencies, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">Unresolved Dependency</a></dt><dt>determining file ownership with, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>displaying packages</dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>displaying packages with Yum, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Packages_and_Package_Gro
ups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>filtering with PackageKit, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dd><dl><dt>Development, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>Free, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>Graphical, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>hide subpackages, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>installed, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>no filter, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages wit
h Filters</a></dt><dt>only available, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>only development, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>only end user files, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>only installed, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>only native packages, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>only newest items, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt></dl></dd><dt>filtering with PackageKit for packages, <a class="indexterm" href="sec-Finding_Packages_with_Filters.html">Finding Packages with Filters</a></dt><dt>finding deleted files from, <a class="inde
xterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>finding RPM packages, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding RPM Packages</a></dt><dt>iFedora installation media, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding RPM Packages</a></dt><dt>initial RPM repositories, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding RPM Packages</a></dt><dt>installing a package group with Yum, <a class="indexterm" href="sec-Installing.html">Installing</a></dt><dt>installing and removing package groups, <a class="indexterm" href="sec-Installing_and_Removing_Package_Groups.html">Installing and Removing Package Groups</a></dt><dt>installing packages with PackageKit, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a>, <a class="indexterm" href="sec-Installing_and_Removing_Packages_and_Dependencies.html">Installing and Removing Packages (and Dependencies)</a></dt><dd><dl><dt>depen
dencies, <a class="indexterm" href="sec-Installing_and_Removing_Packages_and_Dependencies.html">Installing and Removing Packages (and Dependencies)</a></dt></dl></dd><dt>installing RPM, <a class="indexterm" href="sec-Installing_and_Upgrading.html">Installing and Upgrading</a></dt><dt>installing with Yum, <a class="indexterm" href="sec-Installing.html">Installing</a></dt><dt>kernel</dt><dd><dl><dt>for single,multicore and multiprocessor systems, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-devel</dt><dd><dl><dt>kernel headers and makefiles, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-doc</dt><dd><dl><dt> documentation files, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-firmware</dt><dd><dl
><dt> firmware files, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>kernel-headers</dt><dd><dl><dt> C header files files, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>listing packages with Yum, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dd><dl><dt> Glob expressions, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum grouplist, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list a
ll, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list available, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list installed, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum repolist, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum search, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Inf
ormation</a></dt></dl></dd><dt>locating documentation for, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>managing packages with PackageKit, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>obtaining list of files, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>packages and package groups, <a class="indexterm" href="sec-Packages_and_Package_Groups.html">Packages and Package Groups</a></dt><dt>perf</dt><dd><dl><dt> firmware files, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>querying uninstalled, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>removing, <a class="indexterm" href="s2-rpm-uninstalling.html">Uninstalling</a></dt><dt>removing package groups with Yum, <a class="indexterm" href="sec-
Removing.html">Removing</a></dt><dt>removing packages with PackageKit, <a class="indexterm" href="sec-Installing_and_Removing_Packages_and_Dependencies.html">Installing and Removing Packages (and Dependencies)</a></dt><dt>RPM, <a class="indexterm" href="ch-RPM.html">RPM</a></dt><dd><dl><dt>already installed, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-errors">Package Already Installed</a></dt><dt>configuration file changes, <a class="indexterm" href="sec-Configuration_File_Changes.html">Configuration File Changes</a></dt><dt>conflict, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-conflicting-files">Conflicting Files</a></dt><dt>failed dependancies, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">Unresolved Dependency</a></dt><dt>freshening, <a class="indexterm" href="s2-rpm-freshening.html">Freshening</a></dt><dt>prisitne sources, <a class="indexterm" href="ch-RPM.html#s1-rpm-design">RPM
Design Goals</a></dt><dt>querying, <a class="indexterm" href="s2-rpm-querying.html">Querying</a></dt><dt>removing, <a class="indexterm" href="s2-rpm-uninstalling.html">Uninstalling</a></dt><dt>source and binary packages, <a class="indexterm" href="ch-RPM.html">RPM</a></dt><dt>tips, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>uninstalling, <a class="indexterm" href="s2-rpm-uninstalling.html">Uninstalling</a></dt><dt>verifying, <a class="indexterm" href="s2-rpm-verifying.html">Verifying</a></dt></dl></dd><dt>searching for packages with Yum</dt><dd><dl><dt>yum search, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>searching packages with Yum, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searc
hing, Listing and Displaying Package Information</a></dt><dt>setting packages with PackageKit</dt><dd><dl><dt>checking interval, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>uninstalling packages with PackageKit, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>uninstalling packages with Yum, <a class="indexterm" href="sec-Removing.html">Removing</a></dt><dd><dl><dt>yum remove package_name, <a class="indexterm" href="sec-Removing.html">Removing</a></dt></dl></dd><dt>updating currently installed packages</dt><dd><dl><dt>available updates, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>updating packages with PackageKit, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dd><dl><dt>PolicyKit, <a class="indexterm" href="ch-PackageKit.ht
ml#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt><dt>Software Update, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>upgrading RPM, <a class="indexterm" href="sec-Installing_and_Upgrading.html">Installing and Upgrading</a></dt><dt>viewing packages with PackageKit, <a class="indexterm" href="ch-PackageKit.html">PackageKit</a></dt><dt>viewing transaction log, <a class="indexterm" href="sec-Viewing_the_Transaction_Log.html">Viewing the Transaction Log</a></dt><dt>viewing Yum repositories with PackageKit, <a class="indexterm" href="sec-Using_Add_Remove_Software.html#sec-Refreshing_Software_Sources_Yum_Repositories">Refreshing Software Sources (Yum Repositories)</a></dt><dt>Yum insead of RPM, <a class="indexterm" href="ch-RPM.html">RPM</a></dt></dl></dd><dt>password</dt><dd><dl><dt>aging, <a class="indexterm" href="s1-users-tools.htm
l#s2-users-cmd-line">Command Line Configuration</a></dt><dt>expire, <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>passwords</dt><dd><dl><dt>shadow, <a class="indexterm" href="s1-users-groups-shadow-utilities.html">Shadow Passwords</a></dt></dl></dd><dt>PCI devices</dt><dd><dl><dt>listing, <a class="indexterm" href="s1-sysinfo-hardware.html">Hardware</a></dt></dl></dd><dt>PolicyKit, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt><dt>Postfix, <a class="indexterm" href="s1-email-mta.html#s2-email-mta-postfix">Postfix</a></dt><dd><dl><dt>default installation, <a class="indexterm" href="s1-email-mta.html#s3-email-mta-postfix-default">The Default Postfix Installation</a></dt></dl></dd><dt>postfix, <a class="indexterm" href="s2-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt><dt>primary nameserver (see
BIND)</dt><dt> proc file system</dt><dd><dl><dt> /proc/buddyinfo , <a class="indexterm" href="s1-proc-topfiles.html#s2-proc-buddyinfo"> /proc/buddyinfo </a></dt><dt> /proc/bus/ directory, <a class="indexterm" href="s2-proc-dir-bus.html"> /proc/bus/ </a></dt><dt> /proc/bus/pci </dt><dd><dl><dt>viewing using lspci , <a class="indexterm" href="s2-proc-pci.html"> /proc/bus/pci </a></dt></dl></dd><dt> /proc/cmdline , <a class="indexterm" href="s2-proc-cmdline.html"> /proc/cmdline </a></dt><dt> /proc/cpuinfo , <a class="indexterm" href="s2-proc-cpuinfo.html"> /proc/cpuinfo </a></dt><dt> /proc/crypto , <a class="indexterm" href="s2-proc-crypto.html"> /proc/crypto </a></dt><dt> /proc/devices </dt><dd><dl><dt>block devices, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt><dt>character devices, <a class="indexterm" href="s2-proc-devices.html"> /proc/devices </a></dt></dl></dd><dt> /proc/dma , <a class="indexterm" href="s2-proc-dma.html"> /proc/dma </a></dt><d
t> /proc/driver/ directory, <a class="indexterm" href="s2-proc-dir-driver.html"> /proc/driver/ </a></dt><dt> /proc/execdomains , <a class="indexterm" href="s2-proc-execdomains.html"> /proc/execdomains </a></dt><dt> /proc/fb , <a class="indexterm" href="s2-proc-fb.html"> /proc/fb </a></dt><dt> /proc/filesystems , <a class="indexterm" href="s2-proc-filesystems.html"> /proc/filesystems </a></dt><dt> /proc/fs/ directory, <a class="indexterm" href="s2-proc-dir-fs.html"> /proc/fs </a></dt><dt> /proc/interrupts , <a class="indexterm" href="s2-proc-interrupts.html"> /proc/interrupts </a></dt><dt> /proc/iomem , <a class="indexterm" href="s2-proc-iomem.html"> /proc/iomem </a></dt><dt> /proc/ioports , <a class="indexterm" href="s2-proc-ioports.html"> /proc/ioports </a></dt><dt> /proc/irq/ directory, <a class="indexterm" href="s2-proc-dir-irq.html"> /proc/irq/ </a></dt><dt> /proc/kcore , <a class="indexterm" href="s2-proc-kcore.html"> /proc/kcore </a></dt><dt> /proc/kmsg , <a class="ind
exterm" href="s2-proc-kmsg.html"> /proc/kmsg </a></dt><dt> /proc/loadavg , <a class="indexterm" href="s2-proc-loadavg.html"> /proc/loadavg </a></dt><dt> /proc/locks , <a class="indexterm" href="s2-proc-locks.html"> /proc/locks </a></dt><dt> /proc/mdstat , <a class="indexterm" href="s2-proc-mdstat.html"> /proc/mdstat </a></dt><dt> /proc/meminfo , <a class="indexterm" href="s2-proc-meminfo.html"> /proc/meminfo </a></dt><dt> /proc/misc , <a class="indexterm" href="s2-proc-misc.html"> /proc/misc </a></dt><dt> /proc/modules , <a class="indexterm" href="s2-proc-modules.html"> /proc/modules </a></dt><dt> /proc/mounts , <a class="indexterm" href="s2-proc-mounts.html"> /proc/mounts </a></dt><dt> /proc/mtrr , <a class="indexterm" href="s2-proc-mtrr.html"> /proc/mtrr </a></dt><dt> /proc/net/ directory, <a class="indexterm" href="s2-proc-dir-net.html"> /proc/net/ </a></dt><dt> /proc/partitions , <a class="indexterm" href="s2-proc-partitions.html"> /proc/partitions </a></dt><dt> /proc/PI
D/ directory, <a class="indexterm" href="s2-proc-pid.html"> /proc/PID/ </a></dt><dt> /proc/scsi/ directory, <a class="indexterm" href="s2-proc-dir-scsi.html"> /proc/scsi/ </a></dt><dt> /proc/self/ directory, <a class="indexterm" href="s1-proc-directories.html#s3-proc-self"> /proc/self/ </a></dt><dt> /proc/slabinfo , <a class="indexterm" href="s2-proc-slabinfo.html"> /proc/slabinfo </a></dt><dt> /proc/stat , <a class="indexterm" href="s2-proc-stat.html"> /proc/stat </a></dt><dt> /proc/swaps , <a class="indexterm" href="s2-proc-swaps.html"> /proc/swaps </a></dt><dt> /proc/sys/ directory, <a class="indexterm" href="s2-proc-dir-sys.html"> /proc/sys/ </a>, <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</a></dt><dd><dl><dt>(see also sysctl )</dt><dt> /proc/sys/dev/ directory, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-dev"> /proc/sys/dev/ </a></dt><dt> /proc/sys/fs/ directory, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-f
s"> /proc/sys/fs/ </a></dt><dt> /proc/sys/kernel/ directory, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt> /proc/sys/kernel/exec-shield , <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt><dt>/proc/sys/kernel/sysrq (see system request key)</dt><dt> /proc/sys/net/ directory, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-net"> /proc/sys/net/ </a></dt><dt> /proc/sys/vm/ directory, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-vm"> /proc/sys/vm/ </a></dt></dl></dd><dt> /proc/sysrq-trigger , <a class="indexterm" href="s2-proc-sysrq-trigger.html"> /proc/sysrq-trigger </a></dt><dt> /proc/sysvipc/ directory, <a class="indexterm" href="s2-proc-dir-sysvipc.html"> /proc/sysvipc/ </a></dt><dt> /proc/tty/ directory, <a class="indexterm" href="s2-proc-tty.html"> /proc/tty/ </a></dt><dt> /proc/uptime , <a class="indexterm" href="s2-proc-uptime.html"> /proc/uptime
</a></dt><dt> /proc/version , <a class="indexterm" href="s2-proc-version.html"> /proc/version </a></dt><dt>additional resources, <a class="indexterm" href="s1-proc-additional-resources.html">References</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-proc-additional-resources.html#s2-proc-installed-documentation">Installed Documentation</a></dt><dt>useful websites, <a class="indexterm" href="s1-proc-additional-resources.html#s2-proc-useful-websites">Useful Websites</a></dt></dl></dd><dt>changing files within, <a class="indexterm" href="ch-proc.html#s2-proc-change">Changing Virtual Files</a>, <a class="indexterm" href="s2-proc-dir-sys.html"> /proc/sys/ </a>, <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</a></dt><dt>files within, top-level, <a class="indexterm" href="s1-proc-topfiles.html">Top-level Files within the proc File System</a></dt><dt>introduced, <a class="indexterm" href="ch-proc.html">The proc File System</a></d
t><dt>process directories, <a class="indexterm" href="s1-proc-directories.html#s2-proc-processdirs">Process Directories</a></dt><dt>subdirectories within, <a class="indexterm" href="s1-proc-directories.html">Directories within /proc/ </a></dt><dt>viewing files within, <a class="indexterm" href="ch-proc.html#s2-proc-viewing">Viewing Virtual Files</a></dt></dl></dd><dt>processes, <a class="indexterm" href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">System Processes</a></dt><dt>Procmail, <a class="indexterm" href="s1-email-mda.html">Mail Delivery Agents</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-email-additional-resources.html">Additional Resources</a></dt><dt>configuration, <a class="indexterm" href="s1-email-mda.html#s2-email-procmail-configuration">Procmail Configuration</a></dt><dt>recipes, <a class="indexterm" href="s2-email-procmail-recipes.html">Procmail Recipes</a></dt><dd><dl><dt>delivering, <a class="indexterm" href=
"s2-email-procmail-recipes.html#s2-email-procmail-recipes-delivering">Delivering vs. Non-Delivering Recipes</a></dt><dt>examples, <a class="indexterm" href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-examples">Recipe Examples</a></dt><dt>flags, <a class="indexterm" href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-flags">Flags</a></dt><dt>local lockfiles, <a class="indexterm" href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-lockfile">Specifying a Local Lockfile</a></dt><dt>non-delivering, <a class="indexterm" href="s2-email-procmail-recipes.html#s2-email-procmail-recipes-delivering">Delivering vs. Non-Delivering Recipes</a></dt><dt>SpamAssassin, <a class="indexterm" href="s2-email-procmail-recipes.html#s3-email-mda-spam">Spam Filters</a></dt><dt>special actions, <a class="indexterm" href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-special">Special Conditions and Actions</a></dt><dt>special conditions, <a class="indexterm
" href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-special">Special Conditions and Actions</a></dt></dl></dd></dl></dd><dt> ps , <a class="indexterm" href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">System Processes</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAM, <a class="indexterm" href="s1-sysinfo-memory-usage.html">Memory Usage</a></dt><dt> rcp , <a class="indexterm" href="s2-ssh-clients-scp.html">Using the scp Utility</a></dt><dt>recursive nameserver (see BIND)</dt><dt> Red Hat RPM Guide , <a class="indexterm" href="s2-rpm-related-books.html">Related Books</a></dt><dt>removing package groups</dt><dd><dl><dt>removing package groups with PackageKit, <a class="indexterm" href="sec-Installing_and_Removing_Package_Groups.html">Installing and Removing Package Groups</a></dt></dl></dd><dt>resource record (see BIND)</dt><dt> rmmod , <a class="indexterm" href="sec-Unloading_a_Module.html">Unloading a Module</a></dt><dd><dl><dt
>(see also kernel module)</dt></dl></dd><dt>rndc (see BIND)</dt><dt>root nameserver (see BIND)</dt><dt>RPM, <a class="indexterm" href="ch-RPM.html">RPM</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-rpm-additional-resources.html">Additional Resources</a></dt><dt>already installed, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-errors">Package Already Installed</a></dt><dt>basic modes, <a class="indexterm" href="s1-rpm-using.html">Using RPM</a></dt><dt>book about, <a class="indexterm" href="s2-rpm-related-books.html">Related Books</a></dt><dt>checking package signatures, <a class="indexterm" href="s1-check-rpm-sig.html">Checking a Package's Signature</a></dt><dt>configuration file changes, <a class="indexterm" href="sec-Configuration_File_Changes.html">Configuration File Changes</a></dt><dd><dl><dt>conf.rpmsave, <a class="indexterm" href="sec-Configuration_File_Changes.html">Configuration File Changes</a></dt></dl></dd><dt>conflic
ts, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-conflicting-files">Conflicting Files</a></dt><dt>dependencies, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">Unresolved Dependency</a></dt><dt>design goals, <a class="indexterm" href="ch-RPM.html#s1-rpm-design">RPM Design Goals</a></dt><dd><dl><dt>powerful querying, <a class="indexterm" href="ch-RPM.html#s1-rpm-design">RPM Design Goals</a></dt><dt>system verification, <a class="indexterm" href="ch-RPM.html#s1-rpm-design">RPM Design Goals</a></dt><dt>upgradability, <a class="indexterm" href="ch-RPM.html#s1-rpm-design">RPM Design Goals</a></dt></dl></dd><dt>determining file ownership with, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>documentation with, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>failed dependancies, <a class="indexterm" hre
f="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency">Unresolved Dependency</a></dt><dt>file conflicts</dt><dd><dl><dt>resolving, <a class="indexterm" href="sec-Installing_and_Upgrading.html#s3-rpm-conflicting-files">Conflicting Files</a></dt></dl></dd><dt>file name, <a class="indexterm" href="sec-Installing_and_Upgrading.html">Installing and Upgrading</a></dt><dt>finding deleted files with, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>finding RPM packages, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding RPM Packages</a></dt><dt>freshening, <a class="indexterm" href="s2-rpm-freshening.html">Freshening</a></dt><dt>GnuPG, <a class="indexterm" href="s1-check-rpm-sig.html">Checking a Package's Signature</a></dt><dt>installing, <a class="indexterm" href="sec-Installing_and_Upgrading.html">Installing and Upgrading</a></dt><dt>md5sum, <a class="indexterm" href="s1-check-rpm-sig.html">Chec
king a Package's Signature</a></dt><dt>querying, <a class="indexterm" href="s2-rpm-querying.html">Querying</a></dt><dt>querying for file list, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>querying uninstalled packages, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>tips, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>uninstalling, <a class="indexterm" href="s2-rpm-uninstalling.html">Uninstalling</a></dt><dt>upgrading, <a class="indexterm" href="sec-Installing_and_Upgrading.html">Installing and Upgrading</a></dt><dt>verifying, <a class="indexterm" href="s2-rpm-verifying.html">Verifying</a></dt><dt>website, <a class="indexterm" href="s2-rpm-useful-websites.html">Useful Websites</a></dt></dl></dd><dt>RPM Package Manager (see RPM)</dt><dt>RSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="s
2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>RSA Version 1 keys</dt><dd><dl><dt>generating, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt> rsyslog , <a class="indexterm" href="ch-Log_Files.html">Log Files</a></dt><dt> runlevel (see services configuration)</dt></dl></div><div class="indexdiv"><h3>S</h3><dl><dt> scp (see OpenSSH)</dt><dt>secondary nameserver (see BIND)</dt><dt>security plugin (see Security )</dt><dt>Security-Related Packages</dt><dd><dl><dt>updating security-related packages, <a class="indexterm" href="ch-yum.html#sec-Updating_Security-Related_Packages">Updating Security-Related Packages</a></dt></dl></dd><dt>Sendmail, <a class="indexterm" href="s2-email-mta-sendmail.html">Sendmail</a></dt><dd><dl><dt>additional resources, <a class="indexterm" href="s1-email-additional-resources.html">A
dditional Resources</a></dt><dt>aliases, <a class="indexterm" href="s2-email-mta-sendmail.html#s3-email-sendmail-changes-masquerading">Masquerading</a></dt><dt>common configuration changes, <a class="indexterm" href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes">Common Sendmail Configuration Changes</a></dt><dt>default installation, <a class="indexterm" href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-default">The Default Sendmail Installation</a></dt><dt>LDAP and, <a class="indexterm" href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-ldap">Using Sendmail with LDAP</a></dt><dt>limitations, <a class="indexterm" href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-purpose">Purpose and Limitations</a></dt><dt>masquerading, <a class="indexterm" href="s2-email-mta-sendmail.html#s3-email-sendmail-changes-masquerading">Masquerading</a></dt><dt>purpose, <a class="indexterm" href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-purpose">Purpose and Limitatio
ns</a></dt><dt>spam, <a class="indexterm" href="s2-email-mta-sendmail.html#s3-email-sendmail-stopping-spam">Stopping Spam</a></dt><dt>with UUCP, <a class="indexterm" href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes">Common Sendmail Configuration Changes</a></dt></dl></dd><dt>sendmail, <a class="indexterm" href="s2-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt><dt> service (see services configuration)</dt><dt>services configuration, <a class="indexterm" href="ch-Controlling_Access_to_Services.html">Controlling Access to Services</a></dt><dd><dl><dt> chkconfig , <a class="indexterm" href="s2-services-chkconfig.html">Using the chkconfig Utility</a></dt><dt> ntsysv , <a class="indexterm" href="s2-services-ntsysv.html">Using the ntsysv Utility</a></dt><dt> runlevel , <a class="indexterm" href="ch-Controlling_Access_to_Services.html#s1-services-runlevels">Configuring the Default Runlevel</a></dt><dt> service , <a class="indexterm" href="s1-
services-running.html#s2-services-service">Using the service Utility</a></dt><dt> system-config-services , <a class="indexterm" href="s1-services-configuring.html#s2-services-serviceconf">Using the Service Configuration Utility</a></dt></dl></dd><dt> sftp (see OpenSSH)</dt><dt>shadow passwords</dt><dd><dl><dt>overview of, <a class="indexterm" href="s1-users-groups-shadow-utilities.html">Shadow Passwords</a></dt></dl></dd><dt>slab pools (see /proc/slabinfo )</dt><dt>SpamAssassin</dt><dd><dl><dt>using with Procmail, <a class="indexterm" href="s2-email-procmail-recipes.html#s3-email-mda-spam">Spam Filters</a></dt></dl></dd><dt> ssh (see OpenSSH)</dt><dt>SSH protocol</dt><dd><dl><dt>authentication, <a class="indexterm" href="ch-OpenSSH.html#s2-ssh-protocol-authentication">Authentication</a></dt><dt>configuration files, <a class="indexterm" href="s1-ssh-configuration.html#s2-ssh-configuration-configs">Configuration Files</a></dt><dd><dl><dt>system-wide configuration files, <a
class="indexterm" href="s1-ssh-configuration.html#s2-ssh-configuration-configs">Configuration Files</a></dt><dt>user-specific configuration files, <a class="indexterm" href="s1-ssh-configuration.html#s2-ssh-configuration-configs">Configuration Files</a></dt></dl></dd><dt>connection sequence, <a class="indexterm" href="ch-OpenSSH.html#s2-ssh-conn">Event Sequence of an SSH Connection</a></dt><dt>features, <a class="indexterm" href="ch-OpenSSH.html#s2-ssh-features">Main Features</a></dt><dt>insecure protocols, <a class="indexterm" href="s2-ssh-configuration-requiring.html">Requiring SSH for Remote Connections</a></dt><dt>layers</dt><dd><dl><dt>channels, <a class="indexterm" href="ch-OpenSSH.html#s2-ssh-protocol-connection">Channels</a></dt><dt>transport layer, <a class="indexterm" href="ch-OpenSSH.html#s2-ssh-protocol-conn-transport">Transport Layer</a></dt></dl></dd><dt>port forwarding, <a class="indexterm" href="s2-ssh-beyondshell-tcpip.html">Port Forwarding</a></dt><dt>requi
ring for remote login, <a class="indexterm" href="s2-ssh-configuration-requiring.html">Requiring SSH for Remote Connections</a></dt><dt>security risks, <a class="indexterm" href="ch-OpenSSH.html#s2-ssh-why">Why Use SSH?</a></dt><dt>version 1, <a class="indexterm" href="ch-OpenSSH.html#s2-ssh-versions">Protocol Versions</a></dt><dt>version 2, <a class="indexterm" href="ch-OpenSSH.html#s2-ssh-versions">Protocol Versions</a></dt><dt>X11 forwarding, <a class="indexterm" href="s1-ssh-beyondshell.html#s2-ssh-beyondshell-x11">X11 Forwarding</a></dt></dl></dd><dt> ssh-add , <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">Configuring ssh-agent</a></dt><dt> ssh-agent , <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">Configuring ssh-agent</a></dt><dt>SSL, <a class="indexterm" href="s1-apache-mod_ssl.html">Setting Up an SSL Server</a></dt><dd><dl><dt>(see also Apache HTTP Server)</dt></
dl></dd><dt>SSL server (see Apache HTTP Server)</dt><dt>SSSD</dt><dd><dl><dt>Configuring a Microsoft Active Directory Domain for, <a class="indexterm" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Microsoft_Active_Directory_Domain">Configuring a Microsoft Active Directory Domain</a></dt><dt>Configuring a proxy domain for, <a class="indexterm" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Domain_Configuration_Options-Configuring_a_Proxy_Domain">Configuring a Proxy Domain</a></dt><dt>Configuring an LDAP domain for, <a class="indexterm" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LDAP Domain</a></dt><dt>Selecting an LDAP schema for, <a class="indexterm" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LD
AP Domain</a></dt><dt>Setting Up Kerberos authentication for, <a class="indexterm" href="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html">Setting Up Kerberos Authentication</a></dt><dt>Specifying timeout values for, <a class="indexterm" href="chap-SSSD_User_Guide-Configuring_Domains.html#sect-SSSD_User_Guide-Configuring_Domains-Configuring_a_Native_LDAP_Domain">Configuring an LDAP Domain</a></dt></dl></dd><dt> stunnel , <a class="indexterm" href="s1-email-mua.html#s3-email-security-servers">Securing Email Client Communications</a></dt><dt> sysconfig directory</dt><dd><dl><dt> /etc/sysconfig/apm-scripts/ directory, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/arpwatch , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-arpwatch"> /etc/sysconfig/arpwatch </a></dt><dt> /etc/sysconfig/authconfig , <a class="indexterm" href="ch-The_syscon
fig_Directory.html#s2-sysconfig-authconfig"> /etc/sysconfig/authconfig </a></dt><dt> /etc/sysconfig/autofs , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-autofs"> /etc/sysconfig/autofs </a></dt><dt> /etc/sysconfig/cbq/ directory, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/clock , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-clock"> /etc/sysconfig/clock </a></dt><dt> /etc/sysconfig/dhcpd , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-dhcpd"> /etc/sysconfig/dhcpd </a></dt><dt> /etc/sysconfig/firstboot , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-firewall"> /etc/sysconfig/firstboot </a></dt><dt> /etc/sysconfig/init , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-init"> /etc/sysconfig/init </a></dt><dt> /etc/sysconfig/ip6tables-config , <a class="indexterm
" href="ch-The_sysconfig_Directory.html#s2-sysconfig-ip6tables"> /etc/sysconfig/ip6tables-config </a></dt><dt> /etc/sysconfig/keyboard , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-kybd"> /etc/sysconfig/keyboard </a></dt><dt> /etc/sysconfig/ldap , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-ldap"> /etc/sysconfig/ldap </a></dt><dt> /etc/sysconfig/named , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-named"> /etc/sysconfig/named </a></dt><dt> /etc/sysconfig/network , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-network"> /etc/sysconfig/network </a></dt><dt> /etc/sysconfig/network-scripts/ directory, <a class="indexterm" href="ch-Network_Interfaces.html">Network Interfaces</a>, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt><dd><dl><dt>(see also network)</dt></dl></dd><dt> /etc/sysconfig/networking/ direc
tory, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/ntpd , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-ntpd"> /etc/sysconfig/ntpd </a></dt><dt> /etc/sysconfig/quagga , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-quagga"> /etc/sysconfig/quagga </a></dt><dt> /etc/sysconfig/radvd , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-radvd"> /etc/sysconfig/radvd </a></dt><dt> /etc/sysconfig/rhn/ directory, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt><dt> /etc/sysconfig/samba , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-samba"> /etc/sysconfig/samba </a></dt><dt> /etc/sysconfig/selinux , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-selinux"> /etc/sysconfig/selinux </a></dt><dt> /etc/sysconfig/sen
dmail , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-sendmail"> /etc/sysconfig/sendmail </a></dt><dt> /etc/sysconfig/spamassassin , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-spamd"> /etc/sysconfig/spamassassin </a></dt><dt> /etc/sysconfig/squid , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-squid"> /etc/sysconfig/squid </a></dt><dt> /etc/sysconfig/system-config-users , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-rcu"> /etc/sysconfig/system-config-users </a></dt><dt> /etc/sysconfig/vncservers , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-vncservers"> /etc/sysconfig/vncservers </a></dt><dt> /etc/sysconfig/xinetd , <a class="indexterm" href="ch-The_sysconfig_Directory.html#s2-sysconfig-xinetd"> /etc/sysconfig/xinetd </a></dt><dt>additional information about, <a class="indexterm" href="ch-The_sysconfig_Directory.html">The sysconfig Directory
</a></dt><dt>additional resources, <a class="indexterm" href="s1-sysconfig-additional-resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-sysconfig-additional-resources.html#s2-sysconfig-installed-documentation">Installed Documentation</a></dt></dl></dd><dt>directories in, <a class="indexterm" href="s1-sysconfig-etcsysconf-dir.html">Directories in the /etc/sysconfig/ Directory</a></dt><dt>files found in, <a class="indexterm" href="ch-The_sysconfig_Directory.html#s1-sysconfig-files">Files in the /etc/sysconfig/ Directory</a></dt></dl></dd><dt> sysctl </dt><dd><dl><dt>configuring with /etc/sysctl.conf , <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</a></dt><dt>controlling /proc/sys/ , <a class="indexterm" href="s1-proc-sysctl.html">Using the sysctl Command</a></dt></dl></dd><dt>SysRq (see system request key)</dt><dt>system information</dt><dd><dl><dt>file systems, <a class="indexterm" href="
s1-sysinfo-filesystems.html">File Systems</a></dt><dd><dl><dt> /dev/shm , <a class="indexterm" href="s1-sysinfo-filesystems.html">File Systems</a></dt></dl></dd><dt>gathering, <a class="indexterm" href="ch-Gathering_System_Information.html">Gathering System Information</a></dt><dt>hardware, <a class="indexterm" href="s1-sysinfo-hardware.html">Hardware</a></dt><dt>memory usage, <a class="indexterm" href="s1-sysinfo-memory-usage.html">Memory Usage</a></dt><dt>processes, <a class="indexterm" href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">System Processes</a></dt><dd><dl><dt>currently running, <a class="indexterm" href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">System Processes</a></dt></dl></dd></dl></dd><dt>system request key</dt><dd><dl><dt>enabling, <a class="indexterm" href="s2-proc-dir-sys.html"> /proc/sys/ </a></dt></dl></dd><dt>System Request Key</dt><dd><dl><dt>definition of, <a class="indexterm" href="s2-proc-dir-sys.htm
l"> /proc/sys/ </a></dt><dt>setting timing for, <a class="indexterm" href="s2-proc-dir-sys.html#s3-proc-sys-kernel"> /proc/sys/kernel/ </a></dt></dl></dd><dt> system-config-authentication (see Authentication Configuration Tool )</dt><dt> system-config-date (see time configuration, date configuration)</dt><dt>system-config-kdump (see kdump)</dt><dt> system-config-services (see services configuration)</dt><dt> system-config-users (see user configuration and group configuration)</dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt>time configuration</dt><dd><dl><dt> date , <a class="indexterm" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">Date and Time Setup</a></dt><dt>synchronize with NTP server, <a class="indexterm" href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Network_Time_Protocol">Network Time Protocol Properties</a>, <a class="indexter
m" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html">Network Time Protocol Setup</a></dt><dt> system-config-date , <a class="indexterm" href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time">Date and Time Properties</a></dt></dl></dd><dt>time zone configuration, <a class="indexterm" href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Time_Zone">Time Zone Properties</a></dt><dt>TLB cache (see hugepages)</dt><dt>TLS, <a class="indexterm" href="s1-apache-mod_ssl.html">Setting Up an SSL Server</a></dt><dd><dl><dt>(see also Apache HTTP Server)</dt></dl></dd><dt>tool</dt><dd><dl><dt> Authentication Configuration Tool , <a class="indexterm" href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool">The Authentication Configuration Tool</a></dt></dl></dd><dt> top , <a class="indexterm" href="ch-Gathering_System_Information.html#s1-sysinfo-system-proce
sses">System Processes</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>updating currently installed packages</dt><dd><dl><dt>available updates, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>updating packages with PackageKit</dt><dd><dl><dt>PolicyKit, <a class="indexterm" href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">Updating Packages with Software Update</a></dt></dl></dd><dt>user configuration</dt><dd><dl><dt>adding users, <a class="indexterm" href="Users_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing full name, <a class="indexterm" href="Users_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing home directory, <a class="indexterm" href="Users_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing login shell, <a class="indexterm
" href="Users_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>changing password, <a class="indexterm" href="Users_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>command line configuration, <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt><dd><dl><dt> passwd , <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt><dt> useradd , <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>filtering list of users, <a class="indexterm" href="Users_and_Groups.html#s1-users-configui">User and Group Configuration</a></dt><dt>modify groups for a user, <a class="indexterm" href="Users_and_Groups.html#s2-redhat-config-users-user-new">Adding a New User</a></dt><dt>modifying users, <a class="indexterm" href="Users_and_Groups.html#s2-redhat-config-users-user-new">Adding a New
User</a></dt><dt>password</dt><dd><dl><dt>forcing expiration of, <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>viewing list of users, <a class="indexterm" href="Users_and_Groups.html#s1-users-configui">User and Group Configuration</a></dt></dl></dd><dt> User Manager (see user configuration)</dt><dt>user private groups (see groups)</dt><dd><dl><dt>and shared directories, <a class="indexterm" href="s1-users-groups-private-groups.html#s2-users-groups-rationale">Group Directories</a></dt></dl></dd><dt> useradd command</dt><dd><dl><dt>user account creation using, <a class="indexterm" href="s1-users-tools.html#s2-users-cmd-line">Command Line Configuration</a></dt></dl></dd><dt>users (see user configuration)</dt><dd><dl><dt> /etc/passwd , <a class="indexterm" href="s1-users-groups-standard-users.html">Standard Users</a></dt><dt>additional resources, <a class="indexterm" href="s1-users-groups-additional-resources
.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="s1-users-groups-additional-resources.html#s2-users-groups-documentation">Installed Documentation</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="Users_and_Groups.html">Users and Groups</a></dt><dt>standard, <a class="indexterm" href="s1-users-groups-standard-users.html">Standard Users</a></dt><dt>tools for management of</dt><dd><dl><dt> User Manager , <a class="indexterm" href="s1-users-tools.html">User and Group Management Tools</a></dt><dt> useradd , <a class="indexterm" href="s1-users-tools.html">User and Group Management Tools</a></dt></dl></dd><dt>UID, <a class="indexterm" href="Users_and_Groups.html">Users and Groups</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>V</h3><dl><dt>virtual file system (see proc file system)</dt><dt>virtual files (see proc file system)</dt><dt>virtual host (see Apache HTTP Server)</dt></dl></div><div class="indexdiv"><h
3>W</h3><dl><dt>web server (see Apache HTTP Server)</dt></dl></div><div class="indexdiv"><h3>Y</h3><dl><dt>Yum</dt><dd><dl><dt>Additional Resources, <a class="indexterm" href="sec-Additional_Resources.html">Additional Resources</a></dt><dt>configuring plugins, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring and Disabling Yum Plugins</a></dt><dt>configuring Yum and Yum repositories, <a class="indexterm" href="sec-Configuring_Yum_and_Yum_Repositories.html">Configuring Yum and Yum Repositories</a></dt><dt>disabling plugins, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring and Disabling Yum Plugins</a></dt><dt>displaying packages</dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></d
t></dl></dd><dt>displaying packages with Yum, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>enabling plugins, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring and Disabling Yum Plugins</a></dt><dt>installing a package group with Yum, <a class="indexterm" href="sec-Installing.html">Installing</a></dt><dt>installing with Yum, <a class="indexterm" href="sec-Installing.html">Installing</a></dt><dt>listing packages with Yum, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, L
isting and Displaying Package Information</a></dt><dd><dl><dt>Glob expressions, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum grouplist, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list all, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list available, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displayi
ng_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum list installed, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>yum repolist, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>packages and package groups, <a class="indexterm" href="sec-Packages_and_Package_Groups.html">Packages and Package Groups</a></dt><dt>plugins</dt><dd><dl><dt>PackageKit-yum-plugin, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plugin Descriptions</a></dt><dt>rhnplugin, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plugin Descriptions</a></dt><dt>yum-plugin-protect-packages, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plugin Descriptions</a>
</dt><dt>yum-plugin-security, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plugin Descriptions</a></dt><dt>yum-presto, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plugin Descriptions</a></dt><dt>yum-rhn-plugin, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plugin Descriptions</a></dt></dl></dd><dt>repository, <a class="indexterm" href="sec-Creating_a_Yum_Repository.html">Creating a Yum Repository</a></dt><dt>searching for packages with Yum</dt><dd><dl><dt>yum search, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt></dl></dd><dt>searching packages with Yum, <a class="indexterm" href="sec-Packages_and_Package_Groups.html#sec-Searching_Listing_and_Displaying_Package_Information">Searching, Listing and Displaying Package Information</a></dt><dt>setting [main] options, <a class="indexterm" href="sec-Configuring
_Yum_and_Yum_Repositories.html#sec-Setting_main_Options">Setting [main] Options</a></dt><dt>setting [repository] options, <a class="indexterm" href="sec-Setting_repository_Options.html">Setting [repository] Options</a></dt><dt>uninstalling package groups with Yum, <a class="indexterm" href="sec-Removing.html">Removing</a></dt><dt>uninstalling packages with Yum, <a class="indexterm" href="sec-Removing.html">Removing</a></dt><dd><dl><dt>yum remove package_name, <a class="indexterm" href="sec-Removing.html">Removing</a></dt></dl></dd><dt>variables, <a class="indexterm" href="sec-Using_Yum_Variables.html">Using Yum Variables</a></dt><dt>Yum plugins, <a class="indexterm" href="sec-Yum_Plugins.html">Yum Plugins</a></dt><dt>Yum repositories</dt><dd><dl><dt>configuring Yum and Yum repositories, <a class="indexterm" href="sec-Configuring_Yum_and_Yum_Repositories.html">Configuring Yum and Yum Repositories</a></dt></dl></dd></dl></dd><dt>Yum repositories</dt><dd><dl><dt>viewing Yum rep
ositories with PackageKit, <a class="indexterm" href="sec-Using_Add_Remove_Software.html#sec-Refreshing_Software_Sources_Yum_Repositories">Refreshing Software Sources (Yum Repositories)</a></dt></dl></dd><dt>Yum Updates</dt><dd><dl><dt>checking for updates, <a class="indexterm" href="ch-yum.html#sec-Checking_For_Updates">Checking For Updates</a></dt><dt>updating a single package, <a class="indexterm" href="ch-yum.html#sec-Updating_Packages">Updating Packages</a></dt><dt>updating all packages and dependencies, <a class="indexterm" href="ch-yum.html#sec-Updating_Packages">Updating Packages</a></dt><dt>updating packages, <a class="indexterm" href="ch-yum.html#sec-Updating_Packages">Updating Packages</a></dt><dt>updating security-related packages, <a class="indexterm" href="ch-yum.html#sec-Updating_Security-Related_Packages">Updating Security-Related Packages</a></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="app-Revision_Hist
ory.html"><strong>Prev</strong>Appendix A. Revision History</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/lease-database.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/lease-database.html
new file mode 100644
index 0000000..24c0136
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/lease-database.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2.2. Lease Database</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-dhcp-configuring-server.html" title="6.2. Configuring a DHCP Server" /><link rel="prev" href="s1-dhcp-configuring-server.html" title="6.2. Configuring a DHCP Server" /><link rel="next" href="ch06s02s03.html" title="6.2.3. Starting and Stopping the Server" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp-configuring-server.html"><strong>Prev</strong></a></li><
li class="next"><a accesskey="n" href="ch06s02s03.html"><strong>Next</strong></a></li></ul><div class="section" title="6.2.2. Lease Database" id="lease-database"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="lease-database">6.2.2. Lease Database</h3></div></div></div><div class="para">
+ On the DHCP server, the file <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> stores the DHCP client lease database. Do not change this file. DHCP lease information for each recently assigned IP address is automatically stored in the lease database. The information includes the length of the lease, to whom the IP address has been assigned, the start and end dates for the lease, and the MAC address of the network interface card that was used to retrieve the lease.
+ </div><div class="para">
+ All times in the lease database are in Coordinated Universal Time (UTC), not local time.
+ </div><div class="para">
+ The lease database is recreated from time to time so that it is not too large. First, all known leases are saved in a temporary lease database. The <code class="filename">dhcpd.leases</code> file is renamed <code class="filename">dhcpd.leases~</code> and the temporary lease database is written to <code class="filename">dhcpd.leases</code>.
+ </div><div class="para">
+ The DHCP daemon could be killed or the system could crash after the lease database has been renamed to the backup file but before the new file has been written. If this happens, the <code class="filename">dhcpd.leases</code> file does not exist, but it is required to start the service. Do not create a new lease file. If you do, all old leases are lost which causes many problems. The correct solution is to rename the <code class="filename">dhcpd.leases~</code> backup file to <code class="filename">dhcpd.leases</code> and then start the daemon.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp-configuring-server.html"><strong>Prev</strong>6.2. Configuring a DHCP Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch06s02s03.html"><strong>Next</strong>6.2.3. Starting and Stopping the Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/pr01.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/pr01.html
new file mode 100644
index 0000000..6f22926
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/pr01.html
@@ -0,0 +1,95 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Preface</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="index.html" title="Deployment Guide" /><link rel="next" href="sect-RedHat-We_Need_Feedback.html" title="2. We Need Feedback!" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-RedHat-We_Need_Feedback.html"><strong>Next</strong
></a></li></ul><div xml:lang="en-US" class="preface" title="Preface" id="id831893" lang="en-US"><div class="titlepage"><div><div><h1 id="id831893" class="title">Preface</h1></div></div></div><div xml:lang="en-US" class="section" title="1. Document Conventions" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="id698112">1. Document Conventions</h2></div></div></div><div class="para">
+ This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.
+ </div><div class="para">
+ In PDF and paper editions, this manual uses typefaces drawn from the <a href="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</a> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.
+ </div><div class="section" title="1.1. Typographic Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id698088">1.1. Typographic Conventions</h3></div></div></div><div class="para">
+ Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.
+ </div><div class="para">
+ <code class="literal">Mono-spaced Bold</code>
+ </div><div class="para">
+ Used to highlight system input, including shell commands, file names and paths. Also used to highlight keycaps and key combinations. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ To see the contents of the file <code class="filename">my_next_bestselling_novel</code> in your current working directory, enter the <code class="command">cat my_next_bestselling_novel</code> command at the shell prompt and press <span class="keycap"><strong>Enter</strong></span> to execute the command.
+ </div></blockquote></div><div class="para">
+ The above includes a file name, a shell command and a keycap, all presented in mono-spaced bold and all distinguishable thanks to context.
+ </div><div class="para">
+ Key combinations can be distinguished from keycaps by the hyphen connecting each part of a key combination. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to execute the command.
+ </div><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> to switch to the first virtual terminal. Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F1</strong></span> to return to your X-Windows session.
+ </div></blockquote></div><div class="para">
+ The first paragraph highlights the particular keycap to press. The second highlights two key combinations (each a set of three keycaps with each set pressed simultaneously).
+ </div><div class="para">
+ If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in <code class="literal">mono-spaced bold</code>. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ File-related classes include <code class="classname">filesystem</code> for file systems, <code class="classname">file</code> for files, and <code class="classname">dir</code> for directories. Each class has its own associated set of permissions.
+ </div></blockquote></div><div class="para">
+ <span class="application"><strong>Proportional Bold</strong></span>
+ </div><div class="para">
+ This denotes words or phrases encountered on a system, including application names; dialog box text; labeled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Choose <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Mouse</strong></span> from the main menu bar to launch <span class="application"><strong>Mouse Preferences</strong></span>. In the <span class="guilabel"><strong>Buttons</strong></span> tab, click the <span class="guilabel"><strong>Left-handed mouse</strong></span> check box and click <span class="guibutton"><strong>Close</strong></span> to switch the primary mouse button from the left to the right (making the mouse suitable for use in the left hand).
+ </div><div class="para">
+ To insert a special character into a <span class="application"><strong>gedit</strong></span> file, choose <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>Accessories</strong></span> → <span class="guimenuitem"><strong>Character Map</strong></span> from the main menu bar. Next, choose <span class="guimenu"><strong>Search</strong></span> → <span class="guimenuitem"><strong>Find…</strong></span> from the <span class="application"><strong>Character Map</strong></span> menu bar, type the name of the character in the <span class="guilabel"><strong>Search</strong></span> field and click <span class="guibutton"><strong>Next</strong></span>. The character you sought will be highlighted in the <span class="guilabel"><strong>Character Table</strong></span>. Double-click this highlighted character to place it in the <span class="guilabel"><strong>Text to copy</strong></span> field and then click the <span class="guibutton"><stron
g>Copy</strong></span> button. Now switch back to your document and choose <span class="guimenu"><strong>Edit</strong></span> → <span class="guimenuitem"><strong>Paste</strong></span> from the <span class="application"><strong>gedit</strong></span> menu bar.
+ </div></blockquote></div><div class="para">
+ The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in proportional bold and all distinguishable by context.
+ </div><div class="para">
+ <code class="command"><em class="replaceable"><code>Mono-spaced Bold Italic</code></em></code> or <span class="application"><strong><em class="replaceable"><code>Proportional Bold Italic</code></em></strong></span>
+ </div><div class="para">
+ Whether mono-spaced bold or proportional bold, the addition of italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ To connect to a remote machine using ssh, type <code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>domain.name</code></em></code> at a shell prompt. If the remote machine is <code class="filename">example.com</code> and your username on that machine is john, type <code class="command">ssh john at example.com</code>.
+ </div><div class="para">
+ The <code class="command">mount -o remount <em class="replaceable"><code>file-system</code></em></code> command remounts the named file system. For example, to remount the <code class="filename">/home</code> file system, the command is <code class="command">mount -o remount /home</code>.
+ </div><div class="para">
+ To see the version of a currently installed package, use the <code class="command">rpm -q <em class="replaceable"><code>package</code></em></code> command. It will return a result as follows: <code class="command"><em class="replaceable"><code>package-version-release</code></em></code>.
+ </div></blockquote></div><div class="para">
+ Note the words in bold italics above — username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.
+ </div><div class="para">
+ Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:
+ </div><div class="blockquote"><blockquote class="blockquote"><div class="para">
+ Publican is a <em class="firstterm">DocBook</em> publishing system.
+ </div></blockquote></div></div><div class="section" title="1.2. Pull-quote Conventions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id647258">1.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ Terminal output and source code listings are set off visually from the surrounding text.
+ </div><div class="para">
+ Output sent to a terminal is set in <code class="computeroutput">mono-spaced roman</code> and presented thus:
+ </div><pre class="screen">books Desktop documentation drafts mss photos stuff svn
+books_tests Desktop1 downloads images notes scripts svgs</pre><div class="para">
+ Source-code listings are also set in <code class="computeroutput">mono-spaced roman</code> but add syntax highlighting as follows:
+ </div><pre class="programlisting">package org.<span class="perl_Function">jboss</span>.<span class="perl_Function">book</span>.<span class="perl_Function">jca</span>.<span class="perl_Function">ex1</span>;
+
+<span class="perl_Keyword">import</span> javax.naming.InitialContext;
+
+<span class="perl_Keyword">public</span> <span class="perl_Keyword">class</span> ExClient
+{
+ <span class="perl_Keyword">public</span> <span class="perl_DataType">static</span> <span class="perl_DataType">void</span> <span class="perl_Function">main</span>(String args[])
+ <span class="perl_Keyword">throws</span> Exception
+ {
+ InitialContext iniCtx = <span class="perl_Keyword">new</span> InitialContext();
+ Object ref = iniCtx.<span class="perl_Function">lookup</span>(<span class="perl_String">"EchoBean"</span>);
+ EchoHome home = (EchoHome) ref;
+ Echo echo = home.<span class="perl_Function">create</span>();
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Created Echo"</span>);
+
+ System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
+ }
+}</pre></div><div class="section" title="1.3. Notes and Warnings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id698074">1.3. Notes and Warnings</h3></div></div></div><div class="para">
+ Finally, we use three visual styles to draw attention to information that might otherwise be overlooked.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Notes are tips, shortcuts or alternative approaches to the task at hand. Ignoring a note should have no negative consequences, but you might miss out on a trick that makes your life easier.
+ </div></div></div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Important boxes detail things that are easily missed: configuration changes that only apply to the current session, or services that need restarting before an update will apply. Ignoring a box labeled 'Important' will not cause data loss but may cause irritation and frustration.
+ </div></div></div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Warnings should not be ignored. Ignoring warnings will most likely cause data loss.
+ </div></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong>Deployment Guide</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-RedHat-We_Need_Feedback.html"><strong>Next</strong>2. We Need Feedback!</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-kernel-configuration.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-kernel-configuration.html
new file mode 100644
index 0000000..9aae8e4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-kernel-configuration.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part V. Kernel, Module and Driver Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="testing-upload-method.html" title="21.7.2. Testing the Upload Method" /><link rel="next" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="testing-upload-method.html"><strong>Prev</strong></a></li><li class="next"><a acc
esskey="n" href="ch-Working_with_Kernel_Modules.html"><strong>Next</strong></a></li></ul><div class="part" title="Part V. Kernel, Module and Driver Configuration" id="pt-kernel-configuration"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part V. Kernel, Module and Driver Configuration</h1></div></div></div><div class="partintro" title="Kernel, Module and Driver Configuration" id="id436372"><div></div><div class="para">
+ System administrators can learn about and customize their kernels. Fedora contains kernel tools to assist administrators with their customizations.
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ch-Working_with_Kernel_Modules.html">22. Working with Kernel Modules</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="sec-Displaying_Information_About_a_Module.html">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="sec-Loading_a_Module.html">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="sec-Unloading_a_Module.html">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="sec-Setting_Module_Parameters.html">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="sec-Persistent_Module_Loading.html">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="sec-Specific_Kernel_M
odule_Capabilities.html">22.7. Specific Kernel Module Capabilities</a></span></dt><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">22.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Manually_Upgrading_the_Kernel.html">23. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">23.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">23.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">23.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">23.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">23.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="
s1-kernel-boot-loader.html">23.6. Verifying the Boot Loader</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-kdump.html">24. The <code class="systemitem">kdump</code> Crash Recovery Service</a></span></dt><dd><dl><dt><span class="section"><a href="ch-kdump.html#s1-kdump-configuration">24.1. Configuring the <code class="systemitem">kdump</code> Service</a></span></dt><dt><span class="section"><a href="s1-kdump-crash.html">24.2. Analyzing the Core Dump</a></span></dt><dt><span class="section"><a href="s1-kdump-resources.html">24.3. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="testing-upload-method.html"><strong>Prev</strong>21.7.2. Testing the Upload Method</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Working_with_Kernel_M
odules.html"><strong>Next</strong>Chapter 22. Working with Kernel Modules</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-network-related-config.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-network-related-config.html
new file mode 100644
index 0000000..3e0db9a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-network-related-config.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part II. Network-Related Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="s2-rpm-related-books.html" title="3.5.3. Related Books" /><link rel="next" href="ch-Network_Interfaces.html" title="Chapter 4. Network Interfaces" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-related-books.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Network_Interf
aces.html"><strong>Next</strong></a></li></ul><div class="part" title="Part II. Network-Related Configuration" id="pt-network-related-config"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part II. Network-Related Configuration</h1></div></div></div><div class="partintro" title="Network-Related Configuration" id="id435268"><div></div><div class="para">
+ After explaining how to configure the network, this part discusses topics related to networking such as how to allow remote logins, share files and directories over the network, and set up a Web server.
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ch-Network_Interfaces.html">4. Network Interfaces</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Network_Interfaces.html#s1-networkscripts-files">4.1. Network Configuration Files</a></span></dt><dt><span class="section"><a href="s1-networkscripts-interfaces.html">4.2. Interface Configuration Files</a></span></dt><dt><span class="section"><a href="s1-networkscripts-control.html">4.3. Interface Control Scripts</a></span></dt><dt><span class="section"><a href="s1-networkscripts-static-routes.html">4.4. Configuring Static Routes</a></span></dt><dt><span class="section"><a href="s1-networkscripts-functions.html">4.5. Network Function Files</a></span></dt><dt><span class="section"><a href="s1-networkscripts-resources.html">4.6. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Network_Configuration.html">5. Network Configuration</a></span>
</dt><dd><dl><dt><span class="section"><a href="ch-Network_Configuration.html#sec-The_NetworkManager_Daemon">5.1. The NetworkManager Daemon</a></span></dt><dt><span class="section"><a href="sec-Interacting_with_NetworkManager.html">5.2. Interacting with NetworkManager</a></span></dt><dt><span class="section"><a href="sec-Configuring_Connection_Settings.html">5.3. Configuring Connection Settings</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html">6. Dynamic Host Configuration Protocol (DHCP)</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html#s1-dhcp-why">6.1. Why Use DHCP?</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-server.html">6.2. Configuring a DHCP Server</a></span></dt><dt><span class="section"><a href="s1-dhcp-configuring-client.html">6.3. Configuring a DHCP Client</a></span></dt><dt><span class="section"><a href="sect-Configuring_a
_Multihomed_DHCP_Server.html">6.4. Configuring a Multihomed DHCP Server</a></span></dt><dt><span class="section"><a href="s1-dhcp_for_ipv6_dhcpv6.html">6.5. DHCP for IPv6 (DHCPv6)</a></span></dt><dt><span class="section"><a href="s1-dhcp-additional-resources.html">6.6. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Controlling_Access_to_Services.html">7. Controlling Access to Services</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Controlling_Access_to_Services.html#s1-services-runlevels">7.1. Configuring the Default Runlevel</a></span></dt><dt><span class="section"><a href="s1-services-configuring.html">7.2. Configuring the Services</a></span></dt><dt><span class="section"><a href="s1-services-running.html">7.3. Running the Services</a></span></dt><dt><span class="section"><a href="s1-services-additional-resources.html">7.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Authentication_C
onfiguration.html">8. Authentication Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Authentication_Configuration.html#sect-The_Authentication_Configuration_Tool">8.1. The Authentication Configuration Tool</a></span></dt><dt><span class="section"><a href="chap-SSSD_User_Guide-Introduction.html">8.2. The System Security Services Daemon (SSSD)</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-OpenSSH.html">9. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">9.1. The SSH Protocol</a></span></dt><dt><span class="section"><a href="s1-ssh-configuration.html">9.2. An OpenSSH Configuration</a></span></dt><dt><span class="section"><a href="s1-ssh-clients.html">9.3. OpenSSH Clients</a></span></dt><dt><span class="section"><a href="s1-ssh-beyondshell.html">9.4. More Than a Secure Shell</a></span></dt><dt><span class="section"><a href="s1-openssh-additional-resources.html">9.5. Additional Resources
</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-The_BIND_DNS_Server.html">10. The BIND DNS Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_BIND_DNS_Server.html#s1-bind-introduction">10.1. Introduction to DNS</a></span></dt><dt><span class="section"><a href="s1-bind-namedconf.html">10.2. Configuring the <code class="command">named</code> Service</a></span></dt><dt><span class="section"><a href="s1-bind-zone.html">10.3. Editing Zone Files</a></span></dt><dt><span class="section"><a href="s1-bind-rndc.html">10.4. Using the <code class="command">rndc</code> Utility</a></span></dt><dt><span class="section"><a href="s1-bind-dig.html">10.5. Using the <code class="command">dig</code> Utility</a></span></dt><dt><span class="section"><a href="s1-bind-features.html">10.6. Advanced Features of BIND</a></span></dt><dt><span class="section"><a href="s1-bind-mistakes.html">10.7. Common Mistakes to Avoid</a></span></dt><dt><span class="section"><a hre
f="s1-bind-additional-resources.html">10.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-The_Apache_HTTP_Server.html">11. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_Apache_HTTP_Server.html#s1-apache-version2">11.1. The Apache HTTP Server 2.2</a></span></dt><dt><span class="section"><a href="s1-apache-running.html">11.2. Running the <code class="systemitem">httpd</code> Service</a></span></dt><dt><span class="section"><a href="s1-apache-editing.html">11.3. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="s1-apache-dso.html">11.4. Working with Modules</a></span></dt><dt><span class="section"><a href="s1-apache-virtualhosts.html">11.5. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="s1-apache-mod_ssl.html">11.6. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="s1-apache-resources.html">11.7. Additional Resource
s</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-email.html">12. Email</a></span></dt><dd><dl><dt><span class="section"><a href="ch-email.html#s1-email-protocols">12.1. Email Protocols</a></span></dt><dt><span class="section"><a href="s1-email-types.html">12.2. Email Program Classifications</a></span></dt><dt><span class="section"><a href="s1-email-mta.html">12.3. Mail Transport Agents</a></span></dt><dt><span class="section"><a href="s1-email-mda.html">12.4. Mail Delivery Agents</a></span></dt><dt><span class="section"><a href="s1-email-mua.html">12.5. Mail User Agents</a></span></dt><dt><span class="section"><a href="s1-email-additional-resources.html">12.6. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-related-books.html"><strong>Prev</strong>3.5.3. Related Books</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a acces
skey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Network_Interfaces.html"><strong>Next</strong>Chapter 4. Network Interfaces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-pkg-management.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-pkg-management.html
new file mode 100644
index 0000000..37bb330
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-pkg-management.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part I. Package Management</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="ch-intro.html" title="Introduction" /><link rel="next" href="ch-yum.html" title="Chapter 1. Yum" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-intro.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-yum.html"><strong>Next</strong></a></li></ul><div class="part" title="Part I
. Package Management" id="pt-pkg-management"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part I. Package Management</h1></div></div></div><div class="partintro" title="Package Management" id="id669418"><div></div><div class="para">
+ All software on a Fedora system is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages on Fedora using the <span class="application"><strong>Yum</strong></span> and <span class="application"><strong>RPM</strong></span> package managers and the <span class="application"><strong>PackageKit</strong></span> suite of graphical package management tools.
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ch-yum.html">1. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages">1.1. Checking For and Updating Packages</a></span></dt><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">1.2. Packages and Package Groups</a></span></dt><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">1.3. Configuring Yum and Yum Repositories</a></span></dt><dt><span class="section"><a href="sec-Yum_Plugins.html">1.4. Yum Plugins</a></span></dt><dt><span class="section"><a href="sec-Additional_Resources.html">1.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-PackageKit.html">2. PackageKit</a></span></dt><dd><dl><dt><span class="section"><a href="ch-PackageKit.html#sec-Updating_Packages_with_Software_Update">2.1. Updating Packages with Software Update</a></spa
n></dt><dt><span class="section"><a href="sec-Using_Add_Remove_Software.html">2.2. Using Add/Remove Software</a></span></dt><dt><span class="section"><a href="sec-PackageKit_Architecture.html">2.3. PackageKit Architecture</a></span></dt><dt><span class="section"><a href="ch-Graphical_Package_Management-sec-Additional_Resources.html">2.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-RPM.html">3. RPM</a></span></dt><dd><dl><dt><span class="section"><a href="ch-RPM.html#s1-rpm-design">3.1. RPM Design Goals</a></span></dt><dt><span class="section"><a href="s1-rpm-using.html">3.2. Using RPM</a></span></dt><dt><span class="section"><a href="s1-check-rpm-sig.html">3.3. Checking a Package's Signature</a></span></dt><dt><span class="section"><a href="s1-rpm-impressing.html">3.4. Practical and Common Examples of RPM Usage</a></span></dt><dt><span class="section"><a href="s1-rpm-additional-resources.html">3.5. Additional Resources</a></span></dt><
/dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-intro.html"><strong>Prev</strong>Introduction</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-yum.html"><strong>Next</strong>Chapter 1. Yum</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-sysconfig.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-sysconfig.html
new file mode 100644
index 0000000..a12fdd3
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-sysconfig.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part III. System Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="s2-email-related-books.html" title="12.6.3. Related Books" /><link rel="next" href="chap-Date_and_Time_Configuration.html" title="Chapter 13. Date and Time Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-related-books.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="
n" href="chap-Date_and_Time_Configuration.html"><strong>Next</strong></a></li></ul><div class="part" title="Part III. System Configuration" id="pt-sysconfig"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part III. System Configuration</h1></div></div></div><div class="partintro" title="System Configuration" id="id668600"><div></div><div class="para">
+ Part of a system administrator's job is configuring the system for various tasks, types of users, and hardware configurations. This section explains how to configure a Fedora system.
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="chap-Date_and_Time_Configuration.html">13. Date and Time Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="chap-Date_and_Time_Configuration.html#sect-Date_and_Time_Configuration-Date_and_Time_Properties_Tool">13.1. Date/Time Properties Tool</a></span></dt><dt><span class="section"><a href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html">13.2. Command Line Configuration</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Keyboard_Configuration.html">14. Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Keyboard_Configuration.html#s1-keyboard-layout">14.1. Changing the Keyboard Layout</a></span></dt><dt><span class="section"><a href="s1-keyboard-indicator.html">14.2. Adding the Keyboard Layout Indicator</a></span></dt><dt><span class="section"><a href="s1-keyboard-break.html">14.3. Setting Up a Typi
ng Break</a></span></dt></dl></dd><dt><span class="chapter"><a href="Users_and_Groups.html">15. Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="Users_and_Groups.html#s1-users-configui">15.1. User and Group Configuration</a></span></dt><dt><span class="section"><a href="s1-users-tools.html">15.2. User and Group Management Tools</a></span></dt><dt><span class="section"><a href="s1-users-groups-standard-users.html">15.3. Standard Users</a></span></dt><dt><span class="section"><a href="s1-users-groups-standard-groups.html">15.4. Standard Groups</a></span></dt><dt><span class="section"><a href="s1-users-groups-private-groups.html">15.5. User Private Groups</a></span></dt><dt><span class="section"><a href="s1-users-groups-shadow-utilities.html">15.6. Shadow Passwords</a></span></dt><dt><span class="section"><a href="s1-users-groups-additional-resources.html">15.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Automat
ed_Tasks.html">16. Automated Tasks</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Automated_Tasks.html#s1-autotasks-cron-anacron">16.1. Cron and Anacron</a></span></dt><dt><span class="section"><a href="s1-autotasks-at-batch.html">16.2. At and Batch</a></span></dt><dt><span class="section"><a href="s1-autotasks-additional-resources.html">16.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Log_Files.html">17. Log Files</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Log_Files.html#s1-configuring-rsyslog">17.1. Configuring <code class="command">rsyslog</code> </a></span></dt><dt><span class="section"><a href="s1-rsyslog-performance.html">17.2. <code class="command">rsyslog</code> Performance</a></span></dt><dt><span class="section"><a href="s1-logfiles-locating.html">17.3. Locating Log Files</a></span></dt><dt><span class="section"><a href="s1-logfiles-viewing.html">17.4. Viewing Log Files</a></span></dt><dt><spa
n class="section"><a href="s1-logfiles-adding.html">17.5. Adding a Log File</a></span></dt><dt><span class="section"><a href="s1-logfiles-examining.html">17.6. Monitoring Log Files</a></span></dt><dt><span class="section"><a href="s1-log-files-additional-resources.html">17.7. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-The_sysconfig_Directory.html">18. The sysconfig Directory</a></span></dt><dd><dl><dt><span class="section"><a href="ch-The_sysconfig_Directory.html#s1-sysconfig-files">18.1. Files in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="s1-sysconfig-etcsysconf-dir.html">18.2. Directories in the <code class="filename">/etc/sysconfig/</code> Directory</a></span></dt><dt><span class="section"><a href="s1-sysconfig-additional-resources.html">18.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-proc.html">19. The <code class="filename
">proc</code> File System</a></span></dt><dd><dl><dt><span class="section"><a href="ch-proc.html#s1-proc-virtual">19.1. A Virtual File System</a></span></dt><dt><span class="section"><a href="s1-proc-topfiles.html">19.2. Top-level Files within the <code class="filename">proc</code> File System</a></span></dt><dt><span class="section"><a href="s1-proc-directories.html">19.3. Directories within <code class="filename">/proc/</code> </a></span></dt><dt><span class="section"><a href="s1-proc-sysctl.html">19.4. Using the <code class="command">sysctl</code> Command</a></span></dt><dt><span class="section"><a href="s1-proc-additional-resources.html">19.5. References</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-related-books.html"><strong>Prev</strong>12.6.3. Related Books</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>H
ome</strong></a></li><li class="next"><a accesskey="n" href="chap-Date_and_Time_Configuration.html"><strong>Next</strong>Chapter 13. Date and Time Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-system-monitoring.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-system-monitoring.html
new file mode 100644
index 0000000..8caf829
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/pt-system-monitoring.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Part IV. System Monitoring</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="index.html" title="Deployment Guide" /><link rel="prev" href="s1-proc-additional-resources.html" title="19.5. References" /><link rel="next" href="ch-Gathering_System_Information.html" title="Chapter 20. Gathering System Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-additional-resources.html"><strong>Prev</strong></a></li><li class="next"><a acce
sskey="n" href="ch-Gathering_System_Information.html"><strong>Next</strong></a></li></ul><div class="part" title="Part IV. System Monitoring" id="pt-system-monitoring"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part IV. System Monitoring</h1></div></div></div><div class="partintro" title="System Monitoring" id="id465605"><div></div><div class="para">
+ System administrators also monitor system performance. Fedora contains tools to assist administrators with these tasks.
+ </div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="chapter"><a href="ch-Gathering_System_Information.html">20. Gathering System Information</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Gathering_System_Information.html#s1-sysinfo-system-processes">20.1. System Processes</a></span></dt><dt><span class="section"><a href="s1-sysinfo-memory-usage.html">20.2. Memory Usage</a></span></dt><dt><span class="section"><a href="s1-sysinfo-filesystems.html">20.3. File Systems</a></span></dt><dt><span class="section"><a href="s1-sysinfo-hardware.html">20.4. Hardware</a></span></dt><dt><span class="section"><a href="s1-sysinfo-additional-resources.html">20.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-abrt.html">21. ABRT</a></span></dt><dd><dl><dt><span class="section"><a href="ch-abrt.html#id544620">21.1. Overview</a></span></dt><dt><span class="section"><a href="ch21s02.html">21.2. Installing and Running
ABRT</a></span></dt><dt><span class="section"><a href="abrt-plugins.html">21.3. <span class="application"><strong>ABRT</strong></span> Plugins</a></span></dt><dt><span class="section"><a href="generating-backtrace.html">21.4. Generating Backtraces</a></span></dt><dt><span class="section"><a href="ch21s05.html">21.5. Using the Command Line Interface</a></span></dt><dt><span class="section"><a href="configuring.html">21.6. Configuring ABRT</a></span></dt><dt><span class="section"><a href="configuring-centralized-crash-collection.html">21.7. Configuring Centralized Crash Collection</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-additional-resources.html"><strong>Prev</strong>19.5. References</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Gathering_Syste
m_Information.html"><strong>Next</strong>Chapter 20. Gathering System Information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/reporter-plugins.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/reporter-plugins.html
new file mode 100644
index 0000000..fc91b72
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/reporter-plugins.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.3.2. Reporter Plugins</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="abrt-plugins.html" title="21.3. ABRT Plugins" /><link rel="prev" href="abrt-plugins.html" title="21.3. ABRT Plugins" /><link rel="next" href="configuring-plugins-in-the-gui.html" title="21.3.3. Plugin Configuration in the GUI" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="abrt-plugins.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="confi
guring-plugins-in-the-gui.html"><strong>Next</strong></a></li></ul><div class="section" title="21.3.2. Reporter Plugins" id="reporter-plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="reporter-plugins">21.3.2. Reporter Plugins</h3></div></div></div><div class="para">
+ These plugins gather the crash data acquired by the analyzer plugins, combine the data with any user input (such as comments about the crash, reproducibility, etc.), and provide a specific output. Each of these plugins is configurable in its corresponding configuration file placed in the <code class="filename">/etc/abrt/plugins/</code> directory or in the <span class="application"><strong>ABRT</strong></span> GUI application (for more information on reporter plugin configuration in the <span class="application"><strong>ABRT</strong></span> GUI application, refer to <a class="xref" href="configuring-plugins-in-the-gui.html" title="21.3.3. Plugin Configuration in the GUI">Section 21.3.3, “Plugin Configuration in the GUI”</a>).
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">RHTSupport</span></dt><dd><div class="para">
+ — Reports crashes into the Red Hat Technical Support system. Intended for users of Fedora.
+ </div></dd><dt class="varlistentry"><span class="term">MailX</span></dt><dd><div class="para">
+ — Sends a crash report via the <span class="application"><strong>mailx</strong></span> utility to a specified email address.
+ </div></dd><dt class="varlistentry"><span class="term">Report Uploader</span></dt><dd><div class="para">
+ — Uploads a tarball with crash data into a <code class="systemitem">FTP</code>/<code class="systemitem">SCP</code> server
+ </div></dd><dt class="varlistentry"><span class="term">Bugzilla</span></dt><dd><div class="para">
+ — Reports crashes into Bugzilla in the form of Bugzilla database entries.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The use of the Bugzilla plugin to report crashes into Bugzilla in the form of Bugzilla database entries is strongly discouraged. Please use the RHTSupport plugin to report crashes into the Red Hat Ticketing System instead.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Logger</span></dt><dd><div class="para">
+ — Creates a crash report and saves it to a specified local file.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="abrt-plugins.html"><strong>Prev</strong>21.3. ABRT Plugins</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="configuring-plugins-in-the-gui.html"><strong>Next</strong>21.3.3. Plugin Configuration in the GUI</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-dso.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-dso.html
new file mode 100644
index 0000000..45ab89b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-dso.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.4. Working with Modules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_Apache_HTTP_Server.html" title="Chapter 11. The Apache HTTP Server" /><link rel="prev" href="s2-apache-mpm-common.html" title="11.3.3. Common Multi-Processing Module Directives" /><link rel="next" href="s2-apache-dso-writing.html" title="11.4.2. Writing a Module" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-mpm-common.html"><strong>Prev</strong></a
></li><li class="next"><a accesskey="n" href="s2-apache-dso-writing.html"><strong>Next</strong></a></li></ul><div class="section" title="11.4. Working with Modules" id="s1-apache-dso"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-dso">11.4. Working with Modules</h2></div></div></div><a id="id466051" class="indexterm"></a><a id="id466072" class="indexterm"></a><div class="para">
+ Being a modular application, the <code class="systemitem">httpd</code> service is distributed along with a number of <em class="firstterm">Dynamic Shared Objects</em> (<acronym class="acronym">DSO</acronym>s), which can be dynamically loaded or unloaded at runtime as necessary. By default, these modules are located in <code class="filename">/usr/lib/httpd/modules/</code> on 32-bit and in <code class="filename">/usr/lib64/httpd/modules/</code> on 64-bit systems.
+ </div><div class="section" title="11.4.1. Loading a Module" id="s2-apache-dso-loading"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-dso-loading">11.4.1. Loading a Module</h3></div></div></div><a id="id744358" class="indexterm"></a><div class="para">
+ To load a particular DSO module, use the <code class="option">LoadModule</code> directive as described in <a class="xref" href="s1-apache-editing.html#s2-apache-httpdconf-directives" title="11.3.1. Common httpd.conf Directives">Section 11.3.1, “Common <code class="filename">httpd.conf</code> Directives”</a>. Note that modules provided by a separate package often have their own configuration file in the <code class="filename">/etc/httpd/conf.d/</code> directory.
+ </div><div class="example" title="Example 11.79. Loading the mod_ssl DSO" id="example-apache-dso-loading"><h6>Example 11.79. Loading the <code class="systemitem">mod_ssl</code> DSO</h6><div class="example-contents"><pre class="screen">LoadModule ssl_module modules/mod_ssl.so</pre></div></div><br class="example-break" /><div class="para">
+ Once you are finished, restart the web server to reload the configuration. Refer to <a class="xref" href="s3-apache-running-restarting.html" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a> for more information on how to restart the <code class="systemitem">httpd</code> service.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-mpm-common.html"><strong>Prev</strong>11.3.3. Common Multi-Processing Module Directives</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-apache-dso-writing.html"><strong>Next</strong>11.4.2. Writing a Module</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-editing.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-editing.html
new file mode 100644
index 0000000..7604390
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-editing.html
@@ -0,0 +1,949 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.3. Editing the Configuration Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_Apache_HTTP_Server.html" title="Chapter 11. The Apache HTTP Server" /><link rel="prev" href="s3-apache-running-status.html" title="11.2.4. Checking the Service Status" /><link rel="next" href="s2-apache-sslconf-common.html" title="11.3.2. Common ssl.conf Directives" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s3-apache-running-status.html"><strong>Prev</str
ong></a></li><li class="next"><a accesskey="n" href="s2-apache-sslconf-common.html"><strong>Next</strong></a></li></ul><div class="section" title="11.3. Editing the Configuration Files" id="s1-apache-editing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-editing">11.3. Editing the Configuration Files</h2></div></div></div><div class="para">
+ When the <code class="systemitem">httpd</code> service is started, by default, it reads the configuration from locations that are listed in <a class="xref" href="s1-apache-editing.html#table-apache-editing-files" title="Table 11.1. The httpd service configuration files">Table 11.1, “The <code class="systemitem">httpd</code> service configuration files”</a>.
+ </div><div class="table" title="Table 11.1. The httpd service configuration files" id="table-apache-editing-files"><h6>Table 11.1. The <code class="systemitem">httpd</code> service configuration files</h6><div class="table-contents"><table summary="The httpd service configuration files" border="1"><colgroup><col width="33%" /><col width="67%" /></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <a id="id512882" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf/httpd.conf</code>
+ </td><td>
+ The main configuration file.
+ </td></tr><tr><td>
+ <a id="id499706" class="indexterm"></a>
+ <code class="filename">/etc/httpd/conf.d/</code>
+ </td><td>
+ An auxiliary directory for configuration files that are included in the main configuration file.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Although the default configuration should be suitable for most situations, it is a good idea to become at least familiar with some of the more important configuration options. Note that for any changes to take effect, the web server has to be restarted first. Refer to <a class="xref" href="s3-apache-running-restarting.html" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a> for more information on how to restart the <code class="systemitem">httpd</code> service.
+ </div><a id="id499759" class="indexterm"></a><div class="para">
+ To check the configuration for possible errors, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service httpd configtest</code>
+Syntax OK</pre><div class="para">
+ To make the recovery from mistakes easier, it is recommended that you make a copy of the original file before editing it.
+ </div><div class="section" title="11.3.1. Common httpd.conf Directives" id="s2-apache-httpdconf-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-httpdconf-directives">11.3.1. Common <code class="filename">httpd.conf</code> Directives</h3></div></div></div><a id="id499800" class="indexterm"></a><div class="para">
+ The following directives are commonly used in the <code class="filename">/etc/httpd/conf/httpd.conf</code> configuration file:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id795733" class="indexterm"></a>
+ <code class="option"><Directory></code> </span></dt><dd><div class="para">
+ The <code class="option"><Directory></code> directive allows you to apply certain directives to a particular directory only. It takes the following form:
+ </div><pre class="screen"><Directory <em class="replaceable"><code>directory</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Directory></pre><div class="para">
+ The <em class="replaceable"><code>directory</code></em> can be either a full path to an existing directory in the local file system, or a wildcard expression.
+ </div><div class="para">
+ This directive can be used to configure additional <code class="literal">cgi-bin</code> directories for server-side scripts located outside the directory that is specified by <code class="option">ScriptAlias</code>. In this case, the <code class="option">ExecCGI</code> and <code class="option">AddHandler</code> directives must be supplied, and the permissions on the target directory must be set correctly (that is, <code class="literal">0755</code>).
+ </div><div class="example" title="Example 11.1. Using the <Directory> directive" id="example-apache-httpdconf-directory"><h6>Example 11.1. Using the <code class="option"><Directory></code> directive</h6><div class="example-contents"><pre class="screen"><Directory /var/www/html>
+ Options Indexes FollowSymLinks
+ AllowOverride None
+ Order allow,deny
+ Allow from all
+</Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id795842" class="indexterm"></a>
+ <code class="option"><IfDefine></code> </span></dt><dd><div class="para">
+ The <code class="option">IfDefine</code> directive allows you to use certain directives only when a particular parameter is supplied on the command line. It takes the following form:
+ </div><pre class="screen"><IfDefine [<span class="optional">!</span>]<em class="replaceable"><code>parameter</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</IfDefine></pre><div class="para">
+ The <em class="replaceable"><code>parameter</code></em> can be supplied at a shell prompt using the <code class="option">-D</code><em class="replaceable"><code>parameter</code></em> command line option (for example, <code class="command">httpd -DEnableHome</code>). If the optional exclamation mark (that is, <code class="literal">!</code>) is present, the enclosed directives are used only when the parameter is <span class="emphasis"><em>not</em></span> specified.
+ </div><div class="example" title="Example 11.2. Using the <IfDefine> directive" id="example-apache-httpdconf-ifdefine"><h6>Example 11.2. Using the <code class="option"><IfDefine></code> directive</h6><div class="example-contents"><pre class="screen"><IfDefine EnableHome>
+ UserDir public_html
+</IfDefine></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id648560" class="indexterm"></a>
+ <code class="option"><IfModule></code> </span></dt><dd><div class="para">
+ The <code class="option"><IfModule></code> directive allows you to use certain directive only when a particular module is loaded. It takes the following form:
+ </div><pre class="screen"><IfModule [<span class="optional">!</span>]<em class="replaceable"><code>module</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</IfModule></pre><div class="para">
+ The <em class="replaceable"><code>module</code></em> can be identified either by its name, or by the filename. If the optional exclamation mark (that is, <code class="literal">!</code>) is present, the enclosed directives are used only when the module is <span class="emphasis"><em>not</em></span> loaded.
+ </div><div class="example" title="Example 11.3. Using the <IfModule> directive" id="example-apache-httpdconf-ifmodule"><h6>Example 11.3. Using the <code class="option"><IfModule></code> directive</h6><div class="example-contents"><pre class="screen"><IfModule mod_disk_cache.c>
+ CacheEnable disk /
+ CacheRoot /var/cache/mod_proxy
+</IfModule></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id481414" class="indexterm"></a>
+ <code class="option"><Location></code> </span></dt><dd><div class="para">
+ The <code class="option"><Location></code> directive allows you to apply certain directives to a particular URL only. It takes the following form:
+ </div><pre class="screen"><Location <em class="replaceable"><code>url</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Location></pre><div class="para">
+ The <em class="replaceable"><code>url</code></em> can be either a path relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/server-info</code>), or an external URL such as <code class="literal">http://example.com/server-info</code>.
+ </div><div class="example" title="Example 11.4. Using the <Location> directive" id="example-apache-httpdconf-location"><h6>Example 11.4. Using the <code class="option"><Location></code> directive</h6><div class="example-contents"><pre class="screen"><Location /server-info>
+ SetHandler server-info
+ Order deny,allow
+ Deny from all
+ Allow from .example.com
+</Location></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id463686" class="indexterm"></a>
+ <code class="option"><Proxy></code> </span></dt><dd><div class="para">
+ The <code class="option"><Proxy></code> directive allows you to apply certain directives to the proxy server only. It takes the following form:
+ </div><pre class="screen"><Proxy <em class="replaceable"><code>pattern</code></em>>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</Proxy></pre><div class="para">
+ The <em class="replaceable"><code>pattern</code></em> can be an external URL, or a wildcard expression (for example, <code class="literal">http://example.com/*</code>).
+ </div><div class="example" title="Example 11.5. Using the <Proxy> directive" id="example-apache-httpdconf-proxy"><h6>Example 11.5. Using the <code class="option"><Proxy></code> directive</h6><div class="example-contents"><pre class="screen"><Proxy *>
+ Order deny,allow
+ Deny from all
+ Allow from .example.com
+</Proxy></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id463772" class="indexterm"></a>
+ <code class="option"><VirtualHost></code> </span></dt><dd><div class="para">
+ The <code class="option"><VirtualHost></code> directive allows you apply certain directives to particular virtual hosts only. It takes the following form:
+ </div><pre class="screen"><VirtualHost <em class="replaceable"><code>address</code></em>[<span class="optional">:<em class="replaceable"><code>port</code></em></span>]…>
+ <em class="replaceable"><code>directive</code></em>
+ …
+</VirtualHost></pre><div class="para">
+ The <em class="replaceable"><code>address</code></em> can be an IP address, a fully qualified domain name, or a special form as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-virtualhost" title="Table 11.2. Available <VirtualHost> options">Table 11.2, “Available <code class="option"><VirtualHost></code> options”</a>.
+ </div><div class="table" title="Table 11.2. Available <VirtualHost> options" id="table-apache-httpdconf-virtualhost"><h6>Table 11.2. Available <code class="option"><VirtualHost></code> options</h6><div class="table-contents"><table summary="Available <VirtualHost> options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">*</code>
+ </td><td>
+ Represents all IP addresses.
+ </td></tr><tr><td>
+ <code class="option">_default_</code>
+ </td><td>
+ Represents unmatched IP addresses.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.6. Using the <VirtualHost> directive" id="example-apache-httpdconf-virtualhost"><h6>Example 11.6. Using the <code class="option"><VirtualHost></code> directive</h6><div class="example-contents"><pre class="screen"><VirtualHost *:80>
+ ServerAdmin webmaster at penguin.example.com
+ DocumentRoot /www/docs/penguin.example.com
+ ServerName penguin.example.com
+ ErrorLog logs/penguin.example.com-error_log
+ CustomLog logs/penguin.example.com-access_log common
+</VirtualHost></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id640752" class="indexterm"></a>
+ <code class="option">AccessFileName</code> </span></dt><dd><div class="para">
+ The <code class="option">AccessFileName</code> directive allows you to specify the file to be used to customize access control information for each directory. It takes the following form:
+ </div><pre class="screen">AccessFileName <em class="replaceable"><code>filename</code></em>…</pre><a id="id640796" class="indexterm"></a><a id="id640814" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>filename</code></em> is a name of the file to look for in the requested directory. By default, the server looks for <code class="filename">.htaccess</code>.
+ </div><a id="id749192" class="indexterm"></a><a id="id749210" class="indexterm"></a><div class="para">
+ For security reasons, the directive is typically followed by the <code class="literal">Files</code> tag to prevent the files beginning with <code class="filename">.ht</code> from being accessed by web clients. This includes the <code class="filename">.htaccess</code> and <code class="filename">.htpasswd</code> files.
+ </div><div class="example" title="Example 11.7. Using the AccessFileName directive" id="example-apache-httpdconf-accessfilename"><h6>Example 11.7. Using the <code class="option">AccessFileName</code> directive</h6><div class="example-contents"><pre class="screen">AccessFileName .htaccess
+
+<Files ~ "^\.ht">
+ Order allow,deny
+ Deny from all
+ Satisfy All
+</Files></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id749271" class="indexterm"></a>
+ <code class="option">Action</code> </span></dt><dd><div class="para">
+ The <code class="option">Action</code> directive allows you to specify a CGI script to be executed when a certain media type is requested. It takes the following form:
+ </div><pre class="screen">Action <em class="replaceable"><code>content-type</code></em> <em class="replaceable"><code>path</code></em></pre><div class="para">
+ The <em class="replaceable"><code>content-type</code></em> has to be a valid MIME type such as <code class="literal">text/html</code>, <code class="literal">image/png</code>, or <code class="literal">application/pdf</code>. The <em class="replaceable"><code>path</code></em> refers to an existing CGI script, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/cgi-bin/process-image.cgi</code>).
+ </div><div class="example" title="Example 11.8. Using the Action directive" id="example-apache-httpdconf-action"><h6>Example 11.8. Using the <code class="option">Action</code> directive</h6><div class="example-contents"><pre class="screen">Action image/png /cgi-bin/process-image.cgi</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id837417" class="indexterm"></a>
+ <code class="option">AddDescription</code> </span></dt><dd><div class="para">
+ The <code class="option">AddDescription</code> directive allows you to specify a short description to be displayed in server-generated directory listings for a given file. It takes the following form:
+ </div><pre class="screen">AddDescription "<em class="replaceable"><code>description</code></em>" <em class="replaceable"><code>filename</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>description</code></em> should be a short text enclosed in double quotes (that is, <code class="literal">"</code>). The <em class="replaceable"><code>filename</code></em> can be a full filename, a file extension, or a wildcard expression.
+ </div><div class="example" title="Example 11.9. Using the AddDescription directive" id="example-apache-httpdconf-adddescription"><h6>Example 11.9. Using the <code class="option">AddDescription</code> directive</h6><div class="example-contents"><pre class="screen">AddDescription "GZIP compressed tar archive" .tgz</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id825177" class="indexterm"></a>
+ <code class="option">AddEncoding</code> </span></dt><dd><div class="para">
+ The <code class="option">AddEncoding</code> directive allows you to specify an encoding type for a particular file extension. It takes the following form:
+ </div><pre class="screen">AddEncoding <em class="replaceable"><code>encoding</code></em> <em class="replaceable"><code>extension</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>encoding</code></em> has to be a valid MIME encoding such as <code class="literal">x-compress</code>, <code class="literal">x-gzip</code>, etc. The <em class="replaceable"><code>extension</code></em> is a case sensitive file extension, and is conventionally written with a leading dot (for example, <code class="literal">.gz</code>).
+ </div><div class="para">
+ This directive is typically used to instruct web browsers to uncompress certain file types as they are downloaded.
+ </div><div class="example" title="Example 11.10. Using the AddEncoding directive" id="example-apache-httpdconf-addencoding"><h6>Example 11.10. Using the <code class="option">AddEncoding</code> directive</h6><div class="example-contents"><pre class="screen">AddEncoding x-gzip .gz .tgz</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id679081" class="indexterm"></a>
+ <code class="option">AddHandler</code> </span></dt><dd><div class="para">
+ The <code class="option">AddHandler</code> directive allows you to map certain file extensions to a selected handler. It takes the following form:
+ </div><pre class="screen">AddHandler <em class="replaceable"><code>handler</code></em> <em class="replaceable"><code>extension</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>handler</code></em> has to be a name of previously defined handler. The <em class="replaceable"><code>extension</code></em> is a case sensitive file extension, and is conventionally written with a leading dot (for example, <code class="literal">.cgi</code>).
+ </div><div class="para">
+ This directive is typically used to treat files with the <code class="filename">.cgi</code> extension as CGI scripts regardless of the directory they are in. Additionally, it is also commonly used to process server-parsed HTML and image-map files.
+ </div><div class="example" title="Example 11.11. Using the AddHandler option" id="example-apache-httpdconf-addhandler"><h6>Example 11.11. Using the <code class="option">AddHandler</code> option</h6><div class="example-contents"><pre class="screen">AddHandler cgi-script .cgi</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id679183" class="indexterm"></a>
+ <code class="option">AddIcon</code> </span></dt><dd><div class="para">
+ The <code class="option">AddIcon</code> directive allows you to specify an icon to be displayed for a particular file in server-generated directory listings. It takes the following form:
+ </div><pre class="screen">AddIcon <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>pattern</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to an existing icon file, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/icons/folder.png</code>). The <em class="replaceable"><code>pattern</code></em> can be a filename, a file extension, a wildcard expression, or a special form as described in the following table:
+ </div><div class="table" title="Table 11.3. Available AddIcon options" id="table-apache-httpdconf-addicon"><h6>Table 11.3. Available <code class="option">AddIcon</code> options</h6><div class="table-contents"><table summary="Available AddIcon options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">^^DIRECTORY^^</code>
+ </td><td>
+ Represents a directory.
+ </td></tr><tr><td>
+ <code class="option">^^BLANKICON^^</code>
+ </td><td>
+ Represents a blank line.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.12. Using the AddIcon directive" id="example-apache-httpdconf-addicon"><h6>Example 11.12. Using the <code class="option">AddIcon</code> directive</h6><div class="example-contents"><pre class="screen">AddIcon /icons/text.png .txt README</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id467899" class="indexterm"></a>
+ <code class="option">AddIconByEncoding</code> </span></dt><dd><div class="para">
+ The <code class="option">AddIconByEncoding</code> directive allows you to specify an icon to be displayed for a particular encoding type in server-generated directory listings. It takes the following form:
+ </div><pre class="screen">AddIconByEncoding <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>encoding</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to an existing icon file, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/icons/compressed.png</code>). The <em class="replaceable"><code>encoding</code></em> has to be a valid MIME encoding such as <code class="literal">x-compress</code>, <code class="literal">x-gzip</code>, etc.
+ </div><div class="example" title="Example 11.13. Using the AddIconByEncoding directive" id="example-apache-httpdconf-addiconbyencoding"><h6>Example 11.13. Using the <code class="option">AddIconByEncoding</code> directive</h6><div class="example-contents"><pre class="screen">AddIconByEncoding /icons/compressed.png x-compress x-gzip</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id734635" class="indexterm"></a>
+ <code class="option">AddIconByType</code> </span></dt><dd><div class="para">
+ The <code class="option">AddIconByType</code> directive allows you to specify an icon to be displayed for a particular media type in server-generated directory listings. It takes the following form:
+ </div><pre class="screen">AddIconByType <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>content-type</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to an existing icon file, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/icons/text.png</code>). The <em class="replaceable"><code>content-type</code></em> has to be either a valid MIME type (for example, <code class="literal">text/html</code> or <code class="literal">image/png</code>), or a wildcard expression such as <code class="literal">text/*</code>, <code class="literal">image/*</code>, etc.
+ </div><div class="example" title="Example 11.14. Using the AddIconByType directive" id="example-apache-httpdconf-addiconbytype"><h6>Example 11.14. Using the <code class="option">AddIconByType</code> directive</h6><div class="example-contents"><pre class="screen">AddIconByType /icons/video.png video/*</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id637355" class="indexterm"></a>
+ <code class="option">AddLanguage</code> </span></dt><dd><div class="para">
+ The <code class="option">AddLanguage</code> directive allows you to associate a file extension with a specific language. It takes the following form:
+ </div><pre class="screen">AddLanguage <em class="replaceable"><code>language</code></em> <em class="replaceable"><code>extension</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>language</code></em> has to be a valid MIME language such as <code class="literal">cs</code>, <code class="literal">en</code>, or <code class="literal">fr</code>. The <em class="replaceable"><code>extension</code></em> is a case sensitive file extension, and is conventionally written with a leading dot (for example, <code class="literal">.cs</code>).
+ </div><div class="para">
+ This directive is especially useful for web servers that serve content in multiple languages based on the client's language settings.
+ </div><div class="example" title="Example 11.15. Using the AddLanguage directive" id="example-apache-httpdconf-addlanguage"><h6>Example 11.15. Using the <code class="option">AddLanguage</code> directive</h6><div class="example-contents"><pre class="screen">AddLanguage cs .cs .cz</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id637463" class="indexterm"></a>
+ <code class="option">AddType</code> </span></dt><dd><div class="para">
+ The <code class="option">AddType</code> directive allows you to define or override the media type for a particular file extension. It takes the following form:
+ </div><pre class="screen">AddType <em class="replaceable"><code>content-type</code></em> <em class="replaceable"><code>extension</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>content-type</code></em> has to be a valid MIME type such as <code class="literal">text/html</code>, <code class="literal">image/png</code>, etc. The <em class="replaceable"><code>extension</code></em> is a case sensitive file extension, and is conventionally written with a leading dot (for example, <code class="literal">.cs</code>).
+ </div><div class="example" title="Example 11.16. Using the AddType directive" id="example-apache-httpdconf-addtype"><h6>Example 11.16. Using the <code class="option">AddType</code> directive</h6><div class="example-contents"><pre class="screen">AddType application/x-gzip .gz .tgz</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id550318" class="indexterm"></a>
+ <code class="option">Alias</code> </span></dt><dd><div class="para">
+ The <code class="option">Alias</code> directive allows you to refer to files and directories outside the default directory specified by the <code class="option">DocumentRoot</code> directive. It takes the following form:
+ </div><pre class="screen">Alias <em class="replaceable"><code>url-path</code></em> <em class="replaceable"><code>real-path</code></em></pre><div class="para">
+ The <em class="replaceable"><code>url-path</code></em> must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/images/</code>). The <em class="replaceable"><code>real-path</code></em> is a full path to a file or directory in the local file system.
+ </div><a id="id468119" class="indexterm"></a><div class="para">
+ This directive is typically followed by the <code class="option">Directory</code> tag with additional permissions to access the target directory. By default, the <code class="literal">/icons/</code> alias is created so that the icons from <code class="filename">/var/www/icons/</code> are displayed in server-generated directory listings.
+ </div><div class="example" title="Example 11.17. Using the Alias directive" id="example-apache-httpdconf-alias"><h6>Example 11.17. Using the <code class="option">Alias</code> directive</h6><div class="example-contents"><pre class="screen">Alias /icons/ /var/www/icons/
+
+<Directory "/var/www/icons">
+ Options Indexes MultiViews FollowSymLinks
+ AllowOverride None
+ Order allow,deny
+ Allow from all
+<Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id468186" class="indexterm"></a>
+ <code class="option">Allow</code></span></dt><dd><div class="para">
+ The <code class="option">Allow</code> directive allows you to specify which clients have permission to access a given directory. It takes the following form:
+ </div><pre class="screen">Allow from <em class="replaceable"><code>client</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>client</code></em> can be a domain name, an IP address (both full and partial), a <em class="replaceable"><code>network</code></em>/<em class="replaceable"><code>netmask</code></em> pair, or <code class="literal">all</code> for all clients.
+ </div><div class="example" title="Example 11.18. Using the Allow directive" id="example-apache-httpdconf-allow"><h6>Example 11.18. Using the <code class="option">Allow</code> directive</h6><div class="example-contents"><pre class="screen">Allow from 192.168.1.0/255.255.255.0</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id675733" class="indexterm"></a>
+ <code class="option">AllowOverride</code> </span></dt><dd><a id="id675760" class="indexterm"></a><a id="id675779" class="indexterm"></a><div class="para">
+ The <code class="option">AllowOverride</code> directive allows you to specify which directives in a <code class="filename">.htaccess</code> file can override the default configuration. It takes the following form:
+ </div><pre class="screen">AllowOverride <em class="replaceable"><code>type</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>type</code></em> has to be one of the available grouping options as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-allowoverride" title="Table 11.4. Available AllowOverride options">Table 11.4, “Available <code class="option">AllowOverride</code> options”</a>.
+ </div><div class="table" title="Table 11.4. Available AllowOverride options" id="table-apache-httpdconf-allowoverride"><h6>Table 11.4. Available <code class="option">AllowOverride</code> options</h6><div class="table-contents"><table summary="Available AllowOverride options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">All</code>
+ </td><td>
+ All directives in <code class="filename">.htaccess</code> are allowed to override earlier configuration settings.
+ </td></tr><tr><td>
+ <code class="option">None</code>
+ </td><td>
+ No directive in <code class="filename">.htaccess</code> is allowed to override earlier configuration settings.
+ </td></tr><tr><td>
+ <code class="option">AuthConfig</code>
+ </td><td>
+ Allows the use of authorization directives such as <code class="option">AuthName</code>, <code class="option">AuthType</code>, or <code class="option">Require</code>.
+ </td></tr><tr><td>
+ <code class="option">FileInfo</code>
+ </td><td>
+ Allows the use of file type, metadata, and <code class="systemitem">mod_rewrite</code> directives such as <code class="option">DefaultType</code>, <code class="option">RequestHeader</code>, or <code class="option">RewriteEngine</code>, as well as the <code class="option">Action</code> directive.
+ </td></tr><tr><td>
+ <code class="option">Indexes</code>
+ </td><td>
+ Allows the use of directory indexing directives such as <code class="option">AddDescription</code>, <code class="option">AddIcon</code>, or <code class="option">FancyIndexing</code>.
+ </td></tr><tr><td>
+ <code class="option">Limit</code>
+ </td><td>
+ Allows the use of host access directives, that is, <code class="option">Allow</code>, <code class="option">Deny</code>, and <code class="option">Order</code>.
+ </td></tr><tr><td>
+ <code class="option">Options</code>[<span class="optional">=<em class="replaceable"><code>option</code></em>,…</span>]
+ </td><td>
+ Allows the use of the <code class="option">Options</code> directive. Additionally, you can provide a comma-separated list of options to customize which options can be set using this directive.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.19. Using the AllowOverride directive" id="example-apache-httpdconf-allowoverride"><h6>Example 11.19. Using the <code class="option">AllowOverride</code> directive</h6><div class="example-contents"><pre class="screen">AllowOverride FileInfo AuthConfig Limit</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id459024" class="indexterm"></a>
+ <code class="option">BrowserMatch</code> </span></dt><dd><div class="para">
+ The <code class="option">BrowserMatch</code> directive allows you to modify the server behavior based on the client's web browser type. It takes the following form:
+ </div><pre class="screen">BrowserMatch <em class="replaceable"><code>pattern</code></em> <em class="replaceable"><code>variable</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>pattern</code></em> is a regular expression to match the User-Agent HTTP header field. The <em class="replaceable"><code>variable</code></em> is an environment variable that is set when the header field matches the pattern.
+ </div><div class="para">
+ By default, this directive is used to deny connections to specific browsers with known issues, and to disable keepalives and HTTP header flushes for browsers that are known to have problems with these actions.
+ </div><div class="example" title="Example 11.20. Using the BrowserMatch directive" id="example-apache-httpdconf-browsermatch"><h6>Example 11.20. Using the <code class="option">BrowserMatch</code> directive</h6><div class="example-contents"><pre class="screen">BrowserMatch "Mozilla/2" nokeepalive</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id485244" class="indexterm"></a>
+ <code class="option">CacheDefaultExpire</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheDefaultExpire</code> option allows you to set how long to cache a document that does not have any expiration date or the date of its last modification specified. It takes the following form:
+ </div><pre class="screen">CacheDefaultExpire <em class="replaceable"><code>time</code></em></pre><div class="para">
+ The <em class="replaceable"><code>time</code></em> specified in seconds. The default option is <code class="literal">3600</code> (that is, one hour).
+ </div><div class="example" title="Example 11.21. Using the CacheDefaultExpire directive" id="example-apache-httpdconf-cachedefaultexpire"><h6>Example 11.21. Using the <code class="option">CacheDefaultExpire</code> directive</h6><div class="example-contents"><pre class="screen">CacheDefaultExpire 3600</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id485324" class="indexterm"></a>
+ <code class="option">CacheDisable</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheDisable</code> directive allows you to disable caching of certain URLs. It takes the following form:
+ </div><pre class="screen">CacheDisable <em class="replaceable"><code>path</code></em></pre><div class="para">
+ The <em class="replaceable"><code>path</code></em> must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/files/</code>).
+ </div><div class="example" title="Example 11.22. Using the CacheDisable directive" id="example-apache-httpdconf-cachedisable"><h6>Example 11.22. Using the <code class="option">CacheDisable</code> directive</h6><div class="example-contents"><pre class="screen">CacheDisable /temporary</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id456379" class="indexterm"></a>
+ <code class="option">CacheEnable</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheEnable</code> directive allows you to specify a cache type to be used for certain URLs. It takes the following form:
+ </div><pre class="screen">CacheEnable <em class="replaceable"><code>type</code></em> <em class="replaceable"><code>url</code></em></pre><div class="para">
+ The <em class="replaceable"><code>type</code></em> has to be a valid cache type as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-cacheenable" title="Table 11.5. Available cache types">Table 11.5, “Available cache types”</a>. The <em class="replaceable"><code>url</code></em> can be a path relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/images/</code>), a protocol (for example, <code class="literal">ftp://</code>), or an external URL such as <code class="literal">http://example.com/</code>.
+ </div><div class="table" title="Table 11.5. Available cache types" id="table-apache-httpdconf-cacheenable"><h6>Table 11.5. Available cache types</h6><div class="table-contents"><table summary="Available cache types" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Type
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">mem</code>
+ </td><td>
+ The memory-based storage manager.
+ </td></tr><tr><td>
+ <code class="option">disk</code>
+ </td><td>
+ The disk-based storage manager.
+ </td></tr><tr><td>
+ <code class="option">fd</code>
+ </td><td>
+ The file descriptor cache.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.23. Using the CacheEnable directive" id="example-apache-httpdconf-cacheenable"><h6>Example 11.23. Using the <code class="option">CacheEnable</code> directive</h6><div class="example-contents"><pre class="screen">CacheEnable disk /</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id539801" class="indexterm"></a>
+ <code class="option">CacheLastModifiedFactor</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheLastModifiedFactor</code> directive allows you to customize how long to cache a document that does not have any expiration date specified, but that provides information about the date of its last modification. It takes the following form:
+ </div><pre class="screen">CacheLastModifiedFactor <em class="replaceable"><code>number</code></em></pre><div class="para">
+ The <em class="replaceable"><code>number</code></em> is a coefficient to be used to multiply the time that passed since the last modification of the document. The default option is <code class="literal">0.1</code> (that is, one tenth).
+ </div><div class="example" title="Example 11.24. Using the CacheLastModifiedFactor directive" id="example-apache-httpdconf-cachelastmodifiedfactor"><h6>Example 11.24. Using the <code class="option">CacheLastModifiedFactor</code> directive</h6><div class="example-contents"><pre class="screen">CacheLastModifiedFactor 0.1</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id472448" class="indexterm"></a>
+ <code class="option">CacheMaxExpire</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheMaxExpire</code> directive allows you to specify the maximum amount of time to cache a document. It takes the following form:
+ </div><pre class="screen">CacheMaxExpire <em class="replaceable"><code>time</code></em></pre><div class="para">
+ The <em class="replaceable"><code>time</code></em> is specified in seconds. The default option is <code class="literal">86400</code> (that is, one day).
+ </div><div class="example" title="Example 11.25. Using the CacheMaxExpire directive" id="example-apache-httpdconf-cachemaxexpire"><h6>Example 11.25. Using the <code class="option">CacheMaxExpire</code> directive</h6><div class="example-contents"><pre class="screen">CacheMaxExpire 86400</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id651210" class="indexterm"></a>
+ <code class="option">CacheNegotiatedDocs</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheNegotiatedDocs</code> directive allows you to enable caching of the documents that were negotiated on the basis of content. It takes the following form:
+ </div><pre class="screen">CacheNegotiatedDocs <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-cachenegotiateddocs" title="Table 11.6. Available CacheNegotiatedDocs options">Table 11.6, “Available <code class="option">CacheNegotiatedDocs</code> options”</a>. Since the content-negotiated documents may change over time or because of the input from the requester, the default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.6. Available CacheNegotiatedDocs options" id="table-apache-httpdconf-cachenegotiateddocs"><h6>Table 11.6. Available <code class="option">CacheNegotiatedDocs</code> options</h6><div class="table-contents"><table summary="Available CacheNegotiatedDocs options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables caching the content-negotiated documents.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables caching the content-negotiated documents.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.26. Using the CacheNegotiatedDocs directive" id="example-apache-httpdconf-cachenegotiateddocs"><h6>Example 11.26. Using the <code class="option">CacheNegotiatedDocs</code> directive</h6><div class="example-contents"><pre class="screen">CacheNegotiatedDocs On</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1703726" class="indexterm"></a>
+ <code class="option">CacheRoot</code> </span></dt><dd><div class="para">
+ The <code class="option">CacheRoot</code> directive allows you to specify the directory to store cache files in. It takes the following form:
+ </div><pre class="screen">CacheRoot <em class="replaceable"><code>directory</code></em></pre><a id="id1703768" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>directory</code></em> must be a full path to an existing directory in the local file system. The default option is <code class="filename">/var/cache/mod_proxy/</code>.
+ </div><div class="example" title="Example 11.27. Using the CacheRoot directive" id="example-apache-httpdconf-cacheroot"><h6>Example 11.27. Using the <code class="option">CacheRoot</code> directive</h6><div class="example-contents"><pre class="screen">CacheRoot /var/cache/mod_proxy</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id679670" class="indexterm"></a>
+ <code class="option">CustomLog</code> </span></dt><dd><div class="para">
+ The <code class="option">CustomLog</code> directive allows you to specify the log filename and the log file format. It takes the following form:
+ </div><pre class="screen">CustomLog <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>format</code></em></pre><a id="id679716" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to a log file, and must be relative to the directory that is specified by the <code class="option">ServerRoot</code> directive (that is, <code class="filename">/etc/httpd/</code> by default). The <em class="replaceable"><code>format</code></em> has to be either an explicit format string, or a format name that was previously defined using the <code class="option">LogFormat</code> directive.
+ </div><div class="example" title="Example 11.28. Using the CustomLog directive" id="example-apache-httpdconf-customlog"><h6>Example 11.28. Using the <code class="option">CustomLog</code> directive</h6><div class="example-contents"><pre class="screen">CustomLog logs/access_log combined</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id634081" class="indexterm"></a>
+ <code class="option">DefaultIcon</code> </span></dt><dd><div class="para">
+ The <code class="option">DefaultIcon</code> directive allows you to specify an icon to be displayed for a file in server-generated directory listings when no other icon is associated with it. It takes the following form:
+ </div><pre class="screen">DefaultIcon <em class="replaceable"><code>path</code></em></pre><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to an existing icon file, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/icons/unknown.png</code>).
+ </div><div class="example" title="Example 11.29. Using the DefaultIcon directive" id="example-apache-httpdconf-defaulticon"><h6>Example 11.29. Using the <code class="option">DefaultIcon</code> directive</h6><div class="example-contents"><pre class="screen">DefaultIcon /icons/unknown.png</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id634166" class="indexterm"></a>
+ <code class="option">DefaultType</code> </span></dt><dd><div class="para">
+ The <code class="option">DefaultType</code> directive allows you to specify a media type to be used in case the proper MIME type cannot be determined by the server. It takes the following form:
+ </div><pre class="screen">DefaultType <em class="replaceable"><code>content-type</code></em></pre><div class="para">
+ The <em class="replaceable"><code>content-type</code></em> has to be a valid MIME type such as <code class="literal">text/html</code>, <code class="literal">image/png</code>, <code class="literal">application/pdf</code>, etc.
+ </div><div class="example" title="Example 11.30. Using the DefaultType directive" id="example-apache-httpdconf-defaulttype"><h6>Example 11.30. Using the <code class="option">DefaultType</code> directive</h6><div class="example-contents"><pre class="screen">DefaultType text/plain</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id576265" class="indexterm"></a>
+ <code class="option">Deny</code> </span></dt><dd><div class="para">
+ The <code class="option">Deny</code> directive allows you to specify which clients are denied access to a given directory. It takes the following form:
+ </div><pre class="screen">Deny from <em class="replaceable"><code>client</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>client</code></em> can be a domain name, an IP address (both full and partial), a <em class="replaceable"><code>network</code></em>/<em class="replaceable"><code>netmask</code></em> pair, or <code class="literal">all</code> for all clients.
+ </div><div class="example" title="Example 11.31. Using the Deny directive" id="example-apache-httpdconf-deny"><h6>Example 11.31. Using the <code class="option">Deny</code> directive</h6><div class="example-contents"><pre class="screen">Deny from 192.168.1.1</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id543296" class="indexterm"></a>
+ <code class="option">DirectoryIndex</code> </span></dt><dd><div class="para">
+ The <code class="option">DirectoryIndex</code> directive allows you to specify a document to be served to a client when a directory is requested (that is, when the URL ends with the <code class="literal">/</code> character). It takes the following form:
+ </div><pre class="screen">DirectoryIndex <em class="replaceable"><code>filename</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>filename</code></em> is a name of the file to look for in the requested directory. By default, the server looks for <code class="filename">index.html</code>, and <code class="filename">index.html.var</code>.
+ </div><div class="example" title="Example 11.32. Using the DirectoryIndex directive" id="example-apache-httpdconf-directoryindex"><h6>Example 11.32. Using the <code class="option">DirectoryIndex</code> directive</h6><div class="example-contents"><pre class="screen">DirectoryIndex index.html index.html.var</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id549569" class="indexterm"></a>
+ <code class="option">DocumentRoot</code> </span></dt><dd><div class="para">
+ The <code class="option">DocumentRoot</code> directive allows you to specify the main directory from which the content is served. It takes the following form:
+ </div><pre class="screen">DocumentRoot <em class="replaceable"><code>directory</code></em></pre><a id="id549611" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>directory</code></em> must be a full path to an existing directory in the local file system. The default option is <code class="filename">/var/www/html/</code>.
+ </div><div class="example" title="Example 11.33. Using the DocumentRoot directive" id="example-apache-httpdconf-documentroot"><h6>Example 11.33. Using the <code class="option">DocumentRoot</code> directive</h6><div class="example-contents"><pre class="screen">DocumentRoot /var/www/html</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id549674" class="indexterm"></a>
+ <code class="option">ErrorDocument</code> </span></dt><dd><div class="para">
+ The <code class="option">ErrorDocument</code> directive allows you to specify a document or a message to be displayed as a response to a particular error. It takes the following form:
+ </div><pre class="screen">ErrorDocument <em class="replaceable"><code>error-code</code></em> <em class="replaceable"><code>action</code></em></pre><div class="para">
+ The <em class="replaceable"><code>error-code</code></em> has to be a valid code such as <code class="literal">403</code> (Forbidden), <code class="literal">404</code> (Not Found), or <code class="literal">500</code> (Internal Server Error). The <em class="replaceable"><code>action</code></em> can be either a URL (both local and external), or a message string enclosed in double quotes (that is, <code class="literal">"</code>).
+ </div><div class="example" title="Example 11.34. Using the ErrorDocument directive" id="example-apache-httpdconf-errordocument"><h6>Example 11.34. Using the <code class="option">ErrorDocument</code> directive</h6><div class="example-contents"><pre class="screen">ErrorDocument 403 "Access Denied"
+ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id832876" class="indexterm"></a>
+ <code class="option">ErrorLog</code> </span></dt><dd><div class="para">
+ The <code class="option">ErrorLog</code> directive allows you to specify a file to which the server errors are logged. It takes the following form:
+ </div><pre class="screen">ErrorLog <em class="replaceable"><code>path</code></em></pre><a id="id832919" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to a log file, and can be either absolute, or relative to the directory that is specified by the <code class="option">ServerRoot</code> directive (that is, <code class="filename">/etc/httpd/</code> by default). The default option is <code class="filename">logs/error_log</code>
+ </div><div class="example" title="Example 11.35. Using the ErrorLog directive" id="example-apache-httpdconf-errorlog"><h6>Example 11.35. Using the <code class="option">ErrorLog</code> directive</h6><div class="example-contents"><pre class="screen">ErrorLog logs/error_log</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id851520" class="indexterm"></a>
+ <code class="option">ExtendedStatus</code> </span></dt><dd><div class="para">
+ The <code class="option">ExtendedStatus</code> directive allows you to enable detailed server status information. It takes the following form:
+ </div><pre class="screen">ExtendedStatus <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-extendedstatus" title="Table 11.7. Available ExtendedStatus options">Table 11.7, “Available <code class="option">ExtendedStatus</code> options”</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.7. Available ExtendedStatus options" id="table-apache-httpdconf-extendedstatus"><h6>Table 11.7. Available <code class="option">ExtendedStatus</code> options</h6><div class="table-contents"><table summary="Available ExtendedStatus options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables generating the detailed server status.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables generating the detailed server status.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.36. Using the ExtendedStatus directive" id="example-apache-httpdconf-extendedstatus"><h6>Example 11.36. Using the <code class="option">ExtendedStatus</code> directive</h6><div class="example-contents"><pre class="screen">ExtendedStatus On</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id781443" class="indexterm"></a>
+ <code class="option">Group</code> </span></dt><dd><div class="para">
+ The <code class="option">Group</code> directive allows you to specify the group under which the <code class="systemitem">httpd</code> service will run. It takes the following form:
+ </div><pre class="screen">Group <em class="replaceable"><code>group</code></em></pre><div class="para">
+ The <em class="replaceable"><code>group</code></em> has to be an existing UNIX group. The default option is <code class="option">apache</code>.
+ </div><div class="para">
+ Note that <code class="option">Group</code> is no longer supported inside <code class="option"><VirtualHost></code>, and has been replaced by the <code class="option">SuexecUserGroup</code> directive.
+ </div><div class="example" title="Example 11.37. Using the Group directive" id="example-apache-httpdconf-group"><h6>Example 11.37. Using the <code class="option">Group</code> directive</h6><div class="example-contents"><pre class="screen">Group apache</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id1824648" class="indexterm"></a>
+ <code class="option">HeaderName</code> </span></dt><dd><div class="para">
+ The <code class="option">HeaderName</code> directive allows you to specify a file to be prepended to the beginning of the server-generated directory listing. It takes the following form:
+ </div><pre class="screen">HeaderName <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ The <em class="replaceable"><code>filename</code></em> is a name of the file to look for in the requested directory. By default, the server looks for <code class="filename">HEADER.html</code>.
+ </div><div class="example" title="Example 11.38. Using the HeaderName directive" id="example-apache-httpdconf-headername"><h6>Example 11.38. Using the <code class="option">HeaderName</code> directive</h6><div class="example-contents"><pre class="screen">HeaderName HEADER.html</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id690613" class="indexterm"></a>
+ <code class="option">HostnameLookups</code> </span></dt><dd><div class="para">
+ The <code class="option">HostnameLookups</code> directive allows you to enable automatic resolving of IP addresses. It takes the following form:
+ </div><pre class="screen">HostnameLookups <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-hostnamelookup" title="Table 11.8. Available HostnameLookups options">Table 11.8, “Available <code class="option">HostnameLookups</code> options”</a>. To conserve resources on the server, the default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.8. Available HostnameLookups options" id="table-apache-httpdconf-hostnamelookup"><h6>Table 11.8. Available <code class="option">HostnameLookups</code> options</h6><div class="table-contents"><table summary="Available HostnameLookups options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables resolving the IP address for each connection so that the hostname can be logged. However, this also adds a significant processing overhead.
+ </td></tr><tr><td>
+ <code class="option">Double</code>
+ </td><td>
+ Enables performing the double-reverse DNS lookup. In comparison to the above option, this adds even more processing overhead.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables resolving the IP address for each connection.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Note that when the presence of hostnames is required in server log files, it is often possible to use one of the many log analyzer tools that perform the DNS lookups more efficiently.
+ </div><div class="example" title="Example 11.39. Using the HostnameLookups directive" id="example-apache-httpdconf-hostnamelookups"><h6>Example 11.39. Using the <code class="option">HostnameLookups</code> directive</h6><div class="example-contents"><pre class="screen">HostnameLookups Off</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id827093" class="indexterm"></a>
+ <code class="option">Include</code> </span></dt><dd><div class="para">
+ The <code class="option">Include</code> directive allows you to include other configuration files. It takes the following form:
+ </div><pre class="screen">Include <em class="replaceable"><code>filename</code></em></pre><a id="id568118" class="indexterm"></a><div class="para">
+ The <code class="option">filename</code> can be an absolute path, a path relative to the directory specified by the <code class="option">ServerRoot</code> directive, or a wildcard expression. All configuration files from the <code class="filename">/etc/httpd/conf.d/</code> directory are loaded by default.
+ </div><div class="example" title="Example 11.40. Using the Include directive" id="example-apache-httpdconf-include"><h6>Example 11.40. Using the <code class="option">Include</code> directive</h6><div class="example-contents"><pre class="screen">Include conf.d/*.conf</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id568183" class="indexterm"></a>
+ <code class="option">IndexIgnore</code> </span></dt><dd><div class="para">
+ The <code class="option">IndexIgnore</code> directive allows you to specify a list of filenames to be omitted from the server-generated directory listings. It takes the following form:
+ </div><pre class="screen">IndexIgnore <em class="replaceable"><code>filename</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>filename</code></em> option can be either a full filename, or a wildcard expression.
+ </div><div class="example" title="Example 11.41. Using the IndexIgnore directive" id="example-apache-httpdconf-indexignore"><h6>Example 11.41. Using the <code class="option">IndexIgnore</code> directive</h6><div class="example-contents"><pre class="screen">IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id726044" class="indexterm"></a>
+ <code class="option">IndexOptions</code> </span></dt><dd><div class="para">
+ The <code class="option">IndexOptions</code> directive allows you to customize the behavior of server-generated directory listings. It takes the following form:
+ </div><pre class="screen">IndexOptions <em class="replaceable"><code>option</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-indexoptions" title="Table 11.9. Available directory listing options">Table 11.9, “Available directory listing options”</a>. The default options are <code class="option">Charset=UTF-8</code>, <code class="option">FancyIndexing</code>, <code class="option">HTMLTable</code>, <code class="option">NameWidth=*</code>, and <code class="option">VersionSort</code>.
+ </div><div class="table" title="Table 11.9. Available directory listing options" id="table-apache-httpdconf-indexoptions"><h6>Table 11.9. Available directory listing options</h6><div class="table-contents"><table summary="Available directory listing options" border="1"><colgroup><col width="33%" /><col width="67%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Charset</code>=<em class="replaceable"><code>encoding</code></em>
+ </td><td>
+ Specifies the character set of a generated web page. The <em class="replaceable"><code>encoding</code></em> has to be a valid character set such as <code class="literal">UTF-8</code> or <code class="literal">ISO-8859-2</code>.
+ </td></tr><tr><td>
+ <code class="option">Type</code>=<em class="replaceable"><code>content-type</code></em>
+ </td><td>
+ Specifies the media type of a generated web page. The <em class="replaceable"><code>content-type</code></em> has to be a valid MIME type such as <code class="literal">text/html</code> or <code class="literal">text/plain</code>.
+ </td></tr><tr><td>
+ <code class="option">DescriptionWidth</code>=<em class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies the width of the description column. The <em class="replaceable"><code>value</code></em> can be either a number of characters, or an asterisk (that is, <code class="literal">*</code>) to adjust the width automatically.
+ </td></tr><tr><td>
+ <code class="option">FancyIndexing</code>
+ </td><td>
+ Enables advanced features such as different icons for certain files or possibility to re-sort a directory listing by clicking on a column header.
+ </td></tr><tr><td>
+ <code class="option">FolderFirst</code>
+ </td><td>
+ Enables listing directories first, always placing them above files.
+ </td></tr><tr><td>
+ <code class="option">HTMLTable</code>
+ </td><td>
+ Enables the use of HTML tables for directory listings.
+ </td></tr><tr><td>
+ <code class="option">IconsAreLinks</code>
+ </td><td>
+ Enables using the icons as links.
+ </td></tr><tr><td>
+ <code class="option">IconHeight</code>=<em class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies an icon height. The <em class="replaceable"><code>value</code></em> is a number of pixels.
+ </td></tr><tr><td>
+ <code class="option">IconWidth</code>=<em class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies an icon width. The <em class="replaceable"><code>value</code></em> is a number of pixels.
+ </td></tr><tr><td>
+ <code class="option">IgnoreCase</code>
+ </td><td>
+ Enables sorting files and directories in a case-sensitive manner.
+ </td></tr><tr><td>
+ <code class="option">IgnoreClient</code>
+ </td><td>
+ Disables accepting query variables from a client.
+ </td></tr><tr><td>
+ <code class="option">NameWidth</code>=<em class="replaceable"><code>value</code></em>
+ </td><td>
+ Specifies the width of the filename column. The <em class="replaceable"><code>value</code></em> can be either a number of characters, or an asterisk (that is, <code class="literal">*</code>) to adjust the width automatically.
+ </td></tr><tr><td>
+ <code class="option">ScanHTMLTitles</code>
+ </td><td>
+ Enables parsing the file for a description (that is, the <code class="literal">title</code> element) in case it is not provided by the <code class="option">AddDescription</code> directive.
+ </td></tr><tr><td>
+ <code class="option">ShowForbidden</code>
+ </td><td>
+ Enables listing the files with otherwise restricted access.
+ </td></tr><tr><td>
+ <code class="option">SuppressColumnSorting</code>
+ </td><td>
+ Disables re-sorting a directory listing by clicking on a column header.
+ </td></tr><tr><td>
+ <code class="option">SuppressDescription</code>
+ </td><td>
+ Disables reserving a space for file descriptions.
+ </td></tr><tr><td>
+ <code class="option">SuppressHTMLPreamble</code>
+ </td><td>
+ Disables the use of standard HTML preamble when a file specified by the <code class="option">HeaderName</code> directive is present.
+ </td></tr><tr><td>
+ <code class="option">SuppressIcon</code>
+ </td><td>
+ Disables the use of icons in directory listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressLastModified</code>
+ </td><td>
+ Disables displaying the date of the last modification field in directory listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressRules</code>
+ </td><td>
+ Disables the use of horizontal lines in directory listings.
+ </td></tr><tr><td>
+ <code class="option">SuppressSize</code>
+ </td><td>
+ Disables displaying the file size field in directory listings.
+ </td></tr><tr><td>
+ <code class="option">TrackModified</code>
+ </td><td>
+ Enables returning the <code class="literal">Last-Modified</code> and <code class="literal">ETag</code> values in the HTTP header.
+ </td></tr><tr><td>
+ <code class="option">VersionSort</code>
+ </td><td>
+ Enables sorting files that contain a version number in the expected manner.
+ </td></tr><tr><td>
+ <code class="option">XHTML</code>
+ </td><td>
+ Enables the use of XHTML 1.0 instead of the default HTML 3.2.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.42. Using the IndexOptions directive" id="example-apache-httpdconf-indexoptions"><h6>Example 11.42. Using the <code class="option">IndexOptions</code> directive</h6><div class="example-contents"><pre class="screen">IndexOptions FancyIndexing VersionSort NameWidth=* HTMLTable Charset=UTF-8</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id470116" class="indexterm"></a>
+ <code class="option">KeepAlive</code> </span></dt><dd><div class="para">
+ The <code class="option">KeepAlive</code> directive allows you to enable persistent connections. It takes the following form:
+ </div><pre class="screen">KeepAlive <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-keepalive" title="Table 11.10. Available KeepAlive options">Table 11.10, “Available <code class="option">KeepAlive</code> options”</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.10. Available KeepAlive options" id="table-apache-httpdconf-keepalive"><h6>Table 11.10. Available <code class="option">KeepAlive</code> options</h6><div class="table-contents"><table summary="Available KeepAlive options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables the persistent connections. In this case, the server will accept more than one request per connection.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables the keep-alive connections.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Note that when the persistent connections are enabled, on a busy server, the number of child processes can increase rapidly and eventually reach the maximum limit, slowing down the server significantly. To reduce the risk, it is recommended that you set <code class="option">KeepAliveTimeout</code> to a low number, and monitor the <code class="filename">/var/log/httpd/logs/error_log</code> log file carefully.
+ </div><div class="example" title="Example 11.43. Using the KeepAlive directive" id="example-apache-httpdconf-keepalive"><h6>Example 11.43. Using the <code class="option">KeepAlive</code> directive</h6><div class="example-contents"><pre class="screen">KeepAlive Off</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id455341" class="indexterm"></a>
+ <code class="option">KeepAliveTimeout</code> </span></dt><dd><div class="para">
+ The <code class="option">KeepAliveTimeout</code> directive allows you to specify the amount of time to wait for another request before closing the connection. It takes the following form:
+ </div><pre class="screen">KeepAliveTimeout <em class="replaceable"><code>time</code></em></pre><div class="para">
+ The <em class="replaceable"><code>time</code></em> is specified in seconds. The default option is <code class="literal">15</code>.
+ </div><div class="example" title="Example 11.44. Using the KeepAliveTimeout directive" id="example-apache-httpdconf-keepalivetimeout"><h6>Example 11.44. Using the <code class="option">KeepAliveTimeout</code> directive</h6><div class="example-contents"><pre class="screen">KeepAliveTimeout 15</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id731103" class="indexterm"></a>
+ <code class="option">LanguagePriority</code> </span></dt><dd><div class="para">
+ The <code class="option">LanguagePriority</code> directive allows you to customize the precedence of languages. It takes the following form:
+ </div><pre class="screen">LanguagePriority <em class="replaceable"><code>language</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>language</code></em> has to be a valide MIME language such as <code class="literal">cs</code>, <code class="literal">en</code>, or <code class="literal">fr</code>.
+ </div><div class="para">
+ This directive is especially useful for web servers that serve content in multiple languages based on the client's language settings.
+ </div><div class="example" title="Example 11.45. Using the LanguagePriority directive" id="example-apache-httpdconf-languagepriority"><h6>Example 11.45. Using the <code class="option">LanguagePriority</code> directive</h6><div class="example-contents"><pre class="screen">LanguagePriority sk cs en</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id731197" class="indexterm"></a>
+ <code class="option">Listen</code> </span></dt><dd><div class="para">
+ The <em class="replaceable"><code>Listen</code></em> directive allows you to specify IP addresses or ports to listen to. It takes the following form:
+ </div><pre class="screen">Listen [<span class="optional"><em class="replaceable"><code>ip-address</code></em>:</span>]<em class="replaceable"><code>port</code></em> [<span class="optional"><em class="replaceable"><code>protocol</code></em></span>]</pre><div class="para">
+ The <em class="replaceable"><code>ip-address</code></em> is optional and unless supplied, the server will accept incoming requests on a given <em class="replaceable"><code>port</code></em> from all IP addresses. Since the <em class="replaceable"><code>protocol</code></em> is determined automatically from the port number, it can be usually omitted. The default option is to listen to port <code class="literal">80</code>.
+ </div><div class="para">
+ Note that if the server is configured to listen to a port under 1024, only superuser will be able to start the <code class="systemitem">httpd</code> service.
+ </div><div class="example" title="Example 11.46. Using the Listen directive" id="example-apache-httpdconf-listen"><h6>Example 11.46. Using the <code class="option">Listen</code> directive</h6><div class="example-contents"><pre class="screen">Listen 80</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id797366" class="indexterm"></a>
+ <code class="option">LoadModule</code> </span></dt><dd><div class="para">
+ The <code class="option">LoadModule</code> directive allows you to load a <em class="firstterm">Dynamic Shared Object</em> (<acronym class="acronym">DSO</acronym>) module. It takes the following form:
+ </div><pre class="screen">LoadModule <em class="replaceable"><code>name</code></em> <em class="replaceable"><code>path</code></em></pre><a id="id797419" class="indexterm"></a><a id="id794906" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>name</code></em> has to be a valid identifier of the required module. The <em class="replaceable"><code>path</code></em> refers to an existing module file, and must be relative to the directory in which the libraries are placed (that is, <code class="filename">/usr/lib/httpd/</code> on 32-bit and <code class="filename">/usr/lib64/httpd/</code> on 64-bit systems by default).
+ </div><div class="para">
+ Refer to <a class="xref" href="s1-apache-dso.html" title="11.4. Working with Modules">Section 11.4, “Working with Modules”</a> for more information on the Apache HTTP Server's DSO support.
+ </div><div class="example" title="Example 11.47. Using the LoadModule directive" id="example-apache-httpdconf-loadmodule"><h6>Example 11.47. Using the <code class="option">LoadModule</code> directive</h6><div class="example-contents"><pre class="screen">LoadModule php5_module modules/libphp5.so</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id794988" class="indexterm"></a>
+ <code class="option">LogFormat</code> </span></dt><dd><div class="para">
+ The <em class="replaceable"><code>LogFormat</code></em> directive allows you to specify a log file format. It takes the following form:
+ </div><pre class="screen">LogFormat <em class="replaceable"><code>format</code></em> <em class="replaceable"><code>name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>format</code></em> is a string consisting of options as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-logformat" title="Table 11.11. Common LogFormat options">Table 11.11, “Common <code class="option">LogFormat</code> options”</a>. The <em class="replaceable"><code>name</code></em> can be used instead of the format string in the <code class="option">CustomLog</code> directive.
+ </div><div class="table" title="Table 11.11. Common LogFormat options" id="table-apache-httpdconf-logformat"><h6>Table 11.11. Common <code class="option">LogFormat</code> options</h6><div class="table-contents"><table summary="Common LogFormat options" border="1"><colgroup><col width="13%" /><col width="88%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">%b</code>
+ </td><td>
+ Represents the size of the response in bytes.
+ </td></tr><tr><td>
+ <code class="option">%h</code>
+ </td><td>
+ Represents the IP address or hostname of a remote client.
+ </td></tr><tr><td>
+ <code class="option">%l</code>
+ </td><td>
+ Represents the remote log name if supplied. If not, a hyphen (that is, <code class="literal">-</code>) is used instead.
+ </td></tr><tr><td>
+ <code class="option">%r</code>
+ </td><td>
+ Represents the first line of the request string as it came from the browser or client.
+ </td></tr><tr><td>
+ <code class="option">%s</code>
+ </td><td>
+ Represents the status code.
+ </td></tr><tr><td>
+ <code class="option">%t</code>
+ </td><td>
+ Represents the date and time of the request.
+ </td></tr><tr><td>
+ <code class="option">%u</code>
+ </td><td>
+ If the authentication is required, it represents the remote user. If not, a hyphen (that is, <code class="literal">-</code>) is used instead.
+ </td></tr><tr><td>
+ <code class="option">%{<em class="replaceable"><code>field</code></em>}</code>
+ </td><td>
+ Represents the content of the HTTP header <em class="replaceable"><code>field</code></em>. The common options include <code class="option">%{Referer}</code> (the URL of the web page that referred the client to the server) and <code class="option">%{User-Agent}</code> (the type of the web browser making the request).
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.48. Using the LogFormat directive" id="example-apache-httpdconf-logformat"><h6>Example 11.48. Using the <code class="option">LogFormat</code> directive</h6><div class="example-contents"><pre class="screen">LogFormat "%h %l %u %t \"%r\" %>s %b" common</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id827269" class="indexterm"></a>
+ <code class="option">LogLevel</code> </span></dt><dd><div class="para">
+ The <code class="option">LogLevel</code> directive allows you to customize the verbosity level of the error log. It takes the following form:
+ </div><pre class="screen">LogLevel <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-loglevel" title="Table 11.12. Available LogLevel options">Table 11.12, “Available <code class="option">LogLevel</code> options”</a>. The default option is <code class="option">warn</code>.
+ </div><div class="table" title="Table 11.12. Available LogLevel options" id="table-apache-httpdconf-loglevel"><h6>Table 11.12. Available <code class="option">LogLevel</code> options</h6><div class="table-contents"><table summary="Available LogLevel options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">emerg</code>
+ </td><td>
+ Only the emergency situations when the server cannot perform its work are logged.
+ </td></tr><tr><td>
+ <code class="option">alert</code>
+ </td><td>
+ All situations when an immediate action is required are logged.
+ </td></tr><tr><td>
+ <code class="option">crit</code>
+ </td><td>
+ All critical conditions are logged.
+ </td></tr><tr><td>
+ <code class="option">error</code>
+ </td><td>
+ All error messages are logged.
+ </td></tr><tr><td>
+ <code class="option">warn</code>
+ </td><td>
+ All warning messages are logged.
+ </td></tr><tr><td>
+ <code class="option">notice</code>
+ </td><td>
+ Even normal, but still significant situations are logged.
+ </td></tr><tr><td>
+ <code class="option">info</code>
+ </td><td>
+ Various informational messages are logged.
+ </td></tr><tr><td>
+ <code class="option">debug</code>
+ </td><td>
+ Various debugging messages are logged.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.49. Using the LogLevel directive" id="example-apache-httpdconf-loglevel"><h6>Example 11.49. Using the <code class="option">LogLevel</code> directive</h6><div class="example-contents"><pre class="screen">LogLevel warn</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id769439" class="indexterm"></a>
+ <code class="option">MaxKeepAliveRequests</code> </span></dt><dd><div class="para">
+ The <code class="option">MaxKeepAliveRequests</code> directive allows you to specify the maximum number of requests for a persistent connection. It takes the following form:
+ </div><pre class="screen">MaxKeepAliveRequests <em class="replaceable"><code>number</code></em></pre><div class="para">
+ A high <em class="replaceable"><code>number</code></em> can improve the performance of the server. Note that using <code class="literal">0</code> allows unlimited number of requests. The default option is <code class="option">100</code>.
+ </div><div class="example" title="Example 11.50. Using the MaxKeepAliveRequests option" id="example-apache-httpdconf-maxkeepaliverequests"><h6>Example 11.50. Using the <code class="option">MaxKeepAliveRequests</code> option</h6><div class="example-contents"><pre class="screen">MaxKeepAliveRequests 100</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id769523" class="indexterm"></a>
+ <code class="option">NameVirtualHost</code> </span></dt><dd><div class="para">
+ The <code class="option">NameVirtualHost</code> directive allows you to specify the IP address and port number for a name-based virtual host. It takes the following form:
+ </div><pre class="screen">NameVirtualHost <em class="replaceable"><code>ip-address</code></em>[<span class="optional">:<em class="replaceable"><code>port</code></em></span>]</pre><div class="para">
+ The <em class="replaceable"><code>ip-address</code></em> can be either a full IP address, or an asterisk (that is, <code class="literal">*</code>) representing all interfaces. Note that IPv6 addresses have to be enclosed in square brackets (that is, <code class="literal">[</code> and <code class="literal">]</code>). The <em class="replaceable"><code>port</code></em> is optional.
+ </div><div class="para">
+ Name-based virtual hosting allows one Apache HTTP Server to serve different domains without using multiple IP addresses.
+ </div><div class="important" title="Important: Using Secure HTTP Connections"><div class="admonition_header"><h2>Important: Using Secure HTTP Connections</h2></div><div class="admonition"><div class="para">
+ Name-based virtual hosts <span class="emphasis"><em>only</em></span> work with non-secure HTTP connections. If using virtual hosts with a secure server, use IP address-based virtual hosts instead.
+ </div></div></div><div class="example" title="Example 11.51. Using the NameVirtualHost directive" id="example-apache-httpdconf-namevirtualhost"><h6>Example 11.51. Using the <code class="option">NameVirtualHost</code> directive</h6><div class="example-contents"><pre class="screen">NameVirtualHost *:80</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id784624" class="indexterm"></a>
+ <code class="option">Options</code> </span></dt><dd><div class="para">
+ The <code class="option">Options</code> directive allows you to specify which server features are available in a particular directory. It takes the following form:
+ </div><pre class="screen">Options <em class="replaceable"><code>option</code></em>…</pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-options" title="Table 11.13. Available server features">Table 11.13, “Available server features”</a>.
+ </div><div class="table" title="Table 11.13. Available server features" id="table-apache-httpdconf-options"><h6>Table 11.13. Available server features</h6><div class="table-contents"><table summary="Available server features" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">ExecCGI</code>
+ </td><td>
+ Enables the execution of CGI scripts.
+ </td></tr><tr><td>
+ <code class="option">FollowSymLinks</code>
+ </td><td>
+ Enables following symbolic links in the directory.
+ </td></tr><tr><td>
+ <code class="option">Includes</code>
+ </td><td>
+ Enables server-side includes.
+ </td></tr><tr><td>
+ <code class="option">IncludesNOEXEC</code>
+ </td><td>
+ Enables server-side includes, but does not allow the execution of commands.
+ </td></tr><tr><td>
+ <code class="option">Indexes</code>
+ </td><td>
+ Enables server-generated directory listings.
+ </td></tr><tr><td>
+ <code class="option">MultiViews</code>
+ </td><td>
+ Enables content-negotiated <span class="quote">“<span class="quote">MultiViews</span>”</span>.
+ </td></tr><tr><td>
+ <code class="option">SymLinksIfOwnerMatch</code>
+ </td><td>
+ Enables following symbolic links in the directory when both the link and the target file have the same owner.
+ </td></tr><tr><td>
+ <code class="option">All</code>
+ </td><td>
+ Enables all of the features above with the exception of <code class="option">MultiViews</code>.
+ </td></tr><tr><td>
+ <code class="option">None</code>
+ </td><td>
+ Disables all of the features above.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.52. Using the Options directive" id="example-apache-httpdconf-options"><h6>Example 11.52. Using the <code class="option">Options</code> directive</h6><div class="example-contents"><pre class="screen">Options Indexes FollowSymLinks</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id478725" class="indexterm"></a>
+ <code class="option">Order</code> </span></dt><dd><div class="para">
+ The <code class="option">Order</code> directive allows you to specify the order in which the <code class="option">Allow</code> and <code class="option">Deny</code> directives are evaluated. It takes the following form:
+ </div><pre class="screen">Order <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-order" title="Table 11.14. Available Order options">Table 11.14, “Available <code class="option">Order</code> options”</a>. The default option is <code class="option">allow,deny</code>.
+ </div><div class="table" title="Table 11.14. Available Order options" id="table-apache-httpdconf-order"><h6>Table 11.14. Available <code class="option">Order</code> options</h6><div class="table-contents"><table summary="Available Order options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow,deny</code>
+ </td><td>
+ <code class="option">Allow</code> directives are evaluated first.
+ </td></tr><tr><td>
+ <code class="option">deny,allow</code>
+ </td><td>
+ <code class="option">Deny</code> directives are evaluated first.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.53. Using the Order directive" id="example-apache-httpdconf-order"><h6>Example 11.53. Using the <code class="option">Order</code> directive</h6><div class="example-contents"><pre class="screen">Order allow,deny</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id520955" class="indexterm"></a>
+ <code class="option">PidFile</code> </span></dt><dd><div class="para">
+ The <code class="option">PidFile</code> directive allows you to specify a file to which the <em class="firstterm">process ID</em> (<acronym class="acronym">PID</acronym>) of the server is stored. It takes the following form:
+ </div><pre class="screen">PidFile <em class="replaceable"><code>path</code></em></pre><a id="id521004" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to a pid file, and can be either absolute, or relative to the directory that is specified by the <code class="option">ServerRoot</code> directive (that is, <code class="filename">/etc/httpd/</code> by default). The default option is <code class="filename">run/httpd.pid</code>.
+ </div><div class="example" title="Example 11.54. Using the PidFile directive" id="example-apache-httpdconf-pidfile"><h6>Example 11.54. Using the <code class="option">PidFile</code> directive</h6><div class="example-contents"><pre class="screen">PidFile run/httpd.pid</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id455474" class="indexterm"></a>
+ <code class="option">ProxyRequests</code> </span></dt><dd><div class="para">
+ The <code class="option">ProxyRequests</code> directive allows you to enable forward proxy requests. It takes the following form:
+ </div><pre class="screen">ProxyRequests <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-proxyrequests" title="Table 11.15. Available ProxyRequests options">Table 11.15, “Available <code class="option">ProxyRequests</code> options”</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.15. Available ProxyRequests options" id="table-apache-httpdconf-proxyrequests"><h6>Table 11.15. Available <code class="option">ProxyRequests</code> options</h6><div class="table-contents"><table summary="Available ProxyRequests options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables forward proxy requests.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables forward proxy requests.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.55. Using the ProxyRequests directive" id="example-apache-httpdconf-proxyrequests"><h6>Example 11.55. Using the <code class="option">ProxyRequests</code> directive</h6><div class="example-contents"><pre class="screen">ProxyRequests On</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id654180" class="indexterm"></a>
+ <code class="option">ReadmeName</code> </span></dt><dd><div class="para">
+ The <code class="option">ReadmeName</code> directive allows you to specify a file to be appended to the end of the server-generated directory listing. It takes the following form:
+ </div><pre class="screen">ReadmeName <em class="replaceable"><code>filename</code></em></pre><div class="para">
+ The <em class="replaceable"><code>filename</code></em> is a name of the file to look for in the requested directory. By default, the server looks for <code class="filename">README.html</code>.
+ </div><div class="example" title="Example 11.56. Using the ReadmeName directive" id="example-apache-httpdconf-readmename"><h6>Example 11.56. Using the <code class="option">ReadmeName</code> directive</h6><div class="example-contents"><pre class="screen">ReadmeName README.html</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id654261" class="indexterm"></a>
+ <code class="option">Redirect</code> </span></dt><dd><div class="para">
+ The <code class="option">Redirect</code> directive allows you to redirect a client to another URL. It takes the following form:
+ </div><pre class="screen">Redirect [<span class="optional"><em class="replaceable"><code>status</code></em></span>] <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>url</code></em></pre><div class="para">
+ The <em class="replaceable"><code>status</code></em> is optional, and if provided, it has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-redirect" title="Table 11.16. Available status options">Table 11.16, “Available status options”</a>. The <em class="replaceable"><code>path</code></em> refers to the old location, and must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/docs</code>). The <em class="replaceable"><code>url</code></em> refers to the current location of the content (for example, <code class="literal">http://docs.example.com</code>).
+ </div><div class="table" title="Table 11.16. Available status options" id="table-apache-httpdconf-redirect"><h6>Table 11.16. Available status options</h6><div class="table-contents"><table summary="Available status options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Status
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">permanent</code>
+ </td><td>
+ Indicates that the requested resource has been moved permanently. The <code class="literal">301</code> (Moved Permanently) status code is returned to a client.
+ </td></tr><tr><td>
+ <code class="option">temp</code>
+ </td><td>
+ Indicates that the requested resource has been moved only temporarily. The <code class="literal">302</code> (Found) status code is returned to a client.
+ </td></tr><tr><td>
+ <code class="option">seeother</code>
+ </td><td>
+ Indicates that the requested resource has been replaced. The <code class="literal">303</code> (See Other) status code is returned to a client.
+ </td></tr><tr><td>
+ <code class="option">gone</code>
+ </td><td>
+ Indicates that the requested resource has been removed permanently. The <code class="literal">410</code> (Gone) status is returned to a client.
+ </td></tr></tbody></table></div></div><br class="table-break" /><a id="id655161" class="indexterm"></a><div class="para">
+ Note that for more advanced redirection techniques, you can use the <code class="systemitem">mod_rewrite</code> module that is part of the Apache HTTP Server installation.
+ </div><div class="example" title="Example 11.57. Using the Redirect directive" id="example-apache-httpdconf-redirect"><h6>Example 11.57. Using the <code class="option">Redirect</code> directive</h6><div class="example-contents"><pre class="screen">Redirect permanent /docs http://docs.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id837888" class="indexterm"></a>
+ <code class="option">ScriptAlias</code> </span></dt><dd><div class="para">
+ The <code class="option">ScriptAlias</code> directive allows you to specify the location of CGI scripts. It takes the following form:
+ </div><pre class="screen">ScriptAlias <em class="replaceable"><code>url-path</code></em> <em class="replaceable"><code>real-path</code></em></pre><div class="para">
+ The <em class="replaceable"><code>url-path</code></em> must be relative to the directory specified by the <code class="option">DocumentRoot</code> directive (for example, <code class="literal">/cgi-bin/</code>). The <em class="replaceable"><code>real-path</code></em> is a full path to a file or directory in the local file system.
+ </div><a id="id837953" class="indexterm"></a><div class="para">
+ This directive is typically followed by the <code class="option">Directory</code> tag with additional permissions to access the target directory. By default, the <code class="literal">/cgi-bin/</code> alias is created so that the scripts located in the <code class="filename">/var/www/cgi-bin/</code> are accessible.
+ </div><div class="para">
+ The <code class="option">ScriptAlias</code> directive is used for security reasons to prevent CGI scripts from being viewed as ordinary text documents.
+ </div><div class="example" title="Example 11.58. Using the ScriptAlias directive" id="example-apache-httpdconf-scriptalias"><h6>Example 11.58. Using the <code class="option">ScriptAlias</code> directive</h6><div class="example-contents"><pre class="screen">ScriptAlias /cgi-bin/ /var/www/cgi-bin/
+
+<Directory "/var/www/cgi-bin">
+ AllowOverride None
+ Options None
+ Order allow,deny
+ Allow from all
+</Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id710737" class="indexterm"></a>
+ <code class="option">ServerAdmin</code> </span></dt><dd><div class="para">
+ The <code class="option">ServerAdmin</code> directive allows you to specify the email address of the server administrator to be displayed in server-generated web pages. It takes the following form:
+ </div><pre class="screen">ServerAdmin <em class="replaceable"><code>email</code></em></pre><div class="para">
+ The default option is <code class="literal">root at localhost</code>.
+ </div><div class="para">
+ This directive is commonly set to <code class="literal">webmaster@<em class="replaceable"><code>hostname</code></em></code>, where <em class="replaceable"><code>hostname</code></em> is the address of the server. Once set, alias <code class="literal">webmaster</code> to the person responsible for the web server in <code class="filename">/etc/aliases</code>, and as superuser, run the <code class="command">newaliases</code> command.
+ </div><div class="example" title="Example 11.59. Using the ServerAdmin directive" id="example-apache-httpdconf-serveradmin"><h6>Example 11.59. Using the <code class="option">ServerAdmin</code> directive</h6><div class="example-contents"><pre class="screen">ServerAdmin webmaster at penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id710838" class="indexterm"></a>
+ <code class="option">ServerName</code> </span></dt><dd><div class="para">
+ The <code class="option">ServerName</code> directive allows you to specify the hostname and the port number of a web server. It takes the following form:
+ </div><pre class="screen">ServerName <em class="replaceable"><code>hostname</code></em>[<span class="optional">:<em class="replaceable"><code>port</code></em></span>]</pre><div class="para">
+ The <em class="replaceable"><code>hostname</code></em> has to be a <em class="firstterm">fully qualified domain name</em> (<acronym class="acronym">FQDN</acronym>) of the server. The <em class="replaceable"><code>port</code></em> is optional, but when supplied, it has to match the number specified by the <code class="option">Listen</code> directive.
+ </div><div class="para">
+ When using this directive, make sure that the IP address and server name pair are included in the <code class="filename">/etc/hosts</code> file.
+ </div><div class="example" title="Example 11.60. Using the ServerName directive" id="example-apache-httpdconf-servername"><h6>Example 11.60. Using the <code class="option">ServerName</code> directive</h6><div class="example-contents"><pre class="screen">ServerName penguin.example.com:80</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id461578" class="indexterm"></a>
+ <code class="option">ServerRoot</code> </span></dt><dd><div class="para">
+ The <code class="option">ServerRoot</code> directive allows you to specify the directory in which the server operates. It takes the following form:
+ </div><pre class="screen">ServerRoot <em class="replaceable"><code>directory</code></em></pre><a id="id461620" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>directory</code></em> must be a full path to an existing directory in the local file system. The default option is <code class="filename">/etc/httpd/</code>.
+ </div><div class="example" title="Example 11.61. Using the ServerRoot directive" id="example-apache-httpd-serverroot"><h6>Example 11.61. Using the <code class="option">ServerRoot</code> directive</h6><div class="example-contents"><pre class="screen">ServerRoot /etc/httpd</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id624087" class="indexterm"></a>
+ <code class="option">ServerSignature</code> </span></dt><dd><div class="para">
+ The <code class="option">ServerSignature</code> directive allows you to enable displaying information about the server on server-generated documents. It takes the following form:
+ </div><pre class="screen">ServerSignature <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-serversignature" title="Table 11.17. Available ServerSignature options">Table 11.17, “Available <code class="option">ServerSignature</code> options”</a>. The default option is <code class="option">On</code>.
+ </div><div class="table" title="Table 11.17. Available ServerSignature options" id="table-apache-httpdconf-serversignature"><h6>Table 11.17. Available <code class="option">ServerSignature</code> options</h6><div class="table-contents"><table summary="Available ServerSignature options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables appending the server name and version to server-generated pages.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables appending the server name and version to server-generated pages.
+ </td></tr><tr><td>
+ <code class="option">EMail</code>
+ </td><td>
+ Enables appending the server name, version, and the email address of the system administrator as specified by the <code class="option">ServerAdmin</code> directive to server-generated pages.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.62. Using the ServerSignature directive" id="example-apache-httpdconf-serversignature"><h6>Example 11.62. Using the <code class="option">ServerSignature</code> directive</h6><div class="example-contents"><pre class="screen">ServerSignature On</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id834922" class="indexterm"></a>
+ <code class="option">ServerTokens</code> </span></dt><dd><div class="para">
+ The <code class="option">ServerTokens</code> directive allows you to customize what information are included in the Server response header. It takes the following form:
+ </div><pre class="screen">ServerTokens <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-servertokens" title="Table 11.18. Available ServerTokens options">Table 11.18, “Available <code class="option">ServerTokens</code> options”</a>. The default option is <code class="option">OS</code>.
+ </div><div class="table" title="Table 11.18. Available ServerTokens options" id="table-apache-httpdconf-servertokens"><h6>Table 11.18. Available <code class="option">ServerTokens</code> options</h6><div class="table-contents"><table summary="Available ServerTokens options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Prod</code>
+ </td><td>
+ Includes the product name only (that is, <code class="literal">Apache</code>).
+ </td></tr><tr><td>
+ <code class="option">Major</code>
+ </td><td>
+ Includes the product name and the major version of the server (for example, <code class="literal">2</code>).
+ </td></tr><tr><td>
+ <code class="option">Minor</code>
+ </td><td>
+ Includes the product name and the minor version of the server (for example, <code class="literal">2.2</code>).
+ </td></tr><tr><td>
+ <code class="option">Min</code>
+ </td><td>
+ Includes the product name and the minimal version of the server (for example, <code class="literal">2.2.15</code>).
+ </td></tr><tr><td>
+ <code class="option">OS</code>
+ </td><td>
+ Includes the product name, the minimal version of the server, and the type of the operating system it is running on (for example, <code class="literal">Red Hat</code>).
+ </td></tr><tr><td>
+ <code class="option">Full</code>
+ </td><td>
+ Includes all the information above along with the list of loaded modules.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Note that for security reasons, it is recommended to reveal as little information about the server as possible.
+ </div><div class="example" title="Example 11.63. Using the ServerTokens directive" id="example-apache-httpdconf-servertokens"><h6>Example 11.63. Using the <code class="option">ServerTokens</code> directive</h6><div class="example-contents"><pre class="screen">ServerTokens Prod</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id730642" class="indexterm"></a>
+ <code class="option">SuexecUserGroup</code> </span></dt><dd><div class="para">
+ The <code class="option">SuexecUserGroup</code> directive allows you to specify the user and group under which the CGI scripts will be run. It takes the following form:
+ </div><pre class="screen">SuexecUserGroup <em class="replaceable"><code>user</code></em> <em class="replaceable"><code>group</code></em></pre><div class="para">
+ The <em class="replaceable"><code>user</code></em> has to be an existing user, and the <em class="replaceable"><code>group</code></em> must be a valid UNIX group.
+ </div><div class="para">
+ For security reasons, the CGI scripts should not be run with root privileges. Note that in <code class="option"><VirtualHost></code>, <code class="option">SuexecUserGroup</code> replaces the <code class="option">User</code> and <code class="option">Group</code> directives.
+ </div><div class="example" title="Example 11.64. Using the SuexecUserGroup directive" id="example-apache-httpdconf-suexecusergroup"><h6>Example 11.64. Using the <code class="option">SuexecUserGroup</code> directive</h6><div class="example-contents"><pre class="screen">SuexecUserGroup apache apache</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id491157" class="indexterm"></a>
+ <code class="option">Timeout</code> </span></dt><dd><div class="para">
+ The <code class="option">Timeout</code> directive allows you to specify the amount of time to wait for an event before closing a connection. It takes the following form:
+ </div><pre class="screen">Timeout <em class="replaceable"><code>time</code></em></pre><div class="para">
+ The <em class="replaceable"><code>time</code></em> is specified in seconds. The default option is <code class="literal">60</code>.
+ </div><div class="example" title="Example 11.65. Using the Timeout directive" id="example-apache-httpdconf-timeout"><h6>Example 11.65. Using the <code class="option">Timeout</code> directive</h6><div class="example-contents"><pre class="screen">Timeout 60</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id637179" class="indexterm"></a>
+ <code class="option">TypesConfig</code> </span></dt><dd><div class="para">
+ The <code class="option">TypesConfig</code> allows you to specify the location of the MIME types configuration file. It takes the following form:
+ </div><pre class="screen">TypesConfig <em class="replaceable"><code>path</code></em></pre><a id="id637221" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>path</code></em> refers to an existing MIME types configuration file, and can be either absolute, or relative to the directory that is specified by the <code class="option">ServerRoot</code> directive (that is, <code class="filename">/etc/httpd/</code> by default). The default option is <code class="option">/etc/mime.types</code>.
+ </div><div class="para">
+ Note that instead of editing <code class="filename">/etc/mime.types</code>, the recommended way to add MIME type mapping to the Apache HTTP Server is to use the <code class="option">AddType</code> directive.
+ </div><div class="example" title="Example 11.66. Using the TypesConfig directive" id="example-apache-httpdconf-typesconfig"><h6>Example 11.66. Using the <code class="option">TypesConfig</code> directive</h6><div class="example-contents"><pre class="screen">TypesConfig /etc/mime.types</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id637300" class="indexterm"></a>
+ <code class="option">UseCanonicalName</code> </span></dt><dd><div class="para">
+ The <code class="option">UseCanonicalName</code> allows you to specify the way the server refers to itself. It takes the following form:
+ </div><pre class="screen">UseCanonicalName <em class="replaceable"><code>option</code></em></pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> has to be a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-usecanonicalname" title="Table 11.19. Available UseCanonicalName options">Table 11.19, “Available <code class="option">UseCanonicalName</code> options”</a>. The default option is <code class="option">Off</code>.
+ </div><div class="table" title="Table 11.19. Available UseCanonicalName options" id="table-apache-httpdconf-usecanonicalname"><h6>Table 11.19. Available <code class="option">UseCanonicalName</code> options</h6><div class="table-contents"><table summary="Available UseCanonicalName options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">On</code>
+ </td><td>
+ Enables the use of the name that is specified by the <code class="option">ServerName</code> directive.
+ </td></tr><tr><td>
+ <code class="option">Off</code>
+ </td><td>
+ Disables the use of the name that is specified by the <code class="option">ServerName</code> directive. The hostname and port number provided by the requesting client are used instead.
+ </td></tr><tr><td>
+ <code class="option">DNS</code>
+ </td><td>
+ Disables the use of the name that is specified by the <code class="option">ServerName</code> directive. The hostname determined by a reverse DNS lookup is used instead.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 11.67. Using the UseCanonicalName directive" id="example-apache-httpdconf-usecanonicalname"><h6>Example 11.67. Using the <code class="option">UseCanonicalName</code> directive</h6><div class="example-contents"><pre class="screen">UseCanonicalName Off</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id773169" class="indexterm"></a>
+ <code class="option">User</code> </span></dt><dd><div class="para">
+ The <code class="option">User</code> directive allows you to specify the user under which the <code class="systemitem">httpd</code> service will run. It takes the following form:
+ </div><pre class="screen">User <em class="replaceable"><code>user</code></em></pre><div class="para">
+ The <em class="replaceable"><code>user</code></em> has to be an existing UNIX user. The default option is <code class="option">apache</code>.
+ </div><div class="para">
+ For security reasons, the <code class="systemitem">httpd</code> service should not be run with root privileges. Note that <code class="option">User</code> is no longer supported inside <code class="option"><VirtualHost></code>, and has been replaced by the <code class="option">SuexecUserGroup</code> directive.
+ </div><div class="example" title="Example 11.68. Using the User directive" id="example-apache-httpdconf-user"><h6>Example 11.68. Using the <code class="option">User</code> directive</h6><div class="example-contents"><pre class="screen">User apache</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id557125" class="indexterm"></a>
+ <code class="option">UserDir</code> </span></dt><dd><div class="para">
+ The <code class="option">UserDir</code> directive allows you to enable serving content from users' home directories. It takes the following form:
+ </div><pre class="screen">UserDir <em class="replaceable"><code>option</code></em></pre><a id="id557168" class="indexterm"></a><div class="para">
+ The <em class="replaceable"><code>option</code></em> can be either a name of the directory to look for in user's home directory (typically <code class="option">public_html</code>), or a valid keyword as described in <a class="xref" href="s1-apache-editing.html#table-apache-httpdconf-userdir" title="Table 11.20. Available UserDir options">Table 11.20, “Available <code class="option">UserDir</code> options”</a>. The default option is <code class="option">disabled</code>.
+ </div><div class="table" title="Table 11.20. Available UserDir options" id="table-apache-httpdconf-userdir"><h6>Table 11.20. Available <code class="option">UserDir</code> options</h6><div class="table-contents"><table summary="Available UserDir options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">enabled</code> <em class="replaceable"><code>user</code></em>…
+ </td><td>
+ Enables serving content from home directories of given <em class="replaceable"><code>user</code></em>s.
+ </td></tr><tr><td>
+ <code class="option">disabled</code> [<span class="optional"><em class="replaceable"><code>user</code></em>…</span>]
+ </td><td>
+ Disables serving content from home directories, either for all users, or, if a space separated list of <em class="replaceable"><code>user</code></em>s is supplied, for given users only.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note" title="Note: Set the Correct Permissions"><div class="admonition_header"><h2>Note: Set the Correct Permissions</h2></div><div class="admonition"><div class="para">
+ In order for the web server to access the content, the permissions on relevant directories and files must be set correctly. Make sure that all users are able to access the home directories, and that they can access and read the content of the directory specified by the <code class="option">UserDir</code> directive. For example:
+ </div><pre class="screen">~]# <code class="command">chmod a+x /home/<em class="replaceable"><code>username</code></em>/</code>
+~]# <code class="command">chmod a+rx /home/<em class="replaceable"><code>username</code></em>/public_html/</code></pre><div class="para">
+ All files in this directory must be set accordingly.
+ </div></div></div><div class="example" title="Example 11.69. Using the UserDir directive" id="example-apache-httpdconf-userdir"><h6>Example 11.69. Using the <code class="option">UserDir</code> directive</h6><div class="example-contents"><pre class="screen">UserDir public_html</pre></div></div><br class="example-break" /></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s3-apache-running-status.html"><strong>Prev</strong>11.2.4. Checking the Service Status</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-apache-sslconf-common.html"><strong>Next</strong>11.3.2. Common ssl.conf Directives</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-mod_ssl.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-mod_ssl.html
new file mode 100644
index 0000000..7bc671e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-mod_ssl.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.6. Setting Up an SSL Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_Apache_HTTP_Server.html" title="Chapter 11. The Apache HTTP Server" /><link rel="prev" href="s1-apache-virtualhosts.html" title="11.5. Setting Up Virtual Hosts" /><link rel="next" href="s2-apache-mod_ssl-enabling.html" title="11.6.2. Enabling the mod_ssl Module" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-virtualhosts.html"><strong>Prev</strong></
a></li><li class="next"><a accesskey="n" href="s2-apache-mod_ssl-enabling.html"><strong>Next</strong></a></li></ul><div class="section" title="11.6. Setting Up an SSL Server" id="s1-apache-mod_ssl"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-mod_ssl">11.6. Setting Up an SSL Server</h2></div></div></div><a id="id560027" class="indexterm"></a><a id="id560048" class="indexterm"></a><a id="id560062" class="indexterm"></a><a id="id560076" class="indexterm"></a><a id="id560091" class="indexterm"></a><a id="id521749" class="indexterm"></a><div class="para">
+ <em class="firstterm">Secure Sockets Layer</em> (<acronym class="acronym">SSL</acronym>) is a cryptographic protocol that allows a server and a client to communicate securely. Along with its extended and improved version called <em class="firstterm">Transport Layer Security</em> (<acronym class="acronym">TLS</acronym>), it ensures both privacy and data integrity. The Apache HTTP Server in combination with <code class="systemitem">mod_ssl</code>, a module that uses the OpenSSL toolkit to provide the SSL/TLS support, is commonly referred to as the <em class="firstterm">SSL server</em>.
+ </div><div class="para">
+ Unlike a regular HTTP connection that can be read and possibly modified by anybody who is able to intercept it, the use of <code class="systemitem">mod_ssl</code> prevents any inspection or modification of the transmitted content. This section provides basic information on how to enable this module in the Apache HTTP Server configuration, and guides you through the process of generating private keys and self-signed certificates.
+ </div><div class="section" title="11.6.1. An Overview of Certificates and Security" id="s2-apache-mod_ssl-certificates"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mod_ssl-certificates">11.6.1. An Overview of Certificates and Security</h3></div></div></div><a id="id521823" class="indexterm"></a><a id="id521840" class="indexterm"></a><div class="para">
+ Secure communication is based on the use of keys. In conventional or <em class="firstterm">symmetric cryptography</em>, both ends of the transaction have the same key they can use to decode each other's transmissions. On the other hand, in public or <em class="firstterm">asymmetric cryptography</em>, two keys co-exist: a <em class="firstterm">private key</em> that is kept a secret, and a <em class="firstterm">public key</em> that is usually shared with the public. While the data encoded with the public key can only be decoded with the private key, data encoded with the private key can in turn only be decoded with the public key.
+ </div><a id="id850885" class="indexterm"></a><a id="id850902" class="indexterm"></a><div class="para">
+ To provide secure communications using SSL, an SSL server must use a digital certificate signed by a <em class="firstterm">Certificate Authority</em> (<acronym class="acronym">CA</acronym>). The certificate lists various attributes of the server (that is, the server hostname, the name of the company, its location, etc.), and the signature produced using the CA's private key. This signature ensures that a particular certificate authority has issued the certificate, and that the certificate has not been modified in any way.
+ </div><div class="para">
+ When a web browser establishes a new SSL connection, it checks the certificate provided by the web server. If the certificate does not have a signature from a trusted CA, or if the hostname listed in the certificate does not match the hostname used to establish the connection, it refuses to communicate with the server and usually presents a user with an appropriate error message.
+ </div><div class="para">
+ By default, most web browsers are configured to trust a set of widely used certificate authorities. Because of this, an appropriate CA should be chosen when setting up a secure server, so that target users can trust the connection, otherwise they will be presented with an error message, and will have to accept the certificate manually. Since encouraging users to override certificate errors can allow an attacker to intercept the connection, you should use a trusted CA whenever possible. For more information on this, see <a class="xref" href="s1-apache-mod_ssl.html#table-apache-mod_ssl-certificates-authorities" title="Table 11.22. CA lists for most common web browsers">Table 11.22, “CA lists for most common web browsers”</a>.
+ </div><div class="table" title="Table 11.22. CA lists for most common web browsers" id="table-apache-mod_ssl-certificates-authorities"><h6>Table 11.22. CA lists for most common web browsers</h6><div class="table-contents"><table summary="CA lists for most common web browsers" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Web Browser
+ </th><th>
+ Link
+ </th></tr></thead><tbody><tr><td>
+ <span class="application"><strong>Mozilla Firefox</strong></span>
+ </td><td>
+ <a href="http://www.mozilla.org/projects/security/certs/included/">Mozilla root CA list</a>.
+ </td></tr><tr><td>
+ <span class="application"><strong>Opera</strong></span>
+ </td><td>
+ <a href="http://my.opera.com/rootstore/blog/">The Opera Rootstore</a>.
+ </td></tr><tr><td>
+ <span class="application"><strong>Internet Explorer</strong></span>
+ </td><td>
+ <a href="http://support.microsoft.com/kb/931125">Windows root certificate program members</a>.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ When setting up an SSL server, you need to generate a certificate request and a private key, and then send the certificate request, proof of the company's identity, and payment to a certificate authority. Once the CA verifies the certificate request and your identity, it will send you a signed certificate you can use with your server. Alternatively, you can create a self-signed certificate that does not contain a CA signature, and thus should be used for testing purposes only.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-virtualhosts.html"><strong>Prev</strong>11.5. Setting Up Virtual Hosts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-apache-mod_ssl-enabling.html"><strong>Next</strong>11.6.2. Enabling the mod_ssl Module</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-resources.html
new file mode 100644
index 0000000..576ec33
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-resources.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.7. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_Apache_HTTP_Server.html" title="Chapter 11. The Apache HTTP Server" /><link rel="prev" href="s2-apache-mod_ssl-genkey.html" title="11.6.4. Generating a New Key and Certificate" /><link rel="next" href="s2-apache-resources-web.html" title="11.7.2. Useful Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-mod_ssl-genkey.html"><strong>Prev</strong
></a></li><li class="next"><a accesskey="n" href="s2-apache-resources-web.html"><strong>Next</strong></a></li></ul><div class="section" title="11.7. Additional Resources" id="s1-apache-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-resources">11.7. Additional Resources</h2></div></div></div><div class="para">
+ To learn more about the Apache HTTP Server, refer to the following resources.
+ </div><div class="section" title="11.7.1. Installed Documentation" id="s2-apache-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-resources-installed">11.7.1. Installed Documentation</h3></div></div></div><a id="id659555" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><a href="http://localhost/manual/">http://localhost/manual/</a></span></dt><dd><div class="para">
+ The official documentation for the Apache HTTP Server with the full description of its directives and available modules. Note that in order to access this documentation, you must have the <span class="package">httpd-manual</span> package installed, and the web server must be running.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man httpd</code></span></dt><dd><div class="para">
+ The manual page for the <code class="systemitem">httpd</code> service containing the complete list of its command line options.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man genkey</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">genkey</code> containing the full documentation on its usage.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-mod_ssl-genkey.html"><strong>Prev</strong>11.6.4. Generating a New Key and Certificate</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-apache-resources-web.html"><strong>Next</strong>11.7.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-running.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-running.html
new file mode 100644
index 0000000..26cbfab
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-running.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.2. Running the httpd Service</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_Apache_HTTP_Server.html" title="Chapter 11. The Apache HTTP Server" /><link rel="prev" href="ch-The_Apache_HTTP_Server.html" title="Chapter 11. The Apache HTTP Server" /><link rel="next" href="s2-apache-running-stopping.html" title="11.2.2. Stopping the Service" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-The_Apache_HTTP_Server.html"><strong>Prev</stron
g></a></li><li class="next"><a accesskey="n" href="s2-apache-running-stopping.html"><strong>Next</strong></a></li></ul><div class="section" title="11.2. Running the httpd Service" id="s1-apache-running"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-running">11.2. Running the <code class="systemitem">httpd</code> Service</h2></div></div></div><div class="para">
+ This section describes how to start, stop, restart, and check the current status of the Apache HTTP Server. To be able to use the <code class="systemitem">httpd</code> service, make sure you have the <span class="package">httpd</span> installed. You can do so by using the following command:
+ </div><pre class="screen">~]# <code class="command">yum install httpd</code></pre><div class="para">
+ For more information on the concept of runlevels and how to manage system services in Fedora in general, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div><div class="section" title="11.2.1. Starting the Service" id="s2-apache-running-starting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-running-starting">11.2.1. Starting the Service</h3></div></div></div><a id="id822259" class="indexterm"></a><div class="para">
+ To run the <code class="systemitem">httpd</code> service, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service httpd start</code>
+Starting httpd: [ OK ]</pre><div class="para">
+ If you want the service to start automatically at the boot time, use the following command:
+ </div><pre class="screen">~]# <code class="command">chkconfig httpd on</code></pre><div class="para">
+ This will enable the service for runlevel 2, 3, 4, and 5. Alternatively, you can use the <span class="application"><strong>Service Configuration</strong></span> utility as described in <a class="xref" href="s1-services-configuring.html#s3-services-serviceconf-enabling" title="7.2.1.1. Enabling the Service">Section 7.2.1.1, “Enabling the Service”</a>.
+ </div><div class="note" title="Note: Using the Secure Server"><div class="admonition_header"><h2>Note: Using the Secure Server</h2></div><div class="admonition"><div class="para">
+ If running the Apache HTTP Server as a secure server, a password may be required after the machine boots if using an encrypted private SSL key.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-The_Apache_HTTP_Server.html"><strong>Prev</strong>Chapter 11. The Apache HTTP Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-apache-running-stopping.html"><strong>Next</strong>11.2.2. Stopping the Service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-virtualhosts.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-virtualhosts.html
new file mode 100644
index 0000000..11511b9
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-apache-virtualhosts.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.5. Setting Up Virtual Hosts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_Apache_HTTP_Server.html" title="Chapter 11. The Apache HTTP Server" /><link rel="prev" href="s2-apache-dso-writing.html" title="11.4.2. Writing a Module" /><link rel="next" href="s1-apache-mod_ssl.html" title="11.6. Setting Up an SSL Server" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-dso-writing.html"><strong>Prev</strong></a></li><li class="next
"><a accesskey="n" href="s1-apache-mod_ssl.html"><strong>Next</strong></a></li></ul><div class="section" title="11.5. Setting Up Virtual Hosts" id="s1-apache-virtualhosts"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-apache-virtualhosts">11.5. Setting Up Virtual Hosts</h2></div></div></div><a id="id737661" class="indexterm"></a><a id="id737675" class="indexterm"></a><div class="para">
+ The Apache HTTP Server's built in virtual hosting allows the server to provide different information based on which IP address, hostname, or port is being requested.
+ </div><div class="para">
+ To create a name-based virtual host, find the virtual host container provided in <code class="filename">/etc/httpd/conf/httpd.conf</code> as an example, remove the hash sign (that is, <code class="literal">#</code>) from the beginning of each line, and customize the options according to your requirements as shown in <a class="xref" href="s1-apache-virtualhosts.html#example-apache-virtualhosts-config" title="Example 11.80. Sampe virtual host configuration">Example 11.80, “Sampe virtual host configuration”</a>.
+ </div><div class="example" title="Example 11.80. Sampe virtual host configuration" id="example-apache-virtualhosts-config"><h6>Example 11.80. Sampe virtual host configuration</h6><div class="example-contents"><pre class="screen">NameVirtualHost penguin.example.com:80
+
+<VirtualHost penguin.example.com:80>
+ ServerAdmin webmaster at penguin.example.com
+ DocumentRoot /www/docs/penguin.example.com
+ ServerName penguin.example.com:80
+ ErrorLog logs/penguin.example.com-error_log
+ CustomLog logs/penguin.example.com-access_log common
+</VirtualHost></pre></div></div><br class="example-break" /><div class="para">
+ Note that <code class="option">ServerName</code> must be a valid DNS name assigned to the machine. The <code class="option"><VirtualHost></code> container is highly customizable, and accepts most of the directives available within the main server configuration. Directives that are <span class="emphasis"><em>not</em></span> supported within this container include <code class="option">User</code> and <code class="option">Group</code>, which were replaced by <code class="option">SuexecUserGroup</code>.
+ </div><div class="note" title="Note: Changing the Port Number"><div class="admonition_header"><h2>Note: Changing the Port Number</h2></div><div class="admonition"><div class="para">
+ If you configure a virtual host to listen on a non-default port, make sure you update the <code class="option">Listen</code> directive in the global settings section of the <code class="filename">/etc/httpd/conf/httpd.conf</code> file accordingly.
+ </div></div></div><div class="para">
+ To activate a newly created virtual host, the web server has to be restarted first. Refer to <a class="xref" href="s3-apache-running-restarting.html" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a> for more information on how to restart the <code class="systemitem">httpd</code> service.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-dso-writing.html"><strong>Prev</strong>11.4.2. Writing a Module</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-mod_ssl.html"><strong>Next</strong>11.6. Setting Up an SSL Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-autotasks-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-autotasks-additional-resources.html
new file mode 100644
index 0000000..4689cd0
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-autotasks-additional-resources.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.3. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Automated_Tasks.html" title="Chapter 16. Automated Tasks" /><link rel="prev" href="s2-autotasks-at-batch-service.html" title="16.2.6. Starting and Stopping the Service" /><link rel="next" href="ch-Log_Files.html" title="Chapter 17. Log Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-at-batch-service.html"><strong>Prev</strong></a></li><li class
="next"><a accesskey="n" href="ch-Log_Files.html"><strong>Next</strong></a></li></ul><div class="section" title="16.3. Additional Resources" id="s1-autotasks-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-autotasks-additional-resources">16.3. Additional Resources</h2></div></div></div><a id="id578641" class="indexterm"></a><a id="id578655" class="indexterm"></a><a id="id578669" class="indexterm"></a><div class="para">
+ To learn more about configuring automated tasks, refer to the following resources.
+ </div><div class="section" title="16.3.1. Installed Documentation" id="s2-autotasks-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-installed-docs">16.3.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">cron</code> man page — contains an overview of cron.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">crontab</code> man pages in sections 1 and 5 — The man page in section 1 contains an overview of the <code class="filename">crontab</code> file. The man page in section 5 contains the format for the file and some example entries.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">anacron</code> man page — contains an overview of anacron.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">anacrontab</code> man page — contains an overview of the <code class="filename">anacrontab</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/at-<em class="replaceable"><code><version></code></em>/timespec</code> contains more detailed information about the times that can be specified for cron jobs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">at</code> man page — description of <code class="command">at</code> and <code class="command">batch</code> and their command line options.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-at-batch-service.html"><strong>Prev</strong>16.2.6. Starting and Stopping the Service</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Log_Files.html"><strong>Next</strong>Chapter 17. Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-autotasks-at-batch.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-autotasks-at-batch.html
new file mode 100644
index 0000000..66f2c2b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-autotasks-at-batch.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.2. At and Batch</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Automated_Tasks.html" title="Chapter 16. Automated Tasks" /><link rel="prev" href="ch-Automated_Tasks.html" title="Chapter 16. Automated Tasks" /><link rel="next" href="s2-autotasks-batch-configuring.html" title="16.2.2. Configuring Batch Jobs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Automated_Tasks.html"><strong>Prev</strong></a></li><li class="next"><
a accesskey="n" href="s2-autotasks-batch-configuring.html"><strong>Next</strong></a></li></ul><div class="section" title="16.2. At and Batch" id="s1-autotasks-at-batch"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-autotasks-at-batch">16.2. At and Batch</h2></div></div></div><a id="id760014" class="indexterm"></a><a id="id760028" class="indexterm"></a><div class="para">
+ While cron is used to schedule recurring tasks, the <code class="command">at</code> command is used to schedule a one-time task at a specific time and the <code class="command">batch</code> command is used to schedule a one-time task to be executed when the systems load average drops below 0.8.
+ </div><div class="para">
+ To use <code class="command">at</code> or <code class="command">batch</code>, the <code class="filename">at</code> RPM package must be installed, and the <code class="command">atd</code> service must be running. To determine if the package is installed, use the <code class="command">rpm -q at</code> command. To determine if the service is running, use the command <code class="command">/sbin/service atd status</code>.
+ </div><div class="section" title="16.2.1. Configuring At Jobs" id="s2-autotasks-at-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-at-configuring">16.2.1. Configuring At Jobs</h3></div></div></div><div class="para">
+ To schedule a one-time job at a specific time, type the command <code class="command">at <em class="replaceable"><code>time</code></em> </code>, where <code class="command"><em class="replaceable"><code>time</code></em> </code> is the time to execute the command.
+ </div><div class="para">
+ The argument <em class="replaceable"><code>time</code></em> can be one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ HH:MM format — For example, 04:00 specifies 4:00 a.m. If the time is already past, it is executed at the specified time the next day.
+ </div></li><li class="listitem"><div class="para">
+ midnight — Specifies 12:00 a.m.
+ </div></li><li class="listitem"><div class="para">
+ noon — Specifies 12:00 p.m.
+ </div></li><li class="listitem"><div class="para">
+ teatime — Specifies 4:00 p.m.
+ </div></li><li class="listitem"><div class="para">
+ month-name day year format — For example, January 15 2002 specifies the 15th day of January in the year 2002. The year is optional.
+ </div></li><li class="listitem"><div class="para">
+ MMDDYY, MM/DD/YY, or MM.DD.YY formats — For example, 011502 for the 15th day of January in the year 2002.
+ </div></li><li class="listitem"><div class="para">
+ now + time — time is in minutes, hours, days, or weeks. For example, now + 5 days specifies that the command should be executed at the same time five days from now.
+ </div></li></ul></div><div class="para">
+ The time must be specified first, followed by the optional date. For more information about the time format, read the <code class="filename">/usr/share/doc/at-<em class="replaceable"><code><version></code></em>/timespec</code> text file.
+ </div><div class="para">
+ After typing the <code class="command">at</code> command with the time argument, the <code class="prompt">at></code> prompt is displayed. Type the command to execute, press <span class="keycap"><strong>Enter</strong></span>, and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Multiple commands can be specified by typing each command followed by the <span class="keycap"><strong>Enter</strong></span> key. After typing all the commands, press <span class="keycap"><strong>Enter</strong></span> to go to a blank line and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Alternatively, a shell script can be entered at the prompt, pressing <span class="keycap"><strong>Enter</strong></span> after each line in the script, and pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> on a blank line to exit. If a script i
s entered, the shell used is the shell set in the user's <code class="envar">SHELL</code> environment, the user's login shell, or <code class="command">/bin/sh</code> (whichever is found first).
+ </div><div class="para">
+ If the set of commands or script tries to display information to standard output, the output is emailed to the user.
+ </div><div class="para">
+ Use the command <code class="command">atq</code> to view pending jobs. Refer to <a class="xref" href="s2-autotasks-at-batch-viewing.html" title="16.2.3. Viewing Pending Jobs">Section 16.2.3, “Viewing Pending Jobs”</a> for more information.
+ </div><div class="para">
+ Usage of the <code class="command">at</code> command can be restricted. For more information, refer to <a class="xref" href="s2-autotasks-at-batch-controlling-access.html" title="16.2.5. Controlling Access to At and Batch">Section 16.2.5, “Controlling Access to At and Batch”</a> for details.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Automated_Tasks.html"><strong>Prev</strong>Chapter 16. Automated Tasks</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-autotasks-batch-configuring.html"><strong>Next</strong>16.2.2. Configuring Batch Jobs</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-additional-resources.html
new file mode 100644
index 0000000..73437e3
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-additional-resources.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.8. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 10. The BIND DNS Server" /><link rel="prev" href="s1-bind-mistakes.html" title="10.7. Common Mistakes to Avoid" /><link rel="next" href="s2-bind-useful-websites.html" title="10.8.2. Useful Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-mistakes.html"><strong>Prev</strong></a></li><li class="next"><a access
key="n" href="s2-bind-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" title="10.8. Additional Resources" id="s1-bind-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-additional-resources">10.8. Additional Resources</h2></div></div></div><div class="para">
+ The following sources of information provide additional resources regarding BIND.
+ </div><div class="section" title="10.8.1. Installed Documentation" id="s2-bind-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-installed-docs">10.8.1. Installed Documentation</h3></div></div></div><a id="id838590" class="indexterm"></a><div class="para">
+ BIND features a full range of installed documentation covering many different topics, each placed in its own subject directory. For each item below, replace <em class="replaceable"><code>version</code></em> with the version of the <span class="package">bind</span> package installed on the system:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/</code></span></dt><dd><div class="para">
+ The main directory containing the most recent documentation.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/arm/</code></span></dt><dd><div class="para">
+ The directory containing the <em class="citetitle">BIND 9 Administrator Reference Manual</em> in HTML and SGML formats, which details BIND resource requirements, how to configure different types of nameservers, how to perform load balancing, and other advanced topics. For most new users of BIND, this is the best place to start.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/draft/</code></span></dt><dd><div class="para">
+ The directory containing assorted technical documents that review issues related to the DNS service, and propose some methods to address them.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/misc/</code></span></dt><dd><div class="para">
+ The directory designed to address specific advanced issues. Users of BIND version 8 should consult the <code class="filename">migration</code> document for specific changes they must make when moving to BIND 9. The <code class="filename">options</code> file lists all of the options implemented in BIND 9 that are used in <code class="filename">/etc/named.conf</code>.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/bind-<em class="replaceable"><code>version</code></em>/rfc/</code></span></dt><dd><div class="para">
+ The directory providing every RFC document related to BIND.
+ </div></dd></dl></div><div class="para">
+ There is also a number of man pages for the various applications and configuration files involved with BIND:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="command">man rndc</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">rndc</code> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man named</code></span></dt><dd><div class="para">
+ The manual page for <code class="systemitem">named</code> containing the documentation on assorted arguments that can be used to control the BIND nameserver daemon.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man lwresd</code></span></dt><dd><div class="para">
+ The manual page for <code class="systemitem">lwresd</code> containing the full documentation on the lightweight resolver daemon and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man named.conf</code></span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="systemitem">named</code> configuration file.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man rndc.conf</code></span></dt><dd><div class="para">
+ The manual page with a comprehensive list of options available within the <code class="command">rndc</code> configuration file.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-mistakes.html"><strong>Prev</strong>10.7. Common Mistakes to Avoid</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-useful-websites.html"><strong>Next</strong>10.8.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-dig.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-dig.html
new file mode 100644
index 0000000..ea4ef44
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-dig.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.5. Using the dig Utility</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 10. The BIND DNS Server" /><link rel="prev" href="s2-bind-rndc-querylog.html" title="10.4.6. Enabling the Query Logging" /><link rel="next" href="s2-bind-dig-a.html" title="10.5.2. Looking Up an IP Address" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-querylog.html"><strong>Prev</strong></a></li><li class="ne
xt"><a accesskey="n" href="s2-bind-dig-a.html"><strong>Next</strong></a></li></ul><div class="section" title="10.5. Using the dig Utility" id="s1-bind-dig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-dig">10.5. Using the <code class="command">dig</code> Utility</h2></div></div></div><a id="id667025" class="indexterm"></a><div class="para">
+ The <code class="command">dig</code> utility is a command line tool that allows you to perform DNS lookups and debug a nameserver configuration. Its typical usage is as follows:
+ </div><pre class="screen"><code class="command">dig</code> [@<em class="replaceable"><code>server</code></em>] [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>name</code></em> <em class="replaceable"><code>type</code></em></pre><div class="para">
+ Refer to <a class="xref" href="s3-bind-zone-rr.html" title="10.3.2. Common Resource Records">Section 10.3.2, “Common Resource Records”</a> for a list of common <em class="replaceable"><code>type</code></em>s.
+ </div><div class="section" title="10.5.1. Looking Up a Nameserver" id="s2-bind-dig-ns"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-dig-ns">10.5.1. Looking Up a Nameserver</h3></div></div></div><div class="para">
+ To look up a nameserver for a particular domain, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> NS</pre><div class="para">
+ In <a class="xref" href="s1-bind-dig.html#example-bind-dig-ns" title="Example 10.17. A Sample Nameserver Lookup">Example 10.17, “A Sample Nameserver Lookup”</a>, the <code class="command">dig</code> utility is used to display nameservers for <code class="systemitem">example.com</code>.
+ </div><div class="example" title="Example 10.17. A Sample Nameserver Lookup" id="example-bind-dig-ns"><h6>Example 10.17. A Sample Nameserver Lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com NS</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com NS
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57883
+;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN NS
+
+;; ANSWER SECTION:
+example.com. 99374 IN NS a.iana-servers.net.
+example.com. 99374 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:04:06 2010
+;; MSG SIZE rcvd: 77</pre></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-querylog.html"><strong>Prev</strong>10.4.6. Enabling the Query Logging</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-dig-a.html"><strong>Next</strong>10.5.2. Looking Up an IP Address</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-features.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-features.html
new file mode 100644
index 0000000..9f18481
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-features.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.6. Advanced Features of BIND</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 10. The BIND DNS Server" /><link rel="prev" href="s2-bind-dig-x.html" title="10.5.3. Looking Up a Hostname" /><link rel="next" href="s2-bind-features-ixfr.html" title="10.6.2. Incremental Zone Transfers (IXFR)" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-dig-x.html"><strong>Prev</strong></a></li><li class="next">
<a accesskey="n" href="s2-bind-features-ixfr.html"><strong>Next</strong></a></li></ul><div class="section" title="10.6. Advanced Features of BIND" id="s1-bind-features"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-features">10.6. Advanced Features of BIND</h2></div></div></div><div class="para">
+ Most BIND implementations only use the <code class="systemitem">named</code> service to provide name resolution services or to act as an authority for a particular domain. However, BIND version 9 has a number of advanced features that allow for a more secure and efficient DNS service.
+ </div><div class="important" title="Important: Make Sure the Feature is Supported"><div class="admonition_header"><h2>Important: Make Sure the Feature is Supported</h2></div><div class="admonition"><div class="para">
+ Before attempting to use advanced features like DNSSEC, TSIG, or IXFR, make sure that the particular feature is supported by all nameservers in the network environment, especially when you use older versions of BIND or non-BIND servers.
+ </div></div></div><div class="para">
+ All of the features mentioned are discussed in greater detail in the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="s1-bind-additional-resources.html#s2-bind-installed-docs" title="10.8.1. Installed Documentation">Section 10.8.1, “Installed Documentation”</a>.
+ </div><div class="section" title="10.6.1. Multiple Views" id="s2-bind-features-views"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-views">10.6.1. Multiple Views</h3></div></div></div><a id="id748774" class="indexterm"></a><div class="para">
+ Optionally, different information can be presented to a client depending on the network a request originates from. This is primarily used to deny sensitive DNS entries from clients outside of the local network, while allowing queries from clients inside the local network.
+ </div><div class="para">
+ To configure multiple views, add the <code class="command">view</code> statement to the <code class="filename">/etc/named.conf</code> configuration file. Use the <code class="option">match-clients</code> option to match IP addresses or entire networks and give them special options and zone data.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-dig-x.html"><strong>Prev</strong>10.5.3. Looking Up a Hostname</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-features-ixfr.html"><strong>Next</strong>10.6.2. Incremental Zone Transfers (IXFR)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-mistakes.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-mistakes.html
new file mode 100644
index 0000000..4aea3d8
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-mistakes.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.7. Common Mistakes to Avoid</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 10. The BIND DNS Server" /><link rel="prev" href="s2-bind-features-ipv6.html" title="10.6.5. Internet Protocol version 6 (IPv6)" /><link rel="next" href="s1-bind-additional-resources.html" title="10.8. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-ipv6.html"><strong>Prev</strong></a><
/li><li class="next"><a accesskey="n" href="s1-bind-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="10.7. Common Mistakes to Avoid" id="s1-bind-mistakes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-mistakes">10.7. Common Mistakes to Avoid</h2></div></div></div><a id="id719143" class="indexterm"></a><div class="para">
+ The following is a list of advices how to avoid common mistakes users make when configuring a nameserver:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">Use semicolons and curly brackets correctly</span></dt><dd><div class="para">
+ An omitted semicolon or unmatched curly bracket in the <code class="filename">/etc/named.conf</code> file can prevent the <code class="systemitem">named</code> service from starting.
+ </div></dd><dt class="varlistentry"><span class="term">Use period (that is, the <code class="literal">.</code> character) correctly</span></dt><dd><div class="para">
+ In zone files, a period at the end of a domain name denotes a fully qualified domain name. If omitted, the <code class="systemitem">named</code> service will append the name of the zone or the value of <code class="option">$ORIGIN</code> to complete it.
+ </div></dd><dt class="varlistentry"><span class="term">Increment the serial number when editing a zone file</span></dt><dd><div class="para">
+ If the serial number is not incremented, the primary nameserver will have the correct, new information, but the secondary nameservers will never be notified of the change, and will not attempt to refresh their data of that zone.
+ </div></dd><dt class="varlistentry"><span class="term">Configure the firewall</span></dt><dd><div class="para">
+ If a firewall is blocking connections from the <code class="systemitem">named</code> service to other nameservers, the recommended best practice is to change the firewall settings whenever possible.
+ </div><div class="warning" title="Warning: Avoid Using Fixed UDP Source Ports" id="warning-Warning-Avoid_Using_Fixed_UDP_Source_Ports"><div class="admonition_header"><h2>Warning: Avoid Using Fixed UDP Source Ports</h2></div><div class="admonition"><div class="para">
+ According to the recent research in DNS security, using a fixed UDP source port for DNS queries is a potential security vulnerability that could allow an attacker to conduct cache-poisoning attacks more easily. To prevent this, configure your firewall to allow queries from a random UDP source port.
+ </div></div></div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-ipv6.html"><strong>Prev</strong>10.6.5. Internet Protocol version 6 (IPv6)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-bind-additional-resources.html"><strong>Next</strong>10.8. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-namedconf.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-namedconf.html
new file mode 100644
index 0000000..750aec9
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-namedconf.html
@@ -0,0 +1,290 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2. Configuring the named Service</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 10. The BIND DNS Server" /><link rel="prev" href="ch-The_BIND_DNS_Server.html" title="Chapter 10. The BIND DNS Server" /><link rel="next" href="s2-bind-namedconf-state-other.html" title="10.2.2. Other Statement Types" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-The_BIND_DNS_Server.html"><strong>Prev</strong></a></li>
<li class="next"><a accesskey="n" href="s2-bind-namedconf-state-other.html"><strong>Next</strong></a></li></ul><div class="section" title="10.2. Configuring the named Service" id="s1-bind-namedconf"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-namedconf">10.2. Configuring the <code class="command">named</code> Service</h2></div></div></div><a id="id732799" class="indexterm"></a><div class="para">
+ When the <code class="systemitem">named</code> service is started, it reads the configuration from the files as described in <a class="xref" href="s1-bind-namedconf.html#table-bind-namedconf-files" title="Table 10.1. The named service configuration files">Table 10.1, “The <code class="systemitem">named</code> service configuration files”</a>.
+ </div><a id="id778304" class="indexterm"></a><a id="id778317" class="indexterm"></a><a id="id778335" class="indexterm"></a><div class="table" title="Table 10.1. The named service configuration files" id="table-bind-namedconf-files"><h6>Table 10.1. The <code class="systemitem">named</code> service configuration files</h6><div class="table-contents"><table summary="The named service configuration files" border="1"><colgroup><col width="38%" /><col width="63%" /></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc/named.conf</code>
+ </td><td>
+ The main configuration file.
+ </td></tr><tr><td>
+ <code class="filename">/etc/named/</code>
+ </td><td>
+ An auxiliary directory for configuration files that are included in the main configuration file.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The configuration file consists of a collection of statements with nested options surrounded by opening and closing curly brackets (that is, <code class="literal">{</code> and <code class="literal">}</code>). Note that when editing the file, you have to be careful not to make any syntax error, otherwise the <code class="systemitem">named</code> service will not start. A typical <code class="filename">/etc/named.conf</code> file is organized as follows:
+ </div><pre class="screen"><em class="replaceable"><code>statement-1</code></em> ["<em class="replaceable"><code>statement-1-name</code></em>"] [<em class="replaceable"><code>statement-1-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-2</code></em> ["<em class="replaceable"><code>statement-2-name</code></em>"] [<em class="replaceable"><code>statement-2-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};
+<em class="replaceable"><code>statement-N</code></em> ["<em class="replaceable"><code>statement-N-name</code></em>"] [<em class="replaceable"><code>statement-N-class</code></em>] {
+ <em class="replaceable"><code>option-1</code></em>;
+ <em class="replaceable"><code>option-2</code></em>;
+ <em class="replaceable"><code>option-N</code></em>;
+};</pre><div class="note" title="Note: Running BIND in a Chroot Environment"><div class="admonition_header"><h2>Note: Running BIND in a Chroot Environment</h2></div><div class="admonition"><div class="para">
+ If you have installed the <span class="package">bind-chroot</span> package, the BIND service will run in the <code class="filename">/var/named/chroot</code> environment. In that case, the initialization script will mount the above configuration files using the <code class="command">mount --bind</code> command, so that you can manage the configuration outside this environment.
+ </div></div></div><div class="section" title="10.2.1. Common Statement Types" id="s2-bind-namedconf-state"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-namedconf-state">10.2.1. Common Statement Types</h3></div></div></div><div class="para">
+ The following types of statements are commonly used in <code class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id499081" class="indexterm"></a>
+ <code class="option">acl</code> </span></dt><dd><div class="para">
+ The <code class="option">acl</code> (Access Control List) statement allows you to define groups of hosts, so that they can be permitted or denied access to the nameserver. It takes the following form:
+ </div><pre class="screen">acl <em class="replaceable"><code>acl-name</code></em> {
+ <em class="replaceable"><code>match-element</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>acl-name</code></em> statement name is the name of the access control list, and the <em class="replaceable"><code>match-element</code></em> option is usually an individual IP address (such as <code class="literal">10.0.1.1</code>) or a CIDR network notation (for example, <code class="literal">10.0.1.0/24</code>). For a list of already defined keywords, see <a class="xref" href="s1-bind-namedconf.html#table-bind-namedconf-common-acl" title="Table 10.2. Predefined access control lists">Table 10.2, “Predefined access control lists”</a>.
+ </div><div class="table" title="Table 10.2. Predefined access control lists" id="table-bind-namedconf-common-acl"><h6>Table 10.2. Predefined access control lists</h6><div class="table-contents"><table summary="Predefined access control lists" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Keyword
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">any</code>
+ </td><td>
+ Matches every IP address.
+ </td></tr><tr><td>
+ <code class="option">localhost</code>
+ </td><td>
+ Matches any IP address that is in use by the local system.
+ </td></tr><tr><td>
+ <code class="option">localnets</code>
+ </td><td>
+ Matches any IP address on any network to which the local system is connected.
+ </td></tr><tr><td>
+ <code class="option">none</code>
+ </td><td>
+ Does not match any IP address.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="option">acl</code> statement can be especially useful with conjunction with other statements such as <code class="option">options</code>. <a class="xref" href="s1-bind-namedconf.html#example-bind-namedconf-common-acl" title="Example 10.2. Using acl in conjunction with options">Example 10.2, “Using <code class="option">acl</code> in conjunction with <code class="option">options</code>”</a> defines two access control lists, <code class="literal">black-hats</code> and <code class="literal">red-hats</code>, and adds <code class="literal">black-hats</code> on the blacklist while granting <code class="literal">red-hats</code> a normal access.
+ </div><div class="example" title="Example 10.2. Using acl in conjunction with options" id="example-bind-namedconf-common-acl"><h6>Example 10.2. Using <code class="option">acl</code> in conjunction with <code class="option">options</code></h6><div class="example-contents"><pre class="screen">acl black-hats {
+ 10.0.2.0/24;
+ 192.168.0.0/24;
+ 1234:5678::9abc/24;
+};
+acl red-hats {
+ 10.0.1.0/24;
+};
+options {
+ blackhole { black-hats; };
+ allow-query { red-hats; };
+ allow-query-cache { red-hats; };
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id544718" class="indexterm"></a>
+ <code class="option">include</code> </span></dt><dd><div class="para">
+ The <code class="option">include</code> statement allows you to include files in the <code class="filename">/etc/named.conf</code>, so that potentially sensitive data can be placed in a separate file with restricted permissions. It takes the following form:
+ </div><pre class="screen">include "<em class="replaceable"><code>file-name</code></em>"</pre><div class="para">
+ The <em class="replaceable"><code>file-name</code></em> statement name is an absolute path to a file.
+ </div><div class="example" title="Example 10.3. Including a file to /etc/named.conf" id="example-bind-namedconf-common-include"><h6>Example 10.3. Including a file to <code class="filename">/etc/named.conf</code></h6><div class="example-contents"><pre class="screen">include "/etc/named.rfc1912.zones";</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id634354" class="indexterm"></a>
+ <code class="option">options</code> </span></dt><dd><div class="para">
+ The <code class="option">options</code> statement allows you to define global server configuration options as well as to set defaults for other statements. It can be used to specify the location of the <code class="systemitem">named</code> working directory, the types of queries allowed, and much more. It takes the following form:
+ </div><pre class="screen">options {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ For a list of frequently used <em class="replaceable"><code>option</code></em> directives, see <a class="xref" href="s1-bind-namedconf.html#table-bind-namedconf-common-options" title="Table 10.3. Commonly used options">Table 10.3, “Commonly used options”</a> below.
+ </div><div class="table" title="Table 10.3. Commonly used options" id="table-bind-namedconf-common-options"><h6>Table 10.3. Commonly used options</h6><div class="table-contents"><table summary="Commonly used options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow-query</code>
+ </td><td>
+ Specifies which hosts are allowed to query the nameserver for authoritative resource records. It accepts an access control lists, a collection of IP addresses, or networks in the CIDR notation. All hosts are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">allow-query-cache</code>
+ </td><td>
+ Specifies which hosts are allowed to query the nameserver for non-authoritative data such as recursive queries. Only <code class="literal">localhost</code> and <code class="literal">localnets</code> are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">blackhole</code>
+ </td><td>
+ Specifies which hosts are <span class="emphasis"><em>not</em></span> allowed to query the nameserver. This option should be used when particular host or network floods the server with requests. The default option is <code class="literal">none</code>.
+ </td></tr><tr><td>
+ <code class="option">directory</code>
+ </td><td>
+ Specifies a working directory for the <code class="systemitem">named</code> service. The default option is <code class="literal">/var/named/</code>.
+ </td></tr><tr><td>
+ <code class="option">dnssec-enable</code>
+ </td><td>
+ Specifies whether to return DNSSEC related resource records. The default option is <code class="literal">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">dnssec-validation</code>
+ </td><td>
+ Specifies whether to prove that resource records are authentic via DNSSEC. The default option is <code class="option">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">forwarders</code>
+ </td><td>
+ Specifies a list of valid IP addresses for nameservers to which the requests should be forwarded for resolution.
+ </td></tr><tr><td>
+ <code class="option">forward</code>
+ </td><td>
+ <div class="para">
+ Specifies the behavior of the <code class="option">forwarders</code> directive. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">first</code> — The server will query the nameservers listed in the <code class="option">forwarders</code> directive before attempting to resolve the name on its own.
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">only</code> — When unable to query the nameservers listed in the <code class="option">forwarders</code> directive, the server will not attempt to resolve the name on its own.
+ </div></li></ul></div>
+
+ </td></tr><tr><td>
+ <code class="option">listen-on</code>
+ </td><td>
+ Specifies the IPv4 network interface on which to listen for queries. On a DNS server that also acts as a gateway, you can use this option to answer queries originating from a single network only. All IPv4 interfaces are used by default.
+ </td></tr><tr><td>
+ <code class="option">listen-on-v6</code>
+ </td><td>
+ Specifies the IPv6 network interface on which to listen for queries. On a DNS server that also acts as a gateway, you can use this option to answer queries originating from a single network only. All IPv6 interfaces are used by default.
+ </td></tr><tr><td>
+ <code class="option">max-cache-size</code>
+ </td><td>
+ Specifies the maximum amount of memory to be used for server caches. When the limit is reached, the server causes records to expire prematurely so that the limit is not exceeded. In a server with multiple views, the limit applies separately to the cache of each view. The default option is <code class="literal">32M</code>.
+ </td></tr><tr><td>
+ <code class="option">notify</code>
+ </td><td>
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">yes</code> — The server will notify all secondary nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">no</code> — The server will <span class="emphasis"><em>not</em></span> notify any secondary nameserver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master-only</code> — The server will notify primary server for the zone only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">explicit</code> — The server will notify only the secondary servers that are specified in the <code class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td>
+ <code class="option">pid-file</code>
+ </td><td>
+ Specifies the location of the process ID file created by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <code class="option">recursion</code>
+ </td><td>
+ Specifies whether to act as a recursive server. The default option is <code class="literal">yes</code>.
+ </td></tr><tr><td>
+ <code class="option">statistics-file</code>
+ </td><td>
+ Specifies an alternate location for statistics files. The <code class="filename">/var/named/named.stats</code> file is used by default.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="important" title="Important: Restrict Recursive Servers to Selected Clients Only"><div class="admonition_header"><h2>Important: Restrict Recursive Servers to Selected Clients Only</h2></div><div class="admonition"><div class="para">
+ To prevent distributed denial of service (DDoS) attacks, it is recommended that you use the <code class="option">allow-query-cache</code> option to restrict recursive DNS services for a particular subset of clients only.
+ </div></div></div><div class="para">
+ Refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="s1-bind-additional-resources.html#s2-bind-installed-docs" title="10.8.1. Installed Documentation">Section 10.8.1, “Installed Documentation”</a>, and the <code class="filename">named.conf</code> manual page for a complete list of available options.
+ </div><div class="example" title="Example 10.4. Using the options statement" id="example-bind-namedconf-common-options"><h6>Example 10.4. Using the <code class="option">options</code> statement</h6><div class="example-contents"><pre class="screen">options {
+ allow-query { localhost; };
+ listen-on port 53 { 127.0.0.1; };
+ listen-on-v6 port 53 { ::1; };
+ max-cache-size 256M;
+ directory "/var/named";
+ statistics-file "/var/named/data/named_stats.txt";
+
+ recursion yes;
+ dnssec-enable yes;
+ dnssec-validation yes;
+};</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id849165" class="indexterm"></a>
+ <code class="option">zone</code> </span></dt><dd><div class="para">
+ The <code class="option">zone</code> statement allows you to define the characteristics of a zone, such as the location of its configuration file and zone-specific options, and can be used to override the global <code class="option">options</code> statements. It takes the following form:
+ </div><pre class="screen">zone <em class="replaceable"><code>zone-name</code></em> [<em class="replaceable"><code>zone-class</code></em>] {
+ <em class="replaceable"><code>option</code></em>;
+ ...
+};</pre><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is the name of the zone, <em class="replaceable"><code>zone-class</code></em> is the optional class of the zone, and <em class="replaceable"><code>option</code></em> is a <code class="option">zone</code> statement option as described in <a class="xref" href="s1-bind-namedconf.html#table-bind-namedconf-common-zone" title="Table 10.4. Commonly used options">Table 10.4, “Commonly used options”</a>.
+ </div><div class="para">
+ The <em class="replaceable"><code>zone-name</code></em> attribute is particularly important, as it is the default value assigned for the <code class="option">$ORIGIN</code> directive used within the corresponding zone file located in the <code class="filename">/var/named/</code> directory. The <code class="systemitem">named</code> daemon appends the name of the zone to any non-fully qualified domain name listed in the zone file. For example, if a <code class="option">zone</code> statement defines the namespace for <code class="literal">example.com</code>, use <code class="literal">example.com</code> as the <em class="replaceable"><code>zone-name</code></em> so that it is placed at the end of hostnames within the <code class="literal">example.com</code> zone file.
+ </div><div class="para">
+ For more information about zone files, refer to <a class="xref" href="s1-bind-zone.html" title="10.3. Editing Zone Files">Section 10.3, “Editing Zone Files”</a>.
+ </div><div class="table" title="Table 10.4. Commonly used options" id="table-bind-namedconf-common-zone"><h6>Table 10.4. Commonly used options</h6><div class="table-contents"><table summary="Commonly used options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">allow-query</code>
+ </td><td>
+ Specifies which clients are allowed to request information about this zone. This option overrides global <code class="option">allow-query</code> option. All query requests are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">allow-transfer</code>
+ </td><td>
+ Specifies which secondary servers are allowed to request a transfer of the zone's information. All transfer requests are allowed by default.
+ </td></tr><tr><td>
+ <code class="option">allow-update</code>
+ </td><td>
+ <div class="para">
+ Specifies which hosts are allowed to dynamically update information in their zone. The default option is to deny all dynamic update requests.
+ </div>
+ <div class="para">
+ Note that you should be careful when allowing hosts to update information about their zone. Do not set IP addresses in this option unless the server is in the trusted network. Instead, use TSIG key as described in <a class="xref" href="s2-bind-features-tsig.html" title="10.6.3. Transaction SIGnatures (TSIG)">Section 10.6.3, “Transaction SIGnatures (TSIG)”</a>.
+ </div>
+
+ </td></tr><tr><td>
+ <code class="option">file</code>
+ </td><td>
+ Specifies the name of the file in the <code class="systemitem">named</code> working directory that contains the zone's configuration data.
+ </td></tr><tr><td>
+ <code class="option">masters</code>
+ </td><td>
+ Specifies from which IP addresses to request authoritative zone information. This option is used only if the zone is defined as <code class="option">type</code> <code class="option">slave</code>.
+ </td></tr><tr><td>
+ <code class="option">notify</code>
+ </td><td>
+ <div class="para">
+ Specifies whether to notify the secondary nameservers when a zone is updated. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">yes</code> — The server will notify all secondary nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">no</code> — The server will <span class="emphasis"><em>not</em></span> notify any secondary nameserver.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master-only</code> — The server will notify primary server for the zone only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">explicit</code> — The server will notify only the secondary servers that are specified in the <code class="option">also-notify</code> list within a zone statement.
+ </div></li></ul></div>
+
+ </td></tr><tr><td>
+ <code class="option">type</code>
+ </td><td>
+ <div class="para">
+ Specifies the zone type. It accepts the following options:
+ </div>
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">delegation-only</code> — Enforces the delegation status of infrastructure zones such as COM, NET, or ORG. Any answer that is received without an explicit or implicit delegation is treated as <code class="literal">NXDOMAIN</code>. This option is only applicable in TLDs or root zone files used in recursive or caching implementations.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">forward</code> — Forwards all requests for information about this zone to other nameservers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">hint</code> — A special type of zone used to point to the root nameservers which resolve queries when a zone is not otherwise known. No configuration beyond the default is necessary with a <code class="option">hint</code> zone.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">master</code> — Designates the nameserver as authoritative for this zone. A zone should be set as the <code class="option">master</code> if the zone's configuration files reside on the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">slave</code> — Designates the nameserver as a slave server for this zone. Master server is specified in <code class="option">masters</code> directive.
+ </div></li></ul></div>
+
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Most changes to the <code class="filename">/etc/named.conf</code> file of a primary or secondary nameserver involve adding, modifying, or deleting <code class="option">zone</code> statements, and only a small subset of <code class="option">zone</code> statement options is usually needed for a nameserver to work efficiently.
+ </div><div class="para">
+ In <a class="xref" href="s1-bind-namedconf.html#example-bind-namedconf-common-zone-primary" title="Example 10.5. A zone statement for a primary nameserver">Example 10.5, “A <code class="option">zone</code> statement for a primary nameserver”</a>, the zone is identified as <code class="literal">example.com</code>, the type is set to <code class="literal">master</code>, and the <code class="systemitem">named</code> service is instructed to read the <code class="filename">/var/named/example.com.zone</code> file. It also allows only a secondary nameserver (<code class="literal">192.168.0.2</code>) to transfer the zone.
+ </div><div class="example" title="Example 10.5. A zone statement for a primary nameserver" id="example-bind-namedconf-common-zone-primary"><h6>Example 10.5. A <code class="option">zone</code> statement for a primary nameserver</h6><div class="example-contents"><pre class="screen">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-transfer { 192.168.0.2; };
+};</pre></div></div><br class="example-break" /><div class="para">
+ A secondary server's <code class="option">zone</code> statement is slightly different. The type is set to <code class="literal">slave</code>, and the <code class="literal">masters</code> directive is telling <code class="systemitem">named</code> the IP address of the master server.
+ </div><div class="para">
+ In <a class="xref" href="s1-bind-namedconf.html#example-bind-namedconf-common-zone-secondary" title="Example 10.6. A zone statement for a secondary nameserver">Example 10.6, “A <code class="option">zone</code> statement for a secondary nameserver”</a>, the <code class="systemitem">named</code> service is configured to query the primary server at the <code class="literal">192.168.0.1</code> IP address for information about the <code class="literal">example.com</code> zone. The received information is then saved to the <code class="filename">/var/named/slaves/example.com.zone</code> file. Note that you have to put all slave zones to <code class="filename">/var/named/slaves</code> directory, otherwise the service will fail to transfer the zone.
+ </div><div class="example" title="Example 10.6. A zone statement for a secondary nameserver" id="example-bind-namedconf-common-zone-secondary"><h6>Example 10.6. A <code class="option">zone</code> statement for a secondary nameserver</h6><div class="example-contents"><pre class="screen">zone "example.com" {
+ type slave;
+ file "slaves/example.com.zone";
+ masters { 192.168.0.1; };
+};</pre></div></div><br class="example-break" /></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-The_BIND_DNS_Server.html"><strong>Prev</strong>Chapter 10. The BIND DNS Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-namedconf-state-other.html"><strong>Next</strong>10.2.2. Other Statement Types</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-rndc.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-rndc.html
new file mode 100644
index 0000000..a9eaca6
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-rndc.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4. Using the rndc Utility</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 10. The BIND DNS Server" /><link rel="prev" href="s2-bind-zone-examples.html" title="10.3.4. Example Usage" /><link rel="next" href="s2-bind-rndc-status.html" title="10.4.2. Checking the Service Status" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-zone-examples.html"><strong>Prev</strong></a></li><li class="next">
<a accesskey="n" href="s2-bind-rndc-status.html"><strong>Next</strong></a></li></ul><div class="section" title="10.4. Using the rndc Utility" id="s1-bind-rndc"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-rndc">10.4. Using the <code class="command">rndc</code> Utility</h2></div></div></div><a id="id733644" class="indexterm"></a><div class="para">
+ The <code class="command">rndc</code> utility is a command line tool that allows you to administer the <code class="systemitem">named</code> service, both locally and from a remote machine. Its usage is as follows:
+ </div><pre class="screen"><code class="command">rndc</code> [<em class="replaceable"><code>option</code></em>...] <em class="replaceable"><code>command</code></em> [<em class="replaceable"><code>command-option</code></em>]</pre><div class="section" title="10.4.1. Configuring the Utility" id="s2-bind-rndc-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-configuration">10.4.1. Configuring the Utility</h3></div></div></div><div class="para">
+ To prevent unauthorized access to the service, <code class="systemitem">named</code> must be configured to listen on the selected port (that is, <code class="literal">953</code> by default), and an identical key must be used by both the service and the <code class="command">rndc</code> utility.
+ </div><div class="table" title="Table 10.7. Relevant files" id="table-bind-rndc-configuration-files"><h6>Table 10.7. Relevant files</h6><div class="table-contents"><table summary="Relevant files" border="1"><colgroup><col width="38%" /><col width="63%" /></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <a id="id489042" class="indexterm"></a>
+ <code class="filename">/etc/named.conf</code>
+ </td><td>
+ The default configuration file for the <code class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <a id="id495120" class="indexterm"></a>
+ <code class="filename">/etc/rndc.conf</code>
+ </td><td>
+ The default configuration file for the <code class="command">rndc</code> utility.
+ </td></tr><tr><td>
+ <a id="id495157" class="indexterm"></a>
+ <code class="filename">/etc/rndc.key</code>
+ </td><td>
+ The default key location.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">rndc</code> configuration is located in <code class="filename">/etc/rndc.conf</code>. If the file does not exist, the utility will use the key located in <code class="filename">/etc/rndc.key</code>, which was generated automatically during the installation process using the <code class="command">rndc-confgen -a</code> command.
+ </div><div class="para">
+ The <code class="systemitem">named</code> service is configured using the <code class="option">controls</code> statement in the <code class="filename">/etc/named.conf</code> configuration file as described in <a class="xref" href="s2-bind-namedconf-state-other.html" title="10.2.2. Other Statement Types">Section 10.2.2, “Other Statement Types”</a>. Unless this statement is present, only the connections from the loopback address (that is, <code class="systemitem">127.0.0.1</code>) will be allowed, and the key located in <code class="filename">/etc/rndc.key</code> will be used.
+ </div><div class="para">
+ For more information on this topic, refer to manual pages and the <em class="citetitle">BIND 9 Administrator Reference Manual</em> listed in <a class="xref" href="s1-bind-additional-resources.html" title="10.8. Additional Resources">Section 10.8, “Additional Resources”</a>.
+ </div><div class="important" title="Important: Set the Correct Permissions"><div class="admonition_header"><h2>Important: Set the Correct Permissions</h2></div><div class="admonition"><div class="para">
+ To prevent unprivileged users from sending control commands to the service, make sure only root is allowed to read the <code class="filename">/etc/rndc.key</code> file:
+ </div><pre class="screen">~]# <code class="command">chmod o-rwx /etc/rndc.key</code></pre></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-zone-examples.html"><strong>Prev</strong>10.3.4. Example Usage</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-rndc-status.html"><strong>Next</strong>10.4.2. Checking the Service Status</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-zone.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-zone.html
new file mode 100644
index 0000000..8f0a312
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-bind-zone.html
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.3. Editing Zone Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_BIND_DNS_Server.html" title="Chapter 10. The BIND DNS Server" /><link rel="prev" href="s2-bind-namedconf-comm.html" title="10.2.3. Comment Tags" /><link rel="next" href="s3-bind-zone-rr.html" title="10.3.2. Common Resource Records" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-namedconf-comm.html"><strong>Prev</strong></a></li><li class="next"><a acce
sskey="n" href="s3-bind-zone-rr.html"><strong>Next</strong></a></li></ul><div class="section" title="10.3. Editing Zone Files" id="s1-bind-zone"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-bind-zone">10.3. Editing Zone Files</h2></div></div></div><a id="id531590" class="indexterm"></a><a id="id531610" class="indexterm"></a><a id="id841109" class="indexterm"></a><a id="id841128" class="indexterm"></a><div class="para">
+ As outlined in <a class="xref" href="ch-The_BIND_DNS_Server.html#s2-bind-introduction-zones" title="10.1.1. Nameserver Zones">Section 10.1.1, “Nameserver Zones”</a>, zone files contain information about a namespace. They are stored in the <code class="systemitem">named</code> working directory located in <code class="filename">/var/named/</code> by default, and each zone file is named according to the <code class="option">file</code> option in the <code class="option">zone</code> statement, usually in a way that relates to the domain in question and identifies the file as containing zone data, such as <code class="filename">example.com.zone</code>.
+ </div><div class="table" title="Table 10.5. The named service zone files" id="table-bind-zone-files"><h6>Table 10.5. The <code class="systemitem">named</code> service zone files</h6><div class="table-contents"><table summary="The named service zone files" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th>
+ Path
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/var/named/</code>
+ </td><td>
+ The working directory for the <code class="systemitem">named</code> service. The nameserver is <span class="emphasis"><em>not</em></span> allowed to write to this directory.
+ </td></tr><tr><td>
+ <code class="filename">/var/named/slaves/</code>
+ </td><td>
+ The directory for secondary zones. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <code class="filename">/var/named/dynamic/</code>
+ </td><td>
+ The directory for other files, such as dynamic DNS (DDNS) zones or managed DNSSEC keys. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr><tr><td>
+ <code class="filename">/var/named/data/</code>
+ </td><td>
+ The directory for various statistics and debugging files. This directory is writable by the <code class="systemitem">named</code> service.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ A zone file consists of directives and resource records. Directives tell the nameserver to perform tasks or apply special settings to the zone, resource records define the parameters of the zone and assign identities to individual hosts. While the directives are optional, the resource records are required in order to provide name service to a zone.
+ </div><div class="para">
+ All directives and resource records should be entered on individual lines.
+ </div><div class="section" title="10.3.1. Common Directives" id="s2-bind-zone-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-zone-directives">10.3.1. Common Directives</h3></div></div></div><div class="para">
+ Directives begin with the dollar sign character (that is, <code class="literal">$</code>) followed by the name of the directive, and usually appear at the top of the file. The following directives are commonly used in zone files:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id478551" class="indexterm"></a>
+ <code class="command">$INCLUDE</code> </span></dt><dd><div class="para">
+ The <code class="command">$INCLUDE</code> directive allows you to include another file at the place where it appears, so that other zone settings can be stored in a separate zone file.
+ </div><div class="example" title="Example 10.7. Using the $INCLUDE directive" id="example-bind-zone-directive-include"><h6>Example 10.7. Using the <code class="command">$INCLUDE</code> directive</h6><div class="example-contents"><pre class="screen">$INCLUDE /var/named/penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id478612" class="indexterm"></a>
+ <code class="command">$ORIGIN</code> </span></dt><dd><div class="para">
+ The <code class="command">$ORIGIN</code> directive allows you to append the domain name to unqualified records, such as those with the hostname only. Note that the use of this directive is not necessary if the zone is specified in <code class="filename">/etc/named.conf</code>, since the zone name is used by default.
+ </div><div class="para">
+ In <a class="xref" href="s1-bind-zone.html#example-bind-zone-directive-origin" title="Example 10.8. Using the $ORIGIN directive">Example 10.8, “Using the <code class="command">$ORIGIN</code> directive”</a>, any names used in resource records that do not end in a trailing period (that is, the <code class="literal">.</code> character) are appended with <code class="literal">example.com</code>.
+ </div><div class="example" title="Example 10.8. Using the $ORIGIN directive" id="example-bind-zone-directive-origin"><h6>Example 10.8. Using the <code class="command">$ORIGIN</code> directive</h6><div class="example-contents"><pre class="screen">$ORIGIN example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id705595" class="indexterm"></a>
+ <code class="command">$TTL</code> </span></dt><dd><div class="para">
+ The <code class="command">$TTL</code> directive allows you to set the default <em class="firstterm">Time to Live</em> (TTL) value for the zone, that is, how long is a zone record valid. Each resource record can contain its own TTL value, which overrides this directive.
+ </div><div class="para">
+ Increasing this value allows remote nameservers to cache the zone information for a longer period of time, reducing the number of queries for the zone and lengthening the amount of time required to proliferate resource record changes.
+ </div><div class="example" title="Example 10.9. Using the $TTL directive" id="example-bind-zone-directive-ttl"><h6>Example 10.9. Using the <code class="command">$TTL</code> directive</h6><div class="example-contents"><pre class="screen">$TTL 1D</pre></div></div><br class="example-break" /></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-namedconf-comm.html"><strong>Prev</strong>10.2.3. Comment Tags</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s3-bind-zone-rr.html"><strong>Next</strong>10.3.2. Common Resource Records</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-check-rpm-sig.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-check-rpm-sig.html
new file mode 100644
index 0000000..e02f39f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-check-rpm-sig.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3. Checking a Package's Signature</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-RPM.html" title="Chapter 3. RPM" /><link rel="prev" href="s2-rpm-verifying.html" title="3.2.7. Verifying" /><link rel="next" href="s2-keys-checking.html" title="3.3.2. Verifying Signature of Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-verifying.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-keys-checking.html"><s
trong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" title="3.3. Checking a Package's Signature" id="s1-check-rpm-sig" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-check-rpm-sig">3.3. Checking a Package's Signature</h2></div></div></div><a id="id768472" class="indexterm"></a><div class="para">
+ If you wish to verify that a package has not been corrupted or tampered with, you can examine just the md5sum by entering this command at the shell prompt: (where <em class="replaceable"><code><rpm_file></code></em> is the file name of the RPM package):
+ </div><pre class="screen">
+<code class="command">rpm -K --nosignature <em class="replaceable"><code><rpm_file></code></em> </code>
+</pre><div class="para">
+ The output <code class="computeroutput"><em class="replaceable"><code><rpm_file></code></em>: rsa sha1 (md5) pgp md5 OK</code> (specifically the <span class="emphasis"><em>OK</em></span> part of it) indicates that the file was not corrupted during download. To see a more verbose message, replace <code class="option">-K</code> with <code class="option">-Kvv</code> in the command.
+ </div><div class="para">
+ On the other hand, how trustworthy is the developer who created the package? If the package is <em class="firstterm">signed</em> with the developer's GnuPG <em class="firstterm">key</em>, you know that the developer really is who they say they are.
+ </div><a id="id628573" class="indexterm"></a><a id="id628586" class="indexterm"></a><a id="id628600" class="indexterm"></a><div class="para">
+ An RPM package can be signed using <em class="firstterm">Gnu Privacy Guard</em> (or GnuPG), to help you make certain your downloaded package is trustworthy.
+ </div><div class="para">
+ GnuPG is a tool for secure communication; it is a complete and free replacement for the encryption technology of PGP, an electronic privacy program. With GnuPG, you can authenticate the validity of documents and encrypt/decrypt data to and from other recipients. GnuPG is capable of decrypting and verifying PGP 5.<em class="replaceable"><code>x</code></em> files as well.
+ </div><div class="para">
+ During installation, GnuPG is installed by defaut, which enables you to immediately start using it to verify any packages that you download from the Fedora Project. Before doing so, you first need to import the correct Fedora key.
+ </div><div class="section" title="3.3.1. Importing Keys" id="s2-keys-importing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-keys-importing">3.3.1. Importing Keys</h3></div></div></div><div class="para">
+ Fedora GnuPG keys are located in the <code class="filename">/etc/pki/rpm-gpg/</code> directory. To verify a Fedora Project package, first import the correct key based on your processor architecture:
+ </div><pre class="screen">
+<code class="command">rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-<em class="replaceable"><code>x86_64</code></em></code>
+</pre><div class="para">
+ To display a list of all keys installed for RPM verification, execute the command:
+ </div><pre class="screen">
+<code class="command">rpm -qa gpg-pubkey*</code>
+</pre><div class="para">
+ For the Fedora Project key, the output states:
+ </div><pre class="screen">gpg-pubkey-57bbccba-4a6f97af</pre><div class="para">
+ To display details about a specific key, use <code class="command">rpm -qi</code> followed by the output from the previous command:
+ </div><pre class="screen">
+<code class="command">rpm -qi gpg-pubkey-57bbccba-4a6f97af</code>
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-verifying.html"><strong>Prev</strong>3.2.7. Verifying</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-keys-checking.html"><strong>Next</strong>3.3.2. Verifying Signature of Packages</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp-additional-resources.html
new file mode 100644
index 0000000..22cd642
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp-additional-resources.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.6. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)" /><link rel="prev" href="s1-dhcp_for_ipv6_dhcpv6.html" title="6.5. DHCP for IPv6 (DHCPv6)" /><link rel="next" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-
dhcp_for_ipv6_dhcpv6.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Controlling_Access_to_Services.html"><strong>Next</strong></a></li></ul><div class="section" title="6.6. Additional Resources" id="s1-dhcp-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-dhcp-additional-resources">6.6. Additional Resources</h2></div></div></div><a id="id826698" class="indexterm"></a><div class="para">
+ For additional information, refer to <em class="citetitle">The DHCP Handbook; Ralph Droms and Ted Lemon; 2003</em> or the following resources.
+ </div><div class="section" title="6.6.1. Installed Documentation" id="s2-dhcp-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-dhcp-installed-docs">6.6.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">dhcpd</code> man page — Describes how the DHCP daemon works.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.conf</code> man page — Explains how to configure the DHCP configuration file; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcpd.leases</code> man page — Describes a persistent database of leases.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcp-options</code> man page — Explains the syntax for declaring DHCP options in <code class="filename">dhcpd.conf</code>; includes some examples.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dhcrelay</code> man page — Explains the DHCP Relay Agent and its configuration options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/dhcp-<<em class="replaceable"><code>version</code></em>>/</code> — Contains sample files, README files, and release notes for current versions of the DHCP service.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp_for_ipv6_dhcpv6.html"><strong>Prev</strong>6.5. DHCP for IPv6 (DHCPv6)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Controlling_Access_to_Services.html"><strong>Next</strong>Chapter 7. Controlling Access to Services</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp-configuring-client.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp-configuring-client.html
new file mode 100644
index 0000000..effd18c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp-configuring-client.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.3. Configuring a DHCP Client</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)" /><link rel="prev" href="dhcp-relay-agent.html" title="6.2.4. DHCP Relay Agent" /><link rel="next" href="sect-Configuring_a_Multihomed_DHCP_Server.html" title="6.4. Configuring a Multihomed DHCP Server" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="dhcp-re
lay-agent.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Configuring_a_Multihomed_DHCP_Server.html"><strong>Next</strong></a></li></ul><div class="section" title="6.3. Configuring a DHCP Client" id="s1-dhcp-configuring-client"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-dhcp-configuring-client">6.3. Configuring a DHCP Client</h2></div></div></div><a id="id843989" class="indexterm"></a><a id="id844003" class="indexterm"></a><div class="para">
+ To configure a DHCP client manually, modify the <code class="filename">/etc/sysconfig/network</code> file to enable networking and the configuration file for each network device in the <code class="filename">/etc/sysconfig/network-scripts</code> directory. In this directory, each device should have a configuration file named <code class="filename">ifcfg-eth0</code>, where <code class="filename">eth0</code> is the network device name.
+ </div><div class="para">
+ The <code class="filename">/etc/sysconfig/network-scripts/ifcfg-eth0</code> file should contain the following lines:
+ </div><pre class="screen">
+DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes
+</pre><div class="para">
+ A configuration file is needed for each device to be configured to use DHCP.
+ </div><div class="para">
+ Other options for the network script includes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="literal">DHCP_HOSTNAME</code> — Only use this option if the DHCP server requires the client to specify a hostname before receiving an IP address. (The DHCP server daemon in Fedora does not support this feature.)
+ </div></li><li class="listitem"><div class="para">
+ <code class="literal">PEERDNS=<em class="replaceable"><code><answer></code></em> </code>, where <code class="literal"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Modify <code class="filename">/etc/resolv.conf</code> with information from the server. If using DHCP, then <code class="command">yes</code> is the default.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Do not modify <code class="filename">/etc/resolv.conf</code>.
+ </div></li></ul></div></li></ul></div><div class="para">
+ If you prefer using a graphical interface, refer to <a class="xref" href="ch-Network_Configuration.html" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a> for instructions on using the <span class="application"><strong>Network Administration Tool</strong></span> to configure a network interface to use DHCP.
+ </div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ For advanced configurations of client DHCP options such as protocol timing, lease requirements and requests, dynamic DNS support, aliases, as well as a wide variety of values to override, prepend, or append to client-side configurations, refer to the <code class="command">dhclient</code> and <code class="command">dhclient.conf</code> man pages.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="dhcp-relay-agent.html"><strong>Prev</strong>6.2.4. DHCP Relay Agent</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Configuring_a_Multihomed_DHCP_Server.html"><strong>Next</strong>6.4. Configuring a Multihomed DHCP Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp-configuring-server.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp-configuring-server.html
new file mode 100644
index 0000000..63b3ad4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp-configuring-server.html
@@ -0,0 +1,123 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.2. Configuring a DHCP Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)" /><link rel="prev" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)" /><link rel="next" href="lease-database.html" title="6.2.2. Lease Database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" hr
ef="ch-Dynamic_Host_Configuration_Protocol_DHCP.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="lease-database.html"><strong>Next</strong></a></li></ul><div class="section" title="6.2. Configuring a DHCP Server" id="s1-dhcp-configuring-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-dhcp-configuring-server">6.2. Configuring a DHCP Server</h2></div></div></div><a id="id537586" class="indexterm"></a><div class="para">
+ The <code class="filename">dhcp</code> package contains an ISC DHCP server. First, install the package as the superuser:
+ </div><pre class="screen">~]# <code class="command">yum install dhcp</code>
+</pre><div class="para">
+ Installing the <code class="filename">dhcp</code> package creates a file, <code class="filename">/etc/dhcp/dhcpd.conf</code>, which is merely an empty configuration file:
+ </div><pre class="screen">~]# <code class="command">cat /etc/dhcp/dhcpd.conf</code>
+#
+# DHCP Server Configuration file.
+# see /usr/share/doc/dhcp*/dhcpd.conf.sample</pre><div class="para">
+ The sample configuration file can be found at <code class="filename">/usr/share/doc/dhcp-<<em class="replaceable"><code>version</code></em>>/dhcpd.conf.sample</code>. You should use this file to help you configure <code class="filename">/etc/dhcp/dhcpd.conf</code>, which is explained in detail below.
+ </div><div class="para">
+ DHCP also uses the file <code class="filename">/var/lib/dhcpd/dhcpd.leases</code> to store the client lease database. Refer to <a class="xref" href="lease-database.html" title="6.2.2. Lease Database">Section 6.2.2, “Lease Database”</a> for more information.
+ </div><div class="section" title="6.2.1. Configuration File" id="config-file"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="config-file">6.2.1. Configuration File</h3></div></div></div><a id="id492078" class="indexterm"></a><a id="id492092" class="indexterm"></a><div class="para">
+ The first step in configuring a DHCP server is to create the configuration file that stores the network information for the clients. Use this file to declare options and global options for client systems.
+ </div><div class="para">
+ The configuration file can contain extra tabs or blank lines for easier formatting. Keywords are case-insensitive and lines beginning with a hash sign (#) are considered comments.
+ </div><div class="para">
+ There are two types of statements in the configuration file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Parameters — State how to perform a task, whether to perform a task, or what network configuration options to send to the client.
+ </div></li><li class="listitem"><div class="para">
+ Declarations — Describe the topology of the network, describe the clients, provide addresses for the clients, or apply a group of parameters to a group of declarations.
+ </div></li></ul></div><a id="id849273" class="indexterm"></a><div class="para">
+ The parameters that start with the keyword option are reffered to as <em class="firstterm">options</em>. These options control DHCP options; whereas, parameters configure values that are not optional or control how the DHCP server behaves.
+ </div><a id="id692395" class="indexterm"></a><div class="para">
+ Parameters (including options) declared before a section enclosed in curly brackets ({ }) are considered global parameters. Global parameters apply to all the sections below it.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If the configuration file is changed, the changes do not take effect until the DHCP daemon is restarted with the command <code class="command">service dhcpd restart</code>.
+ </div></div></div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ Instead of changing a DHCP configuration file and restarting the service each time, using the <code class="command">omshell</code> command provides an interactive way to connect to, query, and change the configuration of a DHCP server. By using <code class="command">omshell</code>, all changes can be made while the server is running. For more information on <code class="command">omshell</code>, refer to the <code class="command">omshell</code> man page.
+ </div></div></div><div class="para">
+ In <a class="xref" href="s1-dhcp-configuring-server.html#subnet" title="Example 6.1. Subnet Declaration">Example 6.1, “Subnet Declaration”</a>, the <code class="filename">routers</code>, <code class="filename">subnet-mask</code>, <code class="filename">domain-search</code>, <code class="filename">domain-name-servers</code>, and <code class="filename">time-offset</code> options are used for any <code class="filename">host</code> statements declared below it.
+ </div><a id="id619481" class="indexterm"></a><div class="para">
+ Additionally, a <code class="filename">subnet</code> can be declared, a <code class="filename">subnet</code> declaration must be included for every subnet in the network. If it is not, the DHCP server fails to start.
+ </div><div class="para">
+ In this example, there are global options for every DHCP client in the subnet and a <code class="filename">range</code> declared. Clients are assigned an IP address within the <code class="filename">range</code>.
+ </div><div class="example" title="Example 6.1. Subnet Declaration" id="subnet"><h6>Example 6.1. Subnet Declaration</h6><div class="example-contents"><pre class="screen">
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ range 192.168.1.10 192.168.1.100;
+}
+</pre></div></div><br class="example-break" /><div class="para">
+ To configure a DHCP server that leases a dynamic IP address to a system within a subnet, modify <a class="xref" href="s1-dhcp-configuring-server.html#dynamic-ip" title="Example 6.2. Range Parameter">Example 6.2, “Range Parameter”</a> with your values. It declares a default lease time, maximum lease time, and network configuration values for the clients. This example assigns IP addresses in the <code class="filename">range</code> 192.168.1.10 and 192.168.1.100 to client systems.
+ </div><div class="example" title="Example 6.2. Range Parameter" id="dynamic-ip"><h6>Example 6.2. Range Parameter</h6><div class="example-contents"><pre class="screen">
+default-lease-time 600;
+max-lease-time 7200;
+option subnet-mask 255.255.255.0;
+option broadcast-address 192.168.1.255;
+option routers 192.168.1.254;
+option domain-name-servers 192.168.1.1, 192.168.1.2;
+option domain-search "example.com";
+subnet 192.168.1.0 netmask 255.255.255.0 {
+ range 192.168.1.10 192.168.1.100;
+}
+</pre></div></div><br class="example-break" /><div class="para">
+ To assign an IP address to a client based on the MAC address of the network interface card, use the <code class="filename">hardware ethernet</code> parameter within a <code class="filename">host</code> declaration. As demonstrated in <a class="xref" href="s1-dhcp-configuring-server.html#static-ip" title="Example 6.3. Static IP Address using DHCP">Example 6.3, “Static IP Address using DHCP”</a>, the <code class="filename">host apex</code> declaration specifies that the network interface card with the MAC address 00:A0:78:8E:9E:AA always receives the IP address 192.168.1.4.
+ </div><div class="para">
+ Note that the optional parameter <code class="filename">host-name</code> can also be used to assign a host name to the client.
+ </div><div class="example" title="Example 6.3. Static IP Address using DHCP" id="static-ip"><h6>Example 6.3. Static IP Address using DHCP</h6><div class="example-contents"><pre class="screen">
+host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+}
+</pre></div></div><br class="example-break" /><a id="id471610" class="indexterm"></a><div class="para">
+ All subnets that share the same physical network should be declared within a <code class="filename">shared-network</code> declaration as shown in <a class="xref" href="s1-dhcp-configuring-server.html#shared-network" title="Example 6.4. Shared-network Declaration">Example 6.4, “Shared-network Declaration”</a>. Parameters within the <code class="filename">shared-network</code>, but outside the enclosed <code class="filename">subnet</code> declarations, are considered to be global parameters. The name of the <code class="filename">shared-network</code> must be a descriptive title for the network, such as using the title 'test-lab' to describe all the subnets in a test lab environment.
+ </div><div class="example" title="Example 6.4. Shared-network Declaration" id="shared-network"><h6>Example 6.4. Shared-network Declaration</h6><div class="example-contents"><pre class="screen">
+shared-network name {
+ option domain-search "test.redhat.com";
+ option domain-name-servers ns1.redhat.com, ns2.redhat.com;
+ option routers 192.168.0.254;
+ more parameters for EXAMPLE shared-network
+ subnet 192.168.1.0 netmask 255.255.252.0 {
+ parameters for subnet
+ range 192.168.1.1 192.168.1.254;
+ }
+ subnet 192.168.2.0 netmask 255.255.252.0 {
+ parameters for subnet
+ range 192.168.2.1 192.168.2.254;
+ }
+}
+</pre></div></div><br class="example-break" /><a id="id678760" class="indexterm"></a><div class="para">
+ As demonstrated in <a class="xref" href="s1-dhcp-configuring-server.html#group" title="Example 6.5. Group Declaration">Example 6.5, “Group Declaration”</a>, the <code class="filename">group</code> declaration is used to apply global parameters to a group of declarations. For example, shared networks, subnets, and hosts can be grouped.
+ </div><div class="example" title="Example 6.5. Group Declaration" id="group"><h6>Example 6.5. Group Declaration</h6><div class="example-contents"><pre class="screen">
+group {
+ option routers 192.168.1.254;
+ option subnet-mask 255.255.255.0;
+ option domain-search "example.com";
+ option domain-name-servers 192.168.1.1;
+ option time-offset -18000; # Eastern Standard Time
+ host apex {
+ option host-name "apex.example.com";
+ hardware ethernet 00:A0:78:8E:9E:AA;
+ fixed-address 192.168.1.4;
+ }
+ host raleigh {
+ option host-name "raleigh.example.com";
+ hardware ethernet 00:A1:DD:74:C3:F2;
+ fixed-address 192.168.1.6;
+ }
+}
+</pre></div></div><br class="example-break" /><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ The sample configuration file provided can be used as a starting point and custom configuration options can be added to it. To copy it to the proper location, use the following command:
+ </div><pre class="screen">
+<code class="command">cp /usr/share/doc/dhcp-<em class="replaceable"><code><version-number></code></em>/dhcpd.conf.sample /etc/dhcp/dhcpd.conf</code>
+</pre><div class="para">
+ ... where <em class="replaceable"><code><version-number></code></em> is the DHCP version number.
+ </div></div></div><div class="para">
+ For a complete list of option statements and what they do, refer to the <code class="filename">dhcp-options</code> man page.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html"><strong>Prev</strong>Chapter 6. Dynamic Host Configuration Protocol (D...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="lease-database.html"><strong>Next</strong>6.2.2. Lease Database</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.html
new file mode 100644
index 0000000..b9d2813
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-dhcp_for_ipv6_dhcpv6.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.5. DHCP for IPv6 (DHCPv6)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)" /><link rel="prev" href="sect-Configuring_a_Multihomed_DHCP_Server.html" title="6.4. Configuring a Multihomed DHCP Server" /><link rel="next" href="s1-dhcp-additional-resources.html" title="6.6. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p"
href="sect-Configuring_a_Multihomed_DHCP_Server.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-dhcp-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="6.5. DHCP for IPv6 (DHCPv6)" id="s1-dhcp_for_ipv6_dhcpv6"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-dhcp_for_ipv6_dhcpv6">6.5. DHCP for IPv6 (DHCPv6)</h2></div></div></div><a id="id826626" class="indexterm"></a><a id="id826638" class="indexterm"></a><div class="para">
+ The ISC DHCP includes support for IPv6 (DHCPv6) since the 4.x release with a DHCPv6 server, client and relay agent functionality. The server, client and relay agents support both IPv4 and IPv6. However, the client and the server can only manage one protocol at a time — for dual support they must be started separately for IPv4 and IPv6.
+ </div><div class="para">
+ The DHCPv6 server configuration file can be found at <code class="filename">/etc/dhcp/dhcpd6.conf</code>.
+ </div><div class="para">
+ The sample server configuration file can be found at <code class="filename">/usr/share/doc/dhcp-<version>/dhcpd6.conf.sample</code>.
+ </div><div class="para">
+ To start the DHCPv6 service, use the command <code class="command">/sbin/service dhcpd6 start</code>.
+ </div><div class="para">
+ A simple DHCPv6 server configuration file can look like this:
+ </div><pre class="screen">
+subnet6 2001:db8:0:1::/64 {
+ range6 2001:db8:0:1::129 2001:db8:0:1::254;
+ option dhcp6.name-servers fec0:0:0:1::1;
+ option dhcp6.domain-search "domain.example";
+}
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Configuring_a_Multihomed_DHCP_Server.html"><strong>Prev</strong>6.4. Configuring a Multihomed DHCP Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-dhcp-additional-resources.html"><strong>Next</strong>6.6. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-additional-resources.html
new file mode 100644
index 0000000..e9dbc73
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-additional-resources.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.6. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 12. Email" /><link rel="prev" href="s1-email-mua.html" title="12.5. Mail User Agents" /><link rel="next" href="s2-email-useful-websites.html" title="12.6.2. Useful Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-mua.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-email-useful-websites.html
"><strong>Next</strong></a></li></ul><div class="section" title="12.6. Additional Resources" id="s1-email-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-additional-resources">12.6. Additional Resources</h2></div></div></div><a id="id507281" class="indexterm"></a><a id="id507296" class="indexterm"></a><a id="id507310" class="indexterm"></a><a id="id507325" class="indexterm"></a><div class="para">
+ The following is a list of additional documentation about email applications.
+ </div><div class="section" title="12.6.1. Installed Documentation" id="s2-email-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-installed-docs">12.6.1. Installed Documentation</h3></div></div></div><a id="id507353" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Information on configuring Sendmail is included with the <code class="filename">sendmail</code> and <code class="filename">sendmail-cf</code> packages.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/sendmail-cf/README</code> — Contains information on the <code class="command">m4</code> macro processor, file locations for Sendmail, supported mailers, how to access enhanced features, and more.
+ </div></li></ul></div><div class="para">
+ In addition, the <code class="filename">sendmail</code> and <code class="filename">aliases</code> man pages contain helpful information covering various Sendmail options and the proper configuration of the Sendmail <code class="filename">/etc/mail/aliases</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/postfix-<em class="replaceable"><code><version-number></code></em> </code> — Contains a large amount of information about ways to configure Postfix. Replace <em class="replaceable"><code><version-number></code></em> with the version number of Postfix.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/fetchmail-<em class="replaceable"><code><version-number></code></em> </code> — Contains a full list of Fetchmail features in the <code class="filename">FEATURES</code> file and an introductory <code class="filename">FAQ</code> document. Replace <em class="replaceable"><code><version-number></code></em> with the version number of Fetchmail.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/procmail-<em class="replaceable"><code><version-number></code></em> </code> — Contains a <code class="filename">README</code> file that provides an overview of Procmail, a <code class="filename">FEATURES</code> file that explores every program feature, and an <code class="filename">FAQ</code> file with answers to many common configuration questions. Replace <em class="replaceable"><code><version-number></code></em> with the version number of Procmail.
+ </div><div class="para">
+ When learning how Procmail works and creating new recipes, the following Procmail man pages are invaluable:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">procmail</code> — Provides an overview of how Procmail works and the steps involved with filtering email.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">procmailrc</code> — Explains the <code class="filename">rc</code> file format used to construct recipes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">procmailex</code> — Gives a number of useful, real-world examples of Procmail recipes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">procmailsc</code> — Explains the weighted scoring technique used by Procmail to match a particular recipe to a message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/spamassassin-<em class="replaceable"><code><version-number></code></em>/</code> — Contains a large amount of information pertaining to SpamAssassin. Replace <em class="replaceable"><code><version-number></code></em> with the version number of the <code class="filename">spamassassin</code> package.
+ </div></li></ul></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-mua.html"><strong>Prev</strong>12.5. Mail User Agents</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-email-useful-websites.html"><strong>Next</strong>12.6.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-mda.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-mda.html
new file mode 100644
index 0000000..bae247f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-mda.html
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.4. Mail Delivery Agents</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 12. Email" /><link rel="prev" href="s2-email-switchmail.html" title="12.3.4. Mail Transport Agent (MTA) Configuration" /><link rel="next" href="s2-email-procmail-recipes.html" title="12.4.2. Procmail Recipes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-switchmail.html"><strong>Prev</strong></a></li><li class="next"><a accessk
ey="n" href="s2-email-procmail-recipes.html"><strong>Next</strong></a></li></ul><div class="section" title="12.4. Mail Delivery Agents" id="s1-email-mda"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-mda">12.4. Mail Delivery Agents</h2></div></div></div><div class="para">
+ Fedora includes two primary MDAs, Procmail and <code class="command">mail</code>. Both of the applications are considered LDAs and both move email from the MTA's spool file into the user's mailbox. However, Procmail provides a robust filtering system.
+ </div><div class="para">
+ This section details only Procmail. For information on the <code class="command">mail</code> command, consult its man page (<code class="command">man mail</code>).
+ </div><a id="id558183" class="indexterm"></a><a id="id558197" class="indexterm"></a><div class="para">
+ Procmail delivers and filters email as it is placed in the mail spool file of the localhost. It is powerful, gentle on system resources, and widely used. Procmail can play a critical role in delivering email to be read by email client applications.
+ </div><div class="para">
+ Procmail can be invoked in several different ways. Whenever an MTA places an email into the mail spool file, Procmail is launched. Procmail then filters and files the email for the MUA and quits. Alternatively, the MUA can be configured to execute Procmail any time a message is received so that messages are moved into their correct mailboxes. By default, the presence of <code class="filename">/etc/procmailrc</code> or of a <code class="filename">~/.procmailrc</code> file (also called an <em class="firstterm">rc</em> file) in the user's home directory invokes Procmail whenever an MTA receives a new message.
+ </div><div class="para">
+ By default, no system-wide <code class="filename">rc</code> files exist in the <code class="filename">/etc/</code> directory and no <code class="filename">.procmailrc</code> files exist in any user's home directory. Therefore, to use Procmail, each user must construct a <code class="filename">.procmailrc</code> file with specific environment variables and rules.
+ </div><div class="para">
+ Whether Procmail acts upon an email message depends upon whether the message matches a specified set of conditions or <em class="firstterm">recipes</em> in the <code class="filename">rc</code> file. If a message matches a recipe, then the email is placed in a specified file, is deleted, or is otherwise processed.
+ </div><div class="para">
+ When Procmail starts, it reads the email message and separates the body from the header information. Next, Procmail looks for a <code class="filename">/etc/procmailrc</code> file and <code class="filename">rc</code> files in the <code class="filename">/etc/procmailrcs</code> directory for default, system-wide, Procmail environmental variables and recipes. Procmail then searches for a <code class="filename">.procmailrc</code> file in the user's home directory. Many users also create additional <code class="filename">rc</code> files for Procmail that are referred to within the <code class="filename">.procmailrc</code> file in their home directory.
+ </div><div class="section" title="12.4.1. Procmail Configuration" id="s2-email-procmail-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-procmail-configuration">12.4.1. Procmail Configuration</h3></div></div></div><a id="id447338" class="indexterm"></a><a id="id447353" class="indexterm"></a><div class="para">
+ The Procmail configuration file contains important environmental variables. These variables specify things such as which messages to sort and what to do with the messages that do not match any recipes.
+ </div><div class="para">
+ These environmental variables usually appear at the beginning of the <code class="filename">~/.procmailrc</code> file in the following format:
+ </div><pre class="screen">
+<em class="replaceable"><code><env-variable></code></em>="<em class="replaceable"><code><value></code></em>"
+</pre><div class="para">
+ In this example, <code class="command"><em class="replaceable"><code><env-variable></code></em> </code> is the name of the variable and <code class="command"><em class="replaceable"><code><value></code></em> </code> defines the variable.
+ </div><div class="para">
+ There are many environment variables not used by most Procmail users and many of the more important environment variables are already defined by a default value. Most of the time, the following variables are used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">DEFAULT</code> — Sets the default mailbox where messages that do not match any recipes are placed.
+ </div><div class="para">
+ The default <code class="command">DEFAULT</code> value is the same as <code class="command">$ORGMAIL</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">INCLUDERC</code> — Specifies additional <code class="filename">rc</code> files containing more recipes for messages to be checked against. This breaks up the Procmail recipe lists into individual files that fulfill different roles, such as blocking spam and managing email lists, that can then be turned off or on by using comment characters in the user's <code class="filename">~/.procmailrc</code> file.
+ </div><div class="para">
+ For example, lines in a user's <code class="filename">.procmailrc</code> file may look like this:
+ </div><pre class="screen">MAILDIR=$HOME/Msgs INCLUDERC=$MAILDIR/lists.rc INCLUDERC=$MAILDIR/spam.rc</pre><div class="para">
+ To turn off Procmail filtering of email lists but leaving spam control in place, comment out the first <code class="command">INCLUDERC</code> line with a hash sign (<code class="command">#</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">LOCKSLEEP</code> — Sets the amount of time, in seconds, between attempts by Procmail to use a particular lockfile. The default is <code class="constant">8</code> seconds.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">LOCKTIMEOUT</code> — Sets the amount of time, in seconds, that must pass after a lockfile was last modified before Procmail assumes that the lockfile is old and can be deleted. The default is <code class="constant">1024</code> seconds.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">LOGFILE</code> — The file to which any Procmail information or error messages are written.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">MAILDIR</code> — Sets the current working directory for Procmail. If set, all other Procmail paths are relative to this directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ORGMAIL</code> — Specifies the original mailbox, or another place to put the messages if they cannot be placed in the default or recipe-required location.
+ </div><div class="para">
+ By default, a value of <code class="command">/var/spool/mail/$LOGNAME</code> is used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SUSPEND</code> — Sets the amount of time, in seconds, that Procmail pauses if a necessary resource, such as swap space, is not available.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">SWITCHRC</code> — Allows a user to specify an external file containing additional Procmail recipes, much like the <code class="command">INCLUDERC</code> option, except that recipe checking is actually stopped on the referring configuration file and only the recipes on the <code class="command">SWITCHRC</code>-specified file are used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">VERBOSE</code> — Causes Procmail to log more information. This option is useful for debugging.
+ </div></li></ul></div><div class="para">
+ Other important environmental variables are pulled from the shell, such as <code class="command">LOGNAME</code>, which is the login name; <code class="command">HOME</code>, which is the location of the home directory; and <code class="command">SHELL</code>, which is the default shell.
+ </div><div class="para">
+ A comprehensive explanation of all environments variables, as well as their default values, is available in the <code class="filename">procmailrc</code> man page.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-switchmail.html"><strong>Prev</strong>12.3.4. Mail Transport Agent (MTA) Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-email-procmail-recipes.html"><strong>Next</strong>12.4.2. Procmail Recipes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-mta.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-mta.html
new file mode 100644
index 0000000..2fd497f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-mta.html
@@ -0,0 +1,85 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.3. Mail Transport Agents</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 12. Email" /><link rel="prev" href="s2-email-types-mua.html" title="12.2.3. Mail User Agent" /><link rel="next" href="s2-email-mta-sendmail.html" title="12.3.2. Sendmail" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-types-mua.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-email-mta-sendmail.html
"><strong>Next</strong></a></li></ul><div class="section" title="12.3. Mail Transport Agents" id="s1-email-mta"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-mta">12.3. Mail Transport Agents</h2></div></div></div><div class="para">
+ Fedora offers two primary MTAs: Postfix and Sendmail. Postfix is configured as the default MTA, although it is easy to switch the default MTA to Sendmail. To switch the default MTA to Sendmail, you can either uninstall Postfix or use the following command to switch to Sendmail:
+ </div><pre class="screen">
+<code class="command">~]# alternatives --config mta</code>
+</pre><div class="para">
+ You can also use the following command to to enable/disable the desired service:
+ </div><pre class="screen">~]# <code class="command">chkconfig <em class="replaceable"><code><service></code></em> <em class="replaceable"><code><on/off></code></em></code>
+</pre><div class="section" title="12.3.1. Postfix" id="s2-email-mta-postfix"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-mta-postfix">12.3.1. Postfix</h3></div></div></div><a id="id832515" class="indexterm"></a><a id="id832530" class="indexterm"></a><div class="para">
+ Originally developed at IBM by security expert and programmer Wietse Venema, Postfix is a Sendmail-compatible MTA that is designed to be secure, fast, and easy to configure.
+ </div><div class="para">
+ To improve security, Postfix uses a modular design, where small processes with limited privileges are launched by a <em class="firstterm">master</em> daemon. The smaller, less privileged processes perform very specific tasks related to the various stages of mail delivery and run in a change rooted environment to limit the effects of attacks.
+ </div><div class="para">
+ Configuring Postfix to accept network connections from hosts other than the local computer takes only a few minor changes in its configuration file. Yet for those with more complex needs, Postfix provides a variety of configuration options, as well as third party add ons that make it a very versatile and full-featured MTA.
+ </div><div class="para">
+ The configuration files for Postfix are human readable and support upward of 250 directives. Unlike Sendmail, no macro processing is required for changes to take effect and the majority of the most commonly used options are described in the heavily commented files.
+ </div><div class="section" title="12.3.1.1. The Default Postfix Installation" id="s3-email-mta-postfix-default"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-postfix-default">12.3.1.1. The Default Postfix Installation</h4></div></div></div><a id="id832582" class="indexterm"></a><div class="para">
+ The Postfix executable is <code class="filename">/usr/sbin/postfix</code>. This daemon launches all related processes needed to handle mail delivery.
+ </div><div class="para">
+ Postfix stores its configuration files in the <code class="filename">/etc/postfix/</code> directory. The following is a list of the more commonly used files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">access</code> — Used for access control, this file specifies which hosts are allowed to connect to Postfix.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">main.cf</code> — The global Postfix configuration file. The majority of configuration options are specified in this file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">master.cf</code> — Specifies how Postfix interacts with various processes to accomplish mail delivery.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">transport</code> — Maps email addresses to relay hosts.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">aliases</code> file can be found in the <code class="filename">/etc/</code> directory. This file is shared between Postfix and Sendmail. It is a configurable list required by the mail protocol that describes user ID aliases.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The default <code class="filename">/etc/postfix/main.cf</code> file does not allow Postfix to accept network connections from a host other than the local computer. For instructions on configuring Postfix as a server for other clients, refer to <a class="xref" href="s1-email-mta.html#s3-email-mta-postfix-conf" title="12.3.1.2. Basic Postfix Configuration">Section 12.3.1.2, “Basic Postfix Configuration”</a>.
+ </div></div></div><div class="para">
+ Restart the <code class="systemitem">postfix</code> service after changing any options in the configuration files under the <code class="filename">/etc/postfix</code> directory in order for those changes to take effect:
+<pre class="screen">~]# <code class="command">service postfix restart</code>
+</pre>
+
+ </div></div><div class="section" title="12.3.1.2. Basic Postfix Configuration" id="s3-email-mta-postfix-conf"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-postfix-conf">12.3.1.2. Basic Postfix Configuration</h4></div></div></div><div class="para">
+ By default, Postfix does not accept network connections from any host other than the local host. Perform the following steps as root to enable mail delivery for other hosts on the network:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Edit the <code class="filename">/etc/postfix/main.cf</code> file with a text editor, such as <code class="command">vi</code>.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">mydomain</code> line by removing the hash sign (<code class="command">#</code>), and replace <em class="replaceable"><code>domain.tld</code></em> with the domain the mail server is servicing, such as <code class="command">example.com</code>.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">myorigin = $mydomain</code> line.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">myhostname</code> line, and replace <em class="replaceable"><code>host.domain.tld</code></em> with the hostname for the machine.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">mydestination = $myhostname, localhost.$mydomain</code> line.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">mynetworks</code> line, and replace <em class="replaceable"><code>168.100.189.0/28</code></em> with a valid network setting for hosts that can connect to the server.
+ </div></li><li class="listitem"><div class="para">
+ Uncomment the <code class="command">inet_interfaces = all</code> line.
+ </div></li><li class="listitem"><div class="para">
+ Comment the <code class="command">inet_interfaces = localhost</code> line.
+ </div></li><li class="listitem"><div class="para">
+ Restart the <code class="command">postfix</code> service.
+ </div></li></ul></div><div class="para">
+ Once these steps are complete, the host accepts outside emails for delivery.
+ </div><div class="para">
+ Postfix has a large assortment of configuration options. One of the best ways to learn how to configure Postfix is to read the comments within the <code class="filename">/etc/postfix/main.cf</code> configuration file. Additional resources including information about Postfix configuration, SpamAssassin integration, or detailed descriptions of the <code class="filename">/etc/postfix/main.cf</code> parameters are available online at <a href="http://www.postfix.org/">http://www.postfix.org/</a>.
+ </div></div><div class="section" title="12.3.1.3. Using Postfix with LDAP" id="using-postfix-with-ldap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="using-postfix-with-ldap">12.3.1.3. Using Postfix with LDAP</h4></div></div></div><div class="para">
+ Postfix can use an <code class="systemitem">LDAP</code> directory as a source for various lookup tables (e.g.: <code class="filename">aliases</code>, <code class="filename">virtual</code>, <code class="filename">canonical</code>, etc.). This allows <code class="systemitem">LDAP</code> to store hierarchical user information and Postfix to only be given the result of <code class="systemitem">LDAP</code> queries when needed. By not storing this information locally, administrators can easily maintain it.
+ </div><div class="section" title="12.3.1.3.1. The /etc/aliases lookup example" id="aliases-example"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="aliases-example">12.3.1.3.1. <code class="filename">The /etc/aliases</code> lookup example</h5></div></div></div><div class="para">
+ The following is a basic example for using <code class="systemitem">LDAP</code> to look up the <code class="filename">/etc/aliases</code> file. Make sure your <code class="filename">/etc/postfix/main.cf</code> contains the following:
+ </div><pre class="screen">
+alias_maps = hash:/etc/aliases, ldap:/etc/postfix/ldap-aliases.cf
+</pre><div class="para">
+ Create a <code class="filename">/etc/postfix/ldap-aliases.cf</code> file if you do not have one created already and make sure it contains the following:
+ </div><pre class="screen">
+server_host = <em class="replaceable"><code>ldap.example.com</code></em>
+search_base = dc=<em class="replaceable"><code>example</code></em>, dc=<em class="replaceable"><code>com</code></em>
+</pre><div class="para">
+ where <em class="parameter"><code>ldap.example.com</code></em>, <em class="parameter"><code>example</code></em>, and <em class="parameter"><code>com</code></em> are parameters that need to be replaced with specification of an existing available <code class="systemitem">LDAP</code> server.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The /<code class="filename">etc/postfix/ldap-aliases.cf</code> file can specify various parameters, including parameters that enable <code class="systemitem">LDAP</code> <code class="systemitem">SSL</code> and <code class="systemitem">STARTTLS</code>. For more information, refer to the <code class="command">ldap_table(5)</code> man page.
+ </div></div></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-types-mua.html"><strong>Prev</strong>12.2.3. Mail User Agent</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-email-mta-sendmail.html"><strong>Next</strong>12.3.2. Sendmail</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-mua.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-mua.html
new file mode 100644
index 0000000..0e38236
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-mua.html
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.5. Mail User Agents</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 12. Email" /><link rel="prev" href="s2-email-procmail-recipes.html" title="12.4.2. Procmail Recipes" /><link rel="next" href="s1-email-additional-resources.html" title="12.6. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-procmail-recipes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n"
href="s1-email-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="12.5. Mail User Agents" id="s1-email-mua"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-mua">12.5. Mail User Agents</h2></div></div></div><div class="para">
+ Fedora offers a variety of email programs, both, graphical email client programs, such as <span class="application"><strong>Evolution</strong></span>, and text-based email programs such as <code class="command">mutt</code>.
+ </div><div class="para">
+ The remainder of this section focuses on securing communication between a client and a server.
+ </div><div class="section" title="12.5.1. Securing Communication" id="s2-email-security"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-security">12.5.1. Securing Communication</h3></div></div></div><div class="para">
+ Popular MUAs included with Fedora, such as <span class="application"><strong>Evolution</strong></span> and <code class="command">mutt</code> offer SSL-encrypted email sessions.
+ </div><a id="id467508" class="indexterm"></a><div class="para">
+ Like any other service that flows over a network unencrypted, important email information, such as usernames, passwords, and entire messages, may be intercepted and viewed by users on the network. Additionally, since the standard <code class="systemitem">POP</code> and <code class="systemitem">IMAP</code> protocols pass authentication information unencrypted, it is possible for an attacker to gain access to user accounts by collecting usernames and passwords as they are passed over the network.
+ </div><div class="section" title="12.5.1.1. Secure Email Clients" id="s3-email-security-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-security-clients">12.5.1.1. Secure Email Clients</h4></div></div></div><a id="id779120" class="indexterm"></a><div class="para">
+ Most Linux MUAs designed to check email on remote servers support SSL encryption. To use SSL when retrieving email, it must be enabled on both the email client and the server.
+ </div><div class="para">
+ SSL is easy to enable on the client-side, often done with the click of a button in the MUA's configuration window or via an option in the MUA's configuration file. Secure <code class="systemitem">IMAP</code> and <code class="systemitem">POP</code> have known port numbers (<code class="constant">993</code> and <code class="constant">995</code>, respectively) that the MUA uses to authenticate and download messages.
+ </div></div><div class="section" title="12.5.1.2. Securing Email Client Communications" id="s3-email-security-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-security-servers">12.5.1.2. Securing Email Client Communications</h4></div></div></div><a id="id779181" class="indexterm"></a><a id="id779200" class="indexterm"></a><div class="para">
+ Offering SSL encryption to <code class="systemitem">IMAP</code> and <code class="systemitem">POP</code> users on the email server is a simple matter.
+ </div><div class="para">
+ First, create an SSL certificate. This can be done in two ways: by applying to a <em class="firstterm">Certificate Authority</em> (<em class="firstterm">CA</em>) for an SSL certificate or by creating a self-signed certificate.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Self-signed certificates should be used for testing purposes only. Any server used in a production environment should use an SSL certificate granted by a CA.
+ </div></div></div><div class="para">
+ To create a self-signed SSL certificate for <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code>, change to the <code class="filename">/etc/pki/dovecot/</code> directory, edit the certificate parameters in the <code class="filename">/etc/pki/dovecot/dovecot-openssl.conf</code> configuration file as you prefer, and type the following commands, as root:
+ </div><pre class="screen">dovecot]# <code class="command">rm -f certs/dovecot.pem private/dovecot.pem</code>
+dovecot]# <code class="command">/usr/libexec/dovecot/mkcert.sh</code>
+</pre><div class="para">
+ Once finished, make sure you have the following configurations in your <code class="filename">/etc/dovecot/conf.d/10-ssl.conf</code> file:
+ </div><pre class="screen">
+ssl_cert = </etc/pki/dovecot/certs/dovecot.pem
+ssl_key = </etc/pki/dovecot/private/dovecot.pem
+</pre><div class="para">
+ Execute the <code class="command">service dovecot restart</code> command to restart the <code class="command">dovecot</code> daemon.
+ </div><div class="para">
+ Alternatively, the <code class="command">stunnel</code> command can be used as an SSL encryption wrapper around the standard, non-secure connections to <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code> services.
+ </div><div class="para">
+ The <code class="command">stunnel</code> utility uses external OpenSSL libraries included with Fedora to provide strong cryptography and to protect the network connections. It is recommended to apply to a CA to obtain an SSL certificate, but it is also possible to create a self-signed certificate.
+ </div><div class="note" title="Note: Installing the stunnel package"><div class="admonition_header"><h2>Note: Installing the <span class="package">stunnel</span> package</h2></div><div class="admonition"><div class="para">
+ In order to use <code class="command">stunnel</code>, first ensure the <span class="package">stunnel</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install stunnel</code></pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ To create a self-signed SSL certificate, change to the <code class="filename">/etc/pki/tls/certs/</code> directory, and type the following command:
+ </div><pre class="screen">certs]# <code class="command">make stunnel.pem</code>
+</pre><div class="para">
+ Answer all of the questions to complete the process.
+ </div><div class="para">
+ Once the certificate is generated, create an <code class="command">stunnel</code> configuration file, for example <code class="filename">/etc/stunnel/mail.conf</code>, with the following content:
+ </div><pre class="screen">cert = /etc/pki/tls/certs/stunnel.pem
+
+[pop3s]
+accept = 995
+connect = 110
+
+[imaps]
+accept = 993
+connect = 143
+</pre><div class="para">
+ Once you start <code class="command">stunnel</code> with the created configuration file using the <code class="command">/usr/bin/stunnel /etc/stunnel/mail.conf</code> command, it will be possible to use an <code class="systemitem">IMAP</code> or a <code class="systemitem">POP</code> email client and connect to the email server using SSL encryption.
+ </div><div class="para">
+ For more information on <code class="command">stunnel</code>, refer to the <code class="command">stunnel</code> man page or the documents in the <code class="filename">/usr/share/doc/stunnel-<em class="replaceable"><code><version-number></code></em> </code>/ directory, where <em class="replaceable"><code><version-number></code></em> is the version number of <code class="command">stunnel</code>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-procmail-recipes.html"><strong>Prev</strong>12.4.2. Procmail Recipes</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-email-additional-resources.html"><strong>Next</strong>12.6. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-types.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-types.html
new file mode 100644
index 0000000..02c3c96
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-email-types.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.2. Email Program Classifications</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-email.html" title="Chapter 12. Email" /><link rel="prev" href="ch-email.html" title="Chapter 12. Email" /><link rel="next" href="s2-email-types-mda.html" title="12.2.2. Mail Delivery Agent" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-email.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-email-types-mda.html"><strong>Next</stro
ng></a></li></ul><div class="section" title="12.2. Email Program Classifications" id="s1-email-types"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-email-types">12.2. Email Program Classifications</h2></div></div></div><a id="id838040" class="indexterm"></a><div class="para">
+ In general, all email applications fall into at least one of three classifications. Each classification plays a specific role in the process of moving and managing email messages. While most users are only aware of the specific email program they use to receive and send messages, each one is important for ensuring that email arrives at the correct destination.
+ </div><div class="section" title="12.2.1. Mail Transport Agent" id="s2-email-types-mta"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-types-mta">12.2.1. Mail Transport Agent</h3></div></div></div><a id="id838071" class="indexterm"></a><a id="id838090" class="indexterm"></a><a id="id838104" class="indexterm"></a><div class="para">
+ A <em class="firstterm">Mail Transport Agent</em> (<em class="firstterm">MTA</em>) transports email messages between hosts using <code class="systemitem">SMTP</code>. A message may involve several MTAs as it moves to its intended destination.
+ </div><div class="para">
+ While the delivery of messages between machines may seem rather straightforward, the entire process of deciding if a particular MTA can or should accept a message for delivery is quite complicated. In addition, due to problems from spam, use of a particular MTA is usually restricted by the MTA's configuration or the access configuration for the network on which the MTA resides.
+ </div><div class="para">
+ Many modern email client programs can act as an MTA when sending email. However, this action should not be confused with the role of a true MTA. The sole reason email client programs are capable of sending email like an MTA is because the host running the application does not have its own MTA. This is particularly true for email client programs on non-UNIX-based operating systems. However, these client programs only send outbound messages to an MTA they are authorized to use and do not directly deliver the message to the intended recipient's email server.
+ </div><div class="para">
+ Since Fedora offers two MTAs—<em class="firstterm">Postfix</em> and <em class="firstterm">Sendmail</em>—email client programs are often not required to act as an MTA. Fedora also includes a special purpose MTA called <em class="firstterm">Fetchmail</em>.
+ </div><div class="para">
+ For more information on Postfix, Sendmail, and Fetchmail, refer to <a class="xref" href="s1-email-mta.html" title="12.3. Mail Transport Agents">Section 12.3, “Mail Transport Agents”</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-email.html"><strong>Prev</strong>Chapter 12. Email</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-email-types-mda.html"><strong>Next</strong>12.2.2. Mail Delivery Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kdump-crash.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kdump-crash.html
new file mode 100644
index 0000000..097ad58
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kdump-crash.html
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>24.2. Analyzing the Core Dump</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-kdump.html" title="Chapter 24. The kdump Crash Recovery Service" /><link rel="prev" href="ch-kdump.html" title="Chapter 24. The kdump Crash Recovery Service" /><link rel="next" href="s2-kdump-crash-backtrace.html" title="24.2.2. Displaying a Backtrace" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-kdump.html"><strong>Prev</strong></a></li><li class="next"><a
accesskey="n" href="s2-kdump-crash-backtrace.html"><strong>Next</strong></a></li></ul><div class="section" title="24.2. Analyzing the Core Dump" id="s1-kdump-crash"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kdump-crash">24.2. Analyzing the Core Dump</h2></div></div></div><a id="id584190" class="indexterm"></a><div class="para">
+ To determine the cause of the system crash, you can use the <span class="application"><strong>crash</strong></span> utility. This utility allows you to interactively analyze a running Linux system as well as a core dump created by <code class="systemitem">netdump</code>, <code class="systemitem">diskdump</code>, <code class="systemitem">xendump</code>, or <code class="systemitem">kdump</code>. When started, it presents you with an interactive prompt very similar to the GNU Debugger (GDB).
+ </div><a id="id584237" class="indexterm"></a><div class="note" title="Note: Make Sure You Have Relevant Packages Installed"><div class="admonition_header"><h2>Note: Make Sure You Have Relevant Packages Installed</h2></div><div class="admonition"><div class="para">
+ To analyze the <code class="filename">vmcore</code> dump file, you must have the <span class="package">crash</span> and <span class="package">kernel-debuginfo</span> packages installed. To do so, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">yum install --enablerepo=rhel-debuginfo crash kernel-debuginfo</code></pre><div class="para">
+ Refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><a id="id546601" class="indexterm"></a><div class="para">
+ To start the utility, type the command in the following form at a shell prompt:
+ </div><pre class="screen"><code class="command">crash /var/crash/<em class="replaceable"><code>timestamp</code></em>/vmcore /usr/lib/debug/lib/modules/<em class="replaceable"><code>kernel</code></em>/vmlinux</code></pre><div class="para">
+ Note that the <em class="replaceable"><code>kernel</code></em> version should be the same that was captured by <code class="systemitem">kdump</code>. To find out which kernel you are currently running, use the <code class="command">uname -r</code> command.
+ </div><div class="example" title="Example 24.3. Running the crash utility" id="ex-kdump-crash-running"><h6>Example 24.3. Running the <code class="command">crash</code> utility</h6><div class="example-contents"><pre class="screen">~]# <code class="command">crash /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux \</code>
+<code class="command">/var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore</code>
+
+crash 5.0.0-23.el6
+Copyright (C) 2002-2010 Red Hat, Inc.
+Copyright (C) 2004, 2005, 2006 IBM Corporation
+Copyright (C) 1999-2006 Hewlett-Packard Co
+Copyright (C) 2005, 2006 Fujitsu Limited
+Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
+Copyright (C) 2005 NEC Corporation
+Copyright (C) 1999, 2002, 2007 Silicon Graphics, Inc.
+Copyright (C) 1999, 2000, 2001, 2002 Mission Critical Linux, Inc.
+This program is free software, covered by the GNU General Public License,
+and you are welcome to change it and/or distribute copies of it under
+certain conditions. Enter "help copying" to see the conditions.
+This program has absolutely no warranty. Enter "help warranty" for details.
+
+GNU gdb (GDB) 7.0
+Copyright (C) 2009 Free Software Foundation, Inc.
+License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+This is free software: you are free to change and redistribute it.
+There is NO WARRANTY, to the extent permitted by law. Type "show copying"
+and "show warranty" for details.
+This GDB was configured as "i686-pc-linux-gnu"...
+
+ KERNEL: /usr/lib/debug/lib/modules/2.6.32-69.el6.i686/vmlinux
+ DUMPFILE: /var/crash/127.0.0.1-2010-08-25-08:45:02/vmcore [PARTIAL DUMP]
+ CPUS: 4
+ DATE: Wed Aug 25 08:44:47 2010
+ UPTIME: 00:09:02
+LOAD AVERAGE: 0.00, 0.01, 0.00
+ TASKS: 140
+ NODENAME: hp-dl320g5-02.lab.bos.redhat.com
+ RELEASE: 2.6.32-69.el6.i686
+ VERSION: #1 SMP Tue Aug 24 10:31:45 EDT 2010
+ MACHINE: i686 (2394 Mhz)
+ MEMORY: 8 GB
+ PANIC: "Oops: 0002 [#1] SMP " (check log for details)
+ PID: 5591
+ COMMAND: "bash"
+ TASK: f196d560 [THREAD_INFO: ef4da000]
+ CPU: 2
+ STATE: TASK_RUNNING (PANIC)
+
+crash></pre></div></div><br class="example-break" /><div class="para">
+ To exit the interactive prompt and terminate <span class="application"><strong>crash</strong></span>, type <code class="command">exit</code>.
+ </div><div class="section" title="24.2.1. Displaying the Message Buffer" id="s2-kdump-crash-log"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-crash-log">24.2.1. Displaying the Message Buffer</h3></div></div></div><a id="id546713" class="indexterm"></a><div class="para">
+ To display the kernel message buffer, type the <code class="command">log</code> command at the interactive prompt.
+ </div><div class="example" title="Example 24.4. Displaying the kernel message buffer" id="ex-kdump-crash-log"><h6>Example 24.4. Displaying the kernel message buffer</h6><div class="example-contents"><pre class="screen">crash> <code class="command">log</code>
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+EIP: 0060:[<c068124f>] EFLAGS: 00010096 CPU: 2
+EIP is at sysrq_handle_crash+0xf/0x20
+EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000
+ESI: c0a09ca0 EDI: 00000286 EBP: 00000000 ESP: ef4dbf24
+ DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
+Process bash (pid: 5591, ti=ef4da000 task=f196d560 task.ti=ef4da000)
+Stack:
+ c068146b c0960891 c0968653 00000003 00000000 00000002 efade5c0 c06814d0
+<0> fffffffb c068150f b7776000 f2600c40 c0569ec4 ef4dbf9c 00000002 b7776000
+<0> efade5c0 00000002 b7776000 c0569e60 c051de50 ef4dbf9c f196d560 ef4dbfb4
+Call Trace:
+ [<c068146b>] ? __handle_sysrq+0xfb/0x160
+ [<c06814d0>] ? write_sysrq_trigger+0x0/0x50
+ [<c068150f>] ? write_sysrq_trigger+0x3f/0x50
+ [<c0569ec4>] ? proc_reg_write+0x64/0xa0
+ [<c0569e60>] ? proc_reg_write+0x0/0xa0
+ [<c051de50>] ? vfs_write+0xa0/0x190
+ [<c051e8d1>] ? sys_write+0x41/0x70
+ [<c0409adc>] ? syscall_call+0x7/0xb
+Code: a0 c0 01 0f b6 41 03 19 d2 f7 d2 83 e2 03 83 e0 cf c1 e2 04 09 d0 88 41 03 f3 c3 90 c7 05 c8 1b 9e c0 01 00 00 00 0f ae f8 89 f6 <c6> 05 00 00 00 00 01 c3 89 f6 8d bc 27 00 00 00 00 8d 50 d0 83
+EIP: [<c068124f>] sysrq_handle_crash+0xf/0x20 SS:ESP 0068:ef4dbf24
+CR2: 0000000000000000</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help log</code> for more information on the command usage.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-kdump.html"><strong>Prev</strong>Chapter 24. The kdump Crash Recovery Service</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-kdump-crash-backtrace.html"><strong>Next</strong>24.2.2. Displaying a Backtrace</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kdump-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kdump-resources.html
new file mode 100644
index 0000000..eadf85e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kdump-resources.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>24.3. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-kdump.html" title="Chapter 24. The kdump Crash Recovery Service" /><link rel="prev" href="s2-kdump-crash-files.html" title="24.2.5. Displaying Open Files" /><link rel="next" href="s2-kdump-resources-online.html" title="24.3.2. Useful Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-files.html"><strong>Prev</strong></a></li><li class="next"><
a accesskey="n" href="s2-kdump-resources-online.html"><strong>Next</strong></a></li></ul><div class="section" title="24.3. Additional Resources" id="s1-kdump-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kdump-resources">24.3. Additional Resources</h2></div></div></div><div class="section" title="24.3.1. Installed Documentation" id="s2-kdump-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-resources-installed">24.3.1. Installed Documentation</h3></div></div></div><a id="id788803" class="indexterm"></a><a id="id788823" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="command">man kdump.conf</code></span></dt><dd><div class="para">
+ The manual page for the <code class="filename">/etc/kdump.conf</code> configuration file containing the full documentation of available options.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man makedumpfile</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">makedumpfile</code> core collector containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man kexec</code></span></dt><dd><div class="para">
+ The manual page for <code class="command">kexec</code> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man crash</code></span></dt><dd><div class="para">
+ The manual page for the <span class="application"><strong>crash</strong></span> utility containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/kexec-tools-<em class="replaceable"><code>version</code></em>/kexec-kdump-howto.txt</code></span></dt><dd><div class="para">
+ An overview of the <code class="systemitem">kdump</code> and <code class="command">kexec</code> installation and usage.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-files.html"><strong>Prev</strong>24.2.5. Displaying Open Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-kdump-resources-online.html"><strong>Next</strong>24.3.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-boot-loader.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-boot-loader.html
new file mode 100644
index 0000000..3b47cf8
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-boot-loader.html
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>23.6. Verifying the Boot Loader</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 23. Manually Upgrading the Kernel" /><link rel="prev" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="23.5. Verifying the Initial RAM Disk Image" /><link rel="next" href="s2-kernel-boot-loader-iseries.html" title="23.6.2. Configuring the OS/400® Boot Loader" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" hr
ef="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-kernel-boot-loader-iseries.html"><strong>Next</strong></a></li></ul><div class="section" title="23.6. Verifying the Boot Loader" id="s1-kernel-boot-loader"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-boot-loader">23.6. Verifying the Boot Loader</h2></div></div></div><a id="id501360" class="indexterm"></a><div class="para">
+ When you install a kernel using <code class="command">rpm</code>, the kernel package creates an entry in the boot loader configuration file for that new kernel. However, <code class="command">rpm</code> does <span class="emphasis"><em>not</em></span> configure the new kernel to boot as the default kernel. You must do this manually when installing a new kernel with <code class="command">rpm</code>.
+ </div><div class="para">
+ It is always recommended to double-check the boot loader configuration file after installing a new kernel with <code class="command">rpm</code> to ensure that the configuration is correct. Otherwise, the system may not be able to boot into Fedora properly. If this happens, boot the system with the boot media created earlier and re-configure the boot loader.
+ </div><div class="para">
+ In the following table, find your system's architecture to determine the boot loader it uses, and then click on the "Refer to" link to jump to the correct instructions for your system.
+ </div><div class="table" title="Table 23.1. Boot Loaders by Architecture" id="tb-grub-arch-loaders"><h6>Table 23.1. Boot Loaders by Architecture</h6><div class="table-contents"><table summary="Boot Loaders by Architecture" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th>
+ Architecture
+ </th><th>
+ Boot Loader
+ </th><th>
+ Refer to
+ </th></tr></thead><tbody><tr><td>
+ x86
+ </td><td>
+ GRUB
+ </td><td>
+ <a class="xref" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub" title="23.6.1. Configuring the GRUB Boot Loader">Section 23.6.1, “Configuring the GRUB Boot Loader”</a>
+ </td></tr><tr><td>
+ <span class="trademark">AMD</span>® AMD64 <span class="emphasis"><em>or</em></span> <span class="trademark">Intel 64</span>®
+ </td><td>
+ GRUB
+ </td><td>
+ <a class="xref" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub" title="23.6.1. Configuring the GRUB Boot Loader">Section 23.6.1, “Configuring the GRUB Boot Loader”</a>
+ </td></tr><tr><td>
+ <span class="trademark">IBM</span>® <span class="trademark">eServer</span>™ <span class="trademark">System i</span>™
+ </td><td>
+ <span class="trademark">OS/400</span>®
+ </td><td>
+ <a class="xref" href="s2-kernel-boot-loader-iseries.html" title="23.6.2. Configuring the OS/400® Boot Loader">Section 23.6.2, “Configuring the <span class="trademark">OS/400</span>® Boot Loader”</a>
+ </td></tr><tr><td>
+ <span class="trademark">IBM</span>® <span class="trademark">eServer</span>™ <span class="trademark">System p</span>™
+ </td><td>
+ YABOOT
+ </td><td>
+ <a class="xref" href="s2-kernel-boot-loader-pseries.html" title="23.6.3. Configuring the YABOOT Boot Loader">Section 23.6.3, “Configuring the YABOOT Boot Loader”</a>
+ </td></tr><tr><td>
+ <span class="trademark">IBM</span>® <span class="trademark">System z</span>®
+ </td><td>
+ z/IPL
+ </td><td>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" title="23.6.1. Configuring the GRUB Boot Loader" id="s3-kernel-boot-loader-grub"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s3-kernel-boot-loader-grub">23.6.1. Configuring the GRUB Boot Loader</h3></div></div></div><a id="id576837" class="indexterm"></a><a id="id576849" class="indexterm"></a><div class="para">
+ GRUB's configuration file, <code class="filename">/boot/grub/grub.conf</code>, contains a few lines with directives, such as <code class="computeroutput">default</code>, <code class="computeroutput">timeout</code>, <code class="computeroutput">splashimage</code> and <code class="computeroutput">hiddenmenu</code> (the last directive has no argument). The remainder of the file contains 4-line <em class="firstterm">stanzas</em> that each refer to an installed kernel. These stanzas always start with a <code class="computeroutput">title</code> entry, after which the associated <code class="computeroutput">root</code>, <code class="computeroutput">kernel</code> and <code class="computeroutput">initrd</code> directives should always be indented. Ensure that each stanza starts with a <code class="computeroutput">title</code> that contains a version number (in parentheses) that matches the version number in the <code class="computeroutput">kernel /vmlinuz-<em class="replaceable">
<code><version_number></code></em> </code> line of the same stanza.
+ </div><div class="example" title="Example 23.2. /boot/grub/grub.conf" id="ex-_boot_grub_grub.conf"><h6>Example 23.2. /boot/grub/grub.conf</h6><div class="example-contents"><pre class="screen"># grub.conf generated by anaconda
+<em class="lineannotation"><span class="lineannotation">[comments omitted]</span></em>
+default=1
+timeout=0
+splashimage=(hd0,0)/grub/splash.xpm.gz
+hiddenmenu
+
+title Fedora (2.6.32.11-99.fc12.x86_64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32.11-99.fc12.x86_64 ro root=UUID=39e5f931-5dd5-4a90-a0cf-52996767d592 noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=dvorak rhgb quiet
+ initrd /initramfs-2.6.32.11-99.fc12.x86_64.img
+
+title Fedora (2.6.32.10-90.fc12.x86_64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32.10-90.fc12.x86_64 ro root=UUID=39e5f931-5dd5-4a90-a0cf-52996767d592 noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=dvorak rhgb quiet
+ initrd /initramfs-2.6.32.10-90.fc12.x86_64.img
+
+title Fedora (2.6.32.9-70.fc12.x86_64)
+ root (hd0,0)
+ kernel /vmlinuz-2.6.32.9-70.fc12.x86_64 ro root=UUID=39e5f931-5dd5-4a90-a0cf-52996767d592 noiswmd LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=dvorak rhgb quiet
+ initrd /initramfs-2.6.32.9-70.fc12.x86_64.img</pre></div></div><br class="example-break" /><div class="para">
+ If a separate <code class="filename">/boot/</code> partition was created, the paths to the kernel and the <code class="systemitem">initramfs</code> image are relative to <code class="filename">/boot/</code>. This is the case in <a class="xref" href="s1-kernel-boot-loader.html#ex-_boot_grub_grub.conf" title="Example 23.2. /boot/grub/grub.conf">Example 23.2, “/boot/grub/grub.conf”</a>, above. Therefore the <code class="computeroutput">initrd <code class="filename">/initramfs-2.6.32.11-99.fc12.x86_64.img</code> </code> line in the first kernel stanza means that the <code class="systemitem">initramfs</code> image is actually located at <code class="filename">/boot/initramfs-2.6.32.11-99.fc12.x86_64.img</code> when the root file system is mounted, and likewise for the kernel path (for example: <code class="computeroutput">kernel <code class="filename">/vmlinuz-2.6.32.11-99.fc12.x86_64</code> </code>) in each stanza of <code class="filename">grub.conf</code>.
+ </div><div class="note" title="The initrd directive in grub.conf refers to an initramfs image" id="note-The_initrd_directive_in_grub.conf_refers_to_an_initramfs_image"><div class="admonition_header"><h2>The initrd directive in grub.conf refers to an initramfs image</h2></div><div class="admonition"><div class="para">
+ In kernel boot stanzas in <code class="filename">grub.conf</code>, the <code class="computeroutput">initrd</code> directive must point to the location (relative to the <code class="filename">/boot/</code> directory if it is on a separate partition), of the <span class="emphasis"><em><code class="filename">initramfs</code> </em></span> file corresponding to the same kernel version. This directive is called <code class="computeroutput">initrd</code> because the previous tool which created initial RAM disk images, <code class="command">mkinitrd</code>, created what were known as <code class="systemitem">initrd</code> files. Thus the <code class="filename">grub.conf</code> directive remains <code class="systemitem">initrd</code> to maintain compatibility with other tools. The file-naming convention of systems using the <code class="command">dracut</code> utility to create the initial RAM disk image is: <code class="filename">initramfs-<em class="replaceable"><code><kerne
l_version></code></em>.img</code>
+ </div><div class="para">
+ <span class="application"><strong>Dracut</strong></span> is a new utility available in Fedora 14, and much-improved over <code class="command">mkinitrd</code>. For information on using <span class="application"><strong>Dracut</strong></span>, refer to <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="23.5. Verifying the Initial RAM Disk Image">Section 23.5, “Verifying the Initial RAM Disk Image”</a>.
+ </div></div></div><div class="para">
+ You should ensure that the kernel version number as given on the <code class="computeroutput">kernel <code class="filename">/vmlinuz-<em class="replaceable"><code><kernel_version></code></em> </code> </code> line matches the version number of the <code class="systemitem">initramfs</code> image given on the <code class="computeroutput">initrd <code class="filename">/initramfs-<em class="replaceable"><code><kernel_version></code></em>.img</code> </code> line of each stanza. Refer to <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html#procedure-Verifying_the_Initial_RAM_Disk_Image" title="Procedure 23.1. Verifying the Initial RAM Disk Image">Procedure 23.1, “Verifying the Initial RAM Disk Image”</a> for more information.
+ </div><div class="para">
+ The <code class="computeroutput">default=</code> directive tells GRUB which kernel to boot <span class="emphasis"><em>by default</em></span>. Each <code class="computeroutput">title</code> in <code class="filename">grub.conf</code> represents a bootable kernel. GRUB counts the <code class="computeroutput">title</code>d stanzas representing bootable kernels starting with <code class="constant">0</code>. In <a class="xref" href="s1-kernel-boot-loader.html#ex-_boot_grub_grub.conf" title="Example 23.2. /boot/grub/grub.conf">Example 23.2, “/boot/grub/grub.conf”</a>, the line <code class="computeroutput">default=1</code> indicates that GRUB will boot, by default, the <span class="emphasis"><em>second</em></span> kernel entry, i.e. <code class="computeroutput">title Fedora (2.6.32.10-90.fc12.x86_64)</code>.
+ </div><div class="para">
+ In <a class="xref" href="s1-kernel-boot-loader.html#ex-_boot_grub_grub.conf" title="Example 23.2. /boot/grub/grub.conf">Example 23.2, “/boot/grub/grub.conf”</a> GRUB is therefore configured to boot an older kernel, when we compare by version numbers. In order to boot the newer kernel, which is the <span class="emphasis"><em>first</em></span> <code class="computeroutput">title</code> entry in <code class="filename">grub.conf</code>, we would need to change the <code class="computeroutput">default</code> value to <code class="constant">0</code>.
+ </div><div class="para">
+ After installing a new kernel with <code class="command">rpm</code>, verify that <code class="filename">/boot/grub/grub.conf</code> is correct, change the <code class="computeroutput">default=</code> value to the new kernel (while remembering to count from <code class="constant">0</code>), and reboot the computer into the new kernel. Ensure your hardware is detected by watching the boot process output.
+ </div><div class="para">
+ If GRUB presents an error and is unable to boot into the default kernel, it is often easiest to try to boot into an alternative or older kernel so that you can fix the problem.
+ </div><div class="important" title="Important: Causing the GRUB boot menu to display"><div class="admonition_header"><h2>Important: Causing the GRUB boot menu to display</h2></div><div class="admonition"><div class="para">
+ If you set the <code class="computeroutput">timeout</code> directive in <code class="filename">grub.conf</code> to <code class="constant">0</code>, GRUB will not display its list of bootable kernels when the system starts up. In order to display this list when booting, press and hold any alphanumeric key while and immediately after BIOS information is displayed, and GRUB will present you with the GRUB menu.
+ </div></div></div><div class="para">
+ Alternatively, use the boot media you created earlier to boot the system.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>Prev</strong>23.5. Verifying the Initial RAM Disk Image</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-kernel-boot-loader-iseries.html"><strong>Next</strong>23.6.2. Configuring the OS/400® Boot Loader</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-download.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-download.html
new file mode 100644
index 0000000..6bef633
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-download.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>23.3. Downloading the Upgraded Kernel</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 23. Manually Upgrading the Kernel" /><link rel="prev" href="s1-kernel-preparing.html" title="23.2. Preparing to Upgrade" /><link rel="next" href="s1-kernel-perform-upgrade.html" title="23.4. Performing the Upgrade" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-preparing.html"><strong>Prev</strong></a></
li><li class="next"><a accesskey="n" href="s1-kernel-perform-upgrade.html"><strong>Next</strong></a></li></ul><div class="section" title="23.3. Downloading the Upgraded Kernel" id="s1-kernel-download"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-download">23.3. Downloading the Upgraded Kernel</h2></div></div></div><a id="id462502" class="indexterm"></a><a id="id462516" class="indexterm"></a><a id="id462528" class="indexterm"></a><a id="id462543" class="indexterm"></a><div class="para">
+ There are several ways to determine if an updated kernel is available for the system.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Security Errata — Refer to <a href="http://www.redhat.com/security/updates/">http://www.redhat.com/security/updates/</a> for information on security errata, including kernel upgrades that fix security issues.
+ </div></li><li class="listitem"><div class="para">
+ Via Red Hat Network — Download and install the kernel RPM packages. Red Hat Network can download the latest kernel, upgrade the kernel on the system, create an initial RAM disk image if needed, and configure the boot loader to boot the new kernel. For more information, refer to <a href="http://www.redhat.com/docs/manuals/RHNetwork/"> http://www.redhat.com/docs/manuals/RHNetwork/</a>.
+ </div></li></ul></div><div class="para">
+ If Red Hat Network was used to download and install the updated kernel, follow the instructions in <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="23.5. Verifying the Initial RAM Disk Image">Section 23.5, “Verifying the Initial RAM Disk Image”</a> and <a class="xref" href="s1-kernel-boot-loader.html" title="23.6. Verifying the Boot Loader">Section 23.6, “Verifying the Boot Loader”</a>, only <span class="emphasis"><em>do not</em></span> change the kernel to boot by default. Red Hat Network automatically changes the default kernel to the latest version. To install the kernel manually, continue to <a class="xref" href="s1-kernel-perform-upgrade.html" title="23.4. Performing the Upgrade">Section 23.4, “Performing the Upgrade”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-preparing.html"><strong>Prev</strong>23.2. Preparing to Upgrade</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kernel-perform-upgrade.html"><strong>Next</strong>23.4. Performing the Upgrade</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-modules-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-modules-additional-resources.html
new file mode 100644
index 0000000..4762b67
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-modules-additional-resources.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.8. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Using_Channel_Bonding.html" title="22.7.2. Using Channel Bonding" /><link rel="next" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 23. Manually Upgrading the Kernel" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Channel_Bonding.h
tml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Manually_Upgrading_the_Kernel.html"><strong>Next</strong></a></li></ul><div class="section" title="22.8. Additional Resources" id="s1-kernel-modules-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-modules-additional-resources">22.8. Additional Resources</h2></div></div></div><div class="para">
+ For more information on kernel modules and their utilities, refer to the following resources.
+ </div><h3>Manual Page Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man lsmod</code> — The <code class="command">lsmod</code> manual page contains usage information and explanation of all options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man modinfo</code> — The <code class="command">modinfo</code> manual page contains usage information and explanation of all options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man modprobe</code> — The <code class="command">modprobe</code> manual page contains usage information and explanation of all options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man rmmod</code> — The <code class="command">rmmod</code> manual page contains usage information and explanation of all options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man ethtool</code> — The <code class="command">ethtool</code> manual page contains usage information and explanation of all options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man mii-tool</code> — The <code class="command">mii-tool</code> manual page contains usage information and explanation of all options.
+ </div></li></ul></div><h3>Installable and External Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/</code> — This directory, which is provided by the <span class="package">kernel-doc</span> package, contains information on the kernel, kernel modules, and their respective parameters. Before accessing the kernel documentation, you must run the following command as root:
+ </div><pre class="screen">~]# <code class="command">yum install kernel-doc</code>
+</pre></li><li class="listitem"><div class="para">
+ <a href="http://tldp.org/HOWTO/Module-HOWTO/">Linux Loadable Kernel Module HOWTO</a> — The <em class="citetitle">Linux Loadable Kernel Module HOWTO</em> from the Linux Documentation Project contains further information on working with kernel modules.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Channel_Bonding.html"><strong>Prev</strong>22.7.2. Using Channel Bonding</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Manually_Upgrading_the_Kernel.html"><strong>Next</strong>Chapter 23. Manually Upgrading the Kernel</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-perform-upgrade.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-perform-upgrade.html
new file mode 100644
index 0000000..6d3261d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-perform-upgrade.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>23.4. Performing the Upgrade</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 23. Manually Upgrading the Kernel" /><link rel="prev" href="s1-kernel-download.html" title="23.3. Downloading the Upgraded Kernel" /><link rel="next" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="23.5. Verifying the Initial RAM Disk Image" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-down
load.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>Next</strong></a></li></ul><div class="section" title="23.4. Performing the Upgrade" id="s1-kernel-perform-upgrade"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-perform-upgrade">23.4. Performing the Upgrade</h2></div></div></div><a id="id470934" class="indexterm"></a><div class="para">
+ After retrieving all of the necessary packages, it is time to upgrade the existing kernel.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is strongly recommended that you keep the old kernel in case there are problems with the new kernel.
+ </div></div></div><div class="para">
+ At a shell prompt, change to the directory that contains the kernel RPM packages. Use <code class="option">-i</code> argument with the <code class="command">rpm</code> command to keep the old kernel. Do <span class="emphasis"><em>not</em></span> use the <code class="option">-U</code> option, since it overwrites the currently installed kernel, which creates boot loader problems. For example:
+ </div><pre class="screen">~]# <code class="command">rpm -ivh kernel-<em class="replaceable"><code><kernel_version></code></em>.<em class="replaceable"><code><arch></code></em>.rpm </code>
+</pre><div class="para">
+ The next step is to verify that the initial RAM disk image has been created. Refer to <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="23.5. Verifying the Initial RAM Disk Image">Section 23.5, “Verifying the Initial RAM Disk Image”</a> for details.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-download.html"><strong>Prev</strong>23.3. Downloading the Upgraded Kernel</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>Next</strong>23.5. Verifying the Initial RAM Disk Image</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-preparing.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-preparing.html
new file mode 100644
index 0000000..0c371b4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-kernel-preparing.html
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>23.2. Preparing to Upgrade</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 23. Manually Upgrading the Kernel" /><link rel="prev" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 23. Manually Upgrading the Kernel" /><link rel="next" href="s1-kernel-download.html" title="23.3. Downloading the Upgraded Kernel" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Manually_Upgrading_
the_Kernel.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kernel-download.html"><strong>Next</strong></a></li></ul><div class="section" title="23.2. Preparing to Upgrade" id="s1-kernel-preparing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-kernel-preparing">23.2. Preparing to Upgrade</h2></div></div></div><a id="id507469" class="indexterm"></a><a id="id507478" class="indexterm"></a><a id="id507494" class="indexterm"></a><a id="id507506" class="indexterm"></a><div class="para">
+ Before upgrading the kernel, it is recommended that you take some precautionary steps.
+ </div><div class="para">
+ First, ensure that working boot media exists for the system in case a problem occurs. If the boot loader is not configured properly to boot the new kernel, the system cannot be booted into Fedora without working boot media.
+ </div><div class="para">
+ USB media often comes in the form of flash devices sometimes called <em class="firstterm">pen drives</em>, <em class="firstterm">thumb disks</em>, or <em class="firstterm">keys</em>, or as an externally-connected hard disk device. Almost all media of this type is formatted as a <code class="systemitem">VFAT</code> file system. You can create bootable USB media on media formatted as <code class="systemitem">ext2</code>, <code class="systemitem">ext3</code>, or <code class="systemitem">VFAT</code>.
+ </div><div class="para">
+ You can transfer a distribution image file or a minimal boot media image file to USB media. Make sure that sufficient free space is available on the device. Around <code class="constant">4 GB</code> is required for a distribution DVD image, around <code class="constant">700 MB</code> for a distribution CD image, or around <code class="constant">10 MB</code> for a minimal boot media image.
+ </div><div class="para">
+ You must have a copy of the <code class="filename">boot.iso</code> file from a Fedora installation DVD, or installation CD-ROM#1, and you need a USB storage device formatted with the <code class="systemitem">VFAT</code> file system and around <code class="constant">16 MB</code> of free space. The following procedure will not affect existing files on the USB storage device unless they have the same path names as the files that you copy onto it. To create USB boot media, perform the following commands as the root user:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Install the <span class="application"><strong>SYSLINUX</strong></span> bootloader on the USB storage device:
+ </div><pre class="screen">~]# <code class="command">syslinux /dev/<em class="replaceable"><code>sdX1</code></em> </code>
+</pre><div class="para">
+ ...where <em class="replaceable"><code>sdX</code></em> is the device name.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Create mount points for <code class="filename">boot.iso</code> and the USB storage device:
+ </div><pre class="screen">~]# <code class="command">mkdir /mnt/isoboot /mnt/diskboot</code>
+</pre></li><li class="step" title="Step 3"><div class="para">
+ Mount <code class="filename">boot.iso</code>:
+ </div><pre class="screen">~]# <code class="command">mount -o loop boot.iso /mnt/isoboot</code>
+</pre></li><li class="step" title="Step 4"><div class="para">
+ Mount the USB storage device:
+ </div><pre class="screen">~]# <code class="command">mount /dev/<em class="replaceable"><code><sdX1></code></em> /mnt/diskboot</code>
+</pre></li><li class="step" title="Step 5"><div class="para">
+ Copy the <span class="application"><strong>ISOLINUX</strong></span> files from the <code class="filename">boot.iso</code> to the USB storage device:
+ </div><pre class="screen">~]# <code class="command">cp /mnt/isoboot/isolinux/* /mnt/diskboot</code>
+</pre></li><li class="step" title="Step 6"><div class="para">
+ Use the <code class="filename">isolinux.cfg</code> file from <code class="filename">boot.iso</code> as the <code class="filename">syslinux.cfg</code> file for the USB device:
+ </div><pre class="screen">~]# <code class="command">grep -v local /mnt/isoboot/isolinux/isolinux.cfg > /mnt/diskboot/syslinux.cfg</code>
+</pre></li><li class="step" title="Step 7"><div class="para">
+ Unmount <code class="filename">boot.iso</code> and the USB storage device:
+ </div><pre class="screen">~]# <code class="command">umount /mnt/isoboot /mnt/diskboot</code>
+</pre></li><li class="step" title="Step 8"><div class="para">
+ You should reboot the machine with the boot media and verify that you are able to boot with it before continuing.
+ </div></li></ol></div><div class="para">
+ Alternatively, on systems with a floppy drive, you can create a boot diskette by installing the <span class="package">mkbootdisk</span> package and running the <code class="command">mkbootdisk</code> command as root. Refer to <code class="command">man mkbootdisk</code> man page after installing the package for usage information.
+ </div><div class="para">
+ To determine which kernel packages are installed, execute the command <code class="command">yum list installed "kernel-*"</code> at a shell prompt. The output will comprise some or all of the following packages, depending on the system's architecture, and the version numbers may differ:
+ </div><pre class="screen">~]# <code class="command">yum list installed "kernel-*"</code>
+kernel.x86_64 2.6.32-17.el6 installed
+kernel-doc.noarch 2.6.32-17.el6 installed
+kernel-firmware.noarch 2.6.32-17.el6 installed
+kernel-headers.x86_64 2.6.32-17.el6 installed
+</pre><div class="para">
+ From the output, determine which packages need to be download for the kernel upgrade. For a single processor system, the only required package is the <span class="package">kernel</span> package. Refer to <a class="xref" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages" title="23.1. Overview of Kernel Packages">Section 23.1, “Overview of Kernel Packages”</a> for descriptions of the different packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Manually_Upgrading_the_Kernel.html"><strong>Prev</strong>Chapter 23. Manually Upgrading the Kernel</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kernel-download.html"><strong>Next</strong>23.3. Downloading the Upgraded Kernel</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-keyboard-break.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-keyboard-break.html
new file mode 100644
index 0000000..e5717c5
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-keyboard-break.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.3. Setting Up a Typing Break</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Keyboard_Configuration.html" title="Chapter 14. Keyboard Configuration" /><link rel="prev" href="s1-keyboard-indicator.html" title="14.2. Adding the Keyboard Layout Indicator" /><link rel="next" href="Users_and_Groups.html" title="Chapter 15. Users and Groups" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-keyboard-indicator.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="Users_and_Groups.html"><strong>Next</strong></a></li></ul><div class="section" title="14.3. Setting Up a Typing Break" id="s1-keyboard-break"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-keyboard-break">14.3. Setting Up a Typing Break</h2></div></div></div><a id="id419756" class="indexterm"></a><div class="para">
+ Typing for a long period of time can be not only tiresome, but it can also increase the risk of serious health problems, such as the carpal tunnel syndrome. One way of preventing this is to configure the system to enforce the typing break. Simply select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Keyboard</strong></span> from the panel, click the <span class="guilabel"><strong>Typing Break</strong></span> tab, and select the <span class="guilabel"><strong>Lock screen to enforce typing break</strong></span> check box.
+ </div><div class="figure" title="Figure 14.8. Typing Break Properties" id="fig-keyboard-break"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-break.png" alt="Typing Break Properties" /><div class="longdesc"><div class="para">
+ Typing Break Properties
+ </div></div></div></div><h6>Figure 14.8. Typing Break Properties</h6></div><br class="figure-break" /><div class="para">
+ To increase or decrease the amount of time you want to be allowed to type before the break is enforced, click the up or down button next to the <span class="guilabel"><strong>Work interval lasts</strong></span> label respectively. You can do the same with the <span class="guilabel"><strong>Break interval lasts</strong></span> setting to alter the length of the break itself. Finally, select the <span class="guilabel"><strong>Allow postponing of breaks</strong></span> check box if you want to be able to delay the break in case you need to finish the work. The changes take effect immediately.
+ </div><div class="figure" title="Figure 14.9. Taking a break" id="fig-keyboard-break-take"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-break-take.png" alt="Taking a break" /><div class="longdesc"><div class="para">
+ Taking a break
+ </div></div></div></div><h6>Figure 14.9. Taking a break</h6></div><br class="figure-break" /><div class="para">
+ Next time you reach the time limit, you will be presented with a screen advising you to take a break, and a clock displaying the remaining time. If you enabled it, the <span class="guibutton"><strong>Postpone Break</strong></span> button will be located at the bottom right corner of the screen.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-keyboard-indicator.html"><strong>Prev</strong>14.2. Adding the Keyboard Layout Indicator</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="Users_and_Groups.html"><strong>Next</strong>Chapter 15. Users and Groups</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-keyboard-indicator.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-keyboard-indicator.html
new file mode 100644
index 0000000..a7e250e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-keyboard-indicator.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>14.2. Adding the Keyboard Layout Indicator</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Keyboard_Configuration.html" title="Chapter 14. Keyboard Configuration" /><link rel="prev" href="ch-Keyboard_Configuration.html" title="Chapter 14. Keyboard Configuration" /><link rel="next" href="s1-keyboard-break.html" title="14.3. Setting Up a Typing Break" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Keyboard_Configuration.html"><strong>Prev</strong></a>
</li><li class="next"><a accesskey="n" href="s1-keyboard-break.html"><strong>Next</strong></a></li></ul><div class="section" title="14.2. Adding the Keyboard Layout Indicator" id="s1-keyboard-indicator"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-keyboard-indicator">14.2. Adding the Keyboard Layout Indicator</h2></div></div></div><a id="id549964" class="indexterm"></a><a id="id549977" class="indexterm"></a><div class="para">
+ If you want to see what keyboard layout you are currently using, or you would like to switch between different layouts with a single mouse click, add the <span class="application"><strong>Keyboard Indicator</strong></span> applet to the panel. To do so, right-click the empty space on the main panel, and select the <span class="guimenuitem"><strong>Add to Panel...</strong></span> option from the pulldown menu.
+ </div><div class="figure" title="Figure 14.5. Adding a new applet" id="fig-keyboard-indicator-addition"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-applet-addition.png" alt="Adding a new applet" /><div class="longdesc"><div class="para">
+ Adding a New Applet
+ </div></div></div></div><h6>Figure 14.5. Adding a new applet</h6></div><br class="figure-break" /><div class="para">
+ You will be presented with a list of available applets. Scroll through the list (or start typing <span class="quote">“<span class="quote">keyboard</span>”</span> to the search field at the top of the window), select <span class="guimenuitem"><strong>Keyboard Indicator</strong></span>, and click the <span class="guibutton"><strong>Add</strong></span> button.
+ </div><div class="figure" title="Figure 14.6. Selecting the Keyboard Indicator" id="fig-keyboard-indicator-selection"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-applet-selection.png" alt="Selecting the Keyboard Indicator" /><div class="longdesc"><div class="para">
+ Selecting the <span class="application"><strong>Keyboard Indicator</strong></span>
+ </div></div></div></div><h6>Figure 14.6. Selecting the <span class="application">Keyboard Indicator</span></h6></div><br class="figure-break" /><div class="para">
+ The applet appears immediately, displaying the shortened name of the country the current layout is associated with. To display the actual variant, hover the pointer over the applet icon.
+ </div><div class="figure" title="Figure 14.7. The Keyboard Indicator applet" id="fig-keyboard-indicator-observation"><div class="figure-contents"><div class="mediaobject"><img src="images/keyboard-configuration-applet-observation.png" alt="The Keyboard Indicator applet" /><div class="longdesc"><div class="para">
+ The <span class="application"><strong>Keyboard Indicator</strong></span> applet
+ </div></div></div></div><h6>Figure 14.7. The <span class="application">Keyboard Indicator</span> applet</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Keyboard_Configuration.html"><strong>Prev</strong>Chapter 14. Keyboard Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-keyboard-break.html"><strong>Next</strong>14.3. Setting Up a Typing Break</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-log-files-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-log-files-additional-resources.html
new file mode 100644
index 0000000..354d758
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-log-files-additional-resources.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.7. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Log_Files.html" title="Chapter 17. Log Files" /><link rel="prev" href="s1-logfiles-examining.html" title="17.6. Monitoring Log Files" /><link rel="next" href="s2-log-files-useful-websites.html" title="17.7.2. Useful Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-examining.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" h
ref="s2-log-files-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" title="17.7. Additional Resources" id="s1-log-files-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-log-files-additional-resources">17.7. Additional Resources</h2></div></div></div><div class="para">
+ To learn more about <span class="application"><strong>rsyslog</strong></span>, <span class="application"><strong>logrotate</strong></span>, and log files in general, refer to the following resources.
+ </div><div class="section" title="17.7.1. Installed Documentation" id="s2-log-files-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-log-files-installed-docs">17.7.1. Installed Documentation</h3></div></div></div><a id="id804135" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">rsyslogd</code> manual page — Type <code class="command">man rsyslogd</code> to learn more about <code class="command">rsyslogd</code> and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">rsyslog.conf</code> manual page — Type <code class="command">man rsyslog.conf</code> to learn more about the <code class="command">/etc/rsyslog.conf</code> configuration file and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/rsyslog-<em class="replaceable"><code><version-number></code></em> </code> — After installing the <span class="package">rsyslog</span> package, this directory contains extensive documentation in the <code class="systemitem">html</code> format.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">logrotate</code> manual page — Type <code class="command">man logrotate</code> to learn more about <code class="command">logrotate</code> and its many options.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-examining.html"><strong>Prev</strong>17.6. Monitoring Log Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-log-files-useful-websites.html"><strong>Next</strong>17.7.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-adding.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-adding.html
new file mode 100644
index 0000000..85fc34e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-adding.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.5. Adding a Log File</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Log_Files.html" title="Chapter 17. Log Files" /><link rel="prev" href="s1-logfiles-viewing.html" title="17.4. Viewing Log Files" /><link rel="next" href="s1-logfiles-examining.html" title="17.6. Monitoring Log Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-viewing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-log
files-examining.html"><strong>Next</strong></a></li></ul><div class="section" title="17.5. Adding a Log File" id="s1-logfiles-adding"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-adding">17.5. Adding a Log File</h2></div></div></div><div class="para">
+ To add a log file you wish to view in the list, select <span class="guimenu"><strong>File</strong></span> → <span class="guimenuitem"><strong>Open</strong></span>. This will display the <span class="guilabel"><strong>Open Log</strong></span> window where you can select the directory and filename of the log file you wish to view.<a class="xref" href="s1-logfiles-adding.html#fig-redhat-logviewer-add" title="Figure 17.5. Log File Viewer - Adding a Log File">Figure 17.5, “Log File Viewer - Adding a Log File”</a> illustrates the <span class="guimenu"><strong>Open Log</strong></span> window.
+ </div><div class="figure" title="Figure 17.5. Log File Viewer - Adding a Log File" id="fig-redhat-logviewer-add"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-logviewer-add.png" align="middle" alt="Log File Viewer - Adding a Log File" /><div class="longdesc"><div class="para">
+ Log File Viewer - Adding a Log File
+ </div></div></div></div><h6>Figure 17.5. Log File Viewer - Adding a Log File</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Open</strong></span> button to open the file. The file is immediately added to the viewing list where you can select it and view its contents.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ The <span class="application"><strong>Log File Viewer</strong></span> also allows you to open log files zipped in the <code class="literal">.gz</code> format.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-viewing.html"><strong>Prev</strong>17.4. Viewing Log Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-logfiles-examining.html"><strong>Next</strong>17.6. Monitoring Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-examining.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-examining.html
new file mode 100644
index 0000000..5d7fb7c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-examining.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.6. Monitoring Log Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Log_Files.html" title="Chapter 17. Log Files" /><link rel="prev" href="s1-logfiles-adding.html" title="17.5. Adding a Log File" /><link rel="next" href="s1-log-files-additional-resources.html" title="17.7. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-adding.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hr
ef="s1-log-files-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="17.6. Monitoring Log Files" id="s1-logfiles-examining"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-examining">17.6. Monitoring Log Files</h2></div></div></div><a id="id584659" class="indexterm"></a><a id="id584674" class="indexterm"></a><div class="para">
+ <span class="application"><strong>Log File Viewer</strong></span> monitors all opened logs by default. If a new line is added to a monitored log file, the log name appears in bold in the log list. If the log file is selected or displayed, the new lines appear in bold at the bottom of the log file. <a class="xref" href="s1-logfiles-examining.html#fig-redhat-logviewer-monitoring" title="Figure 17.6. Log File Viewer - New Log Alert">Figure 17.6, “Log File Viewer - New Log Alert”</a> illustrates a new alert in the <span class="guilabel"><strong>cron</strong></span> log file and in the <span class="guilabel"><strong>messages</strong></span> log file. Clicking on the <span class="guimenuitem"><strong>cron</strong></span> log file displays the logs in the file with the new lines in bold.
+ </div><div class="figure" title="Figure 17.6. Log File Viewer - New Log Alert" id="fig-redhat-logviewer-monitoring"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-logviewer-monitoring.png" align="middle" alt="Log File Viewer - New Log Alert" /><div class="longdesc"><div class="para">
+ Log File Viewer - New Log Alert
+ </div></div></div></div><h6>Figure 17.6. Log File Viewer - New Log Alert</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-adding.html"><strong>Prev</strong>17.5. Adding a Log File</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-log-files-additional-resources.html"><strong>Next</strong>17.7. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-locating.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-locating.html
new file mode 100644
index 0000000..478e77b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-locating.html
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3. Locating Log Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Log_Files.html" title="Chapter 17. Log Files" /><link rel="prev" href="s1-rsyslog-performance.html" title="17.2. rsyslog Performance" /><link rel="next" href="s1-logfiles-viewing.html" title="17.4. Viewing Log Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rsyslog-performance.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-
logfiles-viewing.html"><strong>Next</strong></a></li></ul><div class="section" title="17.3. Locating Log Files" id="s1-logfiles-locating"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-locating">17.3. Locating Log Files</h2></div></div></div><a id="id762484" class="indexterm"></a><div class="para">
+ Most log files are located in the <code class="filename">/var/log/</code> directory. Some applications such as <code class="command">httpd</code> and <code class="command">samba</code> have a directory within <code class="filename">/var/log/</code> for their log files.
+ </div><a id="id762516" class="indexterm"></a><a id="id620881" class="indexterm"></a><div class="para">
+ You may notice multiple files in the <code class="filename">/var/log/</code> directory with numbers after them (e.g.: <code class="filename">cron-20100906</code>). These numbers represent a timestamp that has been added to a rotated log file. Log files are rotated so their file sizes do not become too large. The <code class="filename">logrotate</code> package contains a cron task that automatically rotates log files according to the <code class="filename">/etc/logrotate.conf</code> configuration file and the configuration files in the <code class="filename">/etc/logrotate.d/</code> directory.
+ </div><div class="section" title="17.3.1. Configuring logrotate" id="configuring-logrotate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="configuring-logrotate">17.3.1. Configuring <span class="package">logrotate</span> </h3></div></div></div><div class="para">
+ The following is a sample <code class="filename">/etc/logrotate.conf</code> configuration file:
+ </div><pre class="screen">
+# rotate log files weekly
+weekly
+# keep 4 weeks worth of backlogs
+rotate 4
+# uncomment this if you want your log files compressed
+compress
+</pre><div class="para">
+ All of the lines in the sample configuration file define global options that apply to every log file. In our example, log files are rotated weekly, rotated log files are kept for the duration of 4 weeks, and all rotated log files are compressed by <span class="application"><strong>gzip</strong></span> into the <code class="literal">.gz</code> format. Any lines that begin with a hash sign (#) are comments and are not processed
+ </div><div class="para">
+ You may define configuration options for a specific log file and place it under the global options. However, it is advisable to create a separate configuration file for any specific log file in the <code class="filename">/etc/logrotate.d/</code> directory and define any configuration options there.
+ </div><div class="para">
+ The following is an example of a configuration file placed in the <code class="filename">/etc/logrotate.d/</code> directory:
+ </div><pre class="screen">
+/var/log/messages {
+ rotate 5
+ weekly
+ postrotate
+ /usr/bin/killall -HUP syslogd
+ endscript
+}
+</pre><div class="para">
+ The configuration options in this file are specific for the <code class="filename">/var/log/messages</code> log file only. The settings specified here override the global settings where possible. Thus the rotated <code class="filename">/var/log/messages</code> log file will be kept for five weeks instead of four weeks as was defined in the global options.
+ </div><div class="para">
+ The following is a list of some of the directives you can specify in your <span class="application"><strong>logrotate</strong></span> configuration file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>weekly</code></em> — Specifies the rotation of log files on a weekly basis. Similar directives include:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>daily</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>monthly</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>yearly</code></em>
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>compress</code></em> — Enables compression of rotated log files. Similar directives include:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>nocompress</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>compresscmd</code></em> — Specifies the command to be used for compressing.
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>uncompresscmd</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>compressext</code></em> — Specifies what extension is to be used for compressing.
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>compressoptions</code></em> — Lets you specify any options that may be passed to the used compression program.
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>delaycompress</code></em> — Postpones the compression of log files to the next rotation of log files.
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>rotate <em class="replaceable"><code><INTEGER></code></em> </code></em> — Specifies the number of rotations a log file undergoes before it is removed or mailed to a specific address. If the value <code class="constant">0</code> is specified, old log files are removed instead of rotated.
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>mail <em class="replaceable"><code><ADDRESS></code></em> </code></em> — This option enables mailing of log files that have been rotated as many times as is defined by the <em class="parameter"><code>rotate</code></em> directive to the specified address. Similar directives include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>nomail</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>mailfirst</code></em> — Specifies that the just-rotated log files are to be mailed, instead of the about-to-expire log files.
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>maillast</code></em> — Specifies that the just-rotated log files are to be mailed, instead of the about-to-expire log files. This is the default option when <em class="parameter"><code>mail</code></em> is enabled.
+ </div></li></ul></div></li></ul></div><div class="para">
+ For the full list of directives and various configuration options, refer to the <code class="command">logrotate</code> man page (<code class="command">man logrotate</code>).
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rsyslog-performance.html"><strong>Prev</strong>17.2. rsyslog Performance</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-logfiles-viewing.html"><strong>Next</strong>17.4. Viewing Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-viewing.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-viewing.html
new file mode 100644
index 0000000..4e37de1
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-logfiles-viewing.html
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.4. Viewing Log Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Log_Files.html" title="Chapter 17. Log Files" /><link rel="prev" href="s1-logfiles-locating.html" title="17.3. Locating Log Files" /><link rel="next" href="s1-logfiles-adding.html" title="17.5. Adding a Log File" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-locating.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-logfil
es-adding.html"><strong>Next</strong></a></li></ul><div class="section" title="17.4. Viewing Log Files" id="s1-logfiles-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-logfiles-viewing">17.4. Viewing Log Files</h2></div></div></div><a id="id623899" class="indexterm"></a><div class="para">
+ Most log files are in plain text format. You can view them with any text editor such as <code class="command">Vi</code> or <span class="application"><strong>Emacs</strong></span>. Some log files are readable by all users on the system; however, root privileges are required to read most log files.
+ </div><a id="id623926" class="indexterm"></a><div class="para">
+ To view system log files in an interactive, real-time application, use the <span class="application"><strong>Log File Viewer</strong></span>.
+ </div><div class="note" title="Note: Installing the gnome-system-log package"><div class="admonition_header"><h2>Note: Installing the <span class="package">gnome-system-log</span> package</h2></div><div class="admonition"><div class="para">
+ In order to use the <span class="application"><strong>Log File Viewer</strong></span>, first ensure the <span class="package">gnome-system-log</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install gnome-system-log</code>
+</pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ After you have installed the <span class="package">gnome-system-log</span> package, you can open the <span class="application"><strong>Log File Viewer</strong></span> by clicking on <span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System</strong></span> → <span class="guimenuitem"><strong>Log File Viewer</strong></span>, or type the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">gnome-system-log</code>
+</pre><div class="para">
+ The application only displays log files that exist; thus, the list might differ from the one shown in <a class="xref" href="s1-logfiles-viewing.html#fig-redhat-logviewer" title="Figure 17.1. Log File Viewer">Figure 17.1, “ <span class="application">Log File Viewer</span> ”</a>.
+ </div><a id="id665028" class="indexterm"></a><a id="id665046" class="indexterm"></a><div class="figure" title="Figure 17.1. Log File Viewer" id="fig-redhat-logviewer"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-logviewer.png" align="middle" alt="Log File Viewer" /><div class="longdesc"><div class="para">
+ Log File Viewer
+ </div></div></div></div><h6>Figure 17.1. <span class="application">Log File Viewer</span> </h6></div><br class="figure-break" /><a id="id665101" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Log File Viewer</strong></span> application lets you filter any existing log file. Click on <span class="guimenuitem"><strong>Filters</strong></span> from the menu and select <span class="guimenuitem"><strong>Manage Filters</strong></span> to define or edit your desired filter.
+ </div><div class="figure" title="Figure 17.2. Log File Viewer - Filters" id="fig-redhat-filters"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-filters.png" align="middle" alt="Log File Viewer - Filters" /><div class="longdesc"><div class="para">
+ Log File Viewer - Filters
+ </div></div></div></div><h6>Figure 17.2. <span class="application">Log File Viewer - Filters</span> </h6></div><br class="figure-break" /><div class="para">
+ Adding or editing a filter lets you define its parameters as is shown in <a class="xref" href="s1-logfiles-viewing.html#fig-redhat-filter-sample" title="Figure 17.3. Log File Viewer - Defining a Filter">Figure 17.3, “ <span class="application">Log File Viewer - Defining a Filter</span> ”</a>.
+ </div><div class="figure" title="Figure 17.3. Log File Viewer - Defining a Filter" id="fig-redhat-filter-sample"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-filter-sample.png" align="middle" alt="Log File Viewer - Defining a Filter" /><div class="longdesc"><div class="para">
+ Log File Viewer - Defining a Filter
+ </div></div></div></div><h6>Figure 17.3. <span class="application">Log File Viewer - Defining a Filter</span> </h6></div><br class="figure-break" /><div class="para">
+ When defining a filter, you can edit the following parameters:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Name</strong></span> — Specifies the name of the filter.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Regular Expression</strong></span> — Specifies the regular expression that will be applied to the log file and will attempt to match any possible strings of text in it.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Effect</strong></span>
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Highlight</strong></span> — If checked, the found results will be highlighted with the selected color. You may select whether to highlight the background or the foreground of the text.
+ </div></li><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>Hide</strong></span> — If checked, the found results will be hidden from the log file you are viewing.
+ </div></li></ul></div></li></ul></div><div class="para">
+ When you have at least one filter defined, you may select it from the <span class="guilabel"><strong>Filters</strong></span> menu and it will automatically search for the strings you have defined in the filter and highlight/hide every successful match in the log file you are currently viewing.
+ </div><div class="figure" title="Figure 17.4. Log File Viewer - Enabling a Filter" id="fig-redhat-filter-enable"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/redhat-filter-enable.png" align="middle" alt="Log File Viewer - Enabling a Filter" /><div class="longdesc"><div class="para">
+ Log File Viewer - Enabling a Filter
+ </div></div></div></div><h6>Figure 17.4. <span class="application">Log File Viewer - Enabling a Filter</span> </h6></div><br class="figure-break" /><div class="para">
+ When you check the <span class="guilabel"><strong>Show matches only</strong></span> option, only the matched strings will be shown in the log file you are currently viewing.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-logfiles-locating.html"><strong>Prev</strong>17.3. Locating Log Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-logfiles-adding.html"><strong>Next</strong>17.5. Adding a Log File</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-control.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-control.html
new file mode 100644
index 0000000..8a6a13a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-control.html
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.3. Interface Control Scripts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Network_Interfaces.html" title="Chapter 4. Network Interfaces" /><link rel="prev" href="s2-networkscripts-interfaces-other.html" title="4.2.5. Other Interfaces" /><link rel="next" href="s1-networkscripts-static-routes.html" title="4.4. Configuring Static Routes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-other.html"><strong>Prev</s
trong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-static-routes.html"><strong>Next</strong></a></li></ul><div class="section" title="4.3. Interface Control Scripts" id="s1-networkscripts-control"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-control">4.3. Interface Control Scripts</h2></div></div></div><a id="id732371" class="indexterm"></a><a id="id732393" class="indexterm"></a><a id="id732415" class="indexterm"></a><a id="id732436" class="indexterm"></a><a id="id732450" class="indexterm"></a><div class="para">
+ The interface control scripts activate and deactivate system interfaces. There are two primary interface control scripts that call on control scripts located in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory: <code class="command">/sbin/ifdown</code> and <code class="command">/sbin/ifup</code>.
+ </div><div class="para">
+ The <code class="filename">ifup</code> and <code class="filename">ifdown</code> interface scripts are symbolic links to scripts in the <code class="filename">/sbin/</code> directory. When either of these scripts are called, they require the value of the interface to be specified, such as:
+ </div><pre class="screen">
+<code class="command">ifup eth0</code>
+</pre><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ The <code class="filename">ifup</code> and <code class="filename">ifdown</code> interface scripts are the only scripts that the user should use to bring up and take down network interfaces.
+ </div><div class="para">
+ The following scripts are described for reference purposes only.
+ </div></div></div><div class="para">
+ Two files used to perform a variety of network initialization tasks during the process of bringing up a network interface are <code class="filename">/etc/rc.d/init.d/functions</code> and <code class="filename">/etc/sysconfig/network-scripts/network-functions</code>. Refer to <a class="xref" href="s1-networkscripts-functions.html" title="4.5. Network Function Files">Section 4.5, “Network Function Files”</a> for more information.
+ </div><div class="para">
+ After verifying that an interface has been specified and that the user executing the request is allowed to control the interface, the correct script brings the interface up or down. The following are common interface control scripts found within the <code class="filename">/etc/sysconfig/network-scripts/</code> directory:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">ifup-aliases</code> </span></dt><dd><div class="para">
+ Configures IP aliases from interface configuration files when more than one IP address is associated with an interface.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-ippp</code> and <code class="filename">ifdown-ippp</code> </span></dt><dd><div class="para">
+ Brings ISDN interfaces up and down.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-ipv6</code> and <code class="filename">ifdown-ipv6</code> </span></dt><dd><div class="para">
+ Brings IPv6 interfaces up and down.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-plip</code> </span></dt><dd><div class="para">
+ Brings up a PLIP interface.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-plusb</code> </span></dt><dd><div class="para">
+ Brings up a USB interface for network connections.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-post</code> and <code class="filename">ifdown-post</code> </span></dt><dd><div class="para">
+ Contains commands to be executed after an interface is brought up or down.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-ppp</code> and <code class="filename">ifdown-ppp</code> </span></dt><dd><div class="para">
+ Brings a PPP interface up or down.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-routes</code> </span></dt><dd><div class="para">
+ Adds static routes for a device as its interface is brought up.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifdown-sit</code> and <code class="filename">ifup-sit</code> </span></dt><dd><div class="para">
+ Contains function calls related to bringing up and down an IPv6 tunnel within an IPv4 connection.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifup-wireless</code> </span></dt><dd><div class="para">
+ Brings up a wireless interface.
+ </div></dd></dl></div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Removing or modifying any scripts in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory can cause interface connections to act irregularly or fail. Only advanced users should modify scripts related to a network interface.
+ </div></div></div><div class="para">
+ The easiest way to manipulate all network scripts simultaneously is to use the <code class="command">/sbin/service</code> command on the network service (<code class="filename">/etc/rc.d/init.d/network</code>), as illustrated the following command:
+ </div><pre class="screen">
+<code class="command">/sbin/service network <em class="replaceable"><code><action></code></em> </code>
+</pre><div class="para">
+ Here, <em class="replaceable"><code><action></code></em> can be either <code class="command">start</code>, <code class="command">stop</code>, or <code class="command">restart</code>.
+ </div><div class="para">
+ To view a list of configured devices and currently active network interfaces, use the following command:
+ </div><pre class="screen">
+<code class="command">/sbin/service network status</code>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-other.html"><strong>Prev</strong>4.2.5. Other Interfaces</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-static-routes.html"><strong>Next</strong>4.4. Configuring Static Routes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-functions.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-functions.html
new file mode 100644
index 0000000..7525cfe
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-functions.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.5. Network Function Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Network_Interfaces.html" title="Chapter 4. Network Interfaces" /><link rel="prev" href="s1-networkscripts-static-routes.html" title="4.4. Configuring Static Routes" /><link rel="next" href="s1-networkscripts-resources.html" title="4.6. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-static-routes.html"><strong>Prev</strong></
a></li><li class="next"><a accesskey="n" href="s1-networkscripts-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="4.5. Network Function Files" id="s1-networkscripts-functions"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-functions">4.5. Network Function Files</h2></div></div></div><a id="id668139" class="indexterm"></a><div class="para">
+ Fedora makes use of several files that contain important common functions used to bring interfaces up and down. Rather than forcing each interface control file to contain these functions, they are grouped together in a few files that are called upon when necessary.
+ </div><div class="para">
+ The <code class="filename">/etc/sysconfig/network-scripts/network-functions</code> file contains the most commonly used IPv4 functions, which are useful to many interface control scripts. These functions include contacting running programs that have requested information about changes in the status of an interface, setting hostnames, finding a gateway device, verifying whether or not a particular device is down, and adding a default route.
+ </div><div class="para">
+ As the functions required for IPv6 interfaces are different from IPv4 interfaces, a <code class="filename">/etc/sysconfig/network-scripts/network-functions-ipv6</code> file exists specifically to hold this information. The functions in this file configure and delete static IPv6 routes, create and remove tunnels, add and remove IPv6 addresses to an interface, and test for the existence of an IPv6 address on an interface.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-static-routes.html"><strong>Prev</strong>4.4. Configuring Static Routes</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-resources.html"><strong>Next</strong>4.6. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-interfaces.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-interfaces.html
new file mode 100644
index 0000000..85c2879
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-interfaces.html
@@ -0,0 +1,107 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Interface Configuration Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Network_Interfaces.html" title="Chapter 4. Network Interfaces" /><link rel="prev" href="ch-Network_Interfaces.html" title="Chapter 4. Network Interfaces" /><link rel="next" href="s2-networkscripts-interfaces-chan.html" title="4.2.2. Channel Bonding Interfaces" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Network_Interfaces.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-chan.html"><strong>Next</strong></a></li></ul><div class="section" title="4.2. Interface Configuration Files" id="s1-networkscripts-interfaces"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-interfaces">4.2. Interface Configuration Files</h2></div></div></div><a id="id499636" class="indexterm"></a><a id="id499649" class="indexterm"></a><div class="para">
+ Interface configuration files control the software interfaces for individual network devices. As the system boots, it uses these files to determine what interfaces to bring up and how to configure them. These files are usually named <code class="filename">ifcfg-<em class="replaceable"><code><name></code></em> </code>, where <em class="replaceable"><code><name></code></em> refers to the name of the device that the configuration file controls.
+ </div><div class="section" title="4.2.1. Ethernet Interfaces" id="s2-networkscripts-interfaces-eth0"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-interfaces-eth0">4.2.1. Ethernet Interfaces</h3></div></div></div><a id="id499688" class="indexterm"></a><a id="id729392" class="indexterm"></a><div class="para">
+ One of the most common interface files is <code class="filename">ifcfg-eth0</code>, which controls the first Ethernet <em class="firstterm">network interface card</em> or <em class="firstterm">NIC</em> in the system. In a system with multiple NICs, there are multiple <code class="filename">ifcfg-eth<em class="replaceable"><code><X></code></em> </code> files (where <em class="replaceable"><code><X></code></em> is a unique number corresponding to a specific interface). Because each device has its own configuration file, an administrator can control how each interface functions individually.
+ </div><div class="para">
+ The following is a sample <code class="filename">ifcfg-eth0</code> file for a system using a fixed IP address:
+ </div><pre class="screen">DEVICE=eth0
+BOOTPROTO=none
+ONBOOT=yes
+NETMASK=255.255.255.0
+IPADDR=10.0.1.27
+USERCTL=no</pre><div class="para">
+ The values required in an interface configuration file can change based on other values. For example, the <code class="filename">ifcfg-eth0</code> file for an interface using DHCP looks different because IP information is provided by the DHCP server:
+ </div><pre class="screen">DEVICE=eth0
+BOOTPROTO=dhcp
+ONBOOT=yes</pre><div class="para">
+ The <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>) is an easy way to make changes to the various network interface configuration files (refer to <a class="xref" href="ch-Network_Configuration.html" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a> for detailed instructions on using this tool).
+ </div><div class="para">
+ However, it is also possible to manually edit the configuration files for a given network interface.
+ </div><div class="para">
+ Below is a listing of the configurable parameters in an Ethernet interface configuration file:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="command">BONDING_OPTS=<em class="replaceable"><code><parameters></code></em> </code> </span></dt><dd><div class="para">
+ sets the configuration parameters for the bonding device, and is used in <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond<em class="replaceable"><code><N></code></em> </code> (see <a class="xref" href="s2-networkscripts-interfaces-chan.html" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a>). These parameters are identical to those used for bonding devices in <code class="filename">/sys/class/net/<em class="replaceable"><code><bonding device></code></em>/bonding</code>, and the module parameters for the bonding driver as described in <span class="emphasis"><em><code class="filename">bonding</code> Module Directives</em></span>.
+ </div><div class="para">
+ This configuration method is used so that multiple bonding devices can have different configurations. It is highly recommened to place all of your bonding options after the <code class="command">BONDING_OPTS</code> directive in <code class="filename">ifcfg-<em class="replaceable"><code><name></code></em></code>. Do <span class="emphasis"><em>not</em></span> specify options for the bonding device in <code class="filename">/etc/modprobe.d/<em class="replaceable"><code><bonding></code></em>.conf</code>, or in the deprecated <code class="filename">/etc/modprobe.conf</code> file.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">BOOTPROTO=<em class="replaceable"><code><protocol></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><protocol></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">none</code> — No boot-time protocol should be used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">bootp</code> — The BOOTP protocol should be used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">dhcp</code> — The DHCP protocol should be used.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">BROADCAST=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is the broadcast address. This directive is deprecated, as the value is calculated automatically with <code class="command">ifcalc</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">DEVICE=<em class="replaceable"><code><name></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><name></code></em> </code> is the name of the physical device (except for dynamically-allocated PPP devices where it is the <span class="emphasis"><em>logical name</em></span>).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">DHCP_HOSTNAME</code> </span></dt><dd><div class="para">
+ Use this option only if the DHCP server requires the client to specify a hostname before receiving an IP address.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">DNS<em class="replaceable"><code>{1,2}</code></em>=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is a name server address to be placed in <code class="filename">/etc/resolv.conf</code> if the <code class="command">PEERDNS</code> directive is set to <code class="command">yes</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">ETHTOOL_OPTS=<em class="replaceable"><code><options></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><options></code></em> </code> are any device-specific options supported by <code class="command">ethtool</code>. For example, if you wanted to force 100Mb, full duplex:
+ </div><pre class="screen">
+<code class="command">ETHTOOL_OPTS="autoneg off speed 100 duplex full"</code>
+</pre><div class="para">
+ Instead of a custom initscript, use <code class="command">ETHTOOL_OPTS</code> to set the interface speed and duplex settings. Custom initscripts run outside of the network init script lead to unpredictable results during a post-boot network service restart.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Changing speed or duplex settings almost always requires disabling autonegotiation with the <code class="command">autoneg off</code> option. This needs to be stated first, as the option entries are order-dependent.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="command">GATEWAY=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code><address></code></em> is the IP address of the network router or gateway device (if any).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">HWADDR=<em class="replaceable"><code><MAC-address></code></em> </code> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code><MAC-address></code></em> is the hardware address of the Ethernet device in the form <em class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em>. This directive must be used in machines containing more than one NIC to ensure that the interfaces are assigned the correct device names regardless of the configured load order for each NIC's module. This directive should <span class="bold bold"><strong>not</strong></span> be used in conjunction with <code class="command">MACADDR</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">IPADDR=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is the IP address.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">MACADDR=<em class="replaceable"><code><MAC-address></code></em> </code> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code><MAC-address></code></em> is the hardware address of the Ethernet device in the form <em class="replaceable"><code>AA:BB:CC:DD:EE:FF</code></em>. This directive is used to assign a MAC address to an interface, overriding the one assigned to the physical NIC. This directive should <span class="bold bold"><strong>not</strong></span> be used in conjunction with <code class="command">HWADDR</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">MASTER=<em class="replaceable"><code><bond-interface></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><bond-interface></code></em> </code> is the channel bonding interface to which the Ethernet interface is linked.
+ </div><div class="para">
+ This directive is used in conjunction with the <code class="command">SLAVE</code> directive.
+ </div><div class="para">
+ Refer to <a class="xref" href="s2-networkscripts-interfaces-chan.html" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a> for more information about channel bonding interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">NETMASK=<em class="replaceable"><code><mask></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><mask></code></em> </code> is the netmask value.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">NETWORK=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is the network address. This directive is deprecated, as the value is calculated automatically with <code class="command">ifcalc</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">ONBOOT=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — This device should be activated at boot-time.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — This device should not be activated at boot-time.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">PEERDNS=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Modify <code class="filename">/etc/resolv.conf</code> if the DNS directive is set. If using DHCP, then <code class="command">yes</code> is the default.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Do not modify <code class="filename">/etc/resolv.conf</code>.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">SLAVE=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — This device is controlled by the channel bonding interface specified in the <code class="command">MASTER</code> directive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — This device is <span class="emphasis"><em>not</em></span> controlled by the channel bonding interface specified in the <code class="command">MASTER</code> directive.
+ </div></li></ul></div><div class="para">
+ This directive is used in conjunction with the <code class="command">MASTER</code> directive.
+ </div><div class="para">
+ Refer to <a class="xref" href="s2-networkscripts-interfaces-chan.html" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a> for more about channel bonding interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">SRCADDR=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is the specified source IP address for outgoing packets.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">USERCTL=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Non-root users are allowed to control this device.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Non-root users are not allowed to control this device.
+ </div></li></ul></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Network_Interfaces.html"><strong>Prev</strong>Chapter 4. Network Interfaces</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-chan.html"><strong>Next</strong>4.2.2. Channel Bonding Interfaces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-resources.html
new file mode 100644
index 0000000..c2adc0a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-resources.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.6. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Network_Interfaces.html" title="Chapter 4. Network Interfaces" /><link rel="prev" href="s1-networkscripts-functions.html" title="4.5. Network Function Files" /><link rel="next" href="ch-Network_Configuration.html" title="Chapter 5. Network Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-functions.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="ch-Network_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="4.6. Additional Resources" id="s1-networkscripts-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-resources">4.6. Additional Resources</h2></div></div></div><a id="id668195" class="indexterm"></a><div class="para">
+ The following are resources which explain more about network interfaces.
+ </div><div class="section" title="4.6.1. Installed Documentation" id="s2-networkscripts-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-docs-inst">4.6.1. Installed Documentation</h3></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code><version></code></em>/sysconfig.txt</code> </span></dt><dd><div class="para">
+ A guide to available options for network configuration files, including IPv6 options not covered in this chapter.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/usr/share/doc/iproute-<em class="replaceable"><code><version></code></em>/ip-cref.ps</code> </span></dt><dd><div class="para">
+ This file contains a wealth of information about the <code class="command">ip</code> command, which can be used to manipulate routing tables, among other things. Use the <span class="application"><strong>ggv</strong></span> or <span class="application"><strong>kghostview</strong></span> application to view this file.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-functions.html"><strong>Prev</strong>4.5. Network Function Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Network_Configuration.html"><strong>Next</strong>Chapter 5. Network Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-static-routes.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-static-routes.html
new file mode 100644
index 0000000..b299048
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-networkscripts-static-routes.html
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4. Configuring Static Routes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Network_Interfaces.html" title="Chapter 4. Network Interfaces" /><link rel="prev" href="s1-networkscripts-control.html" title="4.3. Interface Control Scripts" /><link rel="next" href="s1-networkscripts-functions.html" title="4.5. Network Function Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-control.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s1-networkscripts-functions.html"><strong>Next</strong></a></li></ul><div class="section" title="4.4. Configuring Static Routes" id="s1-networkscripts-static-routes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-networkscripts-static-routes">4.4. Configuring Static Routes</h2></div></div></div><div class="para">
+ Routing will be configured on routing devices, therefore it should not be necessary to configure static routes on Fedora servers or clients. However, if static routes are required they can be configured for each interface. This can be useful if you have multiple interfaces in different subnets. Use the <code class="command">route</code> command to display the IP routing table.
+ </div><div class="para">
+ Static route configuration is stored in a <code class="filename">/etc/sysconfig/network-scripts/route-<em class="replaceable"><code>interface</code></em> </code> file. For example, static routes for the eth0 interface would be stored in the <code class="filename">/etc/sysconfig/network-scripts/route-eth0</code> file. The <code class="filename">route-<em class="replaceable"><code>interface</code></em> </code> file has two formats: IP command arguments and network/netmask directives.
+ </div><div class="formalpara"><h5 class="formalpara" id="id746856">IP Command Arguments Format</h5>
+ Define a default gateway on the first line. This is only required if the default gateway is not set via DHCP:
+ </div><pre class="screen">
+default <em class="replaceable"><code>X.X.X.X</code></em> dev <em class="replaceable"><code>interface</code></em>
+</pre><div class="para">
+ <em class="replaceable"><code>X.X.X.X</code></em> is the IP address of the default gateway. The <em class="replaceable"><code>interface</code></em> is the interface that is connected to, or can reach, the default gateway.
+ </div><div class="para">
+ Define a static route. Each line is parsed as an individual route:
+ </div><pre class="screen">
+<em class="replaceable"><code>X.X.X.X/X</code></em> via <em class="replaceable"><code>X.X.X.X</code></em> dev <em class="replaceable"><code>interface</code></em>
+</pre><div class="para">
+ <em class="replaceable"><code>X.X.X.X/X</code></em> is the network number and netmask for the static route. <em class="replaceable"><code>X.X.X.X</code></em> and <em class="replaceable"><code>interface</code></em> are the IP address and interface for the default gateway respectively. The <em class="replaceable"><code>X.X.X.X</code></em> address does not have to be the default gateway IP address. In most cases, <em class="replaceable"><code>X.X.X.X</code></em> will be an IP address in a different subnet, and <em class="replaceable"><code>interface</code></em> will be the interface that is connected to, or can reach, that subnet. Add as many static routes as required.
+ </div><div class="para">
+ The following is a sample <code class="filename">route-eth0</code> file using the IP command arguments format. The default gateway is 192.168.0.1, interface eth0. The two static routes are for the 10.10.10.0/24 and 172.16.1.0/24 networks:
+ </div><pre class="screen">
+default 192.168.0.1 dev eth0
+10.10.10.0/24 via 192.168.0.1 dev eth0
+172.16.1.0/24 via 192.168.0.1 dev eth0
+</pre><div class="para">
+ Static routes should only be configured for other subnets. The above example is not necessary, since packets going to the 10.10.10.0/24 and 172.16.1.0/24 networks will use the default gateway anyway. Below is an example of setting static routes to a different subnet, on a machine in a 192.168.0.0/24 subnet. The example machine has an eth0 interface in the 192.168.0.0/24 subnet, and an eth1 interface (10.10.10.1) in the 10.10.10.0/24 subnet:
+ </div><pre class="screen">
+10.10.10.0/24 via 10.10.10.1 dev eth1
+</pre><div class="warning" title="Duplicate Default Gateways"><div class="admonition_header"><h2>Duplicate Default Gateways</h2></div><div class="admonition"><div class="para">
+ If the default gateway is already assigned from DHCP, the IP command arguments format can cause one of two errors during start-up, or when bringing up an interface from the down state using the <code class="command">ifup</code> command: "RTNETLINK answers: File exists" or 'Error: either "to" is a duplicate, or "<em class="replaceable"><code>X.X.X.X</code></em>" is a garbage.', where <em class="replaceable"><code>X.X.X.X</code></em> is the gateway, or a different IP address. These errors can also occur if you have another route to another network using the default gateway. Both of these errors are safe to ignore.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="id703361">Network/Netmask Directives Format</h5>
+ You can also use the network/netmask directives format for <code class="filename">route-<em class="replaceable"><code>interface</code></em> </code> files. The following is a template for the network/netmask format, with instructions following afterwards:
+ </div><pre class="screen">
+ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em>
+NETMASK0=<em class="replaceable"><code>X.X.X.X</code></em>
+GATEWAY0=<em class="replaceable"><code>X.X.X.X</code></em>
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em> </code> is the network number for the static route.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">NETMASK0=<em class="replaceable"><code>X.X.X.X</code></em> </code> is the netmask for the network number defined with <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em> </code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">GATEWAY0=<em class="replaceable"><code>X.X.X.X</code></em> </code> is the default gateway, or an IP address that can be used to reach <code class="computeroutput">ADDRESS0=<em class="replaceable"><code>X.X.X.X</code></em> </code>
+ </div></li></ul></div><div class="para">
+ The following is a sample <code class="filename">route-eth0</code> file using the network/netmask directives format. The default gateway is 192.168.0.1, interface eth0. The two static routes are for the 10.10.10.0/24 and 172.16.1.0/24 networks. However, as mentioned before, this example is not necessary as the 10.10.10.0/24 and 172.16.1.0/24 networks would use the default gateway anyway:
+ </div><pre class="screen">
+ADDRESS0=10.10.10.0
+NETMASK0=255.255.255.0
+GATEWAY0=192.168.0.1
+ADDRESS1=172.16.1.0
+NETMASK1=255.255.255.0
+GATEWAY1=192.168.0.1
+</pre><div class="para">
+ Subsequent static routes must be numbered sequentially, and must not skip any values. For example, <code class="computeroutput">ADDRESS0</code>, <code class="computeroutput">ADDRESS1</code>, <code class="computeroutput">ADDRESS2</code>, and so on.
+ </div><div class="para">
+ Below is an example of setting static routes to a different subnet, on a machine in the 192.168.0.0/24 subnet. The example machine has an eth0 interface in the 192.168.0.0/24 subnet, and an eth1 interface (10.10.10.1) in the 10.10.10.0/24 subnet:
+ </div><pre class="screen">
+ADDRESS0=10.10.10.0
+NETMASK0=255.255.255.0
+GATEWAY0=10.10.10.1
+</pre><div class="para">
+ DHCP should assign these settings automatically, therefore it should not be necessary to configure static routes on Fedora servers or clients.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-control.html"><strong>Prev</strong>4.3. Interface Control Scripts</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-functions.html"><strong>Next</strong>4.5. Network Function Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-openssh-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-openssh-additional-resources.html
new file mode 100644
index 0000000..1974997
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-openssh-additional-resources.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 9. OpenSSH" /><link rel="prev" href="s2-ssh-beyondshell-tcpip.html" title="9.4.2. Port Forwarding" /><link rel="next" href="s2-openssh-useful-websites.html" title="9.5.2. Useful Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-beyondshell-tcpip.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s
2-openssh-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" title="9.5. Additional Resources" id="s1-openssh-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-openssh-additional-resources">9.5. Additional Resources</h2></div></div></div><a id="id548727" class="indexterm"></a><a id="id548739" class="indexterm"></a><div class="para">
+ The OpenSSH and OpenSSL projects are in constant development, and the most up-to-date information for them is available from their websites. The man pages for OpenSSH and OpenSSL tools are also good sources of detailed information.
+ </div><div class="section" title="9.5.1. Installed Documentation" id="s2-openssh-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-openssh-installed-docs">9.5.1. Installed Documentation</h3></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="command">man ssh</code></span></dt><dd><div class="para">
+ The manual page for <span class="application"><strong>ssh</strong></span> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man scp</code></span></dt><dd><div class="para">
+ The manual page for <span class="application"><strong>scp</strong></span> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sftp</code></span></dt><dd><div class="para">
+ The manual page for <span class="application"><strong>sftp</strong></span> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sshd</code></span></dt><dd><div class="para">
+ The manual page for <span class="application"><strong>sshd</strong></span> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ssh-keygen</code></span></dt><dd><div class="para">
+ The manual page for <span class="application"><strong>ssh-keygen</strong></span> containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ssh_config</code></span></dt><dd><div class="para">
+ The manual page with full description of available SSH client configuration options.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man sshd_config</code></span></dt><dd><div class="para">
+ The manual page with full description of available SSH daemon configuration options.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-beyondshell-tcpip.html"><strong>Prev</strong>9.4.2. Port Forwarding</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-openssh-useful-websites.html"><strong>Next</strong>9.5.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-additional-resources.html
new file mode 100644
index 0000000..b7436dd
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-additional-resources.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.5. References</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-proc.html" title="Chapter 19. The proc File System" /><link rel="prev" href="s1-proc-sysctl.html" title="19.4. Using the sysctl Command" /><link rel="next" href="pt-system-monitoring.html" title="Part IV. System Monitoring" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-sysctl.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt-
system-monitoring.html"><strong>Next</strong></a></li></ul><div class="section" title="19.5. References" id="s1-proc-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-proc-additional-resources">19.5. References</h2></div></div></div><a id="id589179" class="indexterm"></a><div class="para">
+ Below are additional sources of information about <code class="filename">proc</code> file system.
+ </div><div class="simplesect" title="Installed Documentation" id="s2-proc-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h1 class="title">Installed Documentation</h1></div></div></div><a id="id589214" class="indexterm"></a><div class="para">
+ Some of the best documentation about the <code class="filename">proc</code> file system is installed on the system by default.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt</code> — Contains assorted, but limited, information about all aspects of the <code class="filename">/proc/</code> directory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysrq.txt</code> — An overview of System Request Key options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysctl/</code> — A directory containing a variety of <code class="command">sysctl</code> tips, including modifying values that concern the kernel (<code class="filename">kernel.txt</code>), accessing file systems (<code class="filename">fs.txt</code>), and virtual memory use (<code class="filename">vm.txt</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/networking/ip-sysctl.txt</code> — A detailed overview of IP networking options.
+ </div></li></ul></div></div><div class="simplesect" title="Useful Websites" id="s2-proc-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h1 class="title">Useful Websites</h1></div></div></div><a id="id1770463" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.linuxhq.com/">http://www.linuxhq.com/</a> — This website maintains a complete database of source, patches, and documentation for various versions of the Linux kernel.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-sysctl.html"><strong>Prev</strong>19.4. Using the sysctl Command</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pt-system-monitoring.html"><strong>Next</strong>Part IV. System Monitoring</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-directories.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-directories.html
new file mode 100644
index 0000000..5d5fcb5
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-directories.html
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3. Directories within /proc/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-proc.html" title="Chapter 19. The proc File System" /><link rel="prev" href="s2-proc-version.html" title="19.2.29. /proc/version" /><link rel="next" href="s2-proc-dir-bus.html" title="19.3.2. /proc/bus/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-version.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-bus.html"
><strong>Next</strong></a></li></ul><div class="section" title="19.3. Directories within /proc/" id="s1-proc-directories"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-proc-directories">19.3. Directories within <code class="filename">/proc/</code> </h2></div></div></div><a id="id771287" class="indexterm"></a><div class="para">
+ Common groups of information concerning the kernel are grouped into directories and subdirectories within the <code class="filename">/proc/</code> directory.
+ </div><div class="section" title="19.3.1. Process Directories" id="s2-proc-processdirs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-processdirs">19.3.1. Process Directories</h3></div></div></div><a id="id771324" class="indexterm"></a><div class="para">
+ Every <code class="filename">/proc/</code> directory contains a number of directories with numerical names. A listing of them may be similar to the following:
+ </div><pre class="screen">
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 1
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 1010
+dr-xr-xr-x 3 xfs xfs 0 Feb 13 01:28 1087
+dr-xr-xr-x 3 daemon daemon 0 Feb 13 01:28 1123
+dr-xr-xr-x 3 root root 0 Feb 13 01:28 11307
+dr-xr-xr-x 3 apache apache 0 Feb 13 01:28 13660
+dr-xr-xr-x 3 rpc rpc 0 Feb 13 01:28 637
+dr-xr-xr-x 3 rpcuser rpcuser 0 Feb 13 01:28 666
+</pre><div class="para">
+ These directories are called <em class="firstterm">process directories</em>, as they are named after a program's process ID and contain information specific to that process. The owner and group of each process directory is set to the user running the process. When the process is terminated, its <code class="filename">/proc/</code> process directory vanishes.
+ </div><div class="para">
+ Each process directory contains the following files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">cmdline</code> — Contains the command issued when starting the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cwd</code> — A symbolic link to the current working directory for the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">environ</code> — A list of the environment variables for the process. The environment variable is given in all upper-case characters, and the value is in lower-case characters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">exe</code> — A symbolic link to the executable of this process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">fd</code> — A directory containing all of the file descriptors for a particular process. These are given in numbered links:
+ </div><pre class="screen">
+total 0
+lrwx------ 1 root root 64 May 8 11:31 0 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 1 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 2 -> /dev/null
+lrwx------ 1 root root 64 May 8 11:31 3 -> /dev/ptmx
+lrwx------ 1 root root 64 May 8 11:31 4 -> socket:[7774817]
+lrwx------ 1 root root 64 May 8 11:31 5 -> /dev/ptmx
+lrwx------ 1 root root 64 May 8 11:31 6 -> socket:[7774829]
+lrwx------ 1 root root 64 May 8 11:31 7 -> /dev/ptmx
+</pre></li><li class="listitem"><div class="para">
+ <code class="computeroutput">maps</code> — A list of memory maps to the various executables and library files associated with this process. This file can be rather long, depending upon the complexity of the process, but sample output from the <code class="command">sshd</code> process begins like the following:
+ </div><pre class="screen">
+08048000-08086000 r-xp 00000000 03:03 391479 /usr/sbin/sshd
+08086000-08088000 rw-p 0003e000 03:03 391479 /usr/sbin/sshd
+08088000-08095000 rwxp 00000000 00:00 0
+40000000-40013000 r-xp 0000000 03:03 293205 /lib/ld-2.2.5.so
+40013000-40014000 rw-p 00013000 03:03 293205 /lib/ld-2.2.5.so
+40031000-40038000 r-xp 00000000 03:03 293282 /lib/libpam.so.0.75
+40038000-40039000 rw-p 00006000 03:03 293282 /lib/libpam.so.0.75
+40039000-4003a000 rw-p 00000000 00:00 0
+4003a000-4003c000 r-xp 00000000 03:03 293218 /lib/libdl-2.2.5.so
+4003c000-4003d000 rw-p 00001000 03:03 293218 /lib/libdl-2.2.5.so
+</pre></li><li class="listitem"><div class="para">
+ <code class="computeroutput">mem</code> — The memory held by the process. This file cannot be read by the user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">root</code> — A link to the root directory of the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">stat</code> — The status of the process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">statm</code> — The status of the memory in use by the process. Below is a sample <code class="filename">/proc/statm</code> file:
+ </div><pre class="screen">
+263 210 210 5 0 205 0
+</pre><div class="para">
+ The seven columns relate to different memory statistics for the process. From left to right, they report the following aspects of the memory used:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Total program size, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ Size of memory portions, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages that are shared.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages that are code.
+ </div></li><li class="listitem"><div class="para">
+ Number of pages of data/stack.
+ </div></li><li class="listitem"><div class="para">
+ Number of library pages.
+ </div></li><li class="listitem"><div class="para">
+ Number of dirty pages.
+ </div></li></ol></div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">status</code> — The status of the process in a more readable form than <code class="filename">stat</code> or <code class="filename">statm</code>. Sample output for <code class="command">sshd</code> looks similar to the following:
+ </div><pre class="screen">
+Name: sshd
+State: S (sleeping)
+Tgid: 797
+Pid: 797
+PPid: 1
+TracerPid: 0
+Uid: 0 0 0 0
+Gid: 0 0 0 0
+FDSize: 32
+Groups:
+VmSize: 3072 kB
+VmLck: 0 kB
+VmRSS: 840 kB
+VmData: 104 kB
+VmStk: 12 kB
+VmExe: 300 kB
+VmLib: 2528 kB
+SigPnd: 0000000000000000
+SigBlk: 0000000000000000
+SigIgn: 8000000000001000
+SigCgt: 0000000000014005
+CapInh: 0000000000000000
+CapPrm: 00000000fffffeff
+CapEff: 00000000fffffeff
+</pre><div class="para">
+ The information in this output includes the process name and ID, the state (such as <code class="computeroutput">S (sleeping)</code> or <code class="computeroutput">R (running)</code>), user/group ID running the process, and detailed data regarding memory usage.
+ </div></li></ul></div><div class="section" title="19.3.1.1. /proc/self/" id="s3-proc-self"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-self">19.3.1.1. <code class="filename">/proc/self/</code> </h4></div></div></div><a id="id823057" class="indexterm"></a><div class="para">
+ The <code class="filename">/proc/self/</code> directory is a link to the currently running process. This allows a process to look at itself without having to know its process ID.
+ </div><div class="para">
+ Within a shell environment, a listing of the <code class="filename">/proc/self/</code> directory produces the same contents as listing the process directory for that process.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-version.html"><strong>Prev</strong>19.2.29. /proc/version </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-bus.html"><strong>Next</strong>19.3.2. /proc/bus/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-sysctl.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-sysctl.html
new file mode 100644
index 0000000..8df3bf4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-sysctl.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.4. Using the sysctl Command</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-proc.html" title="Chapter 19. The proc File System" /><link rel="prev" href="s2-proc-pid.html" title="19.3.12. /proc/PID/" /><link rel="next" href="s1-proc-additional-resources.html" title="19.5. References" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-pid.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-proc-additional-res
ources.html"><strong>Next</strong></a></li></ul><div class="section" title="19.4. Using the sysctl Command" id="s1-proc-sysctl"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-proc-sysctl">19.4. Using the <code class="command">sysctl</code> Command</h2></div></div></div><a id="id612057" class="indexterm"></a><a id="id612072" class="indexterm"></a><a id="id612086" class="indexterm"></a><a id="id612109" class="indexterm"></a><a id="id612140" class="indexterm"></a><a id="id612158" class="indexterm"></a><div class="para">
+ The <code class="command">/sbin/sysctl</code> command is used to view, set, and automate kernel settings in the <code class="filename">/proc/sys/</code> directory.
+ </div><div class="para">
+ For a quick overview of all settings configurable in the <code class="filename">/proc/sys/</code> directory, type the <code class="command">/sbin/sysctl -a</code> command as root. This creates a large, comprehensive list, a small portion of which looks something like the following:
+ </div><pre class="screen">
+net.ipv4.route.min_delay = 2 kernel.sysrq = 0 kernel.sem = 250 32000 32 128
+</pre><div class="para">
+ This is the same information seen if each of the files were viewed individually. The only difference is the file location. For example, the <code class="filename">/proc/sys/net/ipv4/route/min_delay</code> file is listed as <code class="computeroutput">net.ipv4.route.min_delay</code>, with the directory slashes replaced by dots and the <code class="computeroutput">proc.sys</code> portion assumed.
+ </div><div class="para">
+ The <code class="command">sysctl</code> command can be used in place of <code class="command">echo</code> to assign values to writable files in the <code class="filename">/proc/sys/</code> directory. For example, instead of using the command
+ </div><pre class="screen">
+echo 1 > /proc/sys/kernel/sysrq
+</pre><div class="para">
+ use the equivalent <code class="command">sysctl</code> command as follows:
+ </div><pre class="screen">
+sysctl -w kernel.sysrq="1"
+kernel.sysrq = 1
+</pre><div class="para">
+ While quickly setting single values like this in <code class="filename">/proc/sys/</code> is helpful during testing, this method does not work as well on a production system as special settings within <code class="filename">/proc/sys/</code> are lost when the machine is rebooted. To preserve custom settings, add them to the <code class="filename">/etc/sysctl.conf</code> file.
+ </div><div class="para">
+ Each time the system boots, the <code class="command">init</code> program runs the <code class="filename">/etc/rc.d/rc.sysinit</code> script. This script contains a command to execute <code class="command">sysctl</code> using <code class="filename">/etc/sysctl.conf</code> to determine the values passed to the kernel. Any values added to <code class="filename">/etc/sysctl.conf</code> therefore take effect each time the system boots.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-pid.html"><strong>Prev</strong>19.3.12. /proc/PID/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-proc-additional-resources.html"><strong>Next</strong>19.5. References</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-topfiles.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-topfiles.html
new file mode 100644
index 0000000..fc7c74f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-proc-topfiles.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2. Top-level Files within the proc File System</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-proc.html" title="Chapter 19. The proc File System" /><link rel="prev" href="ch-proc.html" title="Chapter 19. The proc File System" /><link rel="next" href="s2-proc-cmdline.html" title="19.2.2. /proc/cmdline" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-proc.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-cmdline.html"><s
trong>Next</strong></a></li></ul><div class="section" title="19.2. Top-level Files within the proc File System" id="s1-proc-topfiles"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-proc-topfiles">19.2. Top-level Files within the <code class="filename">proc</code> File System</h2></div></div></div><a id="id490518" class="indexterm"></a><div class="para">
+ Below is a list of some of the more useful virtual files in the top-level of the <code class="filename">/proc/</code> directory.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ In most cases, the content of the files listed in this section are not the same as those installed on your machine. This is because much of the information is specific to the hardware on which Fedora is running for this documentation effort.
+ </div></div></div><div class="section" title="19.2.1. /proc/buddyinfo" id="s2-proc-buddyinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-buddyinfo">19.2.1. <code class="filename">/proc/buddyinfo</code> </h3></div></div></div><a id="id545202" class="indexterm"></a><div class="para">
+ This file is used primarily for diagnosing memory fragmentation issues. Using the buddy algorithm, each column represents the number of pages of a certain order (a certain size) that are available at any given time. For example, for zone <em class="firstterm">direct memory access</em> (DMA), there are 90 of 2<sup>(0*PAGE_SIZE)</sup> chunks of memory. Similarly, there are 6 of 2<sup>(1*PAGE_SIZE)</sup> chunks, and 2 of 2<sup>(2*PAGE_SIZE)</sup> chunks of memory available.
+ </div><div class="para">
+ The <code class="computeroutput">DMA</code> row references the first 16 MB on a system, the <code class="computeroutput">HighMem</code> row references all memory greater than 4 GB on a system, and the <code class="computeroutput">Normal</code> row references all memory in between.
+ </div><div class="para">
+ The following is an example of the output typical of <code class="filename">/proc/buddyinfo</code>:
+ </div><pre class="screen">
+Node 0, zone DMA 90 6 2 1 1 ...
+Node 0, zone Normal 1650 310 5 0 0 ...
+Node 0, zone HighMem 2 0 0 1 1 ...
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-proc.html"><strong>Prev</strong>Chapter 19. The proc File System</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-cmdline.html"><strong>Next</strong>19.2.2. /proc/cmdline </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rpm-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rpm-additional-resources.html
new file mode 100644
index 0000000..cdd2963
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rpm-additional-resources.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.5. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-RPM.html" title="Chapter 3. RPM" /><link rel="prev" href="s1-rpm-impressing.html" title="3.4. Practical and Common Examples of RPM Usage" /><link rel="next" href="s2-rpm-useful-websites.html" title="3.5.2. Useful Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-impressing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2
-rpm-useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" title="3.5. Additional Resources" id="s1-rpm-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-rpm-additional-resources">3.5. Additional Resources</h2></div></div></div><a id="id493871" class="indexterm"></a><div class="para">
+ RPM is an extremely complex utility with many options and methods for querying, installing, upgrading, and removing packages. Refer to the following resources to learn more about RPM.
+ </div><div class="section" title="3.5.1. Installed Documentation" id="s2-rpm-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-installed-docs">3.5.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">rpm --help</code> — This command displays a quick reference of RPM parameters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man rpm</code> — The RPM man page gives more detail about RPM parameters than the <code class="command">rpm --help</code> command.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-impressing.html"><strong>Prev</strong>3.4. Practical and Common Examples of RPM Usage</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-useful-websites.html"><strong>Next</strong>3.5.2. Useful Websites</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rpm-impressing.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rpm-impressing.html
new file mode 100644
index 0000000..adee283
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rpm-impressing.html
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.4. Practical and Common Examples of RPM Usage</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-RPM.html" title="Chapter 3. RPM" /><link rel="prev" href="s2-keys-checking.html" title="3.3.2. Verifying Signature of Packages" /><link rel="next" href="s1-rpm-additional-resources.html" title="3.5. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-keys-checking.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-rp
m-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="3.4. Practical and Common Examples of RPM Usage" id="s1-rpm-impressing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-rpm-impressing">3.4. Practical and Common Examples of RPM Usage</h2></div></div></div><a id="id752539" class="indexterm"></a><a id="id752551" class="indexterm"></a><div class="para">
+ RPM is a useful tool for both managing your system and diagnosing and fixing problems. The best way to make sense of all its options is to look at some examples.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Perhaps you have deleted some files by accident, but you are not sure what you deleted. To verify your entire system and see what might be missing, you could try the following command:
+ </div><a id="id592834" class="indexterm"></a><a id="id592846" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -Va</code>
+</pre><div class="para">
+ If some files are missing or appear to have been corrupted, you should probably either re-install the package or uninstall and then re-install the package.
+ </div></li><li class="listitem"><div class="para">
+ At some point, you might see a file that you do not recognize. To find out which package owns it, enter:
+ </div><a id="id700529" class="indexterm"></a><a id="id700541" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qf /usr/bin/ghostscript</code>
+</pre><div class="para">
+ The output would look like the following:
+ </div><pre class="screen">ghostscript-8.70-1.fc14.x86_64</pre></li><li class="listitem"><div class="para">
+ We can combine the above two examples in the following scenario. Say you are having problems with <code class="filename">/usr/bin/paste</code>. You would like to verify the package that owns that program, but you do not know which package owns <code class="command">paste</code>. Enter the following command,
+ </div><pre class="screen">
+<code class="command">rpm -Vf /usr/bin/paste</code>
+</pre><div class="para">
+ and the appropriate package is verified.
+ </div></li><li class="listitem"><div class="para">
+ Do you want to find out more information about a particular program? You can try the following command to locate the documentation which came with the package that owns that program:
+ </div><a id="id838521" class="indexterm"></a><a id="id838533" class="indexterm"></a><a id="id838544" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qdf /usr/bin/free</code>
+</pre><div class="para">
+ The output would be similar to the following:
+ </div><pre class="screen">/usr/share/doc/procps-3.2.8/BUGS
+/usr/share/doc/procps-3.2.8/FAQ
+/usr/share/doc/procps-3.2.8/NEWS
+/usr/share/doc/procps-3.2.8/TODO
+/usr/share/man/man1/free.1.gz
+/usr/share/man/man1/pgrep.1.gz
+/usr/share/man/man1/pkill.1.gz
+/usr/share/man/man1/pmap.1.gz
+/usr/share/man/man1/ps.1.gz
+/usr/share/man/man1/pwdx.1.gz
+/usr/share/man/man1/skill.1.gz
+/usr/share/man/man1/slabtop.1.gz
+/usr/share/man/man1/snice.1.gz
+/usr/share/man/man1/tload.1.gz
+/usr/share/man/man1/top.1.gz
+/usr/share/man/man1/uptime.1.gz
+/usr/share/man/man1/w.1.gz
+/usr/share/man/man1/watch.1.gz
+/usr/share/man/man5/sysctl.conf.5.gz
+/usr/share/man/man8/sysctl.8.gz
+/usr/share/man/man8/vmstat.8.gz</pre></li><li class="listitem"><div class="para">
+ You may find a new RPM, but you do not know what it does. To find information about it, use the following command:
+ </div><a id="id585415" class="indexterm"></a><a id="id678823" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qip crontabs-1.10-31.fc14.noarch.rpm</code>
+</pre><div class="para">
+ The output would be similar to the following:
+ </div><pre class="screen">Name : crontabs Relocations: (not relocatable)
+Size : 2486 License: Public Domain and GPLv2
+Signature : RSA/SHA1, Tue 11 Aug 2009 01:11:19 PM CEST, Key ID 9d1cc34857bbccba
+Packager : Fedora Project
+Summary : Root crontab files used to schedule the execution of programs
+Description :
+The crontabs package contains root crontab files and directories.
+You will need to install cron daemon to run the jobs from the crontabs.
+The cron daemon such as cronie or fcron checks the crontab files to
+see when particular commands are scheduled to be executed. If commands
+are scheduled, it executes them.
+Crontabs handles a basic system function, so it should be installed on
+your system.</pre></li><li class="listitem"><div class="para">
+ Perhaps you now want to see what files the <code class="filename">crontabs</code> RPM package installs. You would enter the following:
+ </div><a id="id769659" class="indexterm"></a><a id="id769671" class="indexterm"></a><pre class="screen">
+<code class="command">rpm -qlp crontabs-1.10-31.fc14.noarch.rpm</code>
+</pre><div class="para">
+ The output is similar to the following:
+ </div><pre class="screen">/etc/cron.daily
+/etc/cron.hourly
+/etc/cron.monthly
+/etc/cron.weekly
+/etc/crontab
+/usr/bin/run-parts
+/usr/share/man/man4/crontabs.4.gz</pre></li></ul></div><div class="para">
+ These are just a few examples. As you use RPM, you may find more uses for it.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-keys-checking.html"><strong>Prev</strong>3.3.2. Verifying Signature of Packages</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-rpm-additional-resources.html"><strong>Next</strong>3.5. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rpm-using.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rpm-using.html
new file mode 100644
index 0000000..bb37d7f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rpm-using.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2. Using RPM</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-RPM.html" title="Chapter 3. RPM" /><link rel="prev" href="ch-RPM.html" title="Chapter 3. RPM" /><link rel="next" href="sec-Installing_and_Upgrading.html" title="3.2.2. Installing and Upgrading" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-RPM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_and_Upgrading.html"><stron
g>Next</strong></a></li></ul><div class="section" title="3.2. Using RPM" id="s1-rpm-using"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-rpm-using">3.2. Using RPM</h2></div></div></div><div class="para">
+ RPM has five basic modes of operation
+ <a id="id440838" class="indexterm"></a>
+ (not counting package building): installing, uninstalling, upgrading, querying, and verifying. This section contains an overview of each mode. For complete details and options, try <code class="command">rpm --help</code> or <code class="command">man rpm</code>. You can also refer to <a class="xref" href="s1-rpm-additional-resources.html" title="3.5. Additional Resources">Section 3.5, “Additional Resources”</a> for more information on RPM.
+ </div><div class="section" title="3.2.1. Finding RPM Packages" id="s2-rpm-finding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-finding">3.2.1. Finding RPM Packages</h3></div></div></div><a id="id503592" class="indexterm"></a><a id="id485237" class="indexterm"></a><div class="para">
+ Before using any RPM packages, you must know where to find them. An Internet search returns many RPM repositories, but if you are looking for Red Hat RPM packages, they can be found at the following locations:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The Fedora installation media
+ <a id="id622913" class="indexterm"></a>
+ <a id="id576093" class="indexterm"></a>
+ contain many installable RPMs.
+ </div></li><li class="listitem"><div class="para">
+ The initial RPM repositories provided with the YUM package manager
+ <a id="id538917" class="indexterm"></a>
+ <a id="id620672" class="indexterm"></a>
+ . Refer to <a class="xref" href="ch-yum.html" title="Chapter 1. Yum">Chapter 1, <i>Yum</i></a> for details on how to use the official Fedora package repositories.
+ </div></li><li class="listitem"><div class="para">
+ The active Fedora mirrors contains many installable RPMs: <a href="http://mirrors.fedoraproject.org/publiclist/">http://mirrors.fedoraproject.org/publiclist/</a>.
+ </div></li><li class="listitem"><div class="para">
+ Unofficial, third-party repositories not ahffiliated Red Hat also provide RPM packages.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When considering third-party repositories for use with your Fedora system, pay close attention to the repository's web site with regard to package compatibility before adding the repository as a package source. Alternate package repositories may offer different, incompatible versions of the same software, including packages already included in the Fedora repositories.
+ </div></div></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-RPM.html"><strong>Prev</strong>Chapter 3. RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_and_Upgrading.html"><strong>Next</strong>3.2.2. Installing and Upgrading</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rsyslog-performance.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rsyslog-performance.html
new file mode 100644
index 0000000..cb30e46
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-rsyslog-performance.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2. rsyslog Performance</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Log_Files.html" title="Chapter 17. Log Files" /><link rel="prev" href="ch-Log_Files.html" title="Chapter 17. Log Files" /><link rel="next" href="s1-logfiles-locating.html" title="17.3. Locating Log Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Log_Files.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-logfiles-locating.htm
l"><strong>Next</strong></a></li></ul><div class="section" title="17.2. rsyslog Performance" id="s1-rsyslog-performance"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-rsyslog-performance">17.2. <code class="command">rsyslog</code> Performance</h2></div></div></div><div class="para">
+
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Log_Files.html"><strong>Prev</strong>Chapter 17. Log Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-logfiles-locating.html"><strong>Next</strong>17.3. Locating Log Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-services-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-services-additional-resources.html
new file mode 100644
index 0000000..552f25c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-services-additional-resources.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.4. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services" /><link rel="prev" href="s1-services-running.html" title="7.3. Running the Services" /><link rel="next" href="s2-services-additional-resources-books.html" title="7.4.2. Related Books" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-services-running.html"><strong>Prev</strong><
/a></li><li class="next"><a accesskey="n" href="s2-services-additional-resources-books.html"><strong>Next</strong></a></li></ul><div class="section" title="7.4. Additional Resources" id="s1-services-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-services-additional-resources">7.4. Additional Resources</h2></div></div></div><div class="section" title="7.4.1. Installed Documentation" id="s2-services-additional-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-additional-resources-installed">7.4.1. Installed Documentation</h3></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="command">man chkconfig</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">chkconfig</code> utility containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man ntsysv</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">ntsysv</code> utility containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man service</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">service</code> utility containing the full documentation on its usage.
+ </div></dd><dt class="varlistentry"><span class="term"><code class="command">man system-config-services</code></span></dt><dd><div class="para">
+ The manual page for the <code class="command">system-config-services</code> utility containing the full documentation on its usage.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-services-running.html"><strong>Prev</strong>7.3. Running the Services</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-services-additional-resources-books.html"><strong>Next</strong>7.4.2. Related Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-services-configuring.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-services-configuring.html
new file mode 100644
index 0000000..5eec914
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-services-configuring.html
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2. Configuring the Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services" /><link rel="prev" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services" /><link rel="next" href="s2-services-ntsysv.html" title="7.2.2. Using the ntsysv Utility" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Controlling_Access_to_S
ervices.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-services-ntsysv.html"><strong>Next</strong></a></li></ul><div class="section" title="7.2. Configuring the Services" id="s1-services-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-services-configuring">7.2. Configuring the Services</h2></div></div></div><div class="section" title="7.2.1. Using the Service Configuration Utility" id="s2-services-serviceconf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-serviceconf">7.2.1. Using the <span class="application"><strong>Service Configuration</strong></span> Utility</h3></div></div></div><div class="para">
+ The <span class="application"><strong>Service Configuration</strong></span> utility is a graphical application developed by Red Hat to configure which services are started at boot time, as well as to start, stop, and restart them from the menu.
+ </div><a id="id416942" class="indexterm"></a><a id="id416960" class="indexterm"></a><div class="para">
+ To start the utility, select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Services</strong></span> from the panel, or type the command <code class="command">system-config-services</code> at a shell prompt (e.g., <span class="emphasis"><em>xterm</em></span> or <span class="emphasis"><em>GNOME Terminal</em></span>).
+ </div><div class="figure" title="Figure 7.1. The Service Configuration Utility" id="fig-services-serviceconf"><div class="figure-contents"><div class="mediaobject"><img src="images/controlling-access-to-services-service_configuration.png" alt="The Service Configuration Utility" /><div class="longdesc"><div class="para">
+ The Service Configuration Utility
+ </div></div></div></div><h6>Figure 7.1. The <span class="application">Service Configuration</span> Utility </h6></div><br class="figure-break" /><div class="para">
+ The utility displays the list of all available services (i.e., both the services from the <code class="filename">/etc/rc.d/init.d/</code> directory, and the services controlled by <span class="application"><strong>xinetd</strong></span>) along with their description and the current status. See <a class="xref" href="s1-services-configuring.html#tab-services-serviceconf-states" title="Table 7.2. Possible Service States">Table 7.2, “Possible Service States”</a> for a complete list of used icons and an explanation of their meaning.
+ </div><div class="table" title="Table 7.2. Possible Service States" id="tab-services-serviceconf-states"><h6>Table 7.2. Possible Service States</h6><div class="table-contents"><table summary="Possible Service States" border="1"><colgroup><col width="14%" /><col width="86%" /></colgroup><thead><tr><th>
+ Icon
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_enabled.png" /><div class="longdesc"><div class="para">
+ Green bullet
+ </div></div></span>
+
+ </td><td>
+ The service is enabled.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_disabled.png" /><div class="longdesc"><div class="para">
+ Red bullet
+ </div></div></span>
+
+ </td><td>
+ The service is disabled.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_selected.png" /><div class="longdesc"><div class="para">
+ Control panel
+ </div></div></span>
+
+ </td><td>
+ The service is enabled for selected runlevels only.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_running.png" /><div class="longdesc"><div class="para">
+ Plugged plug
+ </div></div></span>
+
+ </td><td>
+ The service is running.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_stopped.png" /><div class="longdesc"><div class="para">
+ Unplugged plug
+ </div></div></span>
+
+ </td><td>
+ The service is stopped.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_wrong.png" /><div class="longdesc"><div class="para">
+ Exclamation mark
+ </div></div></span>
+
+ </td><td>
+ There is something wrong with the service.
+ </td></tr><tr><td>
+ <span class="inlinemediaobject"><img src="images/controlling-access-to-services-service_unknown.png" /><div class="longdesc"><div class="para">
+ Question mark
+ </div></div></span>
+
+ </td><td>
+ The status of the service is unknown.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Unless you are already authenticated, you will be prompted to enter the superuser password the first time you make a change:
+ </div><div class="figure" title="Figure 7.2. Authentication Query" id="fig-services-serviceconf-authentication"><div class="figure-contents"><div class="mediaobject"><img src="images/controlling-access-to-services-authentication.png" alt="Authentication Query" /><div class="longdesc"><div class="para">
+ Authentication Query
+ </div></div></div></div><h6>Figure 7.2. Authentication Query</h6></div><br class="figure-break" /><div class="section" title="7.2.1.1. Enabling the Service" id="s3-services-serviceconf-enabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-enabling">7.2.1.1. Enabling the Service</h4></div></div></div><div class="para">
+ To enable a service, select it from the list and either click the <span class="guilabel"><strong>Enable</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guimenuitem"><strong>Enable</strong></span> from the main menu.
+ </div></div><div class="section" title="7.2.1.2. Disabling the Service" id="s3-services-serviceconf-disabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-disabling">7.2.1.2. Disabling the Service</h4></div></div></div><div class="para">
+ To disable the service, select it from the list and either click the <span class="guilabel"><strong>Disable</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guimenuitem"><strong>Disable</strong></span> from the main menu.
+ </div></div><div class="section" title="7.2.1.3. Running the Service" id="s3-services-serviceconf-running"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-running">7.2.1.3. Running the Service</h4></div></div></div><div class="para">
+ To run the service, select it from the list and either click the <span class="guilabel"><strong>Start</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guimenuitem"><strong>Start</strong></span> from the main menu. Note that this option is not available for services controlled by <span class="application"><strong>xinetd</strong></span>, as they are started by it on demand.
+ </div></div><div class="section" title="7.2.1.4. Stopping the Service" id="s3-services-serviceconf-stopping"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-stopping">7.2.1.4. Stopping the Service</h4></div></div></div><div class="para">
+ To stop the service, select it from the list and either click the <span class="guilabel"><strong>Stop</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guimenuitem"><strong>Stop</strong></span> from the main menu. Note that this option is not available for services controlled by <span class="application"><strong>xinetd</strong></span>, as they are stopped by it when their job is finished.
+ </div></div><div class="section" title="7.2.1.5. Restarting the Running Service" id="s3-services-serviceconf-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-restarting">7.2.1.5. Restarting the Running Service</h4></div></div></div><div class="para">
+ To restart the running service, select it from the list and either click the <span class="guilabel"><strong>Restart</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guimenuitem"><strong>Restart</strong></span> from the main menu. Note that this option is not available for services controlled by <span class="application"><strong>xinetd</strong></span>, as they are started and stopped by it automatically.
+ </div></div><div class="section" title="7.2.1.6. Selecting the Runlevels" id="s3-services-serviceconf-selecting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-serviceconf-selecting">7.2.1.6. Selecting the Runlevels</h4></div></div></div><div class="para">
+ To enable the service for certain runlevels only, select it from the list and either click the <span class="guilabel"><strong>Customize</strong></span> button on the toolbar, or choose <span class="guimenu"><strong>Service</strong></span> → <span class="guisubmenu"><strong>Customize</strong></span> from the main menu. Then select the checkbox beside each runlevel in which you want the service to run. Note that this option is not available for services controlled by <span class="application"><strong>xinetd</strong></span>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Controlling_Access_to_Services.html"><strong>Prev</strong>Chapter 7. Controlling Access to Services</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-services-ntsysv.html"><strong>Next</strong>7.2.2. Using the ntsysv Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-services-running.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-services-running.html
new file mode 100644
index 0000000..48e3cb8
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-services-running.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.3. Running the Services</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services" /><link rel="prev" href="s2-services-chkconfig.html" title="7.2.3. Using the chkconfig Utility" /><link rel="next" href="s1-services-additional-resources.html" title="7.4. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-services-chkconfig.html"><strong>Pr
ev</strong></a></li><li class="next"><a accesskey="n" href="s1-services-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="7.3. Running the Services" id="s1-services-running"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-services-running">7.3. Running the Services</h2></div></div></div><div class="section" title="7.3.1. Using the service Utility" id="s2-services-service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-service">7.3.1. Using the <span class="application"><strong>service</strong></span> Utility</h3></div></div></div><a id="id588978" class="indexterm"></a><a id="id588996" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>service</strong></span> utility enables you to start, stop, or restart the services from the <code class="filename">/etc/init.d/</code> directory. To use it, make sure you have superuser privileges:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ If you are running a graphical user interface, you can also use the <span class="application"><strong>Service Configuration</strong></span> utility. See <a class="xref" href="s1-services-configuring.html#s2-services-serviceconf" title="7.2.1. Using the Service Configuration Utility">Section 7.2.1, “Using the <span class="application"><strong>Service Configuration</strong></span> Utility”</a> for more information.
+ </div></div></div><div class="section" title="7.3.1.1. Running the Service" id="s3-services-running-running"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-running-running">7.3.1.1. Running the Service</h4></div></div></div><div class="para">
+ To run the service, type <code class="command">service <em class="replaceable"><code><service_name></code></em> start</code>. For example:
+ </div><pre class="screen">~]# <code class="command">service httpd start</code>
+Starting httpd: [ OK ]</pre></div><div class="section" title="7.3.1.2. Stopping the Service" id="s3-services-running-stopping"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-running-stopping">7.3.1.2. Stopping the Service</h4></div></div></div><div class="para">
+ To stop the service, type <code class="command">service <em class="replaceable"><code><service_name></code></em> stop</code>. For example:
+ </div><pre class="screen">~]# <code class="command">service httpd stop</code>
+Stopping httpd: [ OK ]</pre></div><div class="section" title="7.3.1.3. Restarting the Service" id="s3-services-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-running-restarting">7.3.1.3. Restarting the Service</h4></div></div></div><div class="para">
+ To restart the service, type <code class="command">service <em class="replaceable"><code><service_name></code></em> restart</code>. For example:
+ </div><pre class="screen">~]# <code class="command">service httpd restart</code>
+Stopping httpd: [ OK ]
+Starting httpd: [ OK ]</pre></div><div class="section" title="7.3.1.4. Checking the Service Status" id="s3-services-running-checking"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-running-checking">7.3.1.4. Checking the Service Status</h4></div></div></div><div class="para">
+ To check the current status of the service, type <code class="command">service <em class="replaceable"><code><service_name></code></em> status</code>. For example:
+ </div><div class="example" title="Example 7.4. Checking the status of httpd" id="ex-services-running-checking-single"><h6>Example 7.4. Checking the status of <span class="application">httpd</span></h6><div class="example-contents"><pre class="screen">~]# <code class="command">service httpd status</code>
+httpd (pid 7474) is running...</pre></div></div><br class="example-break" /><div class="para">
+ You can also display the status of all available services at once using the <code class="option">--status-all</code> option:
+ </div><div class="example" title="Example 7.5. Checking the status of all services" id="ex-services-running-checking-all"><h6>Example 7.5. Checking the status of all services</h6><div class="example-contents"><pre class="screen">~]# <code class="command">service --status-all</code>
+abrt (pid 1492) is running...
+acpid (pid 1305) is running...
+atd (pid 1540) is running...
+auditd (pid 1103) is running...
+automount (pid 1315) is running...
+Avahi daemon is running
+cpuspeed is stopped
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+wpa_supplicant (pid 1227) is running...</pre></div></div><br class="example-break" /></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-services-chkconfig.html"><strong>Prev</strong>7.2.3. Using the chkconfig Utility</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-services-additional-resources.html"><strong>Next</strong>7.4. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-ssh-beyondshell.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-ssh-beyondshell.html
new file mode 100644
index 0000000..7d28040
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-ssh-beyondshell.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.4. More Than a Secure Shell</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 9. OpenSSH" /><link rel="prev" href="s2-ssh-clients-sftp.html" title="9.3.3. Using the sftp Utility" /><link rel="next" href="s2-ssh-beyondshell-tcpip.html" title="9.4.2. Port Forwarding" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-clients-sftp.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ssh
-beyondshell-tcpip.html"><strong>Next</strong></a></li></ul><div class="section" title="9.4. More Than a Secure Shell" id="s1-ssh-beyondshell"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ssh-beyondshell">9.4. More Than a Secure Shell</h2></div></div></div><div class="para">
+ A secure command line interface is just the beginning of the many ways SSH can be used. Given the proper amount of bandwidth, X11 sessions can be directed over an SSH channel. Or, by using TCP/IP forwarding, previously insecure port connections between systems can be mapped to specific SSH channels.
+ </div><div class="section" title="9.4.1. X11 Forwarding" id="s2-ssh-beyondshell-x11"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-beyondshell-x11">9.4.1. X11 Forwarding</h3></div></div></div><a id="id617949" class="indexterm"></a><div class="para">
+ To open an X11 session over an SSH connection, use a command in the following form:
+ </div><pre class="screen"><code class="command">ssh -Y <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em></code></pre><div class="para">
+ For example, to log in to a remote machine named <code class="systemitem">penguin.example.com</code> with <code class="systemitem">john</code> as a username, type:
+ </div><pre class="screen">~]$ <code class="command">ssh -Y john at penguin.example.com</code>
+john at penguin.example.com's password:</pre><div class="para">
+ When an X program is run from the secure shell prompt, the SSH client and server create a new secure channel, and the X program data is sent over that channel to the client machine transparently.
+ </div><div class="para">
+ X11 forwarding can be very useful. For example, X11 forwarding can be used to create a secure, interactive session of the <span class="application"><strong>Printer Configuration</strong></span> utility. To do this, connect to the server using <span class="application"><strong>ssh</strong></span> and type:
+ </div><pre class="screen">~]$ <code class="command">system-config-printer &</code></pre><div class="para">
+ The <span class="application"><strong>Printer Configuration Tool</strong></span> will appear, allowing the remote user to safely configure printing on the remote system.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-clients-sftp.html"><strong>Prev</strong>9.3.3. Using the sftp Utility</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-ssh-beyondshell-tcpip.html"><strong>Next</strong>9.4.2. Port Forwarding</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-ssh-clients.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-ssh-clients.html
new file mode 100644
index 0000000..8315627
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-ssh-clients.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3. OpenSSH Clients</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 9. OpenSSH" /><link rel="prev" href="s2-ssh-configuration-keypairs.html" title="9.2.4. Using a Key-Based Authentication" /><link rel="next" href="s2-ssh-clients-scp.html" title="9.3.2. Using the scp Utility" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-configuration-keypairs.html"><strong>Prev</strong></a></li><li class="next"
><a accesskey="n" href="s2-ssh-clients-scp.html"><strong>Next</strong></a></li></ul><div class="section" title="9.3. OpenSSH Clients" id="s1-ssh-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ssh-clients">9.3. OpenSSH Clients</h2></div></div></div><a id="id722449" class="indexterm"></a><div class="note" title="Note: Make Sure You Have Relevant Packages Installed"><div class="admonition_header"><h2>Note: Make Sure You Have Relevant Packages Installed</h2></div><div class="admonition"><div class="para">
+ To connect to an OpenSSH server from a client machine, you must have the <span class="package">openssh-clients</span> and <span class="package">openssh</span> packages installed. Refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><div class="section" title="9.3.1. Using the ssh Utility" id="s2-ssh-clients-ssh"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-clients-ssh">9.3.1. Using the <code class="command">ssh</code> Utility</h3></div></div></div><a id="id739224" class="indexterm"></a><a id="id739240" class="indexterm"></a><div class="para">
+ <code class="command">ssh</code> allows you to log in to a remote machine and execute commands there. It is a secure replacement for the <code class="command">rlogin</code>, <code class="command">rsh</code>, and <code class="command">telnet</code> programs.
+ </div><div class="para">
+ Similarly to <code class="command">telnet</code>, to log in to a remote machine named <code class="systemitem">penguin.example.com</code>, type the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">ssh penguin.example.com</code></pre><div class="para">
+ This will log you in with the same username you are using on a local machine. If you want to specify a different one, use a command in the <code class="command">ssh <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em></code> form. For example, to log in as <code class="systemitem">john</code>, type:
+ </div><pre class="screen">~]$ <code class="command">ssh john at penguin.example.com</code></pre><div class="para">
+ The first time you initiate a connection, you will be presented with a message similar to this:
+ </div><pre class="screen">The authenticity of host 'penguin.example.com' can't be established.
+RSA key fingerprint is 94:68:3a:3a:bc:f3:9a:9b:01:5d:b3:07:38:e2:11:0c.
+Are you sure you want to continue connecting (yes/no)?</pre><div class="para">
+ Type <strong class="userinput"><code>yes</code></strong> to confirm. You will see a notice that the server has been added to the list of known hosts, and a prompt asking for your password:
+ </div><pre class="screen">Warning: Permanently added 'penguin.example.com' (RSA) to the list of known hosts.
+john at penguin.example.com's password:</pre><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If the SSH server's host key changes, the client notifies the user that the connection cannot proceed until the server's host key is deleted from the <code class="filename">~/.ssh/known_hosts</code> file. To do so, open the file in a text editor, and remove a line containing the remote machine name at the beginning. Before doing this, however, contact the system administrator of the SSH server to verify the server is not compromised.
+ </div></div></div><div class="para">
+ After entering the password, you will be provided with a shell prompt for the remote machine.
+ </div><div class="para">
+ Alternatively, the <code class="command">ssh</code> program can be used to execute a command on the remote machine without logging in to a shell prompt. The syntax for that is <code class="command">ssh [<em class="replaceable"><code>username</code></em>@]<em class="replaceable"><code>hostname</code></em> <em class="replaceable"><code>command</code></em></code>. For example, if you want to execute the <code class="command">whoami</code> command on <code class="systemitem">penguin.example.com</code>, type:
+ </div><pre class="screen">~]$ <code class="command">ssh john at penguin.example.com whoami</code>
+john at penguin.example.com's password:
+john</pre><div class="para">
+ After you enter the correct password, the username will be displayed, and you will return to your local shell prompt.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-configuration-keypairs.html"><strong>Prev</strong>9.2.4. Using a Key-Based Authentication</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-ssh-clients-scp.html"><strong>Next</strong>9.3.2. Using the scp Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-ssh-configuration.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-ssh-configuration.html
new file mode 100644
index 0000000..792d0af
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-ssh-configuration.html
@@ -0,0 +1,97 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2. An OpenSSH Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 9. OpenSSH" /><link rel="prev" href="ch-OpenSSH.html" title="Chapter 9. OpenSSH" /><link rel="next" href="s2-ssh-configuration-sshd.html" title="9.2.2. Starting an OpenSSH Server" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-OpenSSH.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ssh-configuration-s
shd.html"><strong>Next</strong></a></li></ul><div class="section" title="9.2. An OpenSSH Configuration" id="s1-ssh-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-ssh-configuration">9.2. An OpenSSH Configuration</h2></div></div></div><div class="para">
+ In order to perform tasks described in this section, you must have superuser privileges. To obtain them, log in as root by typing:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="section" title="9.2.1. Configuration Files" id="s2-ssh-configuration-configs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-configuration-configs">9.2.1. Configuration Files</h3></div></div></div><a id="id738866" class="indexterm"></a><div class="para">
+ There are two different sets of configuration files: those for client programs (that is, <code class="command">ssh</code>, <code class="command">scp</code>, and <code class="command">sftp</code>), and those for the server (the <code class="command">sshd</code> daemon).
+ </div><a id="id738898" class="indexterm"></a><div class="para">
+ System-wide SSH configuration information is stored in the <code class="filename">/etc/ssh/</code> directory. See <a class="xref" href="s1-ssh-configuration.html#table-ssh-configuration-configs-system" title="Table 9.1. System-wide configuration files">Table 9.1, “System-wide configuration files”</a> for a description of its content.
+ </div><div class="table" title="Table 9.1. System-wide configuration files" id="table-ssh-configuration-configs-system"><h6>Table 9.1. System-wide configuration files</h6><div class="table-contents"><table summary="System-wide configuration files" border="1"><colgroup><col width="38%" /><col width="63%" /></colgroup><thead><tr><th>
+ Configuration File
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">/etc/ssh/moduli</code>
+ </td><td>
+ Contains Diffie-Hellman groups used for the Diffie-Hellman key exchange which is critical for constructing a secure transport layer. When keys are exchanged at the beginning of an SSH session, a shared, secret value is created which cannot be determined by either party alone. This value is then used to provide host authentication.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_config</code>
+ </td><td>
+ The default SSH client configuration file. Note that it is overridden by <code class="filename">~/.ssh/config</code> if it exists.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/sshd_config</code>
+ </td><td>
+ The configuration file for the <code class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_dsa_key</code>
+ </td><td>
+ The DSA private key used by the <code class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_dsa_key.pub</code>
+ </td><td>
+ The DSA public key used by the <code class="command">sshd</code> daemon.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_key</code>
+ </td><td>
+ The RSA private key used by the <code class="command">sshd</code> daemon for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_key.pub</code>
+ </td><td>
+ The RSA public key used by the <code class="command">sshd</code> daemon for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_rsa_key</code>
+ </td><td>
+ The RSA private key used by the <code class="command">sshd</code> daemon for version 2 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">/etc/ssh/ssh_host_rsa_key.pub</code>
+ </td><td>
+ The RSA public key used by the <code class="command">sshd</code> for version 2 of the SSH protocol.
+ </td></tr></tbody></table></div></div><br class="table-break" /><a id="id620318" class="indexterm"></a><div class="para">
+ User-specific SSH configuration information is stored in the user's home directory within the <code class="filename">~/.ssh/</code> directory. See <a class="xref" href="s1-ssh-configuration.html#table-ssh-configuration-configs-user" title="Table 9.2. User-specific configuration files">Table 9.2, “User-specific configuration files”</a> for a description of its content.
+ </div><div class="table" title="Table 9.2. User-specific configuration files" id="table-ssh-configuration-configs-user"><h6>Table 9.2. User-specific configuration files</h6><div class="table-contents"><table summary="User-specific configuration files" border="1"><colgroup><col width="38%" /><col width="63%" /></colgroup><thead><tr><th>
+ Configuration File
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="filename">~/.ssh/authorized_keys</code>
+ </td><td>
+ Holds a list of authorized public keys for servers. When the client connects to a server, the server authenticates the client by checking its signed public key stored within this file.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_dsa</code>
+ </td><td>
+ Contains the DSA private key of the user.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_dsa.pub</code>
+ </td><td>
+ The DSA public key of the user.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_rsa</code>
+ </td><td>
+ The RSA private key used by <code class="command">ssh</code> for version 2 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/id_rsa.pub</code>
+ </td><td>
+ The RSA public key used by <code class="command">ssh</code> for version 2 of the SSH protocol
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/identity</code>
+ </td><td>
+ The RSA private key used by <code class="command">ssh</code> for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/identity.pub</code>
+ </td><td>
+ The RSA public key used by <code class="command">ssh</code> for version 1 of the SSH protocol.
+ </td></tr><tr><td>
+ <code class="filename">~/.ssh/known_hosts</code>
+ </td><td>
+ Contains DSA host keys of SSH servers accessed by the user. This file is very important for ensuring that the SSH client is connecting the correct SSH server.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Refer to the <code class="command">ssh_config</code> and <code class="command">sshd_config</code> man pages for information concerning the various directives available in the SSH configuration files.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-OpenSSH.html"><strong>Prev</strong>Chapter 9. OpenSSH</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-ssh-configuration-sshd.html"><strong>Next</strong>9.2.2. Starting an OpenSSH Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysconfig-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysconfig-additional-resources.html
new file mode 100644
index 0000000..37ab000
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysconfig-additional-resources.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.3. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_sysconfig_Directory.html" title="Chapter 18. The sysconfig Directory" /><link rel="prev" href="s1-sysconfig-etcsysconf-dir.html" title="18.2. Directories in the /etc/sysconfig/ Directory" /><link rel="next" href="ch-proc.html" title="Chapter 19. The proc File System" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysconfig-etcsysconf-dir.html"><strong>Prev
</strong></a></li><li class="next"><a accesskey="n" href="ch-proc.html"><strong>Next</strong></a></li></ul><div class="section" title="18.3. Additional Resources" id="s1-sysconfig-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysconfig-additional-resources">18.3. Additional Resources</h2></div></div></div><a id="id568441" class="indexterm"></a><div class="para">
+ This chapter is only intended as an introduction to the files in the <code class="filename">/etc/sysconfig/</code> directory. The following source contains more comprehensive information.
+ </div><div class="section" title="18.3.1. Installed Documentation" id="s2-sysconfig-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysconfig-installed-documentation">18.3.1. Installed Documentation</h3></div></div></div><a id="id576460" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">/usr/share/doc/initscripts-<em class="replaceable"><code>version</code></em>/sysconfig.txt</code> </span></dt><dd><div class="para">
+ A more authoritative listing of the files found in the <code class="filename">/etc/sysconfig/</code> directory and the configuration options available for them.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysconfig-etcsysconf-dir.html"><strong>Prev</strong>18.2. Directories in the /etc/sysconfig/ Directory</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-proc.html"><strong>Next</strong>Chapter 19. The proc File System</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysconfig-etcsysconf-dir.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysconfig-etcsysconf-dir.html
new file mode 100644
index 0000000..e6a115f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysconfig-etcsysconf-dir.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>18.2. Directories in the /etc/sysconfig/ Directory</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-The_sysconfig_Directory.html" title="Chapter 18. The sysconfig Directory" /><link rel="prev" href="ch-The_sysconfig_Directory.html" title="Chapter 18. The sysconfig Directory" /><link rel="next" href="s1-sysconfig-additional-resources.html" title="18.3. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-The_sysconfig_Directory.html"><strong>P
rev</strong></a></li><li class="next"><a accesskey="n" href="s1-sysconfig-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="18.2. Directories in the /etc/sysconfig/ Directory" id="s1-sysconfig-etcsysconf-dir"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysconfig-etcsysconf-dir">18.2. Directories in the <code class="filename">/etc/sysconfig/</code> Directory</h2></div></div></div><a id="id779266" class="indexterm"></a><div class="para">
+ The following directories are normally found in <code class="filename">/etc/sysconfig/</code>.
+ </div><a id="id779292" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/cbq/</code> </span></dt><dd><div class="para">
+ <a id="id779335" class="indexterm"></a>
+ This directory contains the configuration files needed to do <em class="firstterm">Class Based Queuing</em> for bandwidth management on network interfaces. CBQ divides user traffic into a hierarchy of classes based on any combination of IP addresses, protocols, and application types.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/networking/</code> </span></dt><dd><div class="para">
+ <a id="id779386" class="indexterm"></a>
+ This directory is used by the <span class="application"><strong>Network Administration Tool</strong></span> (<code class="command">system-config-network</code>), and its contents should not be edited manually. For more information about configuring network interfaces using the <span class="application"><strong>Network Administration Tool</strong></span>, refer to <a class="xref" href="ch-Network_Configuration.html" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/network-scripts/</code> </span></dt><dd><div class="para">
+ <a id="id568266" class="indexterm"></a>
+ This directory contains the following network-related configuration files:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Network configuration files for each configured network interface, such as <code class="filename">ifcfg-eth0</code> for the <code class="systemitem">eth0</code> Ethernet interface.
+ </div></li><li class="listitem"><div class="para">
+ Scripts used to bring network interfaces up and down, such as <code class="command">ifup</code> and <code class="command">ifdown</code>.
+ </div></li><li class="listitem"><div class="para">
+ Scripts used to bring ISDN interfaces up and down, such as <code class="command">ifup-isdn</code> and <code class="command">ifdown-isdn</code>.
+ </div></li><li class="listitem"><div class="para">
+ Various shared network function scripts which should not be edited directly.
+ </div></li></ul></div><div class="para">
+ For more information on the <code class="filename">/etc/sysconfig/network-scripts/</code> directory, refer to <a class="xref" href="ch-Network_Interfaces.html" title="Chapter 4. Network Interfaces">Chapter 4, <i>Network Interfaces</i></a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">/etc/sysconfig/rhn/</code> </span></dt><dd><div class="para">
+ <a id="id568394" class="indexterm"></a>
+ This directory contains the configuration files and GPG keys for Red Hat Network. No files in this directory should be edited by hand. For more information on Red Hat Network, refer to the Red Hat Network website online at <a href="https://rhn.redhat.com/">https://rhn.redhat.com/</a>.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-The_sysconfig_Directory.html"><strong>Prev</strong>Chapter 18. The sysconfig Directory</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-sysconfig-additional-resources.html"><strong>Next</strong>18.3. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-additional-resources.html
new file mode 100644
index 0000000..89d688a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-additional-resources.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.5. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Gathering_System_Information.html" title="Chapter 20. Gathering System Information" /><link rel="prev" href="s1-sysinfo-hardware.html" title="20.4. Hardware" /><link rel="next" href="ch-abrt.html" title="Chapter 21. ABRT" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-hardware.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="
ch-abrt.html"><strong>Next</strong></a></li></ul><div class="section" title="20.5. Additional Resources" id="s1-sysinfo-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-additional-resources">20.5. Additional Resources</h2></div></div></div><div class="para">
+ To learn more about gathering system information, refer to the following resources.
+ </div><div class="section" title="20.5.1. Installed Documentation" id="s2-sysinfo-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-sysinfo-installed-docs">20.5.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">ps --help</code> — Displays a list of options that can be used with <code class="command">ps</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">top</code> manual page — Execute <code class="command">man top</code> to learn more about <code class="command">top</code> and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">free</code> manual page — Execute <code class="command">man free</code> to learn more about <code class="command">free</code> and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">df</code> manual page — Execute <code class="command">man df</code> to learn more about the <code class="command">df</code> command and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">du</code> manual page — Execute <code class="command">man du</code> to learn more about the <code class="command">du</code> command and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">lspci</code> manual page — Execute <code class="command">man lspci</code> to learn more about the <code class="command">lspci</code> command and its many options.
+ </div></li><li class="listitem"><div class="para">
+ <a id="id490130" class="indexterm"></a>
+ <code class="filename">/proc/</code> directory — The contents of the <code class="filename">/proc/</code> directory can also be used to gather more detailed system information.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-hardware.html"><strong>Prev</strong>20.4. Hardware</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-abrt.html"><strong>Next</strong>Chapter 21. ABRT</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-filesystems.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-filesystems.html
new file mode 100644
index 0000000..f6bbbfb
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-filesystems.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.3. File Systems</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Gathering_System_Information.html" title="Chapter 20. Gathering System Information" /><link rel="prev" href="s1-sysinfo-memory-usage.html" title="20.2. Memory Usage" /><link rel="next" href="s1-sysinfo-hardware.html" title="20.4. Hardware" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-memory-usage.html"><strong>Prev</strong></a></li><li class="next"><a
accesskey="n" href="s1-sysinfo-hardware.html"><strong>Next</strong></a></li></ul><div class="section" title="20.3. File Systems" id="s1-sysinfo-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-filesystems">20.3. File Systems</h2></div></div></div><a id="id578437" class="indexterm"></a><a id="id578451" class="indexterm"></a><a id="id578460" class="indexterm"></a><div class="para">
+ The <code class="command">df</code> command reports the system's disk space usage. If you Execute the command <code class="command">df</code> at a shell prompt, the output looks similar to the following:
+ </div><pre class="screen">
+Filesystem 1K-blocks Used Available Use% Mounted on
+/dev/mapper/volgrp1-lvroot
+ 14127024 6868092 6541316 52% /
+tmpfs 2008828 592 2008236 1% /dev/shm
+/dev/sda1 495844 65047 405197 14% /boot
+/dev/mapper/luks-b20f8f7a-7f0f-4497-8de4-81bfa3e541cf
+ 122046576 12111420 103735552 11% /home
+</pre><div class="para">
+ By default, this utility shows the partition size in 1 kilobyte blocks and the amount of used and available disk space in kilobytes. To view the information in megabytes and gigabytes, use the command <code class="command">df -h</code>. The <code class="command">-h</code> argument stands for human-readable format. The output looks similar to the following:
+ </div><pre class="screen">
+Filesystem Size Used Avail Use% Mounted on
+/dev/mapper/volgrp1-lvroot
+ 14G 6.6G 6.3G 52% /
+tmpfs 2.0G 592K 2.0G 1% /dev/shm
+/dev/sda1 485M 64M 396M 14% /boot
+/dev/mapper/luks-b20f8f7a-7f0f-4497-8de4-81bfa3e541cf
+ 117G 12G 99G 11% /home
+</pre><a id="id578513" class="indexterm"></a><a id="id578534" class="indexterm"></a><div class="para">
+ In the list of mounted partitions, there is an entry for <code class="filename">/dev/shm</code>. This entry represents the system's virtual memory file system.
+ </div><a id="id578555" class="indexterm"></a><div class="para">
+ The <code class="command">du</code> command displays the estimated amount of space being used by files in a directory. If you execute <code class="command">du</code> at a shell prompt, the disk usage for each of the subdirectories is displayed in a list. The grand total for the current directory and subdirectories are also shown as the last line in the list. If you do not want to see the totals for all the subdirectories, use the command <code class="command">du -hs</code> to see only the grand total for the directory in human-readable format. Use the <code class="command">du --help</code> command to see more options.
+ </div><div class="para">
+ To view the system's partitions and disk space usage in a graphical format, use the <span class="guilabel"><strong>Gnome System Monitor</strong></span> by clicking on <span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> or executing the <code class="command">gnome-system-monitor</code> command at a shell prompt. Select the File Systems tab to view the system's partitions. The figure below illustrates the File Systems tab.
+ </div><div class="figure" title="Figure 20.3. GNOME System Monitor - File Systems tab" id="fig-sysinfo-filesystems"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/gnome-system-monitor-filesystems.png" align="middle" alt="GNOME System Monitor - File Systems tab" /><div class="longdesc"><div class="para">
+ File systems tab of the gnome-system-monitor
+ </div></div></div></div><h6>Figure 20.3. <span class="application">GNOME System Monitor - File Systems tab</span> </h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-memory-usage.html"><strong>Prev</strong>20.2. Memory Usage</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-sysinfo-hardware.html"><strong>Next</strong>20.4. Hardware</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-hardware.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-hardware.html
new file mode 100644
index 0000000..04ba986
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-hardware.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.4. Hardware</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Gathering_System_Information.html" title="Chapter 20. Gathering System Information" /><link rel="prev" href="s1-sysinfo-filesystems.html" title="20.3. File Systems" /><link rel="next" href="s1-sysinfo-additional-resources.html" title="20.5. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-filesystems.html"><strong>Prev</strong></a></
li><li class="next"><a accesskey="n" href="s1-sysinfo-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="20.4. Hardware" id="s1-sysinfo-hardware"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-hardware">20.4. Hardware</h2></div></div></div><a id="id635838" class="indexterm"></a><a id="id635852" class="indexterm"></a><a id="id635865" class="indexterm"></a><a id="id635879" class="indexterm"></a><div class="para">
+ If you are having trouble configuring your hardware or just want to know what hardware is in your system, you can use the <span class="application"><strong>Hardware Browser</strong></span> application to display the hardware that can be probed. To start the program from the desktop, select <span class="guimenu"><strong>System</strong></span> (the main menu on the panel) > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>Hardware</strong></span> or type <code class="command">hwbrowser</code> at a shell prompt. As shown in <a class="xref" href="s1-sysinfo-hardware.html#sysinfo-hwbrowser-fig" title="Figure 20.4. Hardware Browser">Figure 20.4, “ <span class="application">Hardware Browser</span> ”</a>, it displays your CD-ROM devices, diskette drives, hard drives and their partitions, network devices, pointing devices, system devices, and video cards. Click on the category name in the left menu, and the informat
ion is displayed.
+ </div><div class="figure" title="Figure 20.4. Hardware Browser" id="sysinfo-hwbrowser-fig"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/hwbrowser.png" align="middle" width="444" alt="Hardware Browser" /><div class="longdesc"><div class="para">
+ hwbrowser
+ </div></div></div></div><h6>Figure 20.4. <span class="application">Hardware Browser</span> </h6></div><br class="figure-break" /><a id="id758768" class="indexterm"></a><a id="id758782" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Device Manager</strong></span> application can also be used to display your system hardware. This application can be started by selecting <span class="guimenu"><strong>System</strong></span> (the main menu on the panel) > <span class="guimenuitem"><strong>Administration</strong></span> > <span class="guimenuitem"><strong>Hardware</strong></span> like the <span class="application"><strong>Hardware Browser</strong></span>. To start the application from a terminal, type <code class="command">hal-device-manager</code>. Depending on your installation preferences, the graphical menu above may start this application or the <span class="application"><strong>Hardware Browser</strong></span> when clicked. The figure below illustrates the <span class="application"><strong>Device Manager</strong></span> window.
+ </div><div class="figure" title="Figure 20.5. Device Manager" id="sysinfo-devicemngr-fig"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/devicemngr.png" align="middle" width="444" alt="Device Manager" /><div class="longdesc"><div class="para">
+ Device Manager
+ </div></div></div></div><h6>Figure 20.5. <span class="application">Device Manager</span> </h6></div><br class="figure-break" /><div class="para">
+ You can also use the <code class="command">lspci</code> command to list all PCI devices. Use the command <code class="command">lspci -v</code> for more verbose information or <code class="command">lspci -vv</code> for very verbose output.
+ </div><div class="para">
+ For example, <code class="command">lspci</code> can be used to determine the manufacturer, model, and memory size of a system's video card:
+ </div><pre class="screen">
+00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
+ Subsystem: Lenovo Device 20e4
+ Flags: bus master, fast devsel, latency 0
+ Memory at f4200000 (64-bit, non-prefetchable) [size=1M]
+ Capabilities: [d0] Power Management version 3</pre><div class="para">
+ The <code class="command">lspci</code> is also useful to determine the network card in your system if you do not know the manufacturer or model number.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-filesystems.html"><strong>Prev</strong>20.3. File Systems</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-sysinfo-additional-resources.html"><strong>Next</strong>20.5. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-memory-usage.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-memory-usage.html
new file mode 100644
index 0000000..d4cf2e6
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-sysinfo-memory-usage.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2. Memory Usage</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Gathering_System_Information.html" title="Chapter 20. Gathering System Information" /><link rel="prev" href="ch-Gathering_System_Information.html" title="Chapter 20. Gathering System Information" /><link rel="next" href="s1-sysinfo-filesystems.html" title="20.3. File Systems" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Gathering_System_Information.html"><st
rong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-sysinfo-filesystems.html"><strong>Next</strong></a></li></ul><div class="section" title="20.2. Memory Usage" id="s1-sysinfo-memory-usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-sysinfo-memory-usage">20.2. Memory Usage</h2></div></div></div><a id="id647162" class="indexterm"></a><a id="id590264" class="indexterm"></a><a id="id590273" class="indexterm"></a><a id="id590283" class="indexterm"></a><div class="para">
+ The <code class="command">free</code> command displays the total amount of physical memory and swap space for the system as well as the amount of memory that is used, free, shared, in kernel buffers, and cached.
+ </div><pre class="screen">
+ total used free shared buffers cached
+Mem: 4017660 1619044 2398616 0 59864 637968
+-/+ buffers/cache: 921212 3096448
+Swap: 3071996 0 3071996
+</pre><div class="para">
+ The command <code class="command">free -m</code> shows the same information in megabytes, which are easier to read.
+ </div><pre class="screen">
+ total used free shared buffers cached
+Mem: 3923 1569 2353 0 58 626
+-/+ buffers/cache: 884 3038
+Swap: 2999 0 2999
+</pre><div class="para">
+ If you prefer a graphical interface for <code class="command">free</code>, you can use the <span class="application"><strong>GNOME System Monitor</strong></span>. To start it from the desktop, select <span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> or execute <code class="command">gnome-system-monitor</code> at a shell prompt. Click on the <span class="guilabel"><strong>Resources</strong></span> tab.
+ </div><div class="figure" title="Figure 20.2. GNOME System Monitor - Resources tab" id="fig-sysinfo-memory"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/gnome-system-monitor-memory.png" align="middle" alt="GNOME System Monitor - Resources tab" /><div class="longdesc"><div class="para">
+ Resources tab of the gnome-system-monitor
+ </div></div></div></div><h6>Figure 20.2. <span class="application">GNOME System Monitor - Resources tab</span> </h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Gathering_System_Information.html"><strong>Prev</strong>Chapter 20. Gathering System Information</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-sysinfo-filesystems.html"><strong>Next</strong>20.3. File Systems</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-additional-resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-additional-resources.html
new file mode 100644
index 0000000..d9555fd
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-additional-resources.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.7. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="Users_and_Groups.html" title="Chapter 15. Users and Groups" /><link rel="prev" href="s1-users-groups-shadow-utilities.html" title="15.6. Shadow Passwords" /><link rel="next" href="ch-Automated_Tasks.html" title="Chapter 16. Automated Tasks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-shadow-utilities.html"><strong>Prev</strong></a></li><li class="
next"><a accesskey="n" href="ch-Automated_Tasks.html"><strong>Next</strong></a></li></ul><div class="section" title="15.7. Additional Resources" id="s1-users-groups-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-groups-additional-resources">15.7. Additional Resources</h2></div></div></div><a id="id471458" class="indexterm"></a><a id="id471472" class="indexterm"></a><div class="para">
+ For more information about users and groups, and tools to manage them, refer to the following resources.
+ </div><div class="section" title="15.7.1. Installed Documentation" id="s2-users-groups-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-users-groups-documentation">15.7.1. Installed Documentation</h3></div></div></div><a id="id471500" class="indexterm"></a><a id="id672600" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Related man pages — There are a number of man pages for the various applications and configuration files involved with managing users and groups. Some of the more important man pages have been listed here:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">User and Group Administrative Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man chage</code> — A command to modify password aging policies and account expiration.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man gpasswd</code> — A command to administer the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man groupadd</code> — A command to add groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man grpck</code> — A command to verify the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man groupdel</code> — A command to remove groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man groupmod</code> — A command to modify group membership.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man pwck</code> — A command to verify the <code class="filename">/etc/passwd</code> and <code class="filename">/etc/shadow</code> files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man pwconv</code> — A tool to convert standard passwords to shadow passwords.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man pwunconv</code> — A tool to convert shadow passwords to standard passwords.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man useradd</code> — A command to add users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man userdel</code> — A command to remove users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man usermod</code> — A command to modify users.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">man 5 group</code> — The file containing group information for the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man 5 passwd</code> — The file containing user information for the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">man 5 shadow</code> — The file containing passwords and account expiration information for the system.
+ </div></li></ul></div></dd></dl></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-shadow-utilities.html"><strong>Prev</strong>15.6. Shadow Passwords</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Automated_Tasks.html"><strong>Next</strong>Chapter 16. Automated Tasks</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-private-groups.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-private-groups.html
new file mode 100644
index 0000000..9df931e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-private-groups.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.5. User Private Groups</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="Users_and_Groups.html" title="Chapter 15. Users and Groups" /><link rel="prev" href="s1-users-groups-standard-groups.html" title="15.4. Standard Groups" /><link rel="next" href="s1-users-groups-shadow-utilities.html" title="15.6. Shadow Passwords" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-standard-groups.html"><strong>Prev</strong></a></li><li cl
ass="next"><a accesskey="n" href="s1-users-groups-shadow-utilities.html"><strong>Next</strong></a></li></ul><div class="section" title="15.5. User Private Groups" id="s1-users-groups-private-groups"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-groups-private-groups">15.5. User Private Groups</h2></div></div></div><a id="id484818" class="indexterm"></a><a id="id484833" class="indexterm"></a><a id="id484847" class="indexterm"></a><a id="id484870" class="indexterm"></a><div class="para">
+ Fedora uses a <em class="firstterm">user private group</em> (<em class="firstterm">UPG</em>) scheme, which makes UNIX groups easier to manage.
+ </div><div class="para">
+ A UPG is created whenever a new user is added to the system. A UPG has the same name as the user for which it was created and that user is the only member of the UPG.
+ </div><div class="para">
+ UPGs make it safe to set default permissions for a newly created file or directory, allowing both the user and <span class="emphasis"><em>the group of that user</em></span> to make modifications to the file or directory.
+ </div><div class="para">
+ The setting which determines what permissions are applied to a newly created file or directory is called a <em class="firstterm">umask</em> and is configured in the <code class="filename">/etc/bashrc</code> file. Traditionally on UNIX systems, the <code class="command">umask</code> is set to <code class="command">022</code>, which allows only the user who created the file or directory to make modifications. Under this scheme, all other users, <span class="emphasis"><em>including members of the creator's group</em></span>, are not allowed to make any modifications. However, under the UPG scheme, this "group protection" is not necessary since every user has their own private group.
+ </div><div class="section" title="15.5.1. Group Directories" id="s2-users-groups-rationale"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-users-groups-rationale">15.5.1. Group Directories</h3></div></div></div><a id="id484953" class="indexterm"></a><a id="id484968" class="indexterm"></a><div class="para">
+ System administrators usually like to create a group for each major project and assign people to the group when they need to access that project's files. With this traditional scheme, file managing is difficult; when someone creates a file, it is associated with the primary group to which they belong. When a single person works on multiple projects, it becomes difficult to associate the right files with the right group. However, with the UPG scheme, groups are automatically assigned to files created within a directory with the <em class="firstterm">setgid</em> bit set. The setgid bit makes managing group projects that share a common directory very simple because any files a user creates within the directory are owned by the group which owns the directory.
+ </div><div class="para">
+ For example, a group of people need to work on files in the <code class="filename">/usr/share/emacs/site-lisp/</code> directory. Some people are trusted to modify the directory, but not everyone. First create an <code class="computeroutput">emacs</code> group, as in the following command:
+ </div><pre class="screen">
+<code class="command">/usr/sbin/groupadd emacs</code>
+</pre><div class="para">
+ To associate the contents of the directory with the <code class="computeroutput">emacs</code> group, type:
+ </div><pre class="screen">
+<code class="command">chown -R root.emacs <code class="filename">/usr/share/emacs/site-lisp</code> </code>
+</pre><div class="para">
+ Now, it is possible to add the right users to the group with the <code class="command">gpasswd</code> command:
+ </div><pre class="screen">
+<code class="command">/usr/bin/gpasswd -a <em class="replaceable"><code><username></code></em> emacs</code>
+</pre><div class="para">
+ To allow users to create files within the directory, use the following command:
+ </div><pre class="screen">
+<code class="command">chmod 775 <code class="filename">/usr/share/emacs/site-lisp</code> </code>
+</pre><div class="para">
+ When a user creates a new file, it is assigned the group of the user's default private group. Next, set the setgid bit, which assigns everything created in the directory the same group permission as the directory itself (<code class="computeroutput">emacs</code>). Use the following command:
+ </div><pre class="screen">
+<code class="command">chmod 2775 /usr/share/emacs/site-lisp</code>
+</pre><div class="para">
+ At this point, because the default umask of each user is 002, all members of the <code class="computeroutput">emacs</code> group can create and edit files in the <code class="filename">/usr/share/emacs/site-lisp/</code> directory without the administrator having to change file permissions every time users write new files.
+ </div><div class="para">
+ The command <code class="command">ls -l /usr/share/emacs/</code> displays the current settings:
+ </div><pre class="screen">
+ <code class="code">total 4</code>
+<code class="code">drwxrwsr-x. 2 root emacs 4096 May 18 15:41 site-lisp</code>
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-standard-groups.html"><strong>Prev</strong>15.4. Standard Groups</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-users-groups-shadow-utilities.html"><strong>Next</strong>15.6. Shadow Passwords</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-shadow-utilities.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-shadow-utilities.html
new file mode 100644
index 0000000..b0113bf
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-shadow-utilities.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.6. Shadow Passwords</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="Users_and_Groups.html" title="Chapter 15. Users and Groups" /><link rel="prev" href="s1-users-groups-private-groups.html" title="15.5. User Private Groups" /><link rel="next" href="s1-users-groups-additional-resources.html" title="15.7. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-private-groups.html"><strong>Prev</strong></a><
/li><li class="next"><a accesskey="n" href="s1-users-groups-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="15.6. Shadow Passwords" id="s1-users-groups-shadow-utilities"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-groups-shadow-utilities">15.6. Shadow Passwords</h2></div></div></div><a id="id527317" class="indexterm"></a><a id="id527331" class="indexterm"></a><div class="para">
+ In multiuser environments it is very important to use <em class="firstterm">shadow passwords</em> (provided by the <code class="filename">shadow-utils</code> package). Doing so enhances the security of system authentication files. For this reason, the installation program enables shadow passwords by default.
+ </div><div class="para">
+ The following list shows the advantages shadow passwords have over the traditional way of storing passwords on UNIX-based systems:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Improves system security by moving encrypted password hashes from the world-readable <code class="filename">/etc/passwd</code> file to <code class="filename">/etc/shadow</code>, which is readable only by the root user.
+ </div></li><li class="listitem"><div class="para">
+ Stores information about password aging.
+ </div></li><li class="listitem"><div class="para">
+ Allows the <code class="filename">/etc/login.defs</code> file to enforce security policies.
+ </div></li></ul></div><div class="para">
+ Most utilities provided by the <code class="filename">shadow-utils</code> package work properly whether or not shadow passwords are enabled. However, since password aging information is stored exclusively in the <code class="filename">/etc/shadow</code> file, any commands which create or modify password aging information do not work.
+ </div><div class="para">
+ The following is a list of commands which do not work without first enabling shadow passwords:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">chage</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">gpasswd</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">/usr/sbin/usermod</code> <code class="option">-e</code> or <code class="option">-f</code> options
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">/usr/sbin/useradd</code> <code class="option">-e</code> or <code class="option">-f</code> options
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-private-groups.html"><strong>Prev</strong>15.5. User Private Groups</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-users-groups-additional-resources.html"><strong>Next</strong>15.7. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-standard-groups.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-standard-groups.html
new file mode 100644
index 0000000..12ffe6a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-standard-groups.html
@@ -0,0 +1,339 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.4. Standard Groups</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="Users_and_Groups.html" title="Chapter 15. Users and Groups" /><link rel="prev" href="s1-users-groups-standard-users.html" title="15.3. Standard Users" /><link rel="next" href="s1-users-groups-private-groups.html" title="15.5. User Private Groups" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-standard-users.html"><strong>Prev</strong></a></li><li clas
s="next"><a accesskey="n" href="s1-users-groups-private-groups.html"><strong>Next</strong></a></li></ul><div class="section" title="15.4. Standard Groups" id="s1-users-groups-standard-groups"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-groups-standard-groups">15.4. Standard Groups</h2></div></div></div><a id="id740721" class="indexterm"></a><div class="para">
+ <a class="xref" href="s1-users-groups-standard-groups.html#tb-users-groups-group-etc" title="Table 15.5. Standard Groups">Table 15.5, “Standard Groups”</a> lists the standard groups configured by an <span class="guilabel"><strong>Everything</strong></span> installation. Groups are stored in the <code class="filename">/etc/group</code> file.
+ </div><div class="table" title="Table 15.5. Standard Groups" id="tb-users-groups-group-etc"><h6>Table 15.5. Standard Groups</h6><div class="table-contents"><table summary="Standard Groups" border="1"><colgroup><col width="33%" /><col width="33%" /><col width="33%" /></colgroup><thead><tr><th>
+ Group
+ </th><th>
+ GID
+ </th><th>
+ Members
+ </th></tr></thead><tbody><tr><td>
+ root
+ </td><td>
+ 0
+ </td><td>
+ root
+ </td></tr><tr><td>
+ bin
+ </td><td>
+ 1
+ </td><td>
+ root, bin, daemon
+ </td></tr><tr><td>
+ daemon
+ </td><td>
+ 2
+ </td><td>
+ root, bin, daemon
+ </td></tr><tr><td>
+ sys
+ </td><td>
+ 3
+ </td><td>
+ root, bin, adm
+ </td></tr><tr><td>
+ adm
+ </td><td>
+ 4
+ </td><td>
+ root, adm, daemon
+ </td></tr><tr><td>
+ tty
+ </td><td>
+ 5
+ </td><td>
+ </td></tr><tr><td>
+ disk
+ </td><td>
+ 6
+ </td><td>
+ root
+ </td></tr><tr><td>
+ lp
+ </td><td>
+ 7
+ </td><td>
+ daemon, lp
+ </td></tr><tr><td>
+ mem
+ </td><td>
+ 8
+ </td><td>
+ </td></tr><tr><td>
+ kmem
+ </td><td>
+ 9
+ </td><td>
+ </td></tr><tr><td>
+ wheel
+ </td><td>
+ 10
+ </td><td>
+ root
+ </td></tr><tr><td>
+ mail
+ </td><td>
+ 12
+ </td><td>
+ mail, postfix
+ </td></tr><tr><td>
+ uucp
+ </td><td>
+ 14
+ </td><td>
+ uucp
+ </td></tr><tr><td>
+ man
+ </td><td>
+ 15
+ </td><td>
+ </td></tr><tr><td>
+ games
+ </td><td>
+ 20
+ </td><td>
+ </td></tr><tr><td>
+ gopher
+ </td><td>
+ 30
+ </td><td>
+ </td></tr><tr><td>
+ video
+ </td><td>
+ 39
+ </td><td>
+ </td></tr><tr><td>
+ dip
+ </td><td>
+ 40
+ </td><td>
+ </td></tr><tr><td>
+ ftp
+ </td><td>
+ 50
+ </td><td>
+ </td></tr><tr><td>
+ lock
+ </td><td>
+ 54
+ </td><td>
+ </td></tr><tr><td>
+ audio
+ </td><td>
+ 63
+ </td><td>
+ </td></tr><tr><td>
+ nobody
+ </td><td>
+ 99
+ </td><td>
+ </td></tr><tr><td>
+ users
+ </td><td>
+ 100
+ </td><td>
+ </td></tr><tr><td>
+ dbus
+ </td><td>
+ 81
+ </td><td>
+ </td></tr><tr><td>
+ usbmuxd
+ </td><td>
+ 113
+ </td><td>
+ </td></tr><tr><td>
+ utmp
+ </td><td>
+ 22
+ </td><td>
+ </td></tr><tr><td>
+ utempter
+ </td><td>
+ 35
+ </td><td>
+ </td></tr><tr><td>
+ avahi-autoipd
+ </td><td>
+ 170
+ </td><td>
+ </td></tr><tr><td>
+ floppy
+ </td><td>
+ 19
+ </td><td>
+ </td></tr><tr><td>
+ vcsa
+ </td><td>
+ 69
+ </td><td>
+ </td></tr><tr><td>
+ rpc
+ </td><td>
+ 32
+ </td><td>
+ </td></tr><tr><td>
+ rtkit
+ </td><td>
+ 499
+ </td><td>
+ </td></tr><tr><td>
+ abrt
+ </td><td>
+ 498
+ </td><td>
+ </td></tr><tr><td>
+ nscd
+ </td><td>
+ 28
+ </td><td>
+ </td></tr><tr><td>
+ desktop_admin_r
+ </td><td>
+ 497
+ </td><td>
+ </td></tr><tr><td>
+ desktop_user_r
+ </td><td>
+ 496
+ </td><td>
+ </td></tr><tr><td>
+ cdrom
+ </td><td>
+ 11
+ </td><td>
+ </td></tr><tr><td>
+ tape
+ </td><td>
+ 33
+ </td><td>
+ </td></tr><tr><td>
+ dialout
+ </td><td>
+ 18
+ </td><td>
+ </td></tr><tr><td>
+ haldaemon
+ </td><td>
+ 68
+ </td><td>
+ haldaemon
+ </td></tr><tr><td>
+ apache
+ </td><td>
+ 48
+ </td><td>
+ </td></tr><tr><td>
+ ldap
+ </td><td>
+ 55
+ </td><td>
+ </td></tr><tr><td>
+ saslauth
+ </td><td>
+ 495
+ </td><td>
+ </td></tr><tr><td>
+ postdrop
+ </td><td>
+ 90
+ </td><td>
+ </td></tr><tr><td>
+ postfix
+ </td><td>
+ 89
+ </td><td>
+ </td></tr><tr><td>
+ avahi
+ </td><td>
+ 70
+ </td><td>
+ </td></tr><tr><td>
+ ntp
+ </td><td>
+ 38
+ </td><td>
+ </td></tr><tr><td>
+ rpcuser
+ </td><td>
+ 29
+ </td><td>
+ </td></tr><tr><td>
+ nfsnobody
+ </td><td>
+ 4294967294
+ </td><td>
+ </td></tr><tr><td>
+ pulse
+ </td><td>
+ 494
+ </td><td>
+ </td></tr><tr><td>
+ pulse-access
+ </td><td>
+ 493
+ </td><td>
+ </td></tr><tr><td>
+ fuse
+ </td><td>
+ 492
+ </td><td>
+ </td></tr><tr><td>
+ gdm
+ </td><td>
+ 42
+ </td><td>
+ </td></tr><tr><td>
+ stapdev
+ </td><td>
+ 491
+ </td><td>
+ </td></tr><tr><td>
+ stapusr
+ </td><td>
+ 490
+ </td><td>
+ </td></tr><tr><td>
+ sshd
+ </td><td>
+ 74
+ </td><td>
+ </td></tr><tr><td>
+ tcpdump
+ </td><td>
+ 72
+ </td><td>
+ </td></tr><tr><td>
+ slocate
+ </td><td>
+ 21
+ </td><td>
+ </td></tr><tr><td>
+ dovecot
+ </td><td>
+ 97
+ </td><td>
+ </td></tr><tr><td>
+ dovenull
+ </td><td>
+ 489
+ </td><td>
+ </td></tr><tr><td>
+ mailnull
+ </td><td>
+ 47
+ </td><td>
+ </td></tr><tr><td>
+ smmsp
+ </td><td>
+ 51
+ </td><td>
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-standard-users.html"><strong>Prev</strong>15.3. Standard Users</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-users-groups-private-groups.html"><strong>Next</strong>15.5. User Private Groups</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-standard-users.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-standard-users.html
new file mode 100644
index 0000000..f3aa8a9
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-groups-standard-users.html
@@ -0,0 +1,1502 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.3. Standard Users</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="Users_and_Groups.html" title="Chapter 15. Users and Groups" /><link rel="prev" href="s2-redhat-config-users-process.html" title="15.2.2. Explaining the Process" /><link rel="next" href="s1-users-groups-standard-groups.html" title="15.4. Standard Groups" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-redhat-config-users-process.html"><strong>Prev</strong></a></li><
li class="next"><a accesskey="n" href="s1-users-groups-standard-groups.html"><strong>Next</strong></a></li></ul><div class="section" title="15.3. Standard Users" id="s1-users-groups-standard-users"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-groups-standard-users">15.3. Standard Users</h2></div></div></div><a id="id678580" class="indexterm"></a><a id="id678594" class="indexterm"></a><div class="para">
+ <a class="xref" href="s1-users-groups-standard-users.html#tb-users-groups-group-use" title="Table 15.4. Standard Users">Table 15.4, “Standard Users”</a> lists the standard users configured in the <code class="filename">/etc/passwd</code> file by an <span class="guilabel"><strong>Everything</strong></span> installation. The groupid (GID) in this table is the <span class="emphasis"><em>primary group</em></span> for the user. See <a class="xref" href="s1-users-groups-standard-groups.html" title="15.4. Standard Groups">Section 15.4, “Standard Groups”</a> for a listing of standard groups.
+ </div><div class="table" title="Table 15.4. Standard Users" id="tb-users-groups-group-use"><h6>Table 15.4. Standard Users</h6><div class="table-contents"><table summary="Standard Users" border="1"><colgroup><col align="left" width="17%" /><col align="left" width="17%" /><col align="left" width="17%" /><col align="left" width="17%" /><col align="left" width="17%" /><col align="left" width="17%" /></colgroup><thead><tr><th align="left">
+ User
+ </th><th align="left">
+ UID
+ </th><th align="left">
+ GID
+ </th><th align="left">
+ Home Directory
+ </th><th align="left">
+ Shell
+ </th><th align="left">
+ Packages
+ </th></tr></thead><tbody><tr><td align="left">
+ root
+ </td><td align="left">
+ 0
+ </td><td align="left">
+ 0
+ </td><td align="left">
+ /root
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ bin
+ </td><td align="left">
+ 1
+ </td><td align="left">
+ 1
+ </td><td align="left">
+ /bin
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ daemon
+ </td><td align="left">
+ 2
+ </td><td align="left">
+ 2
+ </td><td align="left">
+ /sbin
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ sys
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 3
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ adm
+ </td><td align="left">
+ 3
+ </td><td align="left">
+ 4
+ </td><td align="left">
+ /var/adm
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ tty
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 5
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ disk
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 6
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ lp
+ </td><td align="left">
+ 4
+ </td><td align="left">
+ 7
+ </td><td align="left">
+ /var/spool/lpd
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ mem
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 8
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ kmem
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 9
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ wheel
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 10
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ cdrom
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 11
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">udev,MAKEDEV</code>
+ </td></tr><tr><td align="left">
+ sync
+ </td><td align="left">
+ 5
+ </td><td align="left">
+ (0)
+ </td><td align="left">
+ /sbin
+ </td><td align="left">
+ <code class="filename">/bin/sync</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ shutdown
+ </td><td align="left">
+ 6
+ </td><td align="left">
+ (0)
+ </td><td align="left">
+ /sbin
+ </td><td align="left">
+ <code class="filename">/sbin/shutdown</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ halt
+ </td><td align="left">
+ 7
+ </td><td align="left">
+ (0)
+ </td><td align="left">
+ /sbin
+ </td><td align="left">
+ <code class="filename">/sbin/halt</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ mail
+ </td><td align="left">
+ 8
+ </td><td align="left">
+ 12
+ </td><td align="left">
+ /var/spool/mail
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ news
+ </td><td align="left">
+ 9
+ </td><td align="left">
+ 13
+ </td><td align="left">
+ /var/spool/news
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ uucp
+ </td><td align="left">
+ 10
+ </td><td align="left">
+ 14
+ </td><td align="left">
+ /var/spool/uucp
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ operator
+ </td><td align="left">
+ 11
+ </td><td align="left">
+ (0)
+ </td><td align="left">
+ /root
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ games
+ </td><td align="left">
+ 12
+ </td><td align="left">
+ (100)
+ </td><td align="left">
+ /usr/games
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ gopher
+ </td><td align="left">
+ 13
+ </td><td align="left">
+ 30
+ </td><td align="left">
+ /usr/lib/gopher-data
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ ftp
+ </td><td align="left">
+ 14
+ </td><td align="left">
+ 50
+ </td><td align="left">
+ /var/ftp
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ man
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 15
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ oprofile
+ </td><td align="left">
+ 16
+ </td><td align="left">
+ 16
+ </td><td align="left">
+ /home/oprofile
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">oprofile</code>
+ </td></tr><tr><td align="left">
+ pkiuser
+ </td><td align="left">
+ 17
+ </td><td align="left">
+ 17
+ </td><td align="left">
+ /usr/share/pki
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">pki-ca,rhpki-ca</code>
+ </td></tr><tr><td align="left">
+ dialout
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 18
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">udev,MAKEDEV</code>
+ </td></tr><tr><td align="left">
+ floppy
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 19
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">dev,MAKEDEV</code>
+ </td></tr><tr><td align="left">
+ games
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 20
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ slocate
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 21
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">slocate</code>
+ </td></tr><tr><td align="left">
+ utmp
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 22
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">initscripts,libutempter</code>
+ </td></tr><tr><td align="left">
+ squid
+ </td><td align="left">
+ 23
+ </td><td align="left">
+ 23
+ </td><td align="left">
+ /var/spool/squid
+ </td><td align="left">
+ <code class="filename">/dev/null</code>
+ </td><td align="left">
+ <code class="command">squid</code>
+ </td></tr><tr><td align="left">
+ pvm
+ </td><td align="left">
+ 24
+ </td><td align="left">
+ 24
+ </td><td align="left">
+ /usr/share/pvm3
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">pvm</code>
+ </td></tr><tr><td align="left">
+ named
+ </td><td align="left">
+ 25
+ </td><td align="left">
+ 25
+ </td><td align="left">
+ /var/named
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">bind</code>
+ </td></tr><tr><td align="left">
+ postgres
+ </td><td align="left">
+ 26
+ </td><td align="left">
+ 26
+ </td><td align="left">
+ /var/lib/pgsql
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">postgresql-server</code>
+ </td></tr><tr><td align="left">
+ mysql
+ </td><td align="left">
+ 27
+ </td><td align="left">
+ 27
+ </td><td align="left">
+ /var/lib/mysql
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">mysql</code>
+ </td></tr><tr><td align="left">
+ nscd
+ </td><td align="left">
+ 28
+ </td><td align="left">
+ 28
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">nscd</code>
+ </td></tr><tr><td align="left">
+ rpcuser
+ </td><td align="left">
+ 29
+ </td><td align="left">
+ 29
+ </td><td align="left">
+ /var/lib/nfs
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">nfs-utils</code>
+ </td></tr><tr><td align="left">
+ console
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 31
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">dev</code>
+ </td></tr><tr><td align="left">
+ rpc
+ </td><td align="left">
+ 32
+ </td><td align="left">
+ 32
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">portmap</code>
+ </td></tr><tr><td align="left">
+ amanda
+ </td><td align="left">
+ 33
+ </td><td align="left">
+ (6)
+ </td><td align="left">
+ /var/lib/amanda
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">amanda</code>
+ </td></tr><tr><td align="left">
+ tape
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 33
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">udev,MAKEDEV</code>
+ </td></tr><tr><td align="left">
+ netdump
+ </td><td align="left">
+ 34
+ </td><td align="left">
+ 34
+ </td><td align="left">
+ /var/crash
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">netdump-client, netdump-server</code>
+ </td></tr><tr><td align="left">
+ utempter
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 35
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">libutempter</code>
+ </td></tr><tr><td align="left">
+ vdsm
+ </td><td align="left">
+ 36
+ </td><td align="left">
+ -
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">kvm, vdsm</code>
+ </td></tr><tr><td align="left">
+ kvm
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 36
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">kvm, vdsm, libvirt</code>
+ </td></tr><tr><td align="left">
+ rpm
+ </td><td align="left">
+ 37
+ </td><td align="left">
+ 37
+ </td><td align="left">
+ /var/lib/rpm
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">rpm</code>
+ </td></tr><tr><td align="left">
+ ntp
+ </td><td align="left">
+ 38
+ </td><td align="left">
+ 38
+ </td><td align="left">
+ /etc/ntp
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">ntp</code>
+ </td></tr><tr><td align="left">
+ video
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 39
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ dip
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 40
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ mailman
+ </td><td align="left">
+ 41
+ </td><td align="left">
+ 41
+ </td><td align="left">
+ /var/mailman
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">mailman</code>
+ </td></tr><tr><td align="left">
+ gdm
+ </td><td align="left">
+ 42
+ </td><td align="left">
+ 42
+ </td><td align="left">
+ /var/gdm
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">gdm</code>
+ </td></tr><tr><td align="left">
+ xfs
+ </td><td align="left">
+ 43
+ </td><td align="left">
+ 43
+ </td><td align="left">
+ /etc/X11/fs
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">XFree86-xfs</code>
+ </td></tr><tr><td align="left">
+ pppusers
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 44
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">linuxconf</code>
+ </td></tr><tr><td align="left">
+ popusers
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 45
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">linuxconf</code>
+ </td></tr><tr><td align="left">
+ slipusers
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 46
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">linuxconf</code>
+ </td></tr><tr><td align="left">
+ mailnull
+ </td><td align="left">
+ 47
+ </td><td align="left">
+ 47
+ </td><td align="left">
+ /var/spool/mqueue
+ </td><td align="left">
+ <code class="filename">/dev/null</code>
+ </td><td align="left">
+ <code class="command">sendmail</code>
+ </td></tr><tr><td align="left">
+ apache
+ </td><td align="left">
+ 48
+ </td><td align="left">
+ 48
+ </td><td align="left">
+ /var/www
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">apache</code>
+ </td></tr><tr><td align="left">
+ wnn
+ </td><td align="left">
+ 49
+ </td><td align="left">
+ 49
+ </td><td align="left">
+ /home/wnn
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">FreeWnn</code>
+ </td></tr><tr><td align="left">
+ smmsp
+ </td><td align="left">
+ 51
+ </td><td align="left">
+ 51
+ </td><td align="left">
+ /var/spool/mqueue
+ </td><td align="left">
+ <code class="filename">/dev/null</code>
+ </td><td align="left">
+ <code class="command">sendmail</code>
+ </td></tr><tr><td align="left">
+ puppet
+ </td><td align="left">
+ 52
+ </td><td align="left">
+ 52
+ </td><td align="left">
+ /var/lib/puppet
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">puppet</code>
+ </td></tr><tr><td align="left">
+ tomcat
+ </td><td align="left">
+ 53
+ </td><td align="left">
+ 53
+ </td><td align="left">
+ /var/lib/tomcat
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">tomcat</code>
+ </td></tr><tr><td align="left">
+ lock
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 54
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">lockdev</code>
+ </td></tr><tr><td align="left">
+ ldap
+ </td><td align="left">
+ 55
+ </td><td align="left">
+ 55
+ </td><td align="left">
+ /var/lib/ldap
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">openldap-servers</code>
+ </td></tr><tr><td align="left">
+ frontpage
+ </td><td align="left">
+ 56
+ </td><td align="left">
+ 56
+ </td><td align="left">
+ /var/www
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">mod_frontpage</code>
+ </td></tr><tr><td align="left">
+ nut
+ </td><td align="left">
+ 57
+ </td><td align="left">
+ 57
+ </td><td align="left">
+ /var/lib/ups
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">nut</code>
+ </td></tr><tr><td align="left">
+ beagleindex
+ </td><td align="left">
+ 58
+ </td><td align="left">
+ 58
+ </td><td align="left">
+ /var/cache/beagle
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">beagle</code>
+ </td></tr><tr><td align="left">
+ tss
+ </td><td align="left">
+ 59
+ </td><td align="left">
+ 59
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">trousers</code>
+ </td></tr><tr><td align="left">
+ piranha
+ </td><td align="left">
+ 60
+ </td><td align="left">
+ 60
+ </td><td align="left">
+ /etc/sysconfig/ha
+ </td><td align="left">
+ <code class="filename">/dev/null</code>
+ </td><td align="left">
+ <code class="command">piranha</code>
+ </td></tr><tr><td align="left">
+ prelude-manager
+ </td><td align="left">
+ 61
+ </td><td align="left">
+ 61
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">prelude-manager</code>
+ </td></tr><tr><td align="left">
+ snortd
+ </td><td align="left">
+ 62
+ </td><td align="left">
+ 62
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">snortd</code>
+ </td></tr><tr><td align="left">
+ audio
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 63
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ condor
+ </td><td align="left">
+ 64
+ </td><td align="left">
+ 64
+ </td><td align="left">
+ /var/lib/condor
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">condord</code>
+ </td></tr><tr><td align="left">
+ nslcd
+ </td><td align="left">
+ 65
+ </td><td align="left">
+ (55)
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">nslcd</code>
+ </td></tr><tr><td align="left">
+ wine
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 66
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">wine</code>
+ </td></tr><tr><td align="left">
+ pegasus
+ </td><td align="left">
+ 66
+ </td><td align="left">
+ 65
+ </td><td align="left">
+ /var/lib/Pegasus
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">tog-pegasus</code>
+ </td></tr><tr><td align="left">
+ webalizer
+ </td><td align="left">
+ 67
+ </td><td align="left">
+ 67
+ </td><td align="left">
+ /var/www/html/usage
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">webalizer</code>
+ </td></tr><tr><td align="left">
+ haldaemon
+ </td><td align="left">
+ 68
+ </td><td align="left">
+ 68
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">hal</code>
+ </td></tr><tr><td align="left">
+ vcsa
+ </td><td align="left">
+ 69
+ </td><td align="left">
+ 69
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">dev,MAKEDEV</code>
+ </td></tr><tr><td align="left">
+ avahi
+ </td><td align="left">
+ 70
+ </td><td align="left">
+ 70
+ </td><td align="left">
+ /var/run/avahi-daemon
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">avahi</code>
+ </td></tr><tr><td align="left">
+ realtime
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 71
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">-</code>
+ </td></tr><tr><td align="left">
+ tcpdump
+ </td><td align="left">
+ 72
+ </td><td align="left">
+ 72
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">tcpdump</code>
+ </td></tr><tr><td align="left">
+ privoxy
+ </td><td align="left">
+ 73
+ </td><td align="left">
+ 73
+ </td><td align="left">
+ /etc/privoxy
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">privoxy</code>
+ </td></tr><tr><td align="left">
+ sshd
+ </td><td align="left">
+ 74
+ </td><td align="left">
+ 74
+ </td><td align="left">
+ /var/empty/sshd
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">openssh-server</code>
+ </td></tr><tr><td align="left">
+ radvd
+ </td><td align="left">
+ 75
+ </td><td align="left">
+ 75
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">radvd</code>
+ </td></tr><tr><td align="left">
+ cyrus
+ </td><td align="left">
+ 76
+ </td><td align="left">
+ (12)
+ </td><td align="left">
+ /var/imap
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">cyrus-imapd</code>
+ </td></tr><tr><td align="left">
+ saslauth
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 76
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">cyrus-imapd</code>
+ </td></tr><tr><td align="left">
+ arpwatch
+ </td><td align="left">
+ 77
+ </td><td align="left">
+ 77
+ </td><td align="left">
+ /var/lib/arpwatch
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">arpwatch</code>
+ </td></tr><tr><td align="left">
+ fax
+ </td><td align="left">
+ 78
+ </td><td align="left">
+ 78
+ </td><td align="left">
+ /var/spool/fax
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">mgetty</code>
+ </td></tr><tr><td align="left">
+ nocpulse
+ </td><td align="left">
+ 79
+ </td><td align="left">
+ 79
+ </td><td align="left">
+ /etc/sysconfig/nocpulse
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">nocpulse</code>
+ </td></tr><tr><td align="left">
+ desktop
+ </td><td align="left">
+ 80
+ </td><td align="left">
+ 80
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">desktop-file-utils</code>
+ </td></tr><tr><td align="left">
+ dbus
+ </td><td align="left">
+ 81
+ </td><td align="left">
+ 81
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">dbus</code>
+ </td></tr><tr><td align="left">
+ jonas
+ </td><td align="left">
+ 82
+ </td><td align="left">
+ 82
+ </td><td align="left">
+ /var/lib/jonas
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">jonas</code>
+ </td></tr><tr><td align="left">
+ clamav
+ </td><td align="left">
+ 83
+ </td><td align="left">
+ 83
+ </td><td align="left">
+ /tmp
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">clamav</code>
+ </td></tr><tr><td align="left">
+ screen
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 84
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">screen</code>
+ </td></tr><tr><td align="left">
+ quaggavt
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 85
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">quagga</code>
+ </td></tr><tr><td align="left">
+ sabayon
+ </td><td align="left">
+ 86
+ </td><td align="left">
+ 86
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">sabayon</code>
+ </td></tr><tr><td align="left">
+ polkituser
+ </td><td align="left">
+ 87
+ </td><td align="left">
+ 87
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">PolicyKit</code>
+ </td></tr><tr><td align="left">
+ wbpriv
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 88
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">samba-common</code>
+ </td></tr><tr><td align="left">
+ postfix
+ </td><td align="left">
+ 89
+ </td><td align="left">
+ 89
+ </td><td align="left">
+ /var/spool/postfix
+ </td><td align="left">
+ <code class="filename">/bin/true</code>
+ </td><td align="left">
+ <code class="command">postfix</code>
+ </td></tr><tr><td align="left">
+ postdrop
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 90
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">postfix</code>
+ </td></tr><tr><td align="left">
+ majordomo
+ </td><td align="left">
+ 91
+ </td><td align="left">
+ 91
+ </td><td align="left">
+ /usr/lib/majordomo
+ </td><td align="left">
+ <code class="filename">/bin/bash</code>
+ </td><td align="left">
+ <code class="command">majordomo</code>
+ </td></tr><tr><td align="left">
+ quagga
+ </td><td align="left">
+ 92
+ </td><td align="left">
+ 92
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">quagga</code>
+ </td></tr><tr><td align="left">
+ exim
+ </td><td align="left">
+ 93
+ </td><td align="left">
+ 93
+ </td><td align="left">
+ /var/spool/exim
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">exim</code>
+ </td></tr><tr><td align="left">
+ distcache
+ </td><td align="left">
+ 94
+ </td><td align="left">
+ 94
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">distcache</code>
+ </td></tr><tr><td align="left">
+ radiusd
+ </td><td align="left">
+ 95
+ </td><td align="left">
+ 95
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/bin/false</code>
+ </td><td align="left">
+ <code class="command">freeradius</code>
+ </td></tr><tr><td align="left">
+ hsqldb
+ </td><td align="left">
+ 96
+ </td><td align="left">
+ 96
+ </td><td align="left">
+ /var/lib/hsqldb
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">hsqldb</code>
+ </td></tr><tr><td align="left">
+ dovecot
+ </td><td align="left">
+ 97
+ </td><td align="left">
+ 97
+ </td><td align="left">
+ /usr/libexec/dovecot
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">dovecot</code>
+ </td></tr><tr><td align="left">
+ ident
+ </td><td align="left">
+ 98
+ </td><td align="left">
+ 98
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">ident</code>
+ </td></tr><tr><td align="left">
+ nobody
+ </td><td align="left">
+ 99
+ </td><td align="left">
+ 99
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ users
+ </td><td align="left">
+ -
+ </td><td align="left">
+ 100
+ </td><td align="left">
+ -
+ </td><td align="left">
+ <code class="filename">-</code>
+ </td><td align="left">
+ <code class="command">setup</code>
+ </td></tr><tr><td align="left">
+ qemu
+ </td><td align="left">
+ 107
+ </td><td align="left">
+ 107
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">libvirt</code>
+ </td></tr><tr><td align="left">
+ ovirt
+ </td><td align="left">
+ 108
+ </td><td align="left">
+ 108
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">libvirt</code>
+ </td></tr><tr><td align="left">
+ saned
+ </td><td align="left">
+ 111
+ </td><td align="left">
+ 111
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">sane-backends</code>
+ </td></tr><tr><td align="left">
+ vhostmd
+ </td><td align="left">
+ 112
+ </td><td align="left">
+ 112
+ </td><td align="left">
+ /usr/share/vhostmd
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">vhostmd</code>
+ </td></tr><tr><td align="left">
+ usbmuxd
+ </td><td align="left">
+ 113
+ </td><td align="left">
+ 113
+ </td><td align="left">
+ /
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">usbmuxd</code>
+ </td></tr><tr><td align="left">
+ bacula
+ </td><td align="left">
+ 133
+ </td><td align="left">
+ 133
+ </td><td align="left">
+ /var/spool/bacula
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">bacula</code>
+ </td></tr><tr><td align="left">
+ ricci
+ </td><td align="left">
+ 140
+ </td><td align="left">
+ 140
+ </td><td align="left">
+ /var/lib/ricci
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">ricci</code>
+ </td></tr><tr><td align="left">
+ luci
+ </td><td align="left">
+ 141
+ </td><td align="left">
+ 141
+ </td><td align="left">
+ /var/lib/luci
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">luci</code>
+ </td></tr><tr><td align="left">
+ stap-server
+ </td><td align="left">
+ 155
+ </td><td align="left">
+ 155
+ </td><td align="left">
+ /var/lib/stap-server
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">systemtap</code>
+ </td></tr><tr><td align="left">
+ avahi-autoipd
+ </td><td align="left">
+ 170
+ </td><td align="left">
+ 170
+ </td><td align="left">
+ /var/lib/avahi-autoipd
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">avahi</code>
+ </td></tr><tr><td align="left">
+ pulse
+ </td><td align="left">
+ 171
+ </td><td align="left">
+ 171
+ </td><td align="left">
+ /var/run/pulse
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">pulseaudio</code>
+ </td></tr><tr><td align="left">
+ rtkit
+ </td><td align="left">
+ 172
+ </td><td align="left">
+ 172
+ </td><td align="left">
+ /proc
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">rtkit</code>
+ </td></tr><tr><td align="left">
+ nfsnobody
+ </td><td align="left">
+ 65534<sup>[<a id="id740674" href="#ftn.id740674" class="footnote">a</a>]</sup>
+ </td><td align="left">
+ 65534
+ </td><td align="left">
+ /var/lib/nfs
+ </td><td align="left">
+ <code class="filename">/sbin/nologin</code>
+ </td><td align="left">
+ <code class="command">nfs-utils</code>
+ </td></tr></tbody><tbody class="footnotes"><tr><td colspan="6"><div class="footnote"><p><sup>[<a id="ftn.id740674" href="#id740674" class="para">a</a>] </sup>
+ nfsnobdy is 4294967294 on 64-bit platforms
+ </p></div></td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-redhat-config-users-process.html"><strong>Prev</strong>15.2.2. Explaining the Process</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-users-groups-standard-groups.html"><strong>Next</strong>15.4. Standard Groups</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-tools.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-tools.html
new file mode 100644
index 0000000..6bb0f17
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s1-users-tools.html
@@ -0,0 +1,206 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2. User and Group Management Tools</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="Users_and_Groups.html" title="Chapter 15. Users and Groups" /><link rel="prev" href="Users_and_Groups.html" title="Chapter 15. Users and Groups" /><link rel="next" href="s2-redhat-config-users-process.html" title="15.2.2. Explaining the Process" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="Users_and_Groups.html"><strong>Prev</strong></a></li><li class="next"><a ac
cesskey="n" href="s2-redhat-config-users-process.html"><strong>Next</strong></a></li></ul><div class="section" title="15.2. User and Group Management Tools" id="s1-users-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="s1-users-tools">15.2. User and Group Management Tools</h2></div></div></div><a id="id492651" class="indexterm"></a><a id="id492673" class="indexterm"></a><a id="id672993" class="indexterm"></a><a id="id673015" class="indexterm"></a><div class="para">
+ Managing users and groups can be tiresome; this is why Fedora provides tools and conventions to make this task easier to manage.
+ </div><div class="para">
+ The easiest way to manage users and groups is through the graphical application, <span class="application"><strong>User Manager</strong></span> (<code class="command">system-config-users</code>). For more information on <span class="application"><strong>User Manager</strong></span>, refer to <a class="xref" href="Users_and_Groups.html#s1-users-configui" title="15.1. User and Group Configuration">Section 15.1, “User and Group Configuration”</a>.
+ </div><div class="para">
+ The following command line tools can also be used to manage users and groups:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">useradd</code>, <code class="command">usermod</code>, and <code class="command">userdel</code> — Industry-standard methods of adding, deleting and modifying user accounts
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">groupadd</code>, <code class="command">groupmod</code>, and <code class="command">groupdel</code> — Industry-standard methods of adding, deleting, and modifying user groups
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">gpasswd</code> — Industry-standard method of administering the <code class="filename">/etc/group</code> file
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pwck</code>, <code class="command">grpck</code> — Tools used for the verification of the password, group, and associated shadow files
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">pwconv</code>, <code class="command">pwunconv</code> — Tools used for the conversion of passwords to shadow passwords and back to standard passwords
+ </div></li></ul></div><div class="section" title="15.2.1. Command Line Configuration" id="s2-users-cmd-line"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-users-cmd-line">15.2.1. Command Line Configuration</h3></div></div></div><a id="id459763" class="indexterm"></a><a id="id459778" class="indexterm"></a><a id="id459796" class="indexterm"></a><div class="para">
+ If you prefer command line tools or do not have the X Window System installed, use following to configure users and groups.
+ </div><h4 id="id459815">Adding a User</h4><div class="para">
+ To add a user to the system:
+ </div><a id="id459823" class="indexterm"></a><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Issue the <code class="command">useradd</code> command to create a locked user account:
+ </div><pre class="screen">
+<code class="command">useradd <em class="replaceable"><code><username></code></em> </code>
+</pre></li><li class="listitem"><div class="para">
+ <a id="id459882" class="indexterm"></a>
+ Unlock the account by issuing the <code class="command">passwd</code> command to assign a password and set password aging guidelines:
+ </div><pre class="screen">
+<code class="command">passwd <em class="replaceable"><code><username></code></em> </code>
+</pre></li></ol></div><div class="para">
+ Command line options for <code class="command">useradd</code> are detailed in <a class="xref" href="s1-users-tools.html#table-useradd-options" title="Table 15.1. useradd Command Line Options">Table 15.1, “ <code class="command">useradd</code> Command Line Options”</a>.
+ </div><div class="table" title="Table 15.1. useradd Command Line Options" id="table-useradd-options"><h6>Table 15.1. <code class="command">useradd</code> Command Line Options</h6><div class="table-contents"><table summary=" useradd Command Line Options" border="1"><colgroup><col width="29%" /><col width="71%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-c</code> '<em class="replaceable"><code><comment></code></em>'
+ </td><td>
+ <em class="replaceable"><code><comment></code></em> can be replaced with any string. This option is generally used to specify the full name of a user.
+ </td></tr><tr><td>
+ <code class="option">-d</code> <em class="replaceable"><code><home-dir></code></em>
+ </td><td>
+ Home directory to be used instead of default <code class="filename">/home/<em class="replaceable"><code><username></code></em>/</code>
+ </td></tr><tr><td>
+ <code class="option">-e</code> <em class="replaceable"><code><date></code></em>
+ </td><td>
+ Date for the account to be disabled in the format YYYY-MM-DD
+ </td></tr><tr><td>
+ <code class="option">-f</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Number of days after the password expires until the account is disabled. If <strong class="userinput"><code>0</code></strong> is specified, the account is disabled immediately after the password expires. If <strong class="userinput"><code>-1</code></strong> is specified, the account is not be disabled after the password expires.
+ </td></tr><tr><td>
+ <code class="option">-g</code> <em class="replaceable"><code><group-name></code></em>
+ </td><td>
+ Group name or group number for the user's default group. The group must exist prior to being specified here.
+ </td></tr><tr><td>
+ <code class="option">-G</code> <em class="replaceable"><code><group-list></code></em>
+ </td><td>
+ List of additional (other than default) group names or group numbers, separated by commas, of which the user is a member. The groups must exist prior to being specified here.
+ </td></tr><tr><td>
+ <code class="option">-m</code>
+ </td><td>
+ Create the home directory if it does not exist.
+ </td></tr><tr><td>
+ <code class="option">-M</code>
+ </td><td>
+ Do not create the home directory.
+ </td></tr><tr><td>
+ <code class="option">-N</code>
+ </td><td>
+ Do not create a user private group for the user.
+ </td></tr><tr><td>
+ <code class="option">-p</code> <em class="replaceable"><code><password></code></em>
+ </td><td>
+ The password encrypted with <code class="command">crypt</code>
+ </td></tr><tr><td>
+ <code class="option">-r</code>
+ </td><td>
+ Create a system account with a UID less than 500 and without a home directory
+ </td></tr><tr><td>
+ <code class="option">-s</code>
+ </td><td>
+ User's login shell, which defaults to <code class="filename">/bin/bash</code>
+ </td></tr><tr><td>
+ <code class="option">-u</code> <em class="replaceable"><code><uid></code></em>
+ </td><td>
+ User ID for the user, which must be unique and greater than 499
+ </td></tr></tbody></table></div></div><br class="table-break" /><h4 id="id610996">Adding a Group</h4><a id="id611000" class="indexterm"></a><a id="id611021" class="indexterm"></a><div class="para">
+ To add a group to the system, use the command <code class="command">groupadd</code>:
+ </div><pre class="screen">
+<code class="command">groupadd <em class="replaceable"><code><group-name></code></em> </code>
+</pre><div class="para">
+ Command line options for <code class="command">groupadd</code> are detailed in <a class="xref" href="s1-users-tools.html#table-groupadd-options" title="Table 15.2. groupadd Command Line Options">Table 15.2, “ <code class="command">groupadd</code> Command Line Options”</a>.
+ </div><div class="table" title="Table 15.2. groupadd Command Line Options" id="table-groupadd-options"><h6>Table 15.2. <code class="command">groupadd</code> Command Line Options</h6><div class="table-contents"><table summary=" groupadd Command Line Options" border="1"><colgroup><col width="29%" /><col width="71%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ -f, --force
+ </td><td>
+ When used with <code class="option">-g</code> <em class="replaceable"><code><gid></code></em> and <em class="replaceable"><code><gid></code></em> already exists, <code class="command">groupadd</code> will choose another unique <em class="replaceable"><code><gid></code></em> for the group.
+ </td></tr><tr><td>
+ <code class="option">-g</code> <em class="replaceable"><code><gid></code></em>
+ </td><td>
+ Group ID for the group, which must be unique and greater than 499
+ </td></tr><tr><td>
+ <code class="option">-K, --key KEY=VALUE</code>
+ </td><td>
+ override <code class="code">/etc/login.defs</code> defaults
+ </td></tr><tr><td>
+ <code class="option">-o</code>, <code class="option">--non-unique</code>
+ </td><td>
+ allow to create groups with duplicate
+ </td></tr><tr><td>
+ <code class="option">-p</code>, <code class="option">--password</code> <code class="option">PASSWORD</code>
+ </td><td>
+ use this encrypted password for the new group
+ </td></tr><tr><td>
+ <code class="option">-r</code>
+ </td><td>
+ Create a system group with a GID less than 500
+ </td></tr></tbody></table></div></div><br class="table-break" /><h4 id="id683266">Password Aging</h4><a id="id683270" class="indexterm"></a><a id="id683284" class="indexterm"></a><a id="id683299" class="indexterm"></a><a id="id683309" class="indexterm"></a><a id="id471172" class="indexterm"></a><div class="para">
+ For security reasons, it is advisable to require users to change their passwords periodically. This can be done when adding or editing a user on the <span class="guilabel"><strong>Password Info</strong></span> tab of the <span class="application"><strong>User Manager</strong></span>.
+ </div><div class="para">
+ To configure password expiration for a user from a shell prompt, use the <code class="command">chage</code> command with an option from <a class="xref" href="s1-users-tools.html#table-chage-options" title="Table 15.3. chage Command Line Options">Table 15.3, “ <code class="command">chage</code> Command Line Options”</a>, followed by the username.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Shadow passwords must be enabled to use the <code class="command">chage</code> command. For more information, see <a class="xref" href="s1-users-groups-shadow-utilities.html" title="15.6. Shadow Passwords">Section 15.6, “Shadow Passwords”</a>.
+ </div></div></div><div class="table" title="Table 15.3. chage Command Line Options" id="table-chage-options"><h6>Table 15.3. <code class="command">chage</code> Command Line Options</h6><div class="table-contents"><table summary=" chage Command Line Options" border="1"><colgroup><col width="29%" /><col width="71%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-d</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Specifies the number of days since January 1, 1970 the password was changed
+ </td></tr><tr><td>
+ <code class="option">-E</code> <em class="replaceable"><code><date></code></em>
+ </td><td>
+ Specifies the date on which the account is locked, in the format YYYY-MM-DD. Instead of the date, the number of days since January 1, 1970 can also be used.
+ </td></tr><tr><td>
+ <code class="option">-I</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Specifies the number of inactive days after the password expiration before locking the account. If the value is 0, the account is not locked after the password expires.
+ </td></tr><tr><td>
+ <code class="option">-l</code>
+ </td><td>
+ Lists current account aging settings.
+ </td></tr><tr><td>
+ <code class="option">-m</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Specify the minimum number of days after which the user must change passwords. If the value is 0, the password does not expire.
+ </td></tr><tr><td>
+ <code class="option">-M</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Specify the maximum number of days for which the password is valid. When the number of days specified by this option plus the number of days specified with the <code class="option">-d</code> option is less than the current day, the user must change passwords before using the account.
+ </td></tr><tr><td>
+ <code class="option">-W</code> <em class="replaceable"><code><days></code></em>
+ </td><td>
+ Specifies the number of days before the password expiration date to warn the user.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ If the <code class="command">chage</code> command is followed directly by a username (with no options), it displays the current password aging values and allows them to be changed interactively.
+ </div></div></div><div class="para">
+ You can configure a password to expire the first time a user logs in. This forces users to change passwords immediately.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Set up an initial password</em></span> — There are two common approaches to this step. The administrator can assign a default password or assign a null password.
+ </div><div class="para">
+ To assign a default password, use the following steps:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Start the command line Python interpreter with the <code class="command">python</code> command. It displays the following:
+ </div><pre class="screen">
+Python 2.4.3 (#1, Jul 21 2006, 08:46:09)
+[GCC 4.1.1 20060718 (Application Stack 4.1.1-9)] on linux2
+Type "help", "copyright", "credits" or "license" for more information.
+>>></pre></li><li class="listitem"><div class="para">
+ At the prompt, type the following commands. Replace <em class="replaceable"><code><password></code></em> with the password to encrypt and <em class="replaceable"><code><salt></code></em> with a random combination of at least 2 of the following: any alphanumeric character, the slash (/) character or a dot (.):
+ </div><pre class="screen">
+<code class="command">import crypt; print crypt.crypt("<em class="replaceable"><code><password></code></em>","<em class="replaceable"><code><salt></code></em>")</code>
+</pre><div class="para">
+ The output is the encrypted password, similar to <code class="computeroutput">'12CsGd8FRcMSM'</code>.
+ </div></li><li class="listitem"><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>-<span class="keycap"><strong>D</strong></span> to exit the Python interpreter.
+ </div></li><li class="listitem"><div class="para">
+ At the shell, enter the following command (replacing <em class="replaceable"><code><encrypted-password></code></em> with the encrypted output of the Python interpreter):
+ </div><pre class="screen">usermod -p "<em class="replaceable"><code><encrypted-password></code></em>" <em class="replaceable"><code><username></code></em>
+</pre></li></ul></div><div class="para">
+ Alternatively, you can assign a null password instead of an initial password. To do this, use the following command:
+ </div><pre class="screen">usermod -p "" <em class="replaceable"><code>username</code></em>
+</pre><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Using a null password, while convenient, is a highly unsecure practice, as any third party can log in first and access the system using the unsecure username. Always make sure that the user is ready to log in before unlocking an account with a null password.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>Force immediate password expiration</em></span> — Type the following command:
+ </div><pre class="screen">chage -d 0 <em class="replaceable"><code>username</code></em>
+</pre><div class="para">
+ This command sets the value for the date the password was last changed to the epoch (January 1, 1970). This value forces immediate password expiration no matter what password aging policy, if any, is in place.
+ </div></li></ol></div><div class="para">
+ Upon the initial log in, the user is now prompted for a new password.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="Users_and_Groups.html"><strong>Prev</strong>Chapter 15. Users and Groups</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-redhat-config-users-process.html"><strong>Next</strong>15.2.2. Explaining the Process</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-dso-writing.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-dso-writing.html
new file mode 100644
index 0000000..af171e5
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-dso-writing.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.4.2. Writing a Module</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-dso.html" title="11.4. Working with Modules" /><link rel="prev" href="s1-apache-dso.html" title="11.4. Working with Modules" /><link rel="next" href="s1-apache-virtualhosts.html" title="11.5. Setting Up Virtual Hosts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-dso.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-ap
ache-virtualhosts.html"><strong>Next</strong></a></li></ul><div class="section" title="11.4.2. Writing a Module" id="s2-apache-dso-writing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-dso-writing">11.4.2. Writing a Module</h3></div></div></div><a id="id737586" class="indexterm"></a><div class="para">
+ If you intend to create a new DSO module, make sure you have the <span class="package">httpd-devel</span> package installed. To do so, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">yum install httpd-devel</code></pre><div class="para">
+ This package contains the include files, the header files, and the <span class="application"><strong>APache eXtenSion</strong></span> (<code class="command">apxs</code>) utility required to compile a module.
+ </div><div class="para">
+ Once written, you can build the module with the following command:
+ </div><pre class="screen">~]# <code class="command">apxs -i -a -c <em class="replaceable"><code>module_name</code></em>.c</code></pre><div class="para">
+ If the build was successful, you should be able to load the module the same way as any other module that is distributed with the Apache HTTP Server.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-dso.html"><strong>Prev</strong>11.4. Working with Modules</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-virtualhosts.html"><strong>Next</strong>11.5. Setting Up Virtual Hosts</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mod_ssl-enabling.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mod_ssl-enabling.html
new file mode 100644
index 0000000..faa1f1b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mod_ssl-enabling.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.6.2. Enabling the mod_ssl Module</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-mod_ssl.html" title="11.6. Setting Up an SSL Server" /><link rel="prev" href="s1-apache-mod_ssl.html" title="11.6. Setting Up an SSL Server" /><link rel="next" href="s2-apache-mod_ssl-keypair.html" title="11.6.3. Using an Existing Key and Certificate" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-mod_ssl.html"><strong>Prev</strong></a></li><li cla
ss="next"><a accesskey="n" href="s2-apache-mod_ssl-keypair.html"><strong>Next</strong></a></li></ul><div class="section" title="11.6.2. Enabling the mod_ssl Module" id="s2-apache-mod_ssl-enabling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mod_ssl-enabling">11.6.2. Enabling the <code class="systemitem">mod_ssl</code> Module</h3></div></div></div><div class="para">
+ If you intend to set up an SSL server, make sure you have the <span class="package">mod_ssl</span> (the <code class="systemitem">mod_ssl</code> module) and <span class="package">openssl</span> (the OpenSSL toolkit) packages installed. To do so, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">yum install mod_ssl openssl</code></pre><a id="id622329" class="indexterm"></a><div class="para">
+ This will create the <code class="systemitem">mod_ssl</code> configuration file at <code class="filename">/etc/httpd/conf.d/ssl.conf</code>, which is included in the main Apache HTTP Server configuration file by default. For the module to be loaded, restart the <code class="systemitem">httpd</code> service as described in <a class="xref" href="s3-apache-running-restarting.html" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-mod_ssl.html"><strong>Prev</strong>11.6. Setting Up an SSL Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-apache-mod_ssl-keypair.html"><strong>Next</strong>11.6.3. Using an Existing Key and Certificate</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mod_ssl-genkey.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mod_ssl-genkey.html
new file mode 100644
index 0000000..0d536a7
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mod_ssl-genkey.html
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.6.4. Generating a New Key and Certificate</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-mod_ssl.html" title="11.6. Setting Up an SSL Server" /><link rel="prev" href="s2-apache-mod_ssl-keypair.html" title="11.6.3. Using an Existing Key and Certificate" /><link rel="next" href="s1-apache-resources.html" title="11.7. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-mod_ssl-keypair.html"><strong>Prev</strong></a></li><
li class="next"><a accesskey="n" href="s1-apache-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="11.6.4. Generating a New Key and Certificate" id="s2-apache-mod_ssl-genkey"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mod_ssl-genkey">11.6.4. Generating a New Key and Certificate</h3></div></div></div><a id="id829633" class="indexterm"></a><a id="id829650" class="indexterm"></a><div class="para">
+ In order to generate a new key and certificate pair, you must to have the <span class="package">crypto-utils</span> package installed in your system. You can install it by typing the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">yum install crypto-utils</code></pre><div class="para">
+ This package provides a set of tools to generate and manage SSL certificates and private keys, and includes <span class="application"><strong>genkey</strong></span>, the Red Hat Keypair Generation utility that will guide you through the key generation process.
+ </div><div class="important" title="Important: Replacing an Existing Certificate"><div class="admonition_header"><h2>Important: Replacing an Existing Certificate</h2></div><div class="admonition"><div class="para">
+ If the server already has a valid certificate and you are replacing it with a new one, specify a different serial number. This ensures that client browsers are notified of this change, update to this new certificate as expected, and do not fail to access the page. To create a new certificate with a custom serial number, use the following command instead of <span class="application"><strong>genkey</strong></span>:
+ </div><pre class="screen">~]# <code class="command">openssl req -x509 -new -set_serial <em class="replaceable"><code>number</code></em> -key <em class="replaceable"><code>hostname</code></em>.key -out <em class="replaceable"><code>hostname</code></em>.crt</code></pre></div></div><div class="note" title="Note: Remove a Previously Created Key"><div class="admonition_header"><h2>Note: Remove a Previously Created Key</h2></div><div class="admonition"><div class="para">
+ If there already is a key file for a particular hostname in your system, <span class="application"><strong>genkey</strong></span> will refuse to start. In this case, remove the existing file using the following command:
+ </div><pre class="screen">~]# <code class="command">rm /etc/pki/tls/private/<em class="replaceable"><code>hostname</code></em>.key</code></pre></div></div><div class="para">
+ To run the utility, use the <code class="command">genkey</code> command followed by the appropriate hostname (for example, <code class="systemitem">penguin.example.com</code>):
+ </div><pre class="screen">~]# <code class="command">genkey</code> <em class="replaceable"><code>hostname</code></em></pre><div class="para">
+ To complete the key and certificate creation, take the following steps:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Review the target locations in which the key and certificate will be stored.
+ </div><div class="figure" title="Figure 11.1. Running the genkey utility" id="figure-apache-mod_ssl-genkey-01"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-01.png" alt="Running the genkey utility" /><div class="longdesc"><div class="para">
+ Running the <span class="application"><strong>genkey</strong></span> utility
+ </div></div></div></div><h6>Figure 11.1. Running the <span class="application">genkey</span> utility</h6></div><br class="figure-break" /><div class="para">
+ Use the <span class="keycap"><strong>Tab</strong></span> key to select the <span class="guibutton"><strong>Next</strong></span> button, and press <span class="keycap"><strong>Enter</strong></span> to proceed to the next screen.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Using the <span class="keycap"><strong>Up</strong></span> and <span class="keycap"><strong>down</strong></span> arrow keys, select the suitable key size. Note that while the large key increases the security, it also increases the response time of your server. Because of this, the recommended option is <code class="literal">1024 bits</code>.
+ </div><div class="figure" title="Figure 11.2. Selecting the key size" id="figure-apache-mod_ssl-genkey-02"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-02.png" alt="Selecting the key size" /><div class="longdesc"><div class="para">
+ Selecting the key size
+ </div></div></div></div><h6>Figure 11.2. Selecting the key size</h6></div><br class="figure-break" /><div class="para">
+ Once finished, use the <span class="keycap"><strong>Tab</strong></span> key to select the <span class="guibutton"><strong>Next</strong></span> button, and press <span class="keycap"><strong>Enter</strong></span> to initiate the random bits generation process. Depending on the selected key size, this may take some time.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Decide whether you wish to send a certificate request to a certificate authority.
+ </div><div class="figure" title="Figure 11.3. Generating a certificate request" id="figure-apache-mod_ssl-genkey-03"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-03.png" alt="Generating a certificate request" /><div class="longdesc"><div class="para">
+ Generating a certificate request
+ </div></div></div></div><h6>Figure 11.3. Generating a certificate request</h6></div><br class="figure-break" /><div class="para">
+ Use the <span class="keycap"><strong>Tab</strong></span> key to select <span class="guibutton"><strong>Yes</strong></span> to compose a certificate request, or <span class="guibutton"><strong>No</strong></span> to generate a self-signed certificate. Then press <span class="keycap"><strong>Enter</strong></span> to confirm your choice.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ Using the <span class="keycap"><strong>Spacebar</strong></span> key, enable (<code class="literal">[*]</code>) or disable (<code class="literal">[ ]</code>) the encryption of the private key.
+ </div><div class="figure" title="Figure 11.4. Encrypting the private key" id="figure-apache-mod_ssl-genkey-04"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-04.png" alt="Encrypting the private key" /><div class="longdesc"><div class="para">
+ Encrypting the private key
+ </div></div></div></div><h6>Figure 11.4. Encrypting the private key</h6></div><br class="figure-break" /><div class="para">
+ Use the <span class="keycap"><strong>Tab</strong></span> key to select the <span class="guibutton"><strong>Next</strong></span> button, and press <span class="keycap"><strong>Enter</strong></span> to proceed to the next screen.
+ </div></li><li class="step" title="Step 5"><div class="para">
+ If you have enabled the private key encryption, enter an adequate passphrase. Note that for security reasons, it is not displayed as you type, and it must be at least five characters long.
+ </div><div class="figure" title="Figure 11.5. Entering a passphrase" id="figure-apache-mod_ssl-genkey-05"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-05.png" alt="Entering a passphrase" /><div class="longdesc"><div class="para">
+ Entering a passphrase
+ </div></div></div></div><h6>Figure 11.5. Entering a passphrase</h6></div><br class="figure-break" /><div class="para">
+ Use the <span class="keycap"><strong>Tab</strong></span> key to select the <span class="guibutton"><strong>Next</strong></span> button, and press <span class="keycap"><strong>Enter</strong></span> to proceed to the next screen.
+ </div><div class="important" title="Important: Do Not Forget the Passphrase"><div class="admonition_header"><h2>Important: Do Not Forget the Passphrase</h2></div><div class="admonition"><div class="para">
+ Entering the correct passphrase is required in order for the server to start. If you lose it, you will need to generate a new key and certificate.
+ </div></div></div></li><li class="step" title="Step 6"><div class="para">
+ Customize the certificate details.
+ </div><div class="figure" title="Figure 11.6. Specifying certificate information" id="figure-apache-mod_ssl-genkey-06"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-06.png" alt="Specifying certificate information" /><div class="longdesc"><div class="para">
+ Specifying certificate information
+ </div></div></div></div><h6>Figure 11.6. Specifying certificate information</h6></div><br class="figure-break" /><div class="para">
+ Use the <span class="keycap"><strong>Tab</strong></span> key to select the <span class="guibutton"><strong>Next</strong></span> button, and press <span class="keycap"><strong>Enter</strong></span> to finish the key generation.
+ </div></li><li class="step" title="Step 7"><div class="para">
+ If you have previously enabled the certificate request generation, you will be prompted to send it to a certificate authority.
+ </div><div class="figure" title="Figure 11.7. Instructions on how to send a certificate request" id="figure-apache-mod_ssl-genkey-07"><div class="figure-contents"><div class="mediaobject"><img src="images/apache-mod_ssl-genkey-07.png" alt="Instructions on how to send a certificate request" /><div class="longdesc"><div class="para">
+ Instructions on how to send a certificate request
+ </div></div></div></div><h6>Figure 11.7. Instructions on how to send a certificate request</h6></div><br class="figure-break" /><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to return to a shell prompt.
+ </div></li></ol></div><div class="para">
+ Once generated, add the key and certificate locations to the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> configuration file:
+ </div><pre class="screen">SSLCertificateFile /etc/pki/tls/certs/<em class="replaceable"><code>hostname</code></em>.crt
+SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostname</code></em>.key</pre><div class="para">
+ Finally, restart the <code class="systemitem">httpd</code> service as described in <a class="xref" href="s3-apache-running-restarting.html" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a>, so that the updated configuration is loaded.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-mod_ssl-keypair.html"><strong>Prev</strong>11.6.3. Using an Existing Key and Certificate</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-resources.html"><strong>Next</strong>11.7. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mod_ssl-keypair.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mod_ssl-keypair.html
new file mode 100644
index 0000000..7c20c2a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mod_ssl-keypair.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.6.3. Using an Existing Key and Certificate</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-mod_ssl.html" title="11.6. Setting Up an SSL Server" /><link rel="prev" href="s2-apache-mod_ssl-enabling.html" title="11.6.2. Enabling the mod_ssl Module" /><link rel="next" href="s2-apache-mod_ssl-genkey.html" title="11.6.4. Generating a New Key and Certificate" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-mod_ssl-enabling.html"><strong>Prev</st
rong></a></li><li class="next"><a accesskey="n" href="s2-apache-mod_ssl-genkey.html"><strong>Next</strong></a></li></ul><div class="section" title="11.6.3. Using an Existing Key and Certificate" id="s2-apache-mod_ssl-keypair"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mod_ssl-keypair">11.6.3. Using an Existing Key and Certificate</h3></div></div></div><a id="id1719662" class="indexterm"></a><a id="id1719679" class="indexterm"></a><div class="para">
+ If you have a previously created key and certificate, you can configure the SSL server to use these files instead of generating new ones. There are only two situations where this is not possible:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ <span class="emphasis"><em>You are changing the IP address or domain name.</em></span>
+ </div><div class="para">
+ Certificates are issued for a particular IP address and domain name pair. If one of these values changes, the certificate becomes invalid.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>You have a certificate from VeriSign, and you are changing the server software.</em></span>
+ </div><div class="para">
+ VeriSign, a widely used certificate authority, issues certificates for a particular software product, IP address, and domain name. Changing the software product renders the certificate invalid.
+ </div></li></ol></div><div class="para">
+ In either of the above cases, you will need to obtain a new certificate. For more information on this topic, refer to <a class="xref" href="s2-apache-mod_ssl-genkey.html" title="11.6.4. Generating a New Key and Certificate">Section 11.6.4, “Generating a New Key and Certificate”</a>.
+ </div><div class="para">
+ If you wish to use an existing key and certificate, move the relevant files to the <code class="filename">/etc/pki/tls/private/</code> and <code class="filename">/etc/pki/tls/certs/</code> directories respectively. You can do so by typing the following commands:
+ </div><pre class="screen">~]# <code class="command">mv</code> <code class="filename"><em class="replaceable"><code>key_file</code></em>.key</code> <code class="filename">/etc/pki/tls/private/<em class="replaceable"><code>hostname</code></em>.key</code>
+~]# <code class="command">mv</code> <code class="filename"><em class="replaceable"><code>certificate</code></em>.crt</code> <code class="filename">/etc/pki/tls/certs/<em class="replaceable"><code>hostname</code></em>.crt</code></pre><div class="para">
+ Then add the following lines to the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> configuration file:
+ </div><pre class="screen">SSLCertificateFile /etc/pki/tls/certs/<em class="replaceable"><code>hostname</code></em>.crt
+SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostname</code></em>.key</pre><div class="para">
+ To load the updated configuration, restart the <code class="systemitem">httpd</code> service as described in <a class="xref" href="s3-apache-running-restarting.html" title="11.2.3. Restarting the Service">Section 11.2.3, “Restarting the Service”</a>.
+ </div><div class="example" title="Example 11.81. Using a key and certificate from the Red Hat Secure Web Server" id="example-apache-mod_ssl-keypair"><h6>Example 11.81. Using a key and certificate from the <span class="application">Red Hat Secure Web Server</span></h6><div class="example-contents"><pre class="screen">~]# <code class="command">mv /etc/httpd/conf/httpsd.key /etc/pki/tls/private/penguin.example.com.key</code>
+~]# <code class="command">mv /etc/httpd/conf/httpsd.crt /etc/pki/tls/certs/penguin.example.com.crt</code></pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-mod_ssl-enabling.html"><strong>Prev</strong>11.6.2. Enabling the mod_ssl Module</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-apache-mod_ssl-genkey.html"><strong>Next</strong>11.6.4. Generating a New Key and Certificate</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mpm-common.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mpm-common.html
new file mode 100644
index 0000000..93fdd15
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-mpm-common.html
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.3.3. Common Multi-Processing Module Directives</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-editing.html" title="11.3. Editing the Configuration Files" /><link rel="prev" href="s2-apache-sslconf-common.html" title="11.3.2. Common ssl.conf Directives" /><link rel="next" href="s1-apache-dso.html" title="11.4. Working with Modules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-sslconf-common.html"><strong>Prev</strong></a></li><li class="ne
xt"><a accesskey="n" href="s1-apache-dso.html"><strong>Next</strong></a></li></ul><div class="section" title="11.3.3. Common Multi-Processing Module Directives" id="s2-apache-mpm-common"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-mpm-common">11.3.3. Common Multi-Processing Module Directives</h3></div></div></div><div class="para">
+ The <em class="firstterm">Multi-Processing Module</em> (<acronym class="acronym">MPM</acronym>) directives allow you to customize the behavior of a particular MPM specific server-pool. Since its characteristics differ depending on which MPM is used, the directives are embeded in <code class="option">IfModule</code>. By default, the server-pool is defined for both the <code class="systemitem">prefork</code> and <code class="systemitem">worker</code> MPMs.
+ </div><a id="id807975" class="indexterm"></a><div class="para">
+ The following MPM directives are commonly used in <code class="filename">/etc/httpd/conf/httpd.conf</code>:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id695870" class="indexterm"></a>
+ <code class="option">MaxClients</code> </span></dt><dd><div class="para">
+ The <code class="option">MaxClients</code> directive allows you to specify the maximum number of simultaneously connected clients to process at one time. It takes the following form:
+ </div><pre class="screen">MaxClients <em class="replaceable"><code>number</code></em></pre><div class="para">
+ A high <em class="replaceable"><code>number</code></em> can improve the performance of the server, although it is not recommended to exceed <code class="literal">256</code> when using the <code class="systemitem">prefork</code> MPM.
+ </div><div class="example" title="Example 11.71. Using the MaxClients directive" id="example-apache-mpm-maxclients"><h6>Example 11.71. Using the <code class="option">MaxClients</code> directive</h6><div class="example-contents"><pre class="screen">MaxClients 256</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id695957" class="indexterm"></a>
+ <code class="option">MaxRequestsPerChild</code> </span></dt><dd><div class="para">
+ The <code class="option">MaxRequestsPerChild</code> directive allows you to specify the maximum number of request a child process can serve before it dies. It takes the following form:
+ </div><pre class="screen">MaxRequestsPerChild <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Setting the <em class="replaceable"><code>number</code></em> to <code class="literal">0</code> allows unlimited number of requests.
+ </div><div class="para">
+ The <code class="option">MaxRequestsPerChild</code> directive is used to prevent long-lived processes from causing memory leaks.
+ </div><div class="example" title="Example 11.72. Using the MaxRequestsPerChild directive" id="example-apache-mpm-maxrequestsperchild"><h6>Example 11.72. Using the <code class="option">MaxRequestsPerChild</code> directive</h6><div class="example-contents"><pre class="screen">MaxRequestsPerChild 4000</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id695099" class="indexterm"></a>
+ <code class="option">MaxSpareServers</code> </span></dt><dd><div class="para">
+ The <code class="option">MaxSpareServers</code> directive allows you to specify the maximum number of spare child processes. It takes the following form:
+ </div><pre class="screen">MaxSpareServers <em class="replaceable"><code>number</code></em></pre><div class="para">
+ This directive is used by the <code class="systemitem">prefork</code> MPM only.
+ </div><div class="example" title="Example 11.73. Using the MaxSpareServers directive" id="example-apache-mpm-maxspareservers"><h6>Example 11.73. Using the <code class="option">MaxSpareServers</code> directive</h6><div class="example-contents"><pre class="screen">MaxSpareServers 20</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id695178" class="indexterm"></a>
+ <code class="option">MaxSpareThreads</code> </span></dt><dd><div class="para">
+ The <code class="option">MaxSpareThreads</code> directive allows you to specify the maximum number of spare server threads. It takes the following form:
+ </div><pre class="screen">MaxSpareThreads <em class="replaceable"><code>number</code></em></pre><div class="para">
+ The <em class="replaceable"><code>number</code></em> must be greater than or equal to the sum of <code class="option">MinSpareThreads</code> and <code class="option">ThreadsPerChild</code>. This directive is used by the <code class="systemitem">worker</code> MPM only.
+ </div><div class="example" title="Example 11.74. Using the MaxSpareThreads directive" id="example-apache-mpm-maxsparethreads"><h6>Example 11.74. Using the <code class="option">MaxSpareThreads</code> directive</h6><div class="example-contents"><pre class="screen">MaxSpareThreads 75</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id456036" class="indexterm"></a>
+ <code class="option">MinSpareServers</code> </span></dt><dd><div class="para">
+ The <code class="option">MinSpareServers</code> directive allows you to specify the minimum number of spare child processes. It takes the following form:
+ </div><pre class="screen">MinSpareServers <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Note that a high <em class="replaceable"><code>number</code></em> can create a heavy processing load on the server. This directive is used by the <code class="systemitem">prefork</code> MPM only.
+ </div><div class="example" title="Example 11.75. Using the MinSpareServers directive" id="example-apache-mpm-minspareservers"><h6>Example 11.75. Using the <code class="option">MinSpareServers</code> directive</h6><div class="example-contents"><pre class="screen">MinSpareServers 5</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id797989" class="indexterm"></a>
+ <code class="option">MinSpareThreads</code> </span></dt><dd><div class="para">
+ The <code class="option">MinSpareThreads</code> directive allows you to specify the minimum number of spare server threads. It takes the following form:
+ </div><pre class="screen">MinSpareThreads <em class="replaceable"><code>number</code></em></pre><div class="para">
+ This directive is used by the <code class="systemitem">worker</code> MPM only.
+ </div><div class="example" title="Example 11.76. Using the MinSpareThreads directive" id="example-apache-mpm-minsparethreads"><h6>Example 11.76. Using the <code class="option">MinSpareThreads</code> directive</h6><div class="example-contents"><pre class="screen">MinSpareThreads 75</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id798067" class="indexterm"></a>
+ <code class="option">StartServers</code> </span></dt><dd><div class="para">
+ The <code class="option">StartServers</code> directive allows you to specify the number of child processes to create when the service is started. It takes the following form:
+ </div><pre class="screen">StartServers <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Since the child processes are dynamically created and terminated according to the current traffic load, it is usually not necessary to change this value.
+ </div><div class="example" title="Example 11.77. Using the StartServers directive" id="example-apache-mpm-startservers"><h6>Example 11.77. Using the <code class="option">StartServers</code> directive</h6><div class="example-contents"><pre class="screen">StartServers 8</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id465964" class="indexterm"></a>
+ <code class="option">ThreadsPerChild</code> </span></dt><dd><div class="para">
+ The <code class="option">ThreadsPerChild</code> directive allows you to specify the number of threads a child process can create. It takes the following form:
+ </div><pre class="screen">ThreadsPerChild <em class="replaceable"><code>number</code></em></pre><div class="para">
+ This directive is used by the <code class="systemitem">worker</code> MPM only.
+ </div><div class="example" title="Example 11.78. Using the ThreadsPerChild directive" id="example-apache-mpm-threadsperchild"><h6>Example 11.78. Using the <code class="option">ThreadsPerChild</code> directive</h6><div class="example-contents"><pre class="screen">ThreadsPerChild 25</pre></div></div><br class="example-break" /></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-sslconf-common.html"><strong>Prev</strong>11.3.2. Common ssl.conf Directives</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-dso.html"><strong>Next</strong>11.4. Working with Modules</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-resources-web.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-resources-web.html
new file mode 100644
index 0000000..3bbf0f0
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-resources-web.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.7.2. Useful Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-resources.html" title="11.7. Additional Resources" /><link rel="prev" href="s1-apache-resources.html" title="11.7. Additional Resources" /><link rel="next" href="ch-email.html" title="Chapter 12. Email" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-email.html
"><strong>Next</strong></a></li></ul><div class="section" title="11.7.2. Useful Websites" id="s2-apache-resources-web"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-resources-web">11.7.2. Useful Websites</h3></div></div></div><a id="id706730" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><a href="http://httpd.apache.org/">http://httpd.apache.org/</a></span></dt><dd><div class="para">
+ The official website for the Apache HTTP Server with documentation on all the directives and default modules.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.modssl.org/">http://www.modssl.org/</a></span></dt><dd><div class="para">
+ The official website for the <span class="application"><strong>mod_ssl</strong></span> module.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.openssl.org/">http://www.openssl.org/</a></span></dt><dd><div class="para">
+ The OpenSSL home page containing further documentation, frequently asked questions, links to the mailing lists, and other useful resources.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-resources.html"><strong>Prev</strong>11.7. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-email.html"><strong>Next</strong>Chapter 12. Email</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-running-stopping.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-running-stopping.html
new file mode 100644
index 0000000..eba86d7
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-running-stopping.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.2.2. Stopping the Service</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-running.html" title="11.2. Running the httpd Service" /><link rel="prev" href="s1-apache-running.html" title="11.2. Running the httpd Service" /><link rel="next" href="s3-apache-running-restarting.html" title="11.2.3. Restarting the Service" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-running.html"><strong>Prev</strong></a></li><li class="next">
<a accesskey="n" href="s3-apache-running-restarting.html"><strong>Next</strong></a></li></ul><div class="section" title="11.2.2. Stopping the Service" id="s2-apache-running-stopping"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-running-stopping">11.2.2. Stopping the Service</h3></div></div></div><a id="id786307" class="indexterm"></a><div class="para">
+ To stop the running <code class="systemitem">httpd</code> service, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service httpd stop</code>
+Stopping httpd: [ OK ]</pre><div class="para">
+ To prevent the service from starting automatically at the boot time, type:
+ </div><pre class="screen">~]# <code class="command">chkconfig httpd off</code></pre><div class="para">
+ This will disable the service for all runlevels. Alternatively, you can use the <span class="application"><strong>Service Configuration</strong></span> utility as described in <a class="xref" href="s1-services-configuring.html#s3-services-serviceconf-disabling" title="7.2.1.2. Disabling the Service">Section 7.2.1.2, “Disabling the Service”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-running.html"><strong>Prev</strong>11.2. Running the httpd Service</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s3-apache-running-restarting.html"><strong>Next</strong>11.2.3. Restarting the Service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-sslconf-common.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-sslconf-common.html
new file mode 100644
index 0000000..ae30715
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-apache-sslconf-common.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.3.2. Common ssl.conf Directives</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-editing.html" title="11.3. Editing the Configuration Files" /><link rel="prev" href="s1-apache-editing.html" title="11.3. Editing the Configuration Files" /><link rel="next" href="s2-apache-mpm-common.html" title="11.3.3. Common Multi-Processing Module Directives" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-editing.html"><strong>Prev</strong></a
></li><li class="next"><a accesskey="n" href="s2-apache-mpm-common.html"><strong>Next</strong></a></li></ul><div class="section" title="11.3.2. Common ssl.conf Directives" id="s2-apache-sslconf-common"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-apache-sslconf-common">11.3.2. Common <code class="filename">ssl.conf</code> Directives</h3></div></div></div><div class="para">
+ The <em class="firstterm">Secure Sockets Layer</em> (<acronym class="acronym">SSL</acronym>) directives allow you to customize the behavior of the Apache HTTP Secure Server, and in most cases, they are configured appropriately during the installation. Be careful when changing these settings, as incorrect configuration can lead to security vulnerabilities.
+ </div><a id="id750065" class="indexterm"></a><div class="para">
+ The following directive is commonly used in <code class="filename">/etc/httpd/conf.d/ssl.conf</code>:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id750099" class="indexterm"></a>
+ <code class="option">SetEnvIf</code> </span></dt><dd><div class="para">
+ The <code class="option">SetEnvIf</code> directive allows you to set environment variables based on the headers of incoming connections. It takes the following form:
+ </div><pre class="screen">SetEnvIf <em class="replaceable"><code>option</code></em> <em class="replaceable"><code>pattern</code></em> [<span class="optional">!</span>]<em class="replaceable"><code>variable</code></em>[<span class="optional">=<em class="replaceable"><code>value</code></em></span>]…</pre><div class="para">
+ The <em class="replaceable"><code>option</code></em> can be either a HTTP header field, a previously defined environment variable name, or a valid keyword as described in <a class="xref" href="s2-apache-sslconf-common.html#table-apache-sslconf-setenvif" title="Table 11.21. Available SetEnvIf options">Table 11.21, “Available <code class="option">SetEnvIf</code> options”</a>. The <em class="replaceable"><code>pattern</code></em> is a regular expression. The <em class="replaceable"><code>variable</code></em> is an environment variable that is set when the option matches the pattern. If the optional exclamation mark (that is, <code class="literal">!</code>) is present, the variable is removed instead of being set.
+ </div><div class="table" title="Table 11.21. Available SetEnvIf options" id="table-apache-sslconf-setenvif"><h6>Table 11.21. Available <code class="option">SetEnvIf</code> options</h6><div class="table-contents"><table summary="Available SetEnvIf options" border="1"><colgroup><col width="25%" /><col width="75%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">Remote_Host</code>
+ </td><td>
+ Refers to the client's hostname.
+ </td></tr><tr><td>
+ <code class="option">Remote_Addr</code>
+ </td><td>
+ Refers to the client's IP address.
+ </td></tr><tr><td>
+ <code class="option">Server_Addr</code>
+ </td><td>
+ Refers to the server's IP address.
+ </td></tr><tr><td>
+ <code class="option">Request_Method</code>
+ </td><td>
+ Refers to the request method (for example, <code class="literal">GET</code>).
+ </td></tr><tr><td>
+ <code class="option">Request_Protocol</code>
+ </td><td>
+ Refers to the protocol name and version (for example, <code class="literal">HTTP/1.1</code>).
+ </td></tr><tr><td>
+ <code class="option">Request_URI</code>
+ </td><td>
+ Refers to the requested resource.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="option">SetEnvIf</code> directive is used to disable HTTP keepalives, and to allow SSL to close the connection without a closing notification from the client browser. This is necessary for certain web browsers that do not reliably shut down the SSL connection.
+ </div><div class="example" title="Example 11.70. Using the SetEnvIf directive" id="example-apache-sslconf-setenvif"><h6>Example 11.70. Using the <code class="option">SetEnvIf</code> directive</h6><div class="example-contents"><pre class="screen">SetEnvIf User-Agent ".*MSIE.*" \
+ nokeepalive ssl-unclean-shutdown \
+ downgrade-1.0 force-response-1.0</pre></div></div><br class="example-break" /></dd></dl></div><div class="para">
+ Note that for the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file to be present, the <span class="package">mod_ssl</span> needs to be installed. Refer to <a class="xref" href="s1-apache-mod_ssl.html" title="11.6. Setting Up an SSL Server">Section 11.6, “Setting Up an SSL Server”</a> for more information on how to install and configure an SSL server.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-apache-editing.html"><strong>Prev</strong>11.3. Editing the Configuration Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-apache-mpm-common.html"><strong>Next</strong>11.3.3. Common Multi-Processing Module Directives</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-at-batch-controlling-access.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-at-batch-controlling-access.html
new file mode 100644
index 0000000..4d2f597
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-at-batch-controlling-access.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.2.5. Controlling Access to At and Batch</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-autotasks-at-batch.html" title="16.2. At and Batch" /><link rel="prev" href="s2-autotasks-commandline-options.html" title="16.2.4. Additional Command Line Options" /><link rel="next" href="s2-autotasks-at-batch-service.html" title="16.2.6. Starting and Stopping the Service" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-commandline-options.html"><stron
g>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-autotasks-at-batch-service.html"><strong>Next</strong></a></li></ul><div class="section" title="16.2.5. Controlling Access to At and Batch" id="s2-autotasks-at-batch-controlling-access"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-at-batch-controlling-access">16.2.5. Controlling Access to At and Batch</h3></div></div></div><div class="para">
+ The <code class="filename">/etc/at.allow</code> and <code class="filename">/etc/at.deny</code> files can be used to restrict access to the <code class="command">at</code> and <code class="command">batch</code> commands. The format of both access control files is one username on each line. Whitespace is not permitted in either file. The <code class="command">at</code> daemon (<code class="command">atd</code>) does not have to be restarted if the access control files are modified. The access control files are read each time a user tries to execute the <code class="command">at</code> or <code class="command">batch</code> commands.
+ </div><div class="para">
+ The root user can always execute <code class="command">at</code> and <code class="command">batch</code> commands, regardless of the access control files.
+ </div><div class="para">
+ If the file <code class="filename">at.allow</code> exists, only users listed in it are allowed to use <code class="command">at</code> or <code class="command">batch</code>, and the <code class="filename">at.deny</code> file is ignored.
+ </div><div class="para">
+ If <code class="filename">at.allow</code> does not exist, users listed in <code class="filename">at.deny</code> are not allowed to use <code class="command">at</code> or <code class="command">batch</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-commandline-options.html"><strong>Prev</strong>16.2.4. Additional Command Line Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-autotasks-at-batch-service.html"><strong>Next</strong>16.2.6. Starting and Stopping the Service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-at-batch-service.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-at-batch-service.html
new file mode 100644
index 0000000..dd2b91b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-at-batch-service.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.2.6. Starting and Stopping the Service</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-autotasks-at-batch.html" title="16.2. At and Batch" /><link rel="prev" href="s2-autotasks-at-batch-controlling-access.html" title="16.2.5. Controlling Access to At and Batch" /><link rel="next" href="s1-autotasks-additional-resources.html" title="16.3. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-at-batch-controlling-access.html
"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-autotasks-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="16.2.6. Starting and Stopping the Service" id="s2-autotasks-at-batch-service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-at-batch-service">16.2.6. Starting and Stopping the Service</h3></div></div></div><div class="para">
+ To start the <code class="command">at</code> service, use the command <code class="command">/sbin/service atd start</code>. To stop the service, use the command <code class="command">/sbin/service atd stop</code>. It is recommended that you start the service at boot time. Refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for details on starting the cron service automatically at boot time.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-at-batch-controlling-access.html"><strong>Prev</strong>16.2.5. Controlling Access to At and Batch</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-autotasks-additional-resources.html"><strong>Next</strong>16.3. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-at-batch-viewing.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-at-batch-viewing.html
new file mode 100644
index 0000000..fa8fbb5
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-at-batch-viewing.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.2.3. Viewing Pending Jobs</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-autotasks-at-batch.html" title="16.2. At and Batch" /><link rel="prev" href="s2-autotasks-batch-configuring.html" title="16.2.2. Configuring Batch Jobs" /><link rel="next" href="s2-autotasks-commandline-options.html" title="16.2.4. Additional Command Line Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-batch-configuring.html"><strong>Prev</stro
ng></a></li><li class="next"><a accesskey="n" href="s2-autotasks-commandline-options.html"><strong>Next</strong></a></li></ul><div class="section" title="16.2.3. Viewing Pending Jobs" id="s2-autotasks-at-batch-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-at-batch-viewing">16.2.3. Viewing Pending Jobs</h3></div></div></div><div class="para">
+ To view pending <code class="command">at</code> and <code class="command">batch</code> jobs, use the <code class="command">atq</code> command. The <code class="command">atq</code> command displays a list of pending jobs, with each job on a line. Each line follows the job number, date, hour, job class, and username format. Users can only view their own jobs. If the root user executes the <code class="command">atq</code> command, all jobs for all users are displayed.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-batch-configuring.html"><strong>Prev</strong>16.2.2. Configuring Batch Jobs</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-autotasks-commandline-options.html"><strong>Next</strong>16.2.4. Additional Command Line Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-batch-configuring.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-batch-configuring.html
new file mode 100644
index 0000000..c39014c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-batch-configuring.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.2.2. Configuring Batch Jobs</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-autotasks-at-batch.html" title="16.2. At and Batch" /><link rel="prev" href="s1-autotasks-at-batch.html" title="16.2. At and Batch" /><link rel="next" href="s2-autotasks-at-batch-viewing.html" title="16.2.3. Viewing Pending Jobs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-autotasks-at-batch.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n
" href="s2-autotasks-at-batch-viewing.html"><strong>Next</strong></a></li></ul><div class="section" title="16.2.2. Configuring Batch Jobs" id="s2-autotasks-batch-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-batch-configuring">16.2.2. Configuring Batch Jobs</h3></div></div></div><div class="para">
+ To execute a one-time task when the load average is below 0.8, use the <code class="command">batch</code> command.
+ </div><div class="para">
+ After typing the <code class="command">batch</code> command, the <code class="prompt">at></code> prompt is displayed. Type the command to execute, press <span class="keycap"><strong>Enter</strong></span>, and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Multiple commands can be specified by typing each command followed by the <span class="keycap"><strong>Enter</strong></span> key. After typing all the commands, press <span class="keycap"><strong>Enter</strong></span> to go to a blank line and press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> . Alternatively, a shell script can be entered at the prompt, pressing <span class="keycap"><strong>Enter</strong></span> after each line in the script, and pressing <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>D</strong></span> on a blank line to exit. If a script is entered, the shell
used is the shell set in the user's <code class="envar">SHELL</code> environment, the user's login shell, or <code class="command">/bin/sh</code> (whichever is found first). As soon as the load average is below 0.8, the set of commands or script is executed.
+ </div><div class="para">
+ If the set of commands or script tries to display information to standard out, the output is emailed to the user.
+ </div><div class="para">
+ Use the command <code class="command">atq</code> to view pending jobs. Refer to <a class="xref" href="s2-autotasks-at-batch-viewing.html" title="16.2.3. Viewing Pending Jobs">Section 16.2.3, “Viewing Pending Jobs”</a> for more information.
+ </div><div class="para">
+ Usage of the <code class="command">batch</code> command can be restricted. For more information, refer to <a class="xref" href="s2-autotasks-at-batch-controlling-access.html" title="16.2.5. Controlling Access to At and Batch">Section 16.2.5, “Controlling Access to At and Batch”</a> for details.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-autotasks-at-batch.html"><strong>Prev</strong>16.2. At and Batch</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-autotasks-at-batch-viewing.html"><strong>Next</strong>16.2.3. Viewing Pending Jobs</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-commandline-options.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-commandline-options.html
new file mode 100644
index 0000000..306140f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-autotasks-commandline-options.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>16.2.4. Additional Command Line Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-autotasks-at-batch.html" title="16.2. At and Batch" /><link rel="prev" href="s2-autotasks-at-batch-viewing.html" title="16.2.3. Viewing Pending Jobs" /><link rel="next" href="s2-autotasks-at-batch-controlling-access.html" title="16.2.5. Controlling Access to At and Batch" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-at-batch-viewing.html"><strong>Pre
v</strong></a></li><li class="next"><a accesskey="n" href="s2-autotasks-at-batch-controlling-access.html"><strong>Next</strong></a></li></ul><div class="section" title="16.2.4. Additional Command Line Options" id="s2-autotasks-commandline-options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-autotasks-commandline-options">16.2.4. Additional Command Line Options</h3></div></div></div><div class="para">
+ Additional command line options for <code class="command">at</code> and <code class="command">batch</code> include:
+ </div><div class="table" title="Table 16.1. at and batch Command Line Options" id="tb-at-command-line-options"><h6>Table 16.1. <code class="command">at</code> and <code class="command">batch</code> Command Line Options</h6><div class="table-contents"><table summary=" at and batch Command Line Options" border="1"><colgroup><col width="29%" /><col width="71%" /></colgroup><thead><tr><th>
+ Option
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="option">-f</code>
+ </td><td>
+ Read the commands or shell script from a file instead of specifying them at the prompt.
+ </td></tr><tr><td>
+ <code class="option">-m</code>
+ </td><td>
+ Send email to the user when the job has been completed.
+ </td></tr><tr><td>
+ <code class="option">-v</code>
+ </td><td>
+ Display the time that the job is executed.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-at-batch-viewing.html"><strong>Prev</strong>16.2.3. Viewing Pending Jobs</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-autotasks-at-batch-controlling-access.html"><strong>Next</strong>16.2.5. Controlling Access to At and Batch</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-dig-a.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-dig-a.html
new file mode 100644
index 0000000..192cd92
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-dig-a.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.5.2. Looking Up an IP Address</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-dig.html" title="10.5. Using the dig Utility" /><link rel="prev" href="s1-bind-dig.html" title="10.5. Using the dig Utility" /><link rel="next" href="s2-bind-dig-x.html" title="10.5.3. Looking Up a Hostname" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-dig.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-dig-x.html"
><strong>Next</strong></a></li></ul><div class="section" title="10.5.2. Looking Up an IP Address" id="s2-bind-dig-a"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-dig-a">10.5.2. Looking Up an IP Address</h3></div></div></div><div class="para">
+ To look up an IP address assigned to a particular domain, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <em class="replaceable"><code>name</code></em> A</pre><div class="para">
+ In <a class="xref" href="s2-bind-dig-a.html#example-bind-dig-a" title="Example 10.18. A Sample IP Address Lookup">Example 10.18, “A Sample IP Address Lookup”</a>, the <code class="command">dig</code> utility is used to display the IP address of <code class="systemitem">example.com</code>.
+ </div><div class="example" title="Example 10.18. A Sample IP Address Lookup" id="example-bind-dig-a"><h6>Example 10.18. A Sample IP Address Lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig example.com A</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> example.com A
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4849
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
+
+;; QUESTION SECTION:
+;example.com. IN A
+
+;; ANSWER SECTION:
+example.com. 155606 IN A 192.0.32.10
+
+;; AUTHORITY SECTION:
+example.com. 99175 IN NS a.iana-servers.net.
+example.com. 99175 IN NS b.iana-servers.net.
+
+;; Query time: 1 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:07:25 2010
+;; MSG SIZE rcvd: 93</pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-dig.html"><strong>Prev</strong>10.5. Using the dig Utility</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-dig-x.html"><strong>Next</strong>10.5.3. Looking Up a Hostname</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-dig-x.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-dig-x.html
new file mode 100644
index 0000000..ae0a9a4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-dig-x.html
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.5.3. Looking Up a Hostname</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-dig.html" title="10.5. Using the dig Utility" /><link rel="prev" href="s2-bind-dig-a.html" title="10.5.2. Looking Up an IP Address" /><link rel="next" href="s1-bind-features.html" title="10.6. Advanced Features of BIND" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-dig-a.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-bi
nd-features.html"><strong>Next</strong></a></li></ul><div class="section" title="10.5.3. Looking Up a Hostname" id="s2-bind-dig-x"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-dig-x">10.5.3. Looking Up a Hostname</h3></div></div></div><div class="para">
+ To look up a hostname for a particular IP address, use the command in the following form:
+ </div><pre class="screen"><code class="command">dig</code> <code class="option">-x</code> <em class="replaceable"><code>address</code></em></pre><div class="para">
+ In <a class="xref" href="s2-bind-dig-x.html#example-bind-dig-x" title="Example 10.19. A Sample Hostname Lookup">Example 10.19, “A Sample Hostname Lookup”</a>, the <code class="command">dig</code> utility is used to display the hostname assigned to <code class="systemitem">192.0.32.10</code>.
+ </div><div class="example" title="Example 10.19. A Sample Hostname Lookup" id="example-bind-dig-x"><h6>Example 10.19. A Sample Hostname Lookup</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">dig -x 192.0.32.10</code>
+
+; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 <<>> -x 192.0.32.10
+;; global options: +cmd
+;; Got answer:
+;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29683
+;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 6
+
+;; QUESTION SECTION:
+;10.32.0.192.in-addr.arpa. IN PTR
+
+;; ANSWER SECTION:
+10.32.0.192.in-addr.arpa. 21600 IN PTR www.example.com.
+
+;; AUTHORITY SECTION:
+32.0.192.in-addr.arpa. 21600 IN NS b.iana-servers.org.
+32.0.192.in-addr.arpa. 21600 IN NS c.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS d.iana-servers.net.
+32.0.192.in-addr.arpa. 21600 IN NS ns.icann.org.
+32.0.192.in-addr.arpa. 21600 IN NS a.iana-servers.net.
+
+;; ADDITIONAL SECTION:
+a.iana-servers.net. 13688 IN A 192.0.34.43
+b.iana-servers.org. 5844 IN A 193.0.0.236
+b.iana-servers.org. 5844 IN AAAA 2001:610:240:2::c100:ec
+c.iana-servers.net. 12173 IN A 139.91.1.10
+c.iana-servers.net. 12173 IN AAAA 2001:648:2c30::1:10
+ns.icann.org. 12884 IN A 192.0.34.126
+
+;; Query time: 156 msec
+;; SERVER: 10.34.255.7#53(10.34.255.7)
+;; WHEN: Wed Aug 18 18:25:15 2010
+;; MSG SIZE rcvd: 310</pre></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-dig-a.html"><strong>Prev</strong>10.5.2. Looking Up an IP Address</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-bind-features.html"><strong>Next</strong>10.6. Advanced Features of BIND</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-dnssec.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-dnssec.html
new file mode 100644
index 0000000..e20b96c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-dnssec.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.6.4. DNS Security Extensions (DNSSEC)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-features.html" title="10.6. Advanced Features of BIND" /><link rel="prev" href="s2-bind-features-tsig.html" title="10.6.3. Transaction SIGnatures (TSIG)" /><link rel="next" href="s2-bind-features-ipv6.html" title="10.6.5. Internet Protocol version 6 (IPv6)" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-tsig.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="s2-bind-features-ipv6.html"><strong>Next</strong></a></li></ul><div class="section" title="10.6.4. DNS Security Extensions (DNSSEC)" id="s2-bind-features-dnssec"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-dnssec">10.6.4. DNS Security Extensions (DNSSEC)</h3></div></div></div><a id="id565077" class="indexterm"></a><div class="para">
+ <em class="firstterm">Domain Name System Security Extensions</em> (<em class="firstterm">DNSSEC</em>) provide origin authentication of DNS data, authenticated denial of existence, and data integrity. When a particular domain is marked as secure, the <code class="literal">SERFVAIL</code> response is returned for each resource record that fails the validation.
+ </div><a id="id565110" class="indexterm"></a><div class="para">
+ Note that to debug a DNSSEC-signed domain or a DNSSEC-aware resolver, you can use the <code class="command">dig</code> utility as described in <a class="xref" href="s1-bind-dig.html" title="10.5. Using the dig Utility">Section 10.5, “Using the <code class="command">dig</code> Utility”</a>. Useful options are <code class="option">+dnssec</code> (requests DNSSEC-related resource records by setting the DNSSEC OK bit), <code class="option">+cd</code> (tells recursive nameserver not to validate the response), and <code class="option">+bufsize=512</code> (changes the packet size to 512B to get through some firewalls).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-tsig.html"><strong>Prev</strong>10.6.3. Transaction SIGnatures (TSIG)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-features-ipv6.html"><strong>Next</strong>10.6.5. Internet Protocol version 6 (IPv6)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-ipv6.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-ipv6.html
new file mode 100644
index 0000000..e5745a4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-ipv6.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.6.5. Internet Protocol version 6 (IPv6)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-features.html" title="10.6. Advanced Features of BIND" /><link rel="prev" href="s2-bind-features-dnssec.html" title="10.6.4. DNS Security Extensions (DNSSEC)" /><link rel="next" href="s1-bind-mistakes.html" title="10.7. Common Mistakes to Avoid" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-dnssec.html"><strong>Prev</strong></a></li><li class
="next"><a accesskey="n" href="s1-bind-mistakes.html"><strong>Next</strong></a></li></ul><div class="section" title="10.6.5. Internet Protocol version 6 (IPv6)" id="s2-bind-features-ipv6"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-ipv6">10.6.5. Internet Protocol version 6 (IPv6)</h3></div></div></div><a id="id719091" class="indexterm"></a><div class="para">
+ <em class="firstterm">Internet Protocol version 6</em> (<em class="firstterm">IPv6</em>) is supported through the use of <code class="option">AAAA</code> resource records, and the <code class="option">listen-on-v6</code> directive as described in <a class="xref" href="s1-bind-namedconf.html#table-bind-namedconf-common-options" title="Table 10.3. Commonly used options">Table 10.3, “Commonly used options”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-dnssec.html"><strong>Prev</strong>10.6.4. DNS Security Extensions (DNSSEC)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-bind-mistakes.html"><strong>Next</strong>10.7. Common Mistakes to Avoid</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-ixfr.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-ixfr.html
new file mode 100644
index 0000000..5b6df62
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-ixfr.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.6.2. Incremental Zone Transfers (IXFR)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-features.html" title="10.6. Advanced Features of BIND" /><link rel="prev" href="s1-bind-features.html" title="10.6. Advanced Features of BIND" /><link rel="next" href="s2-bind-features-tsig.html" title="10.6.3. Transaction SIGnatures (TSIG)" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-features.html"><strong>Prev</strong></a></li><li class="next"><a
accesskey="n" href="s2-bind-features-tsig.html"><strong>Next</strong></a></li></ul><div class="section" title="10.6.2. Incremental Zone Transfers (IXFR)" id="s2-bind-features-ixfr"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-ixfr">10.6.2. Incremental Zone Transfers (IXFR)</h3></div></div></div><a id="id748823" class="indexterm"></a><div class="para">
+ <em class="firstterm">Incremental Zone Transfers</em> (<em class="firstterm">IXFR</em>) allow a secondary nameserver to only download the updated portions of a zone modified on a primary nameserver. Compared to the standard transfer process, this makes the notification and update process much more efficient.
+ </div><a id="id748852" class="indexterm"></a><div class="para">
+ Note that IXFR is only available when using dynamic updating to make changes to master zone records. If manually editing zone files to make changes, <em class="firstterm">Automatic Zone Transfer</em> (<em class="firstterm">AXFR</em>) is used.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-features.html"><strong>Prev</strong>10.6. Advanced Features of BIND</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-features-tsig.html"><strong>Next</strong>10.6.3. Transaction SIGnatures (TSIG)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-tsig.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-tsig.html
new file mode 100644
index 0000000..940c42a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-features-tsig.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.6.3. Transaction SIGnatures (TSIG)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-features.html" title="10.6. Advanced Features of BIND" /><link rel="prev" href="s2-bind-features-ixfr.html" title="10.6.2. Incremental Zone Transfers (IXFR)" /><link rel="next" href="s2-bind-features-dnssec.html" title="10.6.4. DNS Security Extensions (DNSSEC)" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-ixfr.html"><strong>Prev</strong></a>
</li><li class="next"><a accesskey="n" href="s2-bind-features-dnssec.html"><strong>Next</strong></a></li></ul><div class="section" title="10.6.3. Transaction SIGnatures (TSIG)" id="s2-bind-features-tsig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-features-tsig">10.6.3. Transaction SIGnatures (TSIG)</h3></div></div></div><a id="id565019" class="indexterm"></a><div class="para">
+ <em class="firstterm">Transaction SIGnatures</em> (TSIG) ensure that a shared secret key exists on both primary and secondary nameserver before allowing a transfer. This strengthens the standard IP address-based method of transfer authorization, since attackers would not only need to have access to the IP address to transfer the zone, but they would also need to know the secret key.
+ </div><div class="para">
+ Since version 9, BIND also supports <em class="firstterm">TKEY</em>, which is another shared secret key method of authorizing zone transfers.
+ </div><div class="important" title="Important: Secure the Transfer"><div class="admonition_header"><h2>Important: Secure the Transfer</h2></div><div class="admonition"><div class="para">
+ When communicating over an insecure network, do not rely on IP address-based authentication only.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-features-ixfr.html"><strong>Prev</strong>10.6.2. Incremental Zone Transfers (IXFR)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-features-dnssec.html"><strong>Next</strong>10.6.4. DNS Security Extensions (DNSSEC)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-namedconf-comm.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-namedconf-comm.html
new file mode 100644
index 0000000..7c56b22
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-namedconf-comm.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2.3. Comment Tags</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-namedconf.html" title="10.2. Configuring the named Service" /><link rel="prev" href="s2-bind-namedconf-state-other.html" title="10.2.2. Other Statement Types" /><link rel="next" href="s1-bind-zone.html" title="10.3. Editing Zone Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-namedconf-state-other.html"><strong>Prev</strong></a></li><li class="ne
xt"><a accesskey="n" href="s1-bind-zone.html"><strong>Next</strong></a></li></ul><div class="section" title="10.2.3. Comment Tags" id="s2-bind-namedconf-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-namedconf-comm">10.2.3. Comment Tags</h3></div></div></div><a id="id628922" class="indexterm"></a><div class="para">
+ Additionally to statements, the <code class="filename">/etc/named.conf</code> file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to a user. The following are valid comment tags:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="literal">//</code></span></dt><dd><div class="para">
+ Any text after the <code class="literal">//</code> characters to the end of the line is considered a comment. For example:
+ </div><pre class="screen">notify yes; // notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"><code class="literal">#</code></span></dt><dd><div class="para">
+ Any text after the <code class="literal">#</code> character to the end of the line is considered a comment. For example:
+ </div><pre class="screen">notify yes; # notify all secondary nameservers</pre></dd><dt class="varlistentry"><span class="term"><code class="literal">/*</code> and <code class="literal">*/</code></span></dt><dd><div class="para">
+ Any block of text enclosed in <code class="literal">/*</code> and <code class="literal">*/</code> is considered a comment. For example:
+ </div><pre class="screen">notify yes; /* notify all secondary nameservers */</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-namedconf-state-other.html"><strong>Prev</strong>10.2.2. Other Statement Types</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-bind-zone.html"><strong>Next</strong>10.3. Editing Zone Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-namedconf-state-other.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-namedconf-state-other.html
new file mode 100644
index 0000000..ec2d4b0
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-namedconf-state-other.html
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.2.2. Other Statement Types</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-namedconf.html" title="10.2. Configuring the named Service" /><link rel="prev" href="s1-bind-namedconf.html" title="10.2. Configuring the named Service" /><link rel="next" href="s2-bind-namedconf-comm.html" title="10.2.3. Comment Tags" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-namedconf.html"><strong>Prev</strong></a></li><li class="next"><a acces
skey="n" href="s2-bind-namedconf-comm.html"><strong>Next</strong></a></li></ul><div class="section" title="10.2.2. Other Statement Types" id="s2-bind-namedconf-state-other"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-namedconf-state-other">10.2.2. Other Statement Types</h3></div></div></div><div class="para">
+ The following types of statements are less commonly used in <code class="filename">/etc/named.conf</code>:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id479141" class="indexterm"></a>
+ <code class="option">controls</code> </span></dt><dd><div class="para">
+ The <code class="option">controls</code> statement allows you to configure various security requirements necessary to use the <code class="command">rndc</code> command to administer the <code class="systemitem">named</code> service.
+ </div><div class="para">
+ Refer to <a class="xref" href="s1-bind-rndc.html" title="10.4. Using the rndc Utility">Section 10.4, “Using the <code class="command">rndc</code> Utility”</a> for more information on the <code class="command">rndc</code> utility and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id803367" class="indexterm"></a>
+ <code class="option">key</code> </span></dt><dd><div class="para">
+ The <code class="option">key</code> statement allows you to define a particular key by name. Keys are used to authenticate various actions, such as secure updates or the use of the <code class="command">rndc</code> command. Two options are used with <code class="option">key</code>:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">algorithm <em class="replaceable"><code>algorithm-name</code></em></code> — The type of algorithm to be used (for example, <code class="literal">hmac-md5</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">secret "<em class="replaceable"><code>key-value</code></em>"</code> — The encrypted key.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref" href="s1-bind-rndc.html" title="10.4. Using the rndc Utility">Section 10.4, “Using the <code class="command">rndc</code> Utility”</a> for more information on the <code class="command">rndc</code> utility and its usage.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id484296" class="indexterm"></a>
+ <code class="option">logging</code> </span></dt><dd><div class="para">
+ The <code class="option">logging</code> statement allows you to use multiple types of logs, so called <em class="firstterm">channels</em>. By using the <code class="option">channel</code> option within the statement, you can construct a customized type of log with its own file name (<code class="option">file</code>), size limit (<code class="option">size</code>), versioning (<code class="option">version</code>), and level of importance (<code class="option">severity</code>). Once a customized channel is defined, a <code class="option">category</code> option is used to categorize the channel and begin logging when the <code class="systemitem">named</code> service is restarted.
+ </div><div class="para">
+ By default, <code class="systemitem">named</code> sends standard messages to the <code class="systemitem">rsyslog</code> daemon, which places them in <code class="filename">/var/log/messages</code>. Several standard channels are built into BIND with various severity levels, such as <code class="literal">default_syslog</code> (which handles informational logging messages) and <code class="literal">default_debug</code> (which specifically handles debugging messages). A default category, called <code class="literal">default</code>, uses the built-in channels to do normal logging without any special configuration.
+ </div><div class="para">
+ Customizing the logging process can be a very detailed process and is beyond the scope of this chapter. For information on creating custom BIND logs, refer to the <em class="citetitle">BIND 9 Administrator Reference Manual</em> referenced in <a class="xref" href="s1-bind-additional-resources.html#s2-bind-installed-docs" title="10.8.1. Installed Documentation">Section 10.8.1, “Installed Documentation”</a>.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id484745" class="indexterm"></a>
+ <code class="option">server</code> </span></dt><dd><div class="para">
+ The <code class="option">server</code> statement allows you to specify options that affect how the <code class="systemitem">named</code> service should respond to remote nameservers, especially with regard to notifications and zone transfers.
+ </div><div class="para">
+ The <code class="option">transfer-format</code> option controls the number of resource records that are sent with each message. It can be either <code class="literal">one-answer</code> (only one resource record), or <code class="literal">many-answers</code> (multiple resource records). Note that while the <code class="literal">many-answers</code> option is more efficient, it is not supported by older versions of BIND.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id734865" class="indexterm"></a>
+ <code class="option">trusted-keys</code> </span></dt><dd><div class="para">
+ The <code class="option">trusted-keys</code> statement allows you to specify assorted public keys used for secure DNS (DNSSEC). Refer to <a class="xref" href="s2-bind-features-dnssec.html" title="10.6.4. DNS Security Extensions (DNSSEC)">Section 10.6.4, “DNS Security Extensions (DNSSEC)”</a> for more information on this topic.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id734913" class="indexterm"></a>
+ <code class="option">view</code> </span></dt><dd><div class="para">
+ The <code class="option">view</code> statement allows you to create special views depending upon which network the host querying the nameserver is on. This allows some hosts to receive one answer regarding a zone while other hosts receive totally different information. Alternatively, certain zones may only be made available to particular trusted hosts while non-trusted hosts can only make queries for other zones.
+ </div><div class="para">
+ Multiple views can be used as long as their names are unique. The <code class="option">match-clients</code> option allows you to specify the IP addresses that apply to a particular view. If the <code class="option">options</code> statement is used within a view, it overrides the already configured global options. Finally, most <code class="option">view</code> statements contain multiple <code class="option">zone</code> statements that apply to the <code class="option">match-clients</code> list.
+ </div><div class="para">
+ Note that the order in which the <code class="option">view</code> statements are listed is important, as the first statement that matches a particular client's IP address is used. For more information on this topic, refer to <a class="xref" href="s1-bind-features.html#s2-bind-features-views" title="10.6.1. Multiple Views">Section 10.6.1, “Multiple Views”</a>.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-namedconf.html"><strong>Prev</strong>10.2. Configuring the named Service</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-namedconf-comm.html"><strong>Next</strong>10.2.3. Comment Tags</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-related-books.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-related-books.html
new file mode 100644
index 0000000..cee4023
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-related-books.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.8.3. Related Books</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-additional-resources.html" title="10.8. Additional Resources" /><link rel="prev" href="s2-bind-useful-websites.html" title="10.8.2. Useful Websites" /><link rel="next" href="ch-The_Apache_HTTP_Server.html" title="Chapter 11. The Apache HTTP Server" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-useful-websites.html"><strong>Prev</strong></a></li><li c
lass="next"><a accesskey="n" href="ch-The_Apache_HTTP_Server.html"><strong>Next</strong></a></li></ul><div class="section" title="10.8.3. Related Books" id="s2-bind-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-related-books">10.8.3. Related Books</h3></div></div></div><a id="id705200" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><em class="citetitle">DNS and BIND</em> by Paul Albitz and Cricket Liu; O'Reilly & Associates</span></dt><dd><div class="para">
+ A popular reference that explains both common and esoteric BIND configuration options, and provides strategies for securing a DNS server.
+ </div></dd><dt class="varlistentry"><span class="term"><em class="citetitle">The Concise Guide to DNS and BIND</em> by Nicolai Langfeldt; Que</span></dt><dd><div class="para">
+ Looks at the connection between multiple network services and BIND, with an emphasis on task-oriented, technical topics.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-useful-websites.html"><strong>Prev</strong>10.8.2. Useful Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-The_Apache_HTTP_Server.html"><strong>Next</strong>Chapter 11. The Apache HTTP Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-querylog.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-querylog.html
new file mode 100644
index 0000000..50657ae
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-querylog.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4.6. Enabling the Query Logging</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-rndc.html" title="10.4. Using the rndc Utility" /><link rel="prev" href="s2-bind-rndc-validation.html" title="10.4.5. Enabling the DNSSEC Validation" /><link rel="next" href="s1-bind-dig.html" title="10.5. Using the dig Utility" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-validation.html"><strong>Prev</strong></a></li><li class="next"><a access
key="n" href="s1-bind-dig.html"><strong>Next</strong></a></li></ul><div class="section" title="10.4.6. Enabling the Query Logging" id="s2-bind-rndc-querylog"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-querylog">10.4.6. Enabling the Query Logging</h3></div></div></div><div class="para">
+ To enable (or disable in case it is currently enabled) the query logging, run the following command:
+ </div><pre class="screen">~]# <code class="command">rndc querylog</code></pre><div class="para">
+ To check the current setting, use the <code class="command">status</code> command as described in <a class="xref" href="s2-bind-rndc-status.html" title="10.4.2. Checking the Service Status">Section 10.4.2, “Checking the Service Status”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-validation.html"><strong>Prev</strong>10.4.5. Enabling the DNSSEC Validation</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-bind-dig.html"><strong>Next</strong>10.5. Using the dig Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-reload.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-reload.html
new file mode 100644
index 0000000..3323306
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-reload.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4.3. Reloading the Configuration and Zones</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-rndc.html" title="10.4. Using the rndc Utility" /><link rel="prev" href="s2-bind-rndc-status.html" title="10.4.2. Checking the Service Status" /><link rel="next" href="s2-bind-rndc-sign.html" title="10.4.4. Updating Zone Keys" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-status.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n
" href="s2-bind-rndc-sign.html"><strong>Next</strong></a></li></ul><div class="section" title="10.4.3. Reloading the Configuration and Zones" id="s2-bind-rndc-reload"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-reload">10.4.3. Reloading the Configuration and Zones</h3></div></div></div><div class="para">
+ To reload both the configuration file and zones, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">rndc reload</code>
+server reload successful</pre><div class="para">
+ This will reload the zones while keeping all previously cached responses, so that you can make changes to the zone files without losing all stored name resolutions.
+ </div><div class="para">
+ To reload a single zone, specify its name after the <code class="command">reload</code> command, for example:
+ </div><pre class="screen">~]# <code class="command">rndc reload localhost</code>
+zone reload up-to-date</pre><div class="para">
+ Finally, to reload the configuration file and newly added zones only, type:
+ </div><pre class="screen">~]# <code class="command">rndc reconfig</code></pre><div class="note" title="Note: Modyfying Zones with Dynamic DNS"><div class="admonition_header"><h2>Note: Modyfying Zones with Dynamic DNS</h2></div><div class="admonition"><div class="para">
+ If you intend to manually modify a zone that uses Dynamic DNS (DDNS), make sure you run the <code class="command">freeze</code> command first:
+ </div><pre class="screen">~]# <code class="command">rndc freeze localhost</code></pre><div class="para">
+ Once you are finished, run the <code class="command">thaw</code> command to allow the DDNS again and reload the zone:
+ </div><pre class="screen">~]# <code class="command">rndc thaw localhost</code>
+The zone reload and thaw was successful.</pre></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-status.html"><strong>Prev</strong>10.4.2. Checking the Service Status</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-rndc-sign.html"><strong>Next</strong>10.4.4. Updating Zone Keys</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-sign.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-sign.html
new file mode 100644
index 0000000..c55f13c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-sign.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4.4. Updating Zone Keys</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-rndc.html" title="10.4. Using the rndc Utility" /><link rel="prev" href="s2-bind-rndc-reload.html" title="10.4.3. Reloading the Configuration and Zones" /><link rel="next" href="s2-bind-rndc-validation.html" title="10.4.5. Enabling the DNSSEC Validation" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-reload.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-bind-rndc-validation.html"><strong>Next</strong></a></li></ul><div class="section" title="10.4.4. Updating Zone Keys" id="s2-bind-rndc-sign"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-sign">10.4.4. Updating Zone Keys</h3></div></div></div><div class="para">
+ To update the DNSSEC keys and sign the zone, use the <code class="command">sign</code> command. For example:
+ </div><pre class="screen">~]# <code class="command">rndc sign localhost</code></pre><div class="para">
+ Note that to sign a zone with the above command, the <code class="option">auto-dnssec</code> option has to be set to <code class="literal">maintain</code> in the zone statement. For instance:
+ </div><pre class="screen">zone "localhost" IN {
+ type master;
+ file "named.localhost";
+ allow-update { none; };
+ auto-dnssec maintain;
+};</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-reload.html"><strong>Prev</strong>10.4.3. Reloading the Configuration and Zones</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-rndc-validation.html"><strong>Next</strong>10.4.5. Enabling the DNSSEC Validation</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-status.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-status.html
new file mode 100644
index 0000000..e9e2531
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-status.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4.2. Checking the Service Status</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-rndc.html" title="10.4. Using the rndc Utility" /><link rel="prev" href="s1-bind-rndc.html" title="10.4. Using the rndc Utility" /><link rel="next" href="s2-bind-rndc-reload.html" title="10.4.3. Reloading the Configuration and Zones" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-rndc.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n
" href="s2-bind-rndc-reload.html"><strong>Next</strong></a></li></ul><div class="section" title="10.4.2. Checking the Service Status" id="s2-bind-rndc-status"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-status">10.4.2. Checking the Service Status</h3></div></div></div><div class="para">
+ To check the current status of the <code class="systemitem">named</code> service, use the following command:
+ </div><pre class="screen">~]# <code class="command">rndc status</code>
+version: 9.7.0-P2-RedHat-9.7.0-5.P2.el6
+CPUs found: 1
+worker threads: 1
+number of zones: 16
+debug level: 0
+xfers running: 0
+xfers deferred: 0
+soa queries in progress: 0
+query logging is OFF
+recursive clients: 0/0/1000
+tcp clients: 0/100
+server is up and running</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-rndc.html"><strong>Prev</strong>10.4. Using the rndc Utility</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-rndc-reload.html"><strong>Next</strong>10.4.3. Reloading the Configuration and Zones</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-validation.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-validation.html
new file mode 100644
index 0000000..2930503
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-rndc-validation.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.4.5. Enabling the DNSSEC Validation</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-rndc.html" title="10.4. Using the rndc Utility" /><link rel="prev" href="s2-bind-rndc-sign.html" title="10.4.4. Updating Zone Keys" /><link rel="next" href="s2-bind-rndc-querylog.html" title="10.4.6. Enabling the Query Logging" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-sign.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n"
href="s2-bind-rndc-querylog.html"><strong>Next</strong></a></li></ul><div class="section" title="10.4.5. Enabling the DNSSEC Validation" id="s2-bind-rndc-validation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-rndc-validation">10.4.5. Enabling the DNSSEC Validation</h3></div></div></div><div class="para">
+ To enable the DNSSEC validation, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">rndc validation on</code></pre><div class="para">
+ Similarly, to disable this option, type:
+ </div><pre class="screen">~]# <code class="command">rndc validation off</code></pre><div class="para">
+ Refer to the <code class="option">options</code> statement described in <a class="xref" href="s1-bind-namedconf.html#s2-bind-namedconf-state" title="10.2.1. Common Statement Types">Section 10.2.1, “Common Statement Types”</a> for information on how configure this option in <code class="filename">/etc/named.conf</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-rndc-sign.html"><strong>Prev</strong>10.4.4. Updating Zone Keys</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-rndc-querylog.html"><strong>Next</strong>10.4.6. Enabling the Query Logging</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-useful-websites.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-useful-websites.html
new file mode 100644
index 0000000..a7ff640
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-useful-websites.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.8.2. Useful Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-additional-resources.html" title="10.8. Additional Resources" /><link rel="prev" href="s1-bind-additional-resources.html" title="10.8. Additional Resources" /><link rel="next" href="s2-bind-related-books.html" title="10.8.3. Related Books" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-additional-resources.html"><strong>Prev</strong></a></li><li class=
"next"><a accesskey="n" href="s2-bind-related-books.html"><strong>Next</strong></a></li></ul><div class="section" title="10.8.2. Useful Websites" id="s2-bind-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-useful-websites">10.8.2. Useful Websites</h3></div></div></div><a id="id705146" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><a href="http://www.isc.org/software/bind">http://www.isc.org/software/bind</a></span></dt><dd><div class="para">
+ The home page of the BIND project containing information about current releases as well as a PDF version of the <em class="citetitle">BIND 9 Administrator Reference Manual</em>.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-additional-resources.html"><strong>Prev</strong>10.8. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-related-books.html"><strong>Next</strong>10.8.3. Related Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-zone-comm.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-zone-comm.html
new file mode 100644
index 0000000..eb7c121
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-zone-comm.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.3.3. Comment Tags</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-zone.html" title="10.3. Editing Zone Files" /><link rel="prev" href="s3-bind-zone-rr.html" title="10.3.2. Common Resource Records" /><link rel="next" href="s2-bind-zone-examples.html" title="10.3.4. Example Usage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s3-bind-zone-rr.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-z
one-examples.html"><strong>Next</strong></a></li></ul><div class="section" title="10.3.3. Comment Tags" id="s2-bind-zone-comm"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-zone-comm">10.3.3. Comment Tags</h3></div></div></div><a id="id697093" class="indexterm"></a><div class="para">
+ Additionally to resource records and directives, a zone file can also contain comments. Comments are ignored by the <code class="systemitem">named</code> service, but can prove useful when providing additional information to the user. Any text after the semicolon character (that is, <code class="literal">;</code>) to the end of the line is considered a comment. For example:
+ </div><pre class="screen"> 604800 ; expire after 1 week</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s3-bind-zone-rr.html"><strong>Prev</strong>10.3.2. Common Resource Records</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-zone-examples.html"><strong>Next</strong>10.3.4. Example Usage</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-zone-examples.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-zone-examples.html
new file mode 100644
index 0000000..026d497
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-bind-zone-examples.html
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.3.4. Example Usage</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-zone.html" title="10.3. Editing Zone Files" /><link rel="prev" href="s2-bind-zone-comm.html" title="10.3.3. Comment Tags" /><link rel="next" href="s1-bind-rndc.html" title="10.4. Using the rndc Utility" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-zone-comm.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-bind-rndc.html"
><strong>Next</strong></a></li></ul><div class="section" title="10.3.4. Example Usage" id="s2-bind-zone-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-bind-zone-examples">10.3.4. Example Usage</h3></div></div></div><div class="para">
+ The following examples show the basic usage of zone files.
+ </div><div class="section" title="10.3.4.1. A Simple Zone File" id="s3-bind-zone-examples-basic"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-bind-zone-examples-basic">10.3.4.1. A Simple Zone File</h4></div></div></div><a id="id415526" class="indexterm"></a><div class="para">
+ <a class="xref" href="s2-bind-zone-examples.html#example-bind-zone-examples-basic" title="Example 10.15. A simple zone file">Example 10.15, “A simple zone file”</a> demonstrates the use of standard directives and <code class="command">SOA</code> values.
+ </div><div class="example" title="Example 10.15. A simple zone file" id="example-bind-zone-examples-basic"><h6>Example 10.15. A simple zone file</h6><div class="example-contents"><pre class="screen">$ORIGIN example.com.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+;
+ IN NS dns1.example.com.
+ IN NS dns2.example.com.
+dns1 IN A 10.0.1.1
+ IN AAAA aaaa:bbbb::1
+dns2 IN A 10.0.1.2
+ IN AAAA aaaa:bbbb::2
+;
+;
+@ IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.
+mail IN A 10.0.1.5
+ IN AAAA aaaa:bbbb::5
+mail2 IN A 10.0.1.6
+ IN AAAA aaaa:bbbb::6
+;
+;
+; This sample zone file illustrates sharing the same IP addresses
+; for multiple services:
+;
+services IN A 10.0.1.10
+ IN AAAA aaaa:bbbb::10
+ IN A 10.0.1.11
+ IN AAAA aaaa:bbbb::11
+
+ftp IN CNAME services.example.com.
+www IN CNAME services.example.com.
+;
+;</pre></div></div><br class="example-break" /><div class="para">
+ In this example, the authoritative nameservers are set as <code class="systemitem">dns1.example.com</code> and <code class="systemitem">dns2.example.com</code>, and are tied to the <code class="systemitem">10.0.1.1</code> and <code class="systemitem">10.0.1.2</code> IP addresses respectively using the <code class="command">A</code> record.
+ </div><div class="para">
+ The email servers configured with the <code class="command">MX</code> records point to <code class="systemitem">mail</code> and <code class="systemitem">mail2</code> via <code class="command">A</code> records. Since these names do not end in a trailing period (that is, the <code class="literal">.</code> character), the <code class="command">$ORIGIN</code> domain is placed after them, expanding them to <code class="systemitem">mail.example.com</code> and <code class="systemitem">mail2.example.com</code>.
+ </div><div class="para">
+ Services available at the standard names, such as <code class="systemitem">www.example.com</code> (<acronym class="acronym">WWW</acronym>), are pointed at the appropriate servers using the <code class="command">CNAME</code> record.
+ </div><div class="para">
+ This zone file would be called into service with a <code class="command">zone</code> statement in the <code class="filename">/etc/named.conf</code> similar to the following:
+ </div><pre class="screen">zone "example.com" IN {
+ type master;
+ file "example.com.zone";
+ allow-update { none; };
+};</pre></div><div class="section" title="10.3.4.2. A Reverse Name Resolution Zone File" id="s2-bind-configuration-zone-reverse"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-bind-configuration-zone-reverse">10.3.4.2. A Reverse Name Resolution Zone File</h4></div></div></div><a id="id842682" class="indexterm"></a><div class="para">
+ A reverse name resolution zone file is used to translate an IP address in a particular namespace into an fully qualified domain name (FQDN). It looks very similar to a standard zone file, except that the <code class="command">PTR</code> resource records are used to link the IP addresses to a fully qualified domain name as shown in <a class="xref" href="s2-bind-zone-examples.html#example-bind-zone-examples-reverse" title="Example 10.16. A reverse name resolution zone file">Example 10.16, “A reverse name resolution zone file”</a>.
+ </div><div class="example" title="Example 10.16. A reverse name resolution zone file" id="example-bind-zone-examples-reverse"><h6>Example 10.16. A reverse name resolution zone file</h6><div class="example-contents"><pre class="screen">$ORIGIN 1.0.10.in-addr.arpa.
+$TTL 86400
+@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day
+;
+@ IN NS dns1.example.com.
+;
+1 IN PTR dns1.example.com.
+2 IN PTR dns2.example.com.
+;
+5 IN PTR server1.example.com.
+6 IN PTR server2.example.com.
+;
+3 IN PTR ftp.example.com.
+4 IN PTR ftp.example.com.</pre></div></div><br class="example-break" /><div class="para">
+ In this example, IP addresses <code class="systemitem">10.0.1.1</code> through <code class="systemitem">10.0.1.6</code> are pointed to the corresponding fully qualified domain name.
+ </div><div class="para">
+ This zone file would be called into service with a <code class="option">zone</code> statement in the <code class="filename">/etc/named.conf</code> file similar to the following:
+ </div><pre class="screen">zone "1.0.10.in-addr.arpa" IN {
+ type master;
+ file "example.com.rr.zone";
+ allow-update { none; };
+};</pre><div class="para">
+ There is very little difference between this example and a standard <code class="command">zone</code> statement, except for the zone name. Note that a reverse name resolution zone requires the first three blocks of the IP address reversed followed by <code class="command">.in-addr.arpa</code>. This allows the single block of IP numbers used in the reverse name resolution zone file to be associated with the zone.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-bind-zone-comm.html"><strong>Prev</strong>10.3.3. Comment Tags</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-bind-rndc.html"><strong>Next</strong>10.4. Using the rndc Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-mta-fetchmail.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-mta-fetchmail.html
new file mode 100644
index 0000000..3c42ba8
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-mta-fetchmail.html
@@ -0,0 +1,116 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.3.3. Fetchmail</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-mta.html" title="12.3. Mail Transport Agents" /><link rel="prev" href="s2-email-mta-sendmail.html" title="12.3.2. Sendmail" /><link rel="next" href="s2-email-switchmail.html" title="12.3.4. Mail Transport Agent (MTA) Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-mta-sendmail.html"><strong>Prev</strong></a></li><li class="next"><a acce
sskey="n" href="s2-email-switchmail.html"><strong>Next</strong></a></li></ul><div class="section" title="12.3.3. Fetchmail" id="s2-email-mta-fetchmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-mta-fetchmail">12.3.3. Fetchmail</h3></div></div></div><a id="id690247" class="indexterm"></a><a id="id690262" class="indexterm"></a><div class="para">
+ Fetchmail is an MTA which retrieves email from remote servers and delivers it to the local MTA. Many users appreciate the ability to separate the process of downloading their messages located on a remote server from the process of reading and organizing their email in an MUA. Designed with the needs of dial-up users in mind, Fetchmail connects and quickly downloads all of the email messages to the mail spool file using any number of protocols, including <code class="systemitem">POP3</code> and <code class="systemitem">IMAP</code>. It can even forward email messages to an <code class="systemitem">SMTP</code> server, if necessary.
+ </div><div class="note" title="Note: Installing the fetchmail package"><div class="admonition_header"><h2>Note: Installing the <span class="package">fetchmail</span> package</h2></div><div class="admonition"><div class="para">
+ In order to use <span class="application"><strong>Fetchmail</strong></span>, first ensure the <span class="package">fetchmail</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install fetchmail</code></pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ Fetchmail is configured for each user through the use of a <code class="filename">.fetchmailrc</code> file in the user's home directory. If it does not already exist, create the <code class="filename">.fetchmailrc</code> file in your home directory
+ </div><div class="para">
+ Using preferences in the <code class="filename">.fetchmailrc</code> file, Fetchmail checks for email on a remote server and downloads it. It then delivers it to port <code class="constant">25</code> on the local machine, using the local MTA to place the email in the correct user's spool file. If Procmail is available, it is launched to filter the email and place it in a mailbox so that it can be read by an MUA.
+ </div><div class="section" title="12.3.3.1. Fetchmail Configuration Options" id="s3-email-mda-fetchmail-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-configuration">12.3.3.1. Fetchmail Configuration Options</h4></div></div></div><a id="id822028" class="indexterm"></a><a id="id822042" class="indexterm"></a><div class="para">
+ Although it is possible to pass all necessary options on the command line to check for email on a remote server when executing Fetchmail, using a <code class="filename">.fetchmailrc</code> file is much easier. Place any desired configuration options in the <code class="filename">.fetchmailrc</code> file for those options to be used each time the <code class="command">fetchmail</code> command is issued. It is possible to override these at the time Fetchmail is run by specifying that option on the command line.
+ </div><div class="para">
+ A user's <code class="filename">.fetchmailrc</code> file contains three classes of configuration options:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>global options</em></span> — Gives Fetchmail instructions that control the operation of the program or provide settings for every connection that checks for email.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>server options</em></span> — Specifies necessary information about the server being polled, such as the hostname, as well as preferences for specific email servers, such as the port to check or number of seconds to wait before timing out. These options affect every user using that server.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>user options</em></span> — Contains information, such as username and password, necessary to authenticate and check for email using a specified email server.
+ </div></li></ul></div><div class="para">
+ Global options appear at the top of the <code class="filename">.fetchmailrc</code> file, followed by one or more server options, each of which designate a different email server that Fetchmail should check. User options follow server options for each user account checking that email server. Like server options, multiple user options may be specified for use with a particular server as well as to check multiple email accounts on the same server.
+ </div><div class="para">
+ Server options are called into service in the <code class="filename">.fetchmailrc</code> file by the use of a special option verb, <code class="command">poll</code> or <code class="command">skip</code>, that precedes any of the server information. The <code class="command">poll</code> action tells Fetchmail to use this server option when it is run, which checks for email using the specified user options. Any server options after a <code class="command">skip</code> action, however, are not checked unless this server's hostname is specified when Fetchmail is invoked. The <code class="command">skip</code> option is useful when testing configurations in the <code class="filename">.fetchmailrc</code> file because it only checks skipped servers when specifically invoked, and does not affect any currently working configurations.
+ </div><div class="para">
+ The following is a sample example of a <code class="filename">.fetchmailrc</code> file:
+ </div><pre class="screen">set postmaster "user1"
+set bouncemail
+
+poll pop.domain.com proto pop3
+ user 'user1' there with password 'secret' is user1 here
+
+poll mail.domain2.com
+ user 'user5' there with password 'secret2' is user1 here
+ user 'user7' there with password 'secret3' is user1 here</pre><div class="para">
+ In this example, the global options specify that the user is sent email as a last resort (<code class="command">postmaster</code> option) and all email errors are sent to the postmaster instead of the sender (<code class="command">bouncemail</code> option). The <code class="command">set</code> action tells Fetchmail that this line contains a global option. Then, two email servers are specified, one set to check using <code class="systemitem">POP3</code>, the other for trying various protocols to find one that works. Two users are checked using the second server option, but all email found for any user is sent to <code class="command">user1</code>'s mail spool. This allows multiple mailboxes to be checked on multiple servers, while appearing in a single MUA inbox. Each user's specific information begins with the <code class="command">user</code> action.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Users are not required to place their password in the <code class="filename">.fetchmailrc</code> file. Omitting the <code class="command">with password '<password>'</code> section causes Fetchmail to ask for a password when it is launched.
+ </div></div></div><div class="para">
+ Fetchmail has numerous global, server, and local options. Many of these options are rarely used or only apply to very specific situations. The <code class="filename">fetchmail</code> man page explains each option in detail, but the most common ones are listed in the following three sections.
+ </div></div><div class="section" title="12.3.3.2. Global Options" id="s3-email-mda-fetchmail-configuration-global"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-configuration-global">12.3.3.2. Global Options</h4></div></div></div><a id="id455731" class="indexterm"></a><a id="id455749" class="indexterm"></a><div class="para">
+ Each global option should be placed on a single line after a <code class="command">set</code> action.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">daemon <em class="replaceable"><code><seconds></code></em> </code> — Specifies daemon-mode, where Fetchmail stays in the background. Replace <em class="replaceable"><code><seconds></code></em> with the number of seconds Fetchmail is to wait before polling the server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">postmaster</code> — Specifies a local user to send mail to in case of delivery problems.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">syslog</code> — Specifies the log file for errors and status messages. By default, this is <code class="filename">/var/log/maillog</code>.
+ </div></li></ul></div></div><div class="section" title="12.3.3.3. Server Options" id="s3-email-mda-fetchmail-configuration-server"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-configuration-server">12.3.3.3. Server Options</h4></div></div></div><a id="id765782" class="indexterm"></a><a id="id765800" class="indexterm"></a><div class="para">
+ Server options must be placed on their own line in <code class="filename">.fetchmailrc</code> after a <code class="command">poll</code> or <code class="command">skip</code> action.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">auth <em class="replaceable"><code><auth-type></code></em> </code> — Replace <em class="replaceable"><code><auth-type></code></em> with the type of authentication to be used. By default, <code class="command">password</code> authentication is used, but some protocols support other types of authentication, including <code class="command">kerberos_v5</code>, <code class="command">kerberos_v4</code>, and <code class="command">ssh</code>. If the <code class="command">any</code> authentication type is used, Fetchmail first tries methods that do not require a password, then methods that mask the password, and finally attempts to send the password unencrypted to authenticate to the server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">interval <em class="replaceable"><code><number></code></em> </code> — Polls the specified server every <code class="command"><em class="replaceable"><code><number></code></em> </code> of times that it checks for email on all configured servers. This option is generally used for email servers where the user rarely receives messages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">port <em class="replaceable"><code><port-number></code></em> </code> — Replace <em class="replaceable"><code><port-number></code></em> with the port number. This value overrides the default port number for the specified protocol.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">proto <em class="replaceable"><code><protocol></code></em> </code> — Replace <em class="replaceable"><code><protocol></code></em> with the protocol, such as <code class="command">pop3</code> or <code class="command">imap</code>, to use when checking for messages on the server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">timeout <em class="replaceable"><code><seconds></code></em> </code> — Replace <em class="replaceable"><code><seconds></code></em> with the number of seconds of server inactivity after which Fetchmail gives up on a connection attempt. If this value is not set, a default of <code class="command">300</code> seconds is assumed.
+ </div></li></ul></div></div><div class="section" title="12.3.3.4. User Options" id="s3-email-fetchmail-configuration-user"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-fetchmail-configuration-user">12.3.3.4. User Options</h4></div></div></div><a id="id526899" class="indexterm"></a><a id="id526918" class="indexterm"></a><div class="para">
+ User options may be placed on their own lines beneath a server option or on the same line as the server option. In either case, the defined options must follow the <code class="command">user</code> option (defined below).
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">fetchall</code> — Orders Fetchmail to download all messages in the queue, including messages that have already been viewed. By default, Fetchmail only pulls down new messages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">fetchlimit <em class="replaceable"><code><number></code></em> </code> — Replace <em class="replaceable"><code><number></code></em> with the number of messages to be retrieved before stopping.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">flush</code> — Deletes all previously viewed messages in the queue before retrieving new messages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">limit <em class="replaceable"><code><max-number-bytes></code></em> </code> — Replace <em class="replaceable"><code><max-number-bytes></code></em> with the maximum size in bytes that messages are allowed to be when retrieved by Fetchmail. This option is useful with slow network links, when a large message takes too long to download.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">password '<em class="replaceable"><code><password></code></em>'</code> — Replace <em class="replaceable"><code><password></code></em> with the user's password.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">preconnect "<em class="replaceable"><code><command></code></em>"</code> — Replace <em class="replaceable"><code><command></code></em> with a command to be executed before retrieving messages for the user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">postconnect "<em class="replaceable"><code><command></code></em>"</code> — Replace <em class="replaceable"><code><command></code></em> with a command to be executed after retrieving messages for the user.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">ssl</code> — Activates SSL encryption.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">user "<em class="replaceable"><code><username></code></em>"</code> — Replace <em class="replaceable"><code><username></code></em> with the username used by Fetchmail to retrieve messages. <span class="emphasis"><em>This option must precede all other user options.</em></span>
+ </div></li></ul></div></div><div class="section" title="12.3.3.5. Fetchmail Command Options" id="s3-email-mda-fetchmail-commands"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-commands">12.3.3.5. Fetchmail Command Options</h4></div></div></div><a id="id703530" class="indexterm"></a><div class="para">
+ Most Fetchmail options used on the command line when executing the <code class="command">fetchmail</code> command mirror the <code class="filename">.fetchmailrc</code> configuration options. In this way, Fetchmail may be used with or without a configuration file. These options are not used on the command line by most users because it is easier to leave them in the <code class="filename">.fetchmailrc</code> file.
+ </div><div class="para">
+ There may be times when it is desirable to run the <code class="command">fetchmail</code> command with other options for a particular purpose. It is possible to issue command options to temporarily override a <code class="filename">.fetchmailrc</code> setting that is causing an error, as any options specified at the command line override configuration file options.
+ </div></div><div class="section" title="12.3.3.6. Informational or Debugging Options" id="s3-email-mda-fetchmail-commands-info"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-commands-info">12.3.3.6. Informational or Debugging Options</h4></div></div></div><a id="id455849" class="indexterm"></a><div class="para">
+ Certain options used after the <code class="command">fetchmail</code> command can supply important information.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">--configdump</code> — Displays every possible option based on information from <code class="filename">.fetchmailrc</code> and Fetchmail defaults. No email is retrieved for any users when using this option.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-s</code> — Executes Fetchmail in silent mode, preventing any messages, other than errors, from appearing after the <code class="command">fetchmail</code> command.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-v</code> — Executes Fetchmail in verbose mode, displaying every communication between Fetchmail and remote email servers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-V</code> — Displays detailed version information, lists its global options, and shows settings to be used with each user, including the email protocol and authentication method. No email is retrieved for any users when using this option.
+ </div></li></ul></div></div><div class="section" title="12.3.3.7. Special Options" id="s3-email-mda-fetchmail-commands-special"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-fetchmail-commands-special">12.3.3.7. Special Options</h4></div></div></div><a id="id755428" class="indexterm"></a><div class="para">
+ These options are occasionally useful for overriding defaults often found in the <code class="filename">.fetchmailrc</code> file.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-a</code> — Fetchmail downloads all messages from the remote email server, whether new or previously viewed. By default, Fetchmail only downloads new messages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-k</code> — Fetchmail leaves the messages on the remote email server after downloading them. This option overrides the default behavior of deleting messages after downloading them.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-l <em class="replaceable"><code><max-number-bytes></code></em> </code> — Fetchmail does not download any messages over a particular size and leaves them on the remote email server.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">--quit</code> — Quits the Fetchmail daemon process.
+ </div></li></ul></div><div class="para">
+ More commands and <code class="filename">.fetchmailrc</code> options can be found in the <code class="command">fetchmail</code> man page.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-mta-sendmail.html"><strong>Prev</strong>12.3.2. Sendmail</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-email-switchmail.html"><strong>Next</strong>12.3.4. Mail Transport Agent (MTA) Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-mta-sendmail.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-mta-sendmail.html
new file mode 100644
index 0000000..dd0c28c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-mta-sendmail.html
@@ -0,0 +1,131 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.3.2. Sendmail</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-mta.html" title="12.3. Mail Transport Agents" /><link rel="prev" href="s1-email-mta.html" title="12.3. Mail Transport Agents" /><link rel="next" href="s2-email-mta-fetchmail.html" title="12.3.3. Fetchmail" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-mta.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-email-mta-fetchm
ail.html"><strong>Next</strong></a></li></ul><div class="section" title="12.3.2. Sendmail" id="s2-email-mta-sendmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-mta-sendmail">12.3.2. Sendmail</h3></div></div></div><a id="id467181" class="indexterm"></a><a id="id467195" class="indexterm"></a><div class="para">
+ Sendmail's core purpose, like other MTAs, is to safely transfer email among hosts, usually using the <code class="systemitem">SMTP</code> protocol. However, Sendmail is highly configurable, allowing control over almost every aspect of how email is handled, including the protocol used. Many system administrators elect to use Sendmail as their MTA due to its power and scalability.
+ </div><div class="section" title="12.3.2.1. Purpose and Limitations" id="s3-email-mta-sendmail-purpose"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-sendmail-purpose">12.3.2.1. Purpose and Limitations</h4></div></div></div><a id="id467228" class="indexterm"></a><a id="id467242" class="indexterm"></a><div class="para">
+ It is important to be aware of what Sendmail is and what it can do, as opposed to what it is not. In these days of monolithic applications that fulfill multiple roles, Sendmail may seem like the only application needed to run an email server within an organization. Technically, this is true, as Sendmail can spool mail to each users' directory and deliver outbound mail for users. However, most users actually require much more than simple email delivery. Users usually want to interact with their email using an MUA, that uses <code class="systemitem">POP</code> or <code class="systemitem">IMAP</code>, to download their messages to their local machine. Or, they may prefer a Web interface to gain access to their mailbox. These other applications can work in conjunction with Sendmail, but they actually exist for different reasons and can operate separately from one another.
+ </div><div class="para">
+ It is beyond the scope of this section to go into all that Sendmail should or could be configured to do. With literally hundreds of different options and rule sets, entire volumes have been dedicated to helping explain everything that can be done and how to fix things that go wrong. Refer to the <a class="xref" href="s1-email-additional-resources.html" title="12.6. Additional Resources">Section 12.6, “Additional Resources”</a> for a list of Sendmail resources.
+ </div><div class="para">
+ This section reviews the files installed with Sendmail by default and reviews basic configuration changes, including how to stop unwanted email (spam) and how to extend Sendmail with the <em class="firstterm">Lightweight Directory Access Protocol (LDAP)</em>.
+ </div></div><div class="section" title="12.3.2.2. The Default Sendmail Installation" id="s3-email-mta-sendmail-default"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-sendmail-default">12.3.2.2. The Default Sendmail Installation</h4></div></div></div><a id="id731271" class="indexterm"></a><div class="para">
+ In order to use Sendmail, first ensure the <span class="package">sendmail</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install sendmail</code></pre><div class="para">
+ In order to configure Sendmail, ensure the <span class="package">sendmail-cf</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install sendmail-cf</code></pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div><div class="para">
+ Before using Sendmail, the default MTA has to be switched from Postfix. For more information how to switch the default MTA refer to <a class="xref" href="s1-email-mta.html" title="12.3. Mail Transport Agents">Section 12.3, “Mail Transport Agents”</a>.
+ </div><div class="para">
+ The Sendmail executable is <code class="filename">/usr/sbin/sendmail</code>.
+ </div><div class="para">
+ Sendmail's lengthy and detailed configuration file is <code class="filename">/etc/mail/sendmail.cf</code>. Avoid editing the <code class="filename">sendmail.cf</code> file directly. To make configuration changes to Sendmail, edit the <code class="filename">/etc/mail/sendmail.mc</code> file, back up the original <code class="filename">/etc/mail/sendmail.cf</code>, and use the following alternatives to generate a new configuration file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Use the included makefile in <code class="filename">/etc/mail/</code> (<code class="command">~]# make all -C /etc/mail/</code>) to create a new <code class="filename">/etc/mail/sendmail.cf</code> configuration file. All other generated files in <code class="filename">/etc/mail</code> (db files) will be regenerated if needed. The old makemap commands are still usable. The make command will automatically be used by <code class="command">service sendmail start | restart | reload</code>.
+ </div></li><li class="listitem"><div class="para">
+ Alternatively you may use the <code class="command">m4</code> macro processor to create a new <code class="filename">/etc/mail/sendmail.cf</code>. The <code class="command">m4</code> macro processor is not installed by default. Before using it to create <code class="filename">/etc/mail/sendmail.cf</code>, install the <span class="package">m4</span> package as root:
+ </div><pre class="screen">~]# <code class="command">yum install m4</code>
+</pre></li></ul></div><div class="para">
+ More information on configuring Sendmail can be found in <a class="xref" href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes" title="12.3.2.3. Common Sendmail Configuration Changes">Section 12.3.2.3, “Common Sendmail Configuration Changes”</a>.
+ </div><div class="para">
+ Various Sendmail configuration files are installed in the <code class="filename">/etc/mail/</code> directory including:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">access</code> — Specifies which systems can use Sendmail for outbound email.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">domaintable</code> — Specifies domain name mapping.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">local-host-names</code> — Specifies aliases for the host.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">mailertable</code> — Specifies instructions that override routing for particular domains.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">virtusertable</code> — Specifies a domain-specific form of aliasing, allowing multiple virtual domains to be hosted on one machine.
+ </div></li></ul></div><div class="para">
+ Several of the configuration files in <code class="filename">/etc/mail/</code>, such as <code class="filename">access</code>, <code class="filename">domaintable</code>, <code class="filename">mailertable</code> and <code class="filename">virtusertable</code>, must actually store their information in database files before Sendmail can use any configuration changes. To include any changes made to these configurations in their database files, run the following command, as root:
+ </div><pre class="screen">~]# <code class="command">makemap hash /etc/mail/<em class="replaceable"><code><name></code></em> < /etc/mail/<em class="replaceable"><code><name></code></em></code>
+</pre><div class="para">
+ where <em class="replaceable"><code><name></code></em> represents the name of the configuration file to be updated. You may also restart the <code class="systemitem">sendmail</code> service for the changes to take effect by running:
+ </div><pre class="screen">~]# <code class="command">service sendmail restart</code>
+</pre><div class="para">
+ For example, to have all emails addressed to the <code class="filename">example.com</code> domain delivered to <code class="email"><a class="email" href="mailto:bob at other-example.com">bob at other-example.com</a></code>
+ , add the following line to the <code class="filename">virtusertable</code> file:
+ </div><pre class="screen">
+<code class="command">@example.com bob at other-example.com</code>
+</pre><div class="para">
+ To finalize the change, the <code class="filename">virtusertable.db</code> file must be updated:
+ </div><pre class="screen">~]# <code class="command">makemap hash /etc/mail/virtusertable < /etc/mail/virtusertable</code>
+</pre><div class="para">
+ Sendmail will create an updated <code class="filename">virtusertable.db</code> file containing the new configuration.
+ </div></div><div class="section" title="12.3.2.3. Common Sendmail Configuration Changes" id="s3-email-mta-sendmail-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-sendmail-changes">12.3.2.3. Common Sendmail Configuration Changes</h4></div></div></div><a id="id774274" class="indexterm"></a><a id="id774288" class="indexterm"></a><div class="para">
+ When altering the Sendmail configuration file, it is best not to edit an existing file, but to generate an entirely new <code class="filename">/etc/mail/sendmail.cf</code> file.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Before changing the <code class="filename">sendmail.cf</code> file, it is a good idea to create a backup copy.
+ </div></div></div><div class="para">
+ To add the desired functionality to Sendmail, edit the <code class="filename">/etc/mail/sendmail.mc</code> file as root. Once you are finished, restart the <code class="systemitem">sendmail</code> service and, if the <span class="package">m4</span> package is installed, the <code class="command">m4</code> macro processor will automatically generate a new <code class="filename">sendmail.cf</code> configuration file:
+ </div><pre class="screen">~]# <code class="command">service sendmail restart</code>
+</pre><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The default <code class="filename">sendmail.cf</code> file does not allow Sendmail to accept network connections from any host other than the local computer. To configure Sendmail as a server for other clients, edit the <code class="filename">/etc/mail/sendmail.mc</code> file, and either change the address specified in the <code class="command">Addr=</code> option of the <code class="command">DAEMON_OPTIONS</code> directive from <code class="command">127.0.0.1</code> to the IP address of an active network device or comment out the <code class="command">DAEMON_OPTIONS</code> directive all together by placing <code class="command">dnl</code> at the beginning of the line. When finished, regenerate <code class="filename">/etc/mail/sendmail.cf</code> by restarting the service
+ </div><pre class="screen">~]# <code class="command">service sendmail restart</code>
+</pre></div></div><div class="para">
+ The default configuration which ships with Fedora works for most <code class="systemitem">SMTP</code>-only sites. However, it does not work for <em class="firstterm">UUCP</em> (<em class="firstterm">UNIX-to-UNIX Copy Protocol</em>) sites. If using UUCP mail transfers, the <code class="filename">/etc/mail/sendmail.mc</code> file must be reconfigured and a new <code class="filename">/etc/mail/sendmail.cf</code> file must be generated.
+ </div><div class="para">
+ Consult the <code class="filename">/usr/share/sendmail-cf/README</code> file before editing any files in the directories under the <code class="filename">/usr/share/sendmail-cf</code> directory, as they can affect the future configuration of the <code class="filename">/etc/mail/sendmail.cf</code> file.
+ </div></div><div class="section" title="12.3.2.4. Masquerading" id="s3-email-sendmail-changes-masquerading"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-sendmail-changes-masquerading">12.3.2.4. Masquerading</h4></div></div></div><a id="id454569" class="indexterm"></a><a id="id454584" class="indexterm"></a><div class="para">
+ One common Sendmail configuration is to have a single machine act as a mail gateway for all machines on the network. For instance, a company may want to have a machine called <code class="computeroutput">mail.example.com</code> that handles all of their email and assigns a consistent return address to all outgoing mail.
+ </div><div class="para">
+ In this situation, the Sendmail server must masquerade the machine names on the company network so that their return address is <code class="computeroutput">user at example.com</code> instead of <code class="computeroutput">user at host.example.com</code>.
+ </div><div class="para">
+ To do this, add the following lines to <code class="filename">/etc/mail/sendmail.mc</code>:
+ </div><pre class="screen">
+FEATURE(always_add_domain)dnl
+FEATURE(`masquerade_entire_domain')dnl
+FEATURE(`masquerade_envelope')dnl
+FEATURE(`allmasquerade')dnl
+MASQUERADE_AS(`bigcorp.com.')dnl
+MASQUERADE_DOMAIN(`bigcorp.com.')dnl
+MASQUERADE_AS(bigcorp.com)dnl
+</pre><div class="para">
+ After generating a new <code class="filename">sendmail.cf</code> using the <code class="command">m4</code> macro processor, this configuration makes all mail from inside the network appear as if it were sent from <code class="computeroutput">bigcorp.com</code>.
+ </div></div><div class="section" title="12.3.2.5. Stopping Spam" id="s3-email-sendmail-stopping-spam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-sendmail-stopping-spam">12.3.2.5. Stopping Spam</h4></div></div></div><a id="id454662" class="indexterm"></a><div class="para">
+ Email spam can be defined as unnecessary and unwanted email received by a user who never requested the communication. It is a disruptive, costly, and widespread abuse of Internet communication standards.
+ </div><div class="para">
+ Sendmail makes it relatively easy to block new spamming techniques being employed to send junk email. It even blocks many of the more usual spamming methods by default. Main anti-spam features available in sendmail are <em class="firstterm">header checks</em>, <em class="firstterm">relaying denial</em> (default from version 8.9), <em class="firstterm">access database and sender information checks</em>.
+ </div><div class="para">
+ For example, forwarding of <code class="systemitem">SMTP</code> messages, also called relaying, has been disabled by default since Sendmail version 8.9. Before this change occurred, Sendmail directed the mail host (<code class="filename">x.edu</code>) to accept messages from one party (<code class="filename">y.com</code>) and sent them to a different party (<code class="filename">z.net</code>). Now, however, Sendmail must be configured to permit any domain to relay mail through the server. To configure relay domains, edit the <code class="filename">/etc/mail/relay-domains</code> file and restart Sendmail
+ </div><pre class="screen">~]# <code class="command">service sendmail restart</code>
+</pre><div class="para">
+ However, many times users are bombarded with spam from other servers throughout the Internet. In these instances, Sendmail's access control features available through the <code class="filename">/etc/mail/access</code> file can be used to prevent connections from unwanted hosts. The following example illustrates how this file can be used to both block and specifically allow access to the Sendmail server:
+ </div><pre class="screen">
+<code class="command">badspammer.com ERROR:550 "Go away and do not spam us anymore" tux.badspammer.com OK 10.0 RELAY</code>
+</pre><div class="para">
+ This example shows that any email sent from <code class="filename">badspammer.com</code> is blocked with a 550 RFC-821 compliant error code, with a message sent back to the spammer. Email sent from the <code class="filename">tux.badspammer.com</code> sub-domain, is accepted. The last line shows that any email sent from the 10.0.*.* network can be relayed through the mail server.
+ </div><div class="para">
+ Because the <code class="filename">/etc/mail/access.db</code> file is a database, use the <code class="command">makemap</code> command to update any changes. Do this using the following command as root:
+ </div><pre class="screen">~]# <code class="command">makemap hash /etc/mail/access < /etc/mail/access</code>
+</pre><div class="para">
+ Message header analysis allows you to reject mail based on header contents. <code class="systemitem">SMTP</code> servers store information about an email's journey in the message header. As the message travels from one MTA to another, each puts in a <code class="literal">Received</code> header above all the other <code class="literal">Received</code> headers. It is important to note that this information may be altered by spammers.
+ </div><div class="para">
+ The above examples only represent a small part of what Sendmail can do in terms of allowing or blocking access. Refer to the <code class="filename">/usr/share/sendmail-cf/README</code> for more information and examples.
+ </div><div class="para">
+ Since Sendmail calls the Procmail MDA when delivering mail, it is also possible to use a spam filtering program, such as SpamAssassin, to identify and file spam for users. Refer to <a class="xref" href="s2-email-procmail-recipes.html#s3-email-mda-spam" title="12.4.2.6. Spam Filters">Section 12.4.2.6, “Spam Filters”</a> for more information about using SpamAssassin.
+ </div></div><div class="section" title="12.3.2.6. Using Sendmail with LDAP" id="s3-email-mta-sendmail-ldap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mta-sendmail-ldap">12.3.2.6. Using Sendmail with LDAP</h4></div></div></div><a id="id512709" class="indexterm"></a><div class="para">
+ Using <code class="systemitem">LDAP</code> is a very quick and powerful way to find specific information about a particular user from a much larger group. For example, an <code class="systemitem">LDAP</code> server can be used to look up a particular email address from a common corporate directory by the user's last name. In this kind of implementation, <code class="systemitem">LDAP</code> is largely separate from Sendmail, with <code class="systemitem">LDAP</code> storing the hierarchical user information and Sendmail only being given the result of <code class="systemitem">LDAP</code> queries in pre-addressed email messages.
+ </div><div class="para">
+ However, Sendmail supports a much greater integration with <code class="systemitem">LDAP</code>, where it uses <code class="systemitem">LDAP</code> to replace separately maintained files, such as <code class="filename">/etc/aliases</code> and <code class="filename">/etc/mail/virtusertables</code>, on different mail servers that work together to support a medium- to enterprise-level organization. In short, <code class="systemitem">LDAP</code> abstracts the mail routing level from Sendmail and its separate configuration files to a powerful <code class="systemitem">LDAP</code> cluster that can be leveraged by many different applications.
+ </div><div class="para">
+ The current version of Sendmail contains support for <code class="systemitem">LDAP</code>. To extend the Sendmail server using <code class="systemitem">LDAP</code>, first get an <code class="systemitem">LDAP</code> server, such as <span class="application"><strong>OpenLDAP</strong></span>, running and properly configured. Then edit the <code class="filename">/etc/mail/sendmail.mc</code> to include the following:
+ </div><pre class="screen">LDAPROUTE_DOMAIN('<em class="replaceable"><code>yourdomain.com</code></em>')dnl
+FEATURE('ldap_routing')dnl
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This is only for a very basic configuration of Sendmail with <code class="systemitem">LDAP</code>. The configuration can differ greatly from this depending on the implementation of <code class="systemitem">LDAP</code>, especially when configuring several Sendmail machines to use a common <code class="systemitem">LDAP</code> server.
+ </div><div class="para">
+ Consult <code class="filename">/usr/share/sendmail-cf/README</code> for detailed <code class="systemitem">LDAP</code> routing configuration instructions and examples.
+ </div></div></div><div class="para">
+ Next, recreate the <code class="filename">/etc/mail/sendmail.cf</code> file by running the <code class="command">m4</code> macro processor and again restarting Sendmail. Refer to <a class="xref" href="s2-email-mta-sendmail.html#s3-email-mta-sendmail-changes" title="12.3.2.3. Common Sendmail Configuration Changes">Section 12.3.2.3, “Common Sendmail Configuration Changes”</a> for instructions.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-mta.html"><strong>Prev</strong>12.3. Mail Transport Agents</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-email-mta-fetchmail.html"><strong>Next</strong>12.3.3. Fetchmail</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-procmail-recipes.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-procmail-recipes.html
new file mode 100644
index 0000000..8678dc1
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-procmail-recipes.html
@@ -0,0 +1,147 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.4.2. Procmail Recipes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-mda.html" title="12.4. Mail Delivery Agents" /><link rel="prev" href="s1-email-mda.html" title="12.4. Mail Delivery Agents" /><link rel="next" href="s1-email-mua.html" title="12.5. Mail User Agents" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-mda.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-email-mua.html"><strong
>Next</strong></a></li></ul><div class="section" title="12.4.2. Procmail Recipes" id="s2-email-procmail-recipes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-procmail-recipes">12.4.2. Procmail Recipes</h3></div></div></div><a id="id476250" class="indexterm"></a><div class="para">
+ New users often find the construction of recipes the most difficult part of learning to use Procmail. To some extent, this is understandable, as recipes do their message matching using <em class="firstterm">regular expressions</em>, which is a particular format used to specify qualifications for a matching string. However, regular expressions are not very difficult to construct and even less difficult to understand when read. Additionally, the consistency of the way Procmail recipes are written, regardless of regular expressions, makes it easy to learn by example. To see example Procmail recipes, refer to <a class="xref" href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-examples" title="12.4.2.5. Recipe Examples">Section 12.4.2.5, “Recipe Examples”</a>.
+ </div><div class="para">
+ Procmail recipes take the following form:
+ </div><pre class="screen">:0<em class="replaceable"><code><flags>: <lockfile-name></code></em> * <em class="replaceable"><code><special-condition-character></code></em>
+ <em class="replaceable"><code><condition-1></code></em> * <em class="replaceable"><code><special-condition-character></code></em>
+ <em class="replaceable"><code><condition-2></code></em> * <em class="replaceable"><code><special-condition-character></code></em>
+ <em class="replaceable"><code><condition-N></code></em>
+ <em class="replaceable"><code><special-action-character></code></em>
+ <em class="replaceable"><code><action-to-perform></code></em>
+</pre><div class="para">
+ The first two characters in a Procmail recipe are a colon and a zero. Various flags can be placed after the zero to control how Procmail processes the recipe. A colon after the <code class="command"><em class="replaceable"><code><flags></code></em> </code> section specifies that a lockfile is created for this message. If a lockfile is created, the name can be specified by replacing <code class="command"><em class="replaceable"><code><lockfile-name></code></em> </code>.
+ </div><div class="para">
+ A recipe can contain several conditions to match against the message. If it has no conditions, every message matches the recipe. Regular expressions are placed in some conditions to facilitate message matching. If multiple conditions are used, they must all match for the action to be performed. Conditions are checked based on the flags set in the recipe's first line. Optional special characters placed after the asterisk character (<code class="command">*</code>) can further control the condition.
+ </div><div class="para">
+ The <code class="command"><em class="replaceable"><code><action-to-perform></code></em></code> argument specifies the action taken when the message matches one of the conditions. There can only be one action per recipe. In many cases, the name of a mailbox is used here to direct matching messages into that file, effectively sorting the email. Special action characters may also be used before the action is specified. Refer to <a class="xref" href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-special" title="12.4.2.4. Special Conditions and Actions">Section 12.4.2.4, “Special Conditions and Actions”</a> for more information.
+ </div><div class="section" title="12.4.2.1. Delivering vs. Non-Delivering Recipes" id="s2-email-procmail-recipes-delivering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s2-email-procmail-recipes-delivering">12.4.2.1. Delivering vs. Non-Delivering Recipes</h4></div></div></div><a id="id699898" class="indexterm"></a><a id="id699917" class="indexterm"></a><div class="para">
+ The action used if the recipe matches a particular message determines whether it is considered a <em class="firstterm">delivering</em> or <em class="firstterm">non-delivering</em> recipe. A delivering recipe contains an action that writes the message to a file, sends the message to another program, or forwards the message to another email address. A non-delivering recipe covers any other actions, such as a <em class="firstterm">nesting block</em>. A nesting block is a set of actions, contained in braces <code class="command">{</code> <code class="command">}</code>, that are performed on messages which match the recipe's conditions. Nesting blocks can be nested inside one another, providing greater control for identifying and performing actions on messages.
+ </div><div class="para">
+ When messages match a delivering recipe, Procmail performs the specified action and stops comparing the message against any other recipes. Messages that match non-delivering recipes continue to be compared against other recipes.
+ </div></div><div class="section" title="12.4.2.2. Flags" id="s3-email-procmail-recipes-flags"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-procmail-recipes-flags">12.4.2.2. Flags</h4></div></div></div><a id="id566372" class="indexterm"></a><div class="para">
+ Flags are essential to determine how or if a recipe's conditions are compared to a message. The following flags are commonly used:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">A</code> — Specifies that this recipe is only used if the previous recipe without an <code class="command">A</code> or <code class="command">a</code> flag also matched this message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">a</code> — Specifies that this recipe is only used if the previous recipe with an <code class="command">A</code> or <code class="command">a</code> flag also matched this message <span class="emphasis"><em>and</em></span> was successfully completed.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">B</code> — Parses the body of the message and looks for matching conditions.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">b</code> — Uses the body in any resulting action, such as writing the message to a file or forwarding it. This is the default behavior.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">c</code> — Generates a carbon copy of the email. This is useful with delivering recipes, since the required action can be performed on the message and a copy of the message can continue being processed in the <code class="filename">rc</code> files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">D</code> — Makes the <code class="command">egrep</code> comparison case-sensitive. By default, the comparison process is not case-sensitive.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">E</code> — While similar to the <code class="command">A</code> flag, the conditions in the recipe are only compared to the message if the immediately preceding the recipe without an <code class="command">E</code> flag did not match. This is comparable to an <em class="wordasword">else</em> action.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">e</code> — The recipe is compared to the message only if the action specified in the immediately preceding recipe fails.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">f</code> — Uses the pipe as a filter.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">H</code> — Parses the header of the message and looks for matching conditions. This is the default behavior.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">h</code> — Uses the header in a resulting action. This is the default behavior.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">w</code> — Tells Procmail to wait for the specified filter or program to finish, and reports whether or not it was successful before considering the message filtered.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">W</code> — Is identical to <code class="command">w</code> except that "Program failure" messages are suppressed.
+ </div></li></ul></div><div class="para">
+ For a detailed list of additional flags, refer to the <code class="filename">procmailrc</code> man page.
+ </div></div><div class="section" title="12.4.2.3. Specifying a Local Lockfile" id="s3-email-procmail-recipes-lockfile"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-procmail-recipes-lockfile">12.4.2.3. Specifying a Local Lockfile</h4></div></div></div><a id="id692491" class="indexterm"></a><div class="para">
+ Lockfiles are very useful with Procmail to ensure that more than one process does not try to alter a message simultaneously. Specify a local lockfile by placing a colon (<code class="command">:</code>) after any flags on a recipe's first line. This creates a local lockfile based on the destination file name plus whatever has been set in the <code class="command">LOCKEXT</code> global environment variable.
+ </div><div class="para">
+ Alternatively, specify the name of the local lockfile to be used with this recipe after the colon.
+ </div></div><div class="section" title="12.4.2.4. Special Conditions and Actions" id="s3-email-procmail-recipes-special"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-procmail-recipes-special">12.4.2.4. Special Conditions and Actions</h4></div></div></div><a id="id692538" class="indexterm"></a><a id="id692557" class="indexterm"></a><div class="para">
+ Special characters used before Procmail recipe conditions and actions change the way they are interpreted.
+ </div><div class="para">
+ The following characters may be used after the asterisk character (<code class="command">*</code>) at the beginning of a recipe's condition line:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">!</code> — In the condition line, this character inverts the condition, causing a match to occur only if the condition does not match the message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command"><</code> — Checks if the message is under a specified number of bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">></code> — Checks if the message is over a specified number of bytes.
+ </div></li></ul></div><div class="para">
+ The following characters are used to perform special actions:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">!</code> — In the action line, this character tells Procmail to forward the message to the specified email addresses.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">$</code> — Refers to a variable set earlier in the <code class="filename">rc</code> file. This is often used to set a common mailbox that is referred to by various recipes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">|</code> — Starts a specified program to process the message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">{</code> and <code class="command">}</code> — Constructs a nesting block, used to contain additional recipes to apply to matching messages.
+ </div></li></ul></div><div class="para">
+ If no special character is used at the beginning of the action line, Procmail assumes that the action line is specifying the mailbox in which to write the message.
+ </div></div><div class="section" title="12.4.2.5. Recipe Examples" id="s3-email-procmail-recipes-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-procmail-recipes-examples">12.4.2.5. Recipe Examples</h4></div></div></div><a id="id741218" class="indexterm"></a><div class="para">
+ Procmail is an extremely flexible program, but as a result of this flexibility, composing Procmail recipes from scratch can be difficult for new users.
+ </div><div class="para">
+ The best way to develop the skills to build Procmail recipe conditions stems from a strong understanding of regular expressions combined with looking at many examples built by others. A thorough explanation of regular expressions is beyond the scope of this section. The structure of Procmail recipes and useful sample Procmail recipes can be found at various places on the Internet (such as <a href="http://www.iki.fi/era/procmail/links.html">http://www.iki.fi/era/procmail/links.html</a>). The proper use and adaptation of regular expressions can be derived by viewing these recipe examples. In addition, introductory information about basic regular expression rules can be found in the <code class="filename">grep</code> man page.
+ </div><div class="para">
+ The following simple examples demonstrate the basic structure of Procmail recipes and can provide the foundation for more intricate constructions.
+ </div><div class="para">
+ A basic recipe may not even contain conditions, as is illustrated in the following example:
+ </div><pre class="screen">:0: new-mail.spool</pre><div class="para">
+ The first line specifies that a local lockfile is to be created but does not specify a name, so Procmail uses the destination file name and appends the value specified in the <code class="command">LOCKEXT</code> environment variable. No condition is specified, so every message matches this recipe and is placed in the single spool file called <code class="filename">new-mail.spool</code>, located within the directory specified by the <code class="command">MAILDIR</code> environment variable. An MUA can then view messages in this file.
+ </div><div class="para">
+ A basic recipe, such as this, can be placed at the end of all <code class="filename">rc</code> files to direct messages to a default location.
+ </div><div class="para">
+ The following example matched messages from a specific email address and throws them away.
+ </div><pre class="screen">:0 * ^From: spammer at domain.com /dev/null</pre><div class="para">
+ With this example, any messages sent by <code class="computeroutput">spammer at domain.com</code> are sent to the <code class="filename">/dev/null</code> device, deleting them.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Be certain that rules are working as intended before sending messages to <code class="filename">/dev/null</code> for permanent deletion. If a recipe inadvertently catches unintended messages, and those messages disappear, it becomes difficult to troubleshoot the rule.
+ </div><div class="para">
+ A better solution is to point the recipe's action to a special mailbox, which can be checked from time to time to look for false positives. Once satisfied that no messages are accidentally being matched, delete the mailbox and direct the action to send the messages to <code class="filename">/dev/null</code>.
+ </div></div></div><div class="para">
+ The following recipe grabs email sent from a particular mailing list and places it in a specified folder.
+ </div><pre class="screen">:0: * ^(From|Cc|To).*tux-lug tuxlug</pre><div class="para">
+ Any messages sent from the <code class="computeroutput">tux-lug at domain.com</code> mailing list are placed in the <code class="filename">tuxlug</code> mailbox automatically for the MUA. Note that the condition in this example matches the message if it has the mailing list's email address on the <code class="computeroutput">From</code>, <code class="computeroutput">Cc</code>, or <code class="computeroutput">To</code> lines.
+ </div><div class="para">
+ Consult the many Procmail online resources available in <a class="xref" href="s1-email-additional-resources.html" title="12.6. Additional Resources">Section 12.6, “Additional Resources”</a> for more detailed and powerful recipes.
+ </div></div><div class="section" title="12.4.2.6. Spam Filters" id="s3-email-mda-spam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-email-mda-spam">12.4.2.6. Spam Filters</h4></div></div></div><a id="id716075" class="indexterm"></a><a id="id716094" class="indexterm"></a><a id="id716108" class="indexterm"></a><div class="para">
+ Because it is called by Sendmail, Postfix, and Fetchmail upon receiving new emails, Procmail can be used as a powerful tool for combating spam.
+ </div><div class="para">
+ This is particularly true when Procmail is used in conjunction with SpamAssassin. When used together, these two applications can quickly identify spam emails, and sort or destroy them.
+ </div><div class="para">
+ SpamAssassin uses header analysis, text analysis, blacklists, a spam-tracking database, and self-learning Bayesian spam analysis to quickly and accurately identify and tag spam.
+ </div><div class="note" title="Note: Installing the spamassassin package"><div class="admonition_header"><h2>Note: Installing the <span class="package">spamassassin</span> package</h2></div><div class="admonition"><div class="para">
+ In order to use <span class="application"><strong>SpamAssassin</strong></span>, first ensure the <span class="package">spamassassin</span> package is installed on your system by running, as root:
+ </div><pre class="screen">~]# <code class="command">yum install spamassassin</code></pre><div class="para">
+ For more information on installing packages with Yum, refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a>.
+ </div></div></div><div class="para">
+ The easiest way for a local user to use SpamAssassin is to place the following line near the top of the <code class="filename">~/.procmailrc</code> file:
+ </div><pre class="screen">
+<code class="command">INCLUDERC=/etc/mail/spamassassin/spamassassin-default.rc</code>
+</pre><div class="para">
+ The <code class="filename">/etc/mail/spamassassin/spamassassin-default.rc</code> contains a simple Procmail rule that activates SpamAssassin for all incoming email. If an email is determined to be spam, it is tagged in the header as such and the title is prepended with the following pattern:
+ </div><pre class="screen">*****SPAM*****</pre><div class="para">
+ The message body of the email is also prepended with a running tally of what elements caused it to be diagnosed as spam.
+ </div><div class="para">
+ To file email tagged as spam, a rule similar to the following can be used:
+ </div><pre class="screen">
+<code class="command">:0 Hw * ^X-Spam-Status: Yes spam</code>
+</pre><div class="para">
+ This rule files all email tagged in the header as spam into a mailbox called <code class="filename">spam</code>.
+ </div><div class="para">
+ Since SpamAssassin is a Perl script, it may be necessary on busy servers to use the binary SpamAssassin daemon (<code class="systemitem">spamd</code>) and the client application (<span class="application"><strong>spamc</strong></span>). Configuring SpamAssassin this way, however, requires root access to the host.
+ </div><div class="para">
+ To start the <code class="systemitem">spamd</code> daemon, type the following command:
+ </div><pre class="screen">~]# <code class="command">service spamassassin start</code>
+</pre><div class="para">
+ To start the SpamAssassin daemon when the system is booted, use an initscript utility, such as the <span class="application"><strong>Services Configuration Tool</strong></span> (<code class="command">system-config-services</code>), to turn on the <code class="computeroutput">spamassassin</code> service. Refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for more information about starting and stopping services.
+ </div><div class="para">
+ To configure Procmail to use the SpamAssassin client application instead of the Perl script, place the following line near the top of the <code class="filename">~/.procmailrc</code> file. For a system-wide configuration, place it in <code class="filename">/etc/procmailrc</code>:
+ </div><pre class="screen">
+<code class="command">INCLUDERC=/etc/mail/spamassassin/spamassassin-spamc.rc</code>
+</pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-mda.html"><strong>Prev</strong>12.4. Mail Delivery Agents</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-email-mua.html"><strong>Next</strong>12.5. Mail User Agents</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-related-books.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-related-books.html
new file mode 100644
index 0000000..068a911
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-related-books.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.6.3. Related Books</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-additional-resources.html" title="12.6. Additional Resources" /><link rel="prev" href="s2-email-useful-websites.html" title="12.6.2. Useful Websites" /><link rel="next" href="pt-sysconfig.html" title="Part III. System Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-useful-websites.html"><strong>Prev</strong></a></li><li class="next"><a
accesskey="n" href="pt-sysconfig.html"><strong>Next</strong></a></li></ul><div class="section" title="12.6.3. Related Books" id="s2-email-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-related-books">12.6.3. Related Books</h3></div></div></div><a id="id713890" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="citetitle">Sendmail Milters: A Guide for Fighting Spam</em> by Bryan Costales and Marcia Flynt; Addison-Wesley — A good Sendmail guide that can help you customise your mail filters.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Sendmail</em> by Bryan Costales with Eric Allman et al; O'Reilly & Associates — A good Sendmail reference written with the assistance of the original creator of Delivermail and Sendmail.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Removing the Spam: Email Processing and Filtering</em> by Geoff Mulligan; Addison-Wesley Publishing Company — A volume that looks at various methods used by email administrators using established tools, such as Sendmail and Procmail, to manage spam problems.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Internet Email Protocols: A Developer's Guide</em> by Kevin Johnson; Addison-Wesley Publishing Company — Provides a very thorough review of major email protocols and the security they provide.
+ </div></li><li class="listitem"><div class="para">
+ <em class="citetitle">Managing IMAP</em> by Dianna Mullet and Kevin Mullet; O'Reilly & Associates — Details the steps required to configure an IMAP server.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-useful-websites.html"><strong>Prev</strong>12.6.2. Useful Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pt-sysconfig.html"><strong>Next</strong>Part III. System Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-switchmail.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-switchmail.html
new file mode 100644
index 0000000..bcb0060
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-switchmail.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.3.4. Mail Transport Agent (MTA) Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-mta.html" title="12.3. Mail Transport Agents" /><link rel="prev" href="s2-email-mta-fetchmail.html" title="12.3.3. Fetchmail" /><link rel="next" href="s1-email-mda.html" title="12.4. Mail Delivery Agents" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-mta-fetchmail.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-email-m
da.html"><strong>Next</strong></a></li></ul><div class="section" title="12.3.4. Mail Transport Agent (MTA) Configuration" id="s2-email-switchmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-switchmail">12.3.4. Mail Transport Agent (MTA) Configuration</h3></div></div></div><a id="id755537" class="indexterm"></a><a id="id450613" class="indexterm"></a><a id="id450628" class="indexterm"></a><a id="id450646" class="indexterm"></a><a id="id450670" class="indexterm"></a><a id="id450680" class="indexterm"></a><div class="para">
+ A <em class="firstterm">Mail Transport Agent</em> (MTA) is essential for sending email. A <em class="firstterm">Mail User Agent</em> (MUA) such as <span class="application"><strong>Evolution</strong></span>, <span class="application"><strong>Thunderbird</strong></span>, and <span class="application"><strong>Mutt</strong></span>, is used to read and compose email. When a user sends an email from an MUA, the message is handed off to the MTA, which sends the message through a series of MTAs until it reaches its destination.
+ </div><div class="para">
+ Even if a user does not plan to send email from the system, some automated tasks or system programs might use the <code class="command">/bin/mail</code> command to send email containing log messages to the root user of the local system.
+ </div><a id="id558099" class="indexterm"></a><a id="id558109" class="indexterm"></a><div class="para">
+ Fedora 14 provides two MTAs: Postfix and Sendmail. If both are installed, Postfix is the default MTA.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-mta-fetchmail.html"><strong>Prev</strong>12.3.3. Fetchmail</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-email-mda.html"><strong>Next</strong>12.4. Mail Delivery Agents</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-types-mda.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-types-mda.html
new file mode 100644
index 0000000..809d341
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-types-mda.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.2.2. Mail Delivery Agent</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-types.html" title="12.2. Email Program Classifications" /><link rel="prev" href="s1-email-types.html" title="12.2. Email Program Classifications" /><link rel="next" href="s2-email-types-mua.html" title="12.2.3. Mail User Agent" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-types.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" h
ref="s2-email-types-mua.html"><strong>Next</strong></a></li></ul><div class="section" title="12.2.2. Mail Delivery Agent" id="s2-email-types-mda"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-types-mda">12.2.2. Mail Delivery Agent</h3></div></div></div><a id="id788147" class="indexterm"></a><a id="id788165" class="indexterm"></a><a id="id788180" class="indexterm"></a><div class="para">
+ A <em class="firstterm">Mail Delivery Agent</em> (<em class="firstterm">MDA</em>) is invoked by the MTA to file incoming email in the proper user's mailbox. In many cases, the MDA is actually a <em class="firstterm">Local Delivery Agent</em> (<em class="firstterm">LDA</em>), such as <code class="command">mail</code> or Procmail.
+ </div><div class="para">
+ Any program that actually handles a message for delivery to the point where it can be read by an email client application can be considered an MDA. For this reason, some MTAs (such as Sendmail and Postfix) can fill the role of an MDA when they append new email messages to a local user's mail spool file. In general, MDAs do not transport messages between systems nor do they provide a user interface; MDAs distribute and sort messages on the local machine for an email client application to access.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-types.html"><strong>Prev</strong>12.2. Email Program Classifications</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-email-types-mua.html"><strong>Next</strong>12.2.3. Mail User Agent</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-types-mua.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-types-mua.html
new file mode 100644
index 0000000..3bc39fe
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-types-mua.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.2.3. Mail User Agent</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-types.html" title="12.2. Email Program Classifications" /><link rel="prev" href="s2-email-types-mda.html" title="12.2.2. Mail Delivery Agent" /><link rel="next" href="s1-email-mta.html" title="12.3. Mail Transport Agents" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-types-mda.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hre
f="s1-email-mta.html"><strong>Next</strong></a></li></ul><div class="section" title="12.2.3. Mail User Agent" id="s2-email-types-mua"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-types-mua">12.2.3. Mail User Agent</h3></div></div></div><a id="id725822" class="indexterm"></a><a id="id725841" class="indexterm"></a><a id="id725855" class="indexterm"></a><div class="para">
+ A <em class="firstterm">Mail User Agent</em> (<em class="firstterm">MUA</em>) is synonymous with an email client application. An MUA is a program that, at the very least, allows a user to read and compose email messages. Many MUAs are capable of retrieving messages via the <code class="systemitem">POP</code> or <code class="systemitem">IMAP</code> protocols, setting up mailboxes to store messages, and sending outbound messages to an MTA.
+ </div><div class="para">
+ MUAs may be graphical, such as <span class="application"><strong>Evolution</strong></span>, or have simple text-based interfaces, such as <span class="application"><strong>pine</strong></span>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-types-mda.html"><strong>Prev</strong>12.2.2. Mail Delivery Agent</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-email-mta.html"><strong>Next</strong>12.3. Mail Transport Agents</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-useful-websites.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-useful-websites.html
new file mode 100644
index 0000000..0e9b939
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-email-useful-websites.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>12.6.2. Useful Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-email-additional-resources.html" title="12.6. Additional Resources" /><link rel="prev" href="s1-email-additional-resources.html" title="12.6. Additional Resources" /><link rel="next" href="s2-email-related-books.html" title="12.6.3. Related Books" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-additional-resources.html"><strong>Prev</strong></a></li><li cl
ass="next"><a accesskey="n" href="s2-email-related-books.html"><strong>Next</strong></a></li></ul><div class="section" title="12.6.2. Useful Websites" id="s2-email-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-email-useful-websites">12.6.2. Useful Websites</h3></div></div></div><a id="id798171" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.sendmail.org/">http://www.sendmail.org/</a> — Offers a thorough technical breakdown of Sendmail features, documentation and configuration examples.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.sendmail.com/">http://www.sendmail.com/</a> — Contains news, interviews and articles concerning Sendmail, including an expanded view of the many options available.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.postfix.org/">http://www.postfix.org/</a> — The Postfix project home page contains a wealth of information about Postfix. The mailing list is a particularly good place to look for information.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://fetchmail.berlios.de/">http://fetchmail.berlios.de/</a> — The home page for Fetchmail, featuring an online manual, and a thorough FAQ.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.procmail.org/">http://www.procmail.org/</a> — The home page for Procmail with links to assorted mailing lists dedicated to Procmail as well as various FAQ documents.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://partmaps.org/era/procmail/mini-faq.html">http://partmaps.org/era/procmail/mini-faq.html</a> — An excellent Procmail FAQ, offers troubleshooting tips, details about file locking, and the use of wildcard characters.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.uwasa.fi/~ts/info/proctips.html">http://www.uwasa.fi/~ts/info/proctips.html</a> — Contains dozens of tips that make using Procmail much easier. Includes instructions on how to test <code class="filename">.procmailrc</code> files and use Procmail scoring to decide if a particular action should be taken.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.spamassassin.org/">http://www.spamassassin.org/</a> — The official site of the SpamAssassin project.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-email-additional-resources.html"><strong>Prev</strong>12.6. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-email-related-books.html"><strong>Next</strong>12.6.3. Related Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-backtrace.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-backtrace.html
new file mode 100644
index 0000000..56bef25
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-backtrace.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>24.2.2. Displaying a Backtrace</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-kdump-crash.html" title="24.2. Analyzing the Core Dump" /><link rel="prev" href="s1-kdump-crash.html" title="24.2. Analyzing the Core Dump" /><link rel="next" href="s2-kdump-crash-processes.html" title="24.2.3. Displaying a Process Status" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kdump-crash.html"><strong>Prev</strong></a></li><li class="next"><a accesskey
="n" href="s2-kdump-crash-processes.html"><strong>Next</strong></a></li></ul><div class="section" title="24.2.2. Displaying a Backtrace" id="s2-kdump-crash-backtrace"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-crash-backtrace">24.2.2. Displaying a Backtrace</h3></div></div></div><a id="id546788" class="indexterm"></a><div class="para">
+ To display the kernel stack trace, type the <code class="command">bt</code> command at the interactive prompt. You can use <code class="command">bt <em class="replaceable"><code>pid</code></em></code> to display the backtrace of the selected process.
+ </div><div class="example" title="Example 24.5. Displaying the kernel stack trace" id="ex-kdump-crash-backtrace"><h6>Example 24.5. Displaying the kernel stack trace</h6><div class="example-contents"><pre class="screen">crash> <code class="command">bt</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ #0 [ef4dbdcc] crash_kexec at c0494922
+ #1 [ef4dbe20] oops_end at c080e402
+ #2 [ef4dbe34] no_context at c043089d
+ #3 [ef4dbe58] bad_area at c0430b26
+ #4 [ef4dbe6c] do_page_fault at c080fb9b
+ #5 [ef4dbee4] error_code (via page_fault) at c080d809
+ EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000 EBP: 00000000
+ DS: 007b ESI: c0a09ca0 ES: 007b EDI: 00000286 GS: 00e0
+ CS: 0060 EIP: c068124f ERR: ffffffff EFLAGS: 00010096
+ #6 [ef4dbf18] sysrq_handle_crash at c068124f
+ #7 [ef4dbf24] __handle_sysrq at c0681469
+ #8 [ef4dbf48] write_sysrq_trigger at c068150a
+ #9 [ef4dbf54] proc_reg_write at c0569ec2
+#10 [ef4dbf74] vfs_write at c051de4e
+#11 [ef4dbf94] sys_write at c051e8cc
+#12 [ef4dbfb0] system_call at c0409ad5
+ EAX: ffffffda EBX: 00000001 ECX: b7776000 EDX: 00000002
+ DS: 007b ESI: 00000002 ES: 007b EDI: b7776000
+ SS: 007b ESP: bfcb2088 EBP: bfcb20b4 GS: 0033
+ CS: 0073 EIP: 00edc416 ERR: 00000004 EFLAGS: 00000246</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help bt</code> for more information on the command usage.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kdump-crash.html"><strong>Prev</strong>24.2. Analyzing the Core Dump</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-kdump-crash-processes.html"><strong>Next</strong>24.2.3. Displaying a Process Status</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-files.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-files.html
new file mode 100644
index 0000000..2c7ea88
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-files.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>24.2.5. Displaying Open Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-kdump-crash.html" title="24.2. Analyzing the Core Dump" /><link rel="prev" href="s2-kdump-crash-memory.html" title="24.2.4. Displaying Virtual Memory Information" /><link rel="next" href="s1-kdump-resources.html" title="24.3. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-memory.html"><strong>Prev</strong></a></li><li class="nex
t"><a accesskey="n" href="s1-kdump-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="24.2.5. Displaying Open Files" id="s2-kdump-crash-files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-crash-files">24.2.5. Displaying Open Files</h3></div></div></div><a id="id468701" class="indexterm"></a><div class="para">
+ To display information about open files, type the <code class="command">files</code> command at the interactive prompt. You can use <code class="command">files <em class="replaceable"><code>pid</code></em></code> to display files opened by the selected process.
+ </div><div class="example" title="Example 24.8. Displaying information about open files of the current context" id="ex-kdump-crash-files"><h6>Example 24.8. Displaying information about open files of the current context</h6><div class="example-contents"><pre class="screen">crash> <code class="command">files</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ROOT: / CWD: /root
+ FD FILE DENTRY INODE TYPE PATH
+ 0 f734f640 eedc2c6c eecd6048 CHR /pts/0
+ 1 efade5c0 eee14090 f00431d4 REG /proc/sysrq-trigger
+ 2 f734f640 eedc2c6c eecd6048 CHR /pts/0
+ 10 f734f640 eedc2c6c eecd6048 CHR /pts/0
+255 f734f640 eedc2c6c eecd6048 CHR /pts/0</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help files</code> for more information on the command usage.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-memory.html"><strong>Prev</strong>24.2.4. Displaying Virtual Memory Information</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kdump-resources.html"><strong>Next</strong>24.3. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-memory.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-memory.html
new file mode 100644
index 0000000..d607901
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-memory.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>24.2.4. Displaying Virtual Memory Information</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-kdump-crash.html" title="24.2. Analyzing the Core Dump" /><link rel="prev" href="s2-kdump-crash-processes.html" title="24.2.3. Displaying a Process Status" /><link rel="next" href="s2-kdump-crash-files.html" title="24.2.5. Displaying Open Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-processes.html"><strong>Prev</strong></a></li><li class="ne
xt"><a accesskey="n" href="s2-kdump-crash-files.html"><strong>Next</strong></a></li></ul><div class="section" title="24.2.4. Displaying Virtual Memory Information" id="s2-kdump-crash-memory"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-crash-memory">24.2.4. Displaying Virtual Memory Information</h3></div></div></div><a id="id468618" class="indexterm"></a><div class="para">
+ To display basic virtual memory information, type the <code class="command">vm</code> command at the interactive prompt. You can use <code class="command">vm <em class="replaceable"><code>pid</code></em></code> to display information on the selected process.
+ </div><div class="example" title="Example 24.7. Displaying virtual memory information of the current context" id="ex-kdump-crash-memory"><h6>Example 24.7. Displaying virtual memory information of the current context</h6><div class="example-contents"><pre class="screen">crash> <code class="command">vm</code>
+PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash"
+ MM PGD RSS TOTAL_VM
+f19b5900 ef9c6000 1648k 5084k
+ VMA START END FLAGS FILE
+f1bb0310 242000 260000 8000875 /lib/ld-2.12.so
+f26af0b8 260000 261000 8100871 /lib/ld-2.12.so
+efbc275c 261000 262000 8100873 /lib/ld-2.12.so
+efbc2a18 268000 3ed000 8000075 /lib/libc-2.12.so
+efbc23d8 3ed000 3ee000 8000070 /lib/libc-2.12.so
+efbc2888 3ee000 3f0000 8100071 /lib/libc-2.12.so
+efbc2cd4 3f0000 3f1000 8100073 /lib/libc-2.12.so
+efbc243c 3f1000 3f4000 100073
+efbc28ec 3f6000 3f9000 8000075 /lib/libdl-2.12.so
+efbc2568 3f9000 3fa000 8100071 /lib/libdl-2.12.so
+efbc2f2c 3fa000 3fb000 8100073 /lib/libdl-2.12.so
+f26af888 7e6000 7fc000 8000075 /lib/libtinfo.so.5.7
+f26aff2c 7fc000 7ff000 8100073 /lib/libtinfo.so.5.7
+efbc211c d83000 d8f000 8000075 /lib/libnss_files-2.12.so
+efbc2504 d8f000 d90000 8100071 /lib/libnss_files-2.12.so
+efbc2950 d90000 d91000 8100073 /lib/libnss_files-2.12.so
+f26afe00 edc000 edd000 4040075
+f1bb0a18 8047000 8118000 8001875 /bin/bash
+f1bb01e4 8118000 811d000 8101873 /bin/bash
+f1bb0c70 811d000 8122000 100073
+f26afae0 9fd9000 9ffa000 100073
+<span class="emphasis"><em>... several lines omitted ...</em></span></pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help vm</code> for more information on the command usage.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-processes.html"><strong>Prev</strong>24.2.3. Displaying a Process Status</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-kdump-crash-files.html"><strong>Next</strong>24.2.5. Displaying Open Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-processes.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-processes.html
new file mode 100644
index 0000000..7b053dc
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-crash-processes.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>24.2.3. Displaying a Process Status</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-kdump-crash.html" title="24.2. Analyzing the Core Dump" /><link rel="prev" href="s2-kdump-crash-backtrace.html" title="24.2.2. Displaying a Backtrace" /><link rel="next" href="s2-kdump-crash-memory.html" title="24.2.4. Displaying Virtual Memory Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-backtrace.html"><strong>Prev</strong></a></li><
li class="next"><a accesskey="n" href="s2-kdump-crash-memory.html"><strong>Next</strong></a></li></ul><div class="section" title="24.2.3. Displaying a Process Status" id="s2-kdump-crash-processes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-crash-processes">24.2.3. Displaying a Process Status</h3></div></div></div><a id="id468541" class="indexterm"></a><div class="para">
+ To display status of processes in the system, type the <code class="command">ps</code> command at the interactive prompt. You can use <code class="command">ps <em class="replaceable"><code>pid</code></em></code> to display the status of the selected process.
+ </div><div class="example" title="Example 24.6. Displaying status of processes in the system" id="ex-kdump-crash-processes"><h6>Example 24.6. Displaying status of processes in the system</h6><div class="example-contents"><pre class="screen">crash> <code class="command">ps</code>
+ PID PPID CPU TASK ST %MEM VSZ RSS COMM
+> 0 0 0 c09dc560 RU 0.0 0 0 [swapper]
+> 0 0 1 f7072030 RU 0.0 0 0 [swapper]
+ 0 0 2 f70a3a90 RU 0.0 0 0 [swapper]
+> 0 0 3 f70ac560 RU 0.0 0 0 [swapper]
+ 1 0 1 f705ba90 IN 0.0 2828 1424 init
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+ 5566 1 1 f2592560 IN 0.0 12876 784 auditd
+ 5567 1 2 ef427560 IN 0.0 12876 784 auditd
+ 5587 5132 0 f196d030 IN 0.0 11064 3184 sshd
+> 5591 5587 2 f196d560 RU 0.0 5084 1648 bash</pre></div></div><br class="example-break" /><div class="para">
+ Type <code class="command">help ps</code> for more information on the command usage.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kdump-crash-backtrace.html"><strong>Prev</strong>24.2.2. Displaying a Backtrace</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-kdump-crash-memory.html"><strong>Next</strong>24.2.4. Displaying Virtual Memory Information</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-resources-online.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-resources-online.html
new file mode 100644
index 0000000..11cb955
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kdump-resources-online.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>24.3.2. Useful Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-kdump-resources.html" title="24.3. Additional Resources" /><link rel="prev" href="s1-kdump-resources.html" title="24.3. Additional Resources" /><link rel="next" href="app-Revision_History.html" title="Appendix A. Revision History" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kdump-resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n"
href="app-Revision_History.html"><strong>Next</strong></a></li></ul><div class="section" title="24.3.2. Useful Websites" id="s2-kdump-resources-online"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kdump-resources-online">24.3.2. Useful Websites</h3></div></div></div><a id="id788972" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><a href="https://access.redhat.com/kb/docs/DOC-6039">https://access.redhat.com/kb/docs/DOC-6039</a></span></dt><dd><div class="para">
+ The Red Hat Knowledgebase article about the <code class="command">kexec</code> and <code class="systemitem">kdump</code> configuration.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://people.redhat.com/anderson/">http://people.redhat.com/anderson/</a></span></dt><dd><div class="para">
+ The <span class="application"><strong>crash</strong></span> utility homepage.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kdump-resources.html"><strong>Prev</strong>24.3. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="app-Revision_History.html"><strong>Next</strong>Appendix A. Revision History</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kernel-boot-loader-iseries.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kernel-boot-loader-iseries.html
new file mode 100644
index 0000000..08089a9
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kernel-boot-loader-iseries.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>23.6.2. Configuring the OS/400® Boot Loader</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-kernel-boot-loader.html" title="23.6. Verifying the Boot Loader" /><link rel="prev" href="s1-kernel-boot-loader.html" title="23.6. Verifying the Boot Loader" /><link rel="next" href="s2-kernel-boot-loader-pseries.html" title="23.6.3. Configuring the YABOOT Boot Loader" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-boot-loader.html"><strong>Prev</strong><
/a></li><li class="next"><a accesskey="n" href="s2-kernel-boot-loader-pseries.html"><strong>Next</strong></a></li></ul><div class="section" title="23.6.2. Configuring the OS/400® Boot Loader" id="s2-kernel-boot-loader-iseries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kernel-boot-loader-iseries">23.6.2. Configuring the <span class="trademark">OS/400</span>® Boot Loader</h3></div></div></div><a id="id472632" class="indexterm"></a><a id="id472644" class="indexterm"></a><div class="para">
+ The <code class="filename">/boot/vmlinitrd-<em class="replaceable"><code><kernel-version></code></em> </code> file is installed when you upgrade the kernel. However, you must use the <code class="command">dd</code> command to configure the system to boot the new kernel.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ As root, issue the command <code class="command">cat /proc/iSeries/mf/side</code> to determine the default side (either A, B, or C).
+ </div></li><li class="listitem"><div class="para">
+ As root, issue the following command, where <em class="replaceable"><code><kernel-version></code></em> is the version of the new kernel and <em class="replaceable"><code><side></code></em> is the side from the previous command:
+ </div><pre class="screen">
+<code class="command">dd if=/boot/vmlinitrd-<em class="replaceable"><code><kernel-version></code></em> of=/proc/iSeries/mf/<em class="replaceable"><code><side></code></em>/vmlinux bs=8k</code>
+</pre></li></ol></div><div class="para">
+ Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-boot-loader.html"><strong>Prev</strong>23.6. Verifying the Boot Loader</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-kernel-boot-loader-pseries.html"><strong>Next</strong>23.6.3. Configuring the YABOOT Boot Loader</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kernel-boot-loader-pseries.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kernel-boot-loader-pseries.html
new file mode 100644
index 0000000..e2f885d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-kernel-boot-loader-pseries.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>23.6.3. Configuring the YABOOT Boot Loader</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-kernel-boot-loader.html" title="23.6. Verifying the Boot Loader" /><link rel="prev" href="s2-kernel-boot-loader-iseries.html" title="23.6.2. Configuring the OS/400® Boot Loader" /><link rel="next" href="ch-kdump.html" title="Chapter 24. The kdump Crash Recovery Service" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kernel-boot-loader-iseries.html"><strong>Pre
v</strong></a></li><li class="next"><a accesskey="n" href="ch-kdump.html"><strong>Next</strong></a></li></ul><div class="section" title="23.6.3. Configuring the YABOOT Boot Loader" id="s2-kernel-boot-loader-pseries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-kernel-boot-loader-pseries">23.6.3. Configuring the YABOOT Boot Loader</h3></div></div></div><div class="para">
+ IBM eServer System p uses YABOOT as its boot loader. YABOOT uses <code class="filename">/etc/aboot.conf</code> as its configuration file. Confirm that the file contains an <code class="computeroutput">image</code> section with the same version as the <span class="package">kernel</span> package just installed, and likewise for the <code class="systemitem">initramfs</code> image:
+ </div><pre class="screen">boot=/dev/sda1 init-message=Welcome to Fedora! Hit <TAB> for boot options
+partition=2 timeout=30 install=/usr/lib/yaboot/yaboot delay=10 nonvram
+image=/vmlinuz-2.6.32-17.EL
+ label=old
+ read-only
+ initrd=/initramfs-2.6.32-17.EL.img
+ append="root=LABEL=/"
+image=/vmlinuz-2.6.32-19.EL
+ label=linux
+ read-only
+ initrd=/initramfs-2.6.32-19.EL.img
+ append="root=LABEL=/"</pre><div class="para">
+ Notice that the default is not set to the new kernel. The kernel in the first image is booted by default. To change the default kernel to boot either move its image stanza so that it is the first one listed or add the directive <code class="computeroutput">default</code> and set it to the <code class="computeroutput">label</code> of the image stanza that contains the new kernel.
+ </div><div class="para">
+ Begin testing the new kernel by rebooting the computer and watching the messages to ensure that the hardware is detected properly.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kernel-boot-loader-iseries.html"><strong>Prev</strong>23.6.2. Configuring the OS/400® Boot Loader</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-kdump.html"><strong>Next</strong>Chapter 24. The kdump Crash Recovery Service</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-keys-checking.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-keys-checking.html
new file mode 100644
index 0000000..3e5a5c5
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-keys-checking.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.3.2. Verifying Signature of Packages</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-check-rpm-sig.html" title="3.3. Checking a Package's Signature" /><link rel="prev" href="s1-check-rpm-sig.html" title="3.3. Checking a Package's Signature" /><link rel="next" href="s1-rpm-impressing.html" title="3.4. Practical and Common Examples of RPM Usage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-check-rpm-sig.html"><strong>Prev</strong></a></li><li cl
ass="next"><a accesskey="n" href="s1-rpm-impressing.html"><strong>Next</strong></a></li></ul><div class="section" title="3.3.2. Verifying Signature of Packages" id="s2-keys-checking"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-keys-checking">3.3.2. Verifying Signature of Packages</h3></div></div></div><div class="para">
+ To check the GnuPG signature of an RPM file after importing the builder's GnuPG key, use the following command (replace <em class="replaceable"><code><rpm_file></code></em> with the filename of the RPM package):
+ </div><pre class="screen">
+<code class="command">rpm -K <em class="replaceable"><code><rpm_file></code></em> </code>
+</pre><div class="para">
+ If all goes well, the following message is displayed: <code class="computeroutput">rsa sha1 (md5) pgp md5 OK</code>. This means that the signature of the package has been verified, that it is not corrupt, and is therefore safe to install and use.
+ </div><div class="para">
+ For more information, including a list of currently-used Fedora Project keys and their fingerprints, refer to <a href="http://fedoraproject.org/en/keys">http://fedoraproject.org/en/keys</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-check-rpm-sig.html"><strong>Prev</strong>3.3. Checking a Package's Signature</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-rpm-impressing.html"><strong>Next</strong>3.4. Practical and Common Examples of RPM Usage</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-log-files-useful-websites.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-log-files-useful-websites.html
new file mode 100644
index 0000000..aa6aa29
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-log-files-useful-websites.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.7.2. Useful Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-log-files-additional-resources.html" title="17.7. Additional Resources" /><link rel="prev" href="s1-log-files-additional-resources.html" title="17.7. Additional Resources" /><link rel="next" href="ch-The_sysconfig_Directory.html" title="Chapter 18. The sysconfig Directory" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-log-files-additional-resources.html"><stro
ng>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-The_sysconfig_Directory.html"><strong>Next</strong></a></li></ul><div class="section" title="17.7.2. Useful Websites" id="s2-log-files-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-log-files-useful-websites">17.7.2. Useful Websites</h3></div></div></div><a id="id804252" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.rsyslog.com/">http://www.rsyslog.com/</a> — Offers a thorough technical breakdown of <span class="package">rsyslog</span> features, documentation, configuration examples, and video tutorials.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://wiki.rsyslog.com/index.php/Main_Page">http://wiki.rsyslog.com/index.php/Main_Page</a> — Contains useful <code class="filename">/etc/rsyslog.conf</code> configuration examples.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-log-files-additional-resources.html"><strong>Prev</strong>17.7. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-The_sysconfig_Directory.html"><strong>Next</strong>Chapter 18. The sysconfig Directory</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-alias.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-alias.html
new file mode 100644
index 0000000..46ee2f3
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-alias.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.3. Alias and Clone Files</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-networkscripts-interfaces.html" title="4.2. Interface Configuration Files" /><link rel="prev" href="s2-networkscripts-interfaces-chan.html" title="4.2.2. Channel Bonding Interfaces" /><link rel="next" href="s2-networkscripts-interfaces-ppp0.html" title="4.2.4. Dialup Interfaces" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-chan.html">
<strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-ppp0.html"><strong>Next</strong></a></li></ul><div class="section" title="4.2.3. Alias and Clone Files" id="s2-networkscripts-interfaces-alias"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-interfaces-alias">4.2.3. Alias and Clone Files</h3></div></div></div><a id="id658748" class="indexterm"></a><a id="id658766" class="indexterm"></a><div class="para">
+ Two lesser-used types of interface configuration files are <em class="firstterm">alias</em> and <em class="firstterm">clone</em> files.
+ </div><div class="para">
+ Alias interface configuration files, which are used to bind multiple addresses to a single interface, use the <code class="filename">ifcfg-<em class="replaceable"><code><if-name></code></em>:<em class="replaceable"><code><alias-value></code></em> </code> naming scheme.
+ </div><div class="para">
+ For example, an <code class="filename">ifcfg-eth0:0</code> file could be configured to specify <code class="computeroutput">DEVICE=eth0:0</code> and a static IP address of 10.0.0.2, serving as an alias of an Ethernet interface already configured to receive its IP information via DHCP in <code class="filename">ifcfg-eth0</code>. Under this configuration, <code class="filename">eth0</code> is bound to a dynamic IP address, but the same physical network card can receive requests via the fixed, 10.0.0.2 IP address.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Alias interfaces do not support DHCP.
+ </div></div></div><div class="para">
+ A clone interface configuration file should use the following naming convention: <code class="filename">ifcfg-<em class="replaceable"><code><if-name></code></em>-<em class="replaceable"><code><clone-name></code></em> </code>. While an alias file allows multiple addresses for an existing interface, a clone file is used to specify additional options for an interface. For example, a standard DHCP Ethernet interface called <code class="filename">eth0</code>, may look similar to this:
+ </div><pre class="screen">DEVICE=eth0
+ONBOOT=yes
+BOOTPROTO=dhcp</pre><div class="para">
+ Since the default value for the <code class="command">USERCTL</code> directive is <code class="command">no</code> if it is not specified, users cannot bring this interface up and down. To give users the ability to control the interface, create a clone by copying <code class="filename">ifcfg-eth0</code> to <code class="filename">ifcfg-eth0-user</code> and add the following line to <code class="filename">ifcfg-eth0-user</code>:
+ </div><pre class="screen">USERCTL=yes</pre><div class="para">
+ This way a user can bring up the <code class="filename">eth0</code> interface using the <code class="command">/sbin/ifup eth0-user</code> command because the configuration options from <code class="filename">ifcfg-eth0</code> and <code class="filename">ifcfg-eth0-user</code> are combined. While this is a very basic example, this method can be used with a variety of options and interfaces.
+ </div><div class="para">
+ The easiest way to create alias and clone interface configuration files is to use the graphical <span class="application"><strong>Network Administration Tool</strong></span>. For more information on using this tool, refer to <a class="xref" href="ch-Network_Configuration.html" title="Chapter 5. Network Configuration">Chapter 5, <i>Network Configuration</i></a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-chan.html"><strong>Prev</strong>4.2.2. Channel Bonding Interfaces</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-ppp0.html"><strong>Next</strong>4.2.4. Dialup Interfaces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html
new file mode 100644
index 0000000..a4f1827
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-chan.html
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.2. Channel Bonding Interfaces</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-networkscripts-interfaces.html" title="4.2. Interface Configuration Files" /><link rel="prev" href="s1-networkscripts-interfaces.html" title="4.2. Interface Configuration Files" /><link rel="next" href="s2-networkscripts-interfaces-alias.html" title="4.2.3. Alias and Clone Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-interfaces.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-alias.html"><strong>Next</strong></a></li></ul><div class="section" title="4.2.2. Channel Bonding Interfaces" id="s2-networkscripts-interfaces-chan"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-interfaces-chan">4.2.2. Channel Bonding Interfaces</h3></div></div></div><a id="id466529" class="indexterm"></a><a id="id466546" class="indexterm"></a><div class="para">
+ Fedora allows administrators to bind multiple network interfaces together into a single channel using the <code class="filename">bonding</code> kernel module and a special network interface called a <em class="firstterm">channel bonding interface</em>. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
+ </div><div class="para">
+ To create a channel bonding interface, create a file in the <code class="filename">/etc/sysconfig/network-scripts/</code> directory called <code class="filename">ifcfg-bond<em class="replaceable"><code><N></code></em> </code>, replacing <em class="replaceable"><code><N></code></em> with the number for the interface, such as <code class="filename">0</code>.
+ </div><div class="para">
+ The contents of the file can be identical to whatever type of interface is getting bonded, such as an Ethernet interface. The only difference is that the <code class="command">DEVICE=</code> directive must be <code class="command">bond<em class="replaceable"><code><N></code></em> </code>, replacing <em class="replaceable"><code><N></code></em> with the number for the interface.
+ </div><div class="para">
+ The following is a sample channel bonding configuration file:
+ </div><div class="example" title="Example 4.1. Sample ifcfg-bond0 interface configuration file" id="ex-Sample_ifcfg-bond0_interface_configuration_file"><h6>Example 4.1. Sample ifcfg-bond0 interface configuration file</h6><div class="example-contents"><pre class="screen">DEVICE=bond0
+IPADDR=192.168.1.1
+NETMASK=255.255.255.0
+ONBOOT=yes
+BOOTPROTO=none
+USERCTL=no
+BONDING_OPTS="<em class="replaceable"><code><bonding parameters separated by spaces></code></em>"</pre></div></div><br class="example-break" /><div class="para">
+ After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the <code class="command">MASTER=</code> and <code class="command">SLAVE=</code> directives to their configuration files. The configuration files for each of the channel-bonded interfaces can be nearly identical.
+ </div><div class="para">
+ For example, if two Ethernet interfaces are being channel bonded, both <code class="filename">eth0</code> and <code class="filename">eth1</code> may look like the following example:
+ </div><pre class="screen">
+DEVICE=eth<em class="replaceable"><code><N></code></em>
+BOOTPROTO=none
+ONBOOT=yes
+MASTER=bond0
+SLAVE=yes
+USERCTL=no
+</pre><div class="para">
+ In this example, replace <em class="replaceable"><code><N></code></em> with the numerical value for the interface.
+ </div><div class="para">
+ For a channel bonding interface to be valid, the kernel module must be loaded. To ensure that the module is loaded when the channel bonding interface is brought up, create a new file as root named <code class="filename"><em class="replaceable"><code><bonding></code></em>.conf</code> in the <code class="filename">/etc/modprobe.d/</code> directory. Note that you can name this file anything you like as long as it ends with a <code class="filename">.conf</code> extension. Insert the following line in this new file:
+ </div><pre class="screen">alias bond<em class="replaceable"><code><N></code></em> bonding</pre><div class="para">
+ Replace <em class="replaceable"><code><N></code></em> with the interface number, such as <code class="command">0</code>. For each configured channel bonding interface, there must be a corresponding entry in your new <code class="filename">/etc/modprobe.d/<em class="replaceable"><code><bonding></code></em>.conf</code> file.
+ </div><div class="important" title="Important: put all bonding module parameters in ifcfg-bondN files"><div class="admonition_header"><h2>Important: put all bonding module parameters in ifcfg-bondN files</h2></div><div class="admonition"><div class="para">
+ Parameters for the bonding kernel module must be specified as a space-separated list in the <em class="parameter"><code>BONDING_OPTS="<em class="replaceable"><code><bonding parameters></code></em>"</code></em> directive in the ifcfg-bond<em class="replaceable"><code><N></code></em> interface file. Do <span class="emphasis"><em>not</em></span> specify options for the bonding device in <code class="filename">/etc/modprobe.d/<em class="replaceable"><code><bonding></code></em>.conf</code>, or in the deprecated <code class="filename">/etc/modprobe.conf</code> file. For further instructions and advice on configuring the bonding module and to view the list of bonding parameters, refer to <a class="xref" href="sec-Using_Channel_Bonding.html" title="22.7.2. Using Channel Bonding">Section 22.7.2, “Using Channel Bonding”</a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-networkscripts-interfaces.html"><strong>Prev</strong>4.2. Interface Configuration Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-alias.html"><strong>Next</strong>4.2.3. Alias and Clone Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-other.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-other.html
new file mode 100644
index 0000000..24dea08
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-other.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.5. Other Interfaces</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-networkscripts-interfaces.html" title="4.2. Interface Configuration Files" /><link rel="prev" href="s2-networkscripts-interfaces-ppp0.html" title="4.2.4. Dialup Interfaces" /><link rel="next" href="s1-networkscripts-control.html" title="4.3. Interface Control Scripts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-ppp0.html"><strong>Pre
v</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-control.html"><strong>Next</strong></a></li></ul><div class="section" title="4.2.5. Other Interfaces" id="s2-networkscripts-interfaces-other"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-interfaces-other">4.2.5. Other Interfaces</h3></div></div></div><div class="para">
+ Other common interface configuration files include the following:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="filename">ifcfg-lo</code> </span></dt><dd><div class="para">
+ A local <em class="firstterm">loopback interface</em> is often used in testing, as well as being used in a variety of applications that require an IP address pointing back to the same system. Any data sent to the loopback device is immediately returned to the host's network layer.
+ </div><div class="warning" title="Warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ The loopback interface script, <code class="filename">/etc/sysconfig/network-scripts/ifcfg-lo</code>, should never be edited manually. Doing so can prevent the system from operating correctly.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifcfg-irlan0</code> </span></dt><dd><div class="para">
+ An <em class="firstterm">infrared interface</em> allows information between devices, such as a laptop and a printer, to flow over an infrared link. This works in a similar way to an Ethernet device except that it commonly occurs over a peer-to-peer connection.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="filename">ifcfg-plip0</code> </span></dt><dd><div class="para">
+ A <em class="firstterm">Parallel Line Interface Protocol (PLIP)</em> connection works much the same way as an Ethernet device, except that it utilizes a parallel port.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-ppp0.html"><strong>Prev</strong>4.2.4. Dialup Interfaces</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-networkscripts-control.html"><strong>Next</strong>4.3. Interface Control Scripts</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-ppp0.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-ppp0.html
new file mode 100644
index 0000000..a5eb858
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-networkscripts-interfaces-ppp0.html
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2.4. Dialup Interfaces</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-networkscripts-interfaces.html" title="4.2. Interface Configuration Files" /><link rel="prev" href="s2-networkscripts-interfaces-alias.html" title="4.2.3. Alias and Clone Files" /><link rel="next" href="s2-networkscripts-interfaces-other.html" title="4.2.5. Other Interfaces" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-alias.html"><st
rong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-other.html"><strong>Next</strong></a></li></ul><div class="section" title="4.2.4. Dialup Interfaces" id="s2-networkscripts-interfaces-ppp0"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-networkscripts-interfaces-ppp0">4.2.4. Dialup Interfaces</h3></div></div></div><a id="id507771" class="indexterm"></a><div class="para">
+ If you are connecting to the Internet via a dialup connection, a configuration file is necessary for the interface.
+ </div><div class="para">
+ PPP interface files are named using the following format:
+ <div class="variablelist"><dl><dt class="varlistentry"><span class="term"><code class="filename">ifcfg-ppp<em class="replaceable"><code><X></code></em> </code> </span></dt><dd><div class="para">
+ where <em class="replaceable"><code><X></code></em> is a unique number corresponding to a specific interface.
+ </div></dd></dl></div>
+
+ </div><div class="para">
+ The PPP interface configuration file is created automatically when <code class="command">wvdial</code>, the <span class="application"><strong>Network Administration Tool</strong></span> or <span class="application"><strong>Kppp</strong></span> is used to create a dialup account. It is also possible to create and edit this file manually.
+ </div><div class="para">
+ The following is a typical <code class="filename">ifcfg-ppp0</code> file:
+ </div><pre class="screen">DEVICE=ppp0
+NAME=test
+WVDIALSECT=test
+MODEMPORT=/dev/modem
+LINESPEED=115200
+PAPNAME=test
+USERCTL=true
+ONBOOT=no
+PERSIST=no
+DEFROUTE=yes
+PEERDNS=yes
+DEMAND=no
+IDLETIMEOUT=600</pre><div class="para">
+ <em class="firstterm">Serial Line Internet Protocol (SLIP)</em> is another dialup interface, although it is used less frequently. SLIP files have interface configuration file names such as <code class="filename">ifcfg-sl0</code>.
+ </div><div class="para">
+ Other options that may be used in these files include:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="command">DEFROUTE=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — Set this interface as the default route.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — Do not set this interface as the default route.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">DEMAND=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — This interface allows <code class="command">pppd</code> to initiate a connection when someone attempts to use it.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — A connection must be manually established for this interface.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">IDLETIMEOUT=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the number of seconds of idle activity before the interface disconnects itself.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">INITSTRING=<em class="replaceable"><code><string></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><string></code></em> </code> is the initialization string passed to the modem device. This option is primarily used in conjunction with SLIP interfaces.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">LINESPEED=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the baud rate of the device. Possible standard values include <code class="command">57600</code>, <code class="command">38400</code>, <code class="command">19200</code>, and <code class="command">9600</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">MODEMPORT=<em class="replaceable"><code><device></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><device></code></em> </code> is the name of the serial device that is used to establish the connection for the interface.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">MTU=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><value></code></em> </code> is the <em class="firstterm">Maximum Transfer Unit (MTU)</em> setting for the interface. The MTU refers to the largest number of bytes of data a frame can carry, not counting its header information. In some dialup situations, setting this to a value of <code class="command">576</code> results in fewer packets dropped and a slight improvement to the throughput for a connection.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">NAME=<em class="replaceable"><code><name></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><name></code></em> </code> is the reference to the title given to a collection of dialup connection configurations.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">PAPNAME=<em class="replaceable"><code><name></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><name></code></em> </code> is the username given during the <em class="firstterm">Password Authentication Protocol (PAP)</em> exchange that occurs to allow connections to a remote system.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">PERSIST=<em class="replaceable"><code><answer></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><answer></code></em> </code> is one of the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yes</code> — This interface should be kept active at all times, even if deactivated after a modem hang up.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">no</code> — This interface should not be kept active at all times.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="command">REMIP=<em class="replaceable"><code><address></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><address></code></em> </code> is the IP address of the remote system. This is usually left unspecified.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="command">WVDIALSECT=<em class="replaceable"><code><name></code></em> </code> </span></dt><dd><div class="para">
+ where <code class="command"><em class="replaceable"><code><name></code></em> </code> associates this interface with a dialer configuration in <code class="filename">/etc/wvdial.conf</code>. This file contains the phone number to be dialed and other important information for the interface.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-networkscripts-interfaces-alias.html"><strong>Prev</strong>4.2.3. Alias and Clone Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-networkscripts-interfaces-other.html"><strong>Next</strong>4.2.5. Other Interfaces</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-openssh-useful-websites.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-openssh-useful-websites.html
new file mode 100644
index 0000000..6c9ce6b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-openssh-useful-websites.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.5.2. Useful Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-openssh-additional-resources.html" title="9.5. Additional Resources" /><link rel="prev" href="s1-openssh-additional-resources.html" title="9.5. Additional Resources" /><link rel="next" href="ch-The_BIND_DNS_Server.html" title="Chapter 10. The BIND DNS Server" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-openssh-additional-resources.html"><strong>Prev</strong>
</a></li><li class="next"><a accesskey="n" href="ch-The_BIND_DNS_Server.html"><strong>Next</strong></a></li></ul><div class="section" title="9.5.2. Useful Websites" id="s2-openssh-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-openssh-useful-websites">9.5.2. Useful Websites</h3></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"><a href="http://www.openssh.com/">http://www.openssh.com/</a></span></dt><dd><div class="para">
+ The OpenSSH home page containing further documentation, frequently asked questions, links to the mailing lists, bug reports, and other useful resources.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.openssl.org/">http://www.openssl.org/</a></span></dt><dd><div class="para">
+ The OpenSSL home page containing further documentation, frequently asked questions, links to the mailing lists, and other useful resources.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.freesshd.com/">http://www.freesshd.com/</a></span></dt><dd><div class="para">
+ Another implementation of an SSH server.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-openssh-additional-resources.html"><strong>Prev</strong>9.5. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-The_BIND_DNS_Server.html"><strong>Next</strong>Chapter 10. The BIND DNS Server</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-cmdline.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-cmdline.html
new file mode 100644
index 0000000..f7ce66b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-cmdline.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.2. /proc/cmdline</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="next" href="s2-proc-cpuinfo.html" title="19.2.3. /proc/cpuinfo" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-topfiles.html"><strong>Prev</strong></a></li><li c
lass="next"><a accesskey="n" href="s2-proc-cpuinfo.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.2. /proc/cmdline" id="s2-proc-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-cmdline">19.2.2. <code class="filename">/proc/cmdline</code> </h3></div></div></div><a id="id576520" class="indexterm"></a><div class="para">
+ This file shows the parameters passed to the kernel at the time it is started. A sample <code class="filename">/proc/cmdline</code> file looks like the following:
+ </div><pre class="screen">
+ro root=/dev/VolGroup00/LogVol00 rhgb quiet 3
+</pre><div class="para">
+ This tells us that the kernel is mounted read-only (signified by <code class="computeroutput">(ro)</code>), located on the first logical volume (<code class="computeroutput">LogVol00</code>) of the first volume group (<code class="computeroutput">/dev/VolGroup00</code>). <code class="computeroutput">LogVol00</code> is the equivalent of a disk partition in a non-LVM system (Logical Volume Management), just as <code class="computeroutput">/dev/VolGroup00</code> is similar in concept to <code class="filename">/dev/hda1</code>, but much more extensible.
+ </div><div class="para">
+ For more information on LVM used in Fedora, refer to <a href="http://www.tldp.org/HOWTO/LVM-HOWTO/index.html">http://www.tldp.org/HOWTO/LVM-HOWTO/index.html</a>.
+ </div><div class="para">
+ Next, <code class="computeroutput">rhgb</code> signals that the <code class="filename">rhgb</code> package has been installed, and graphical booting is supported, assuming <code class="filename">/etc/inittab</code> shows a default runlevel set to <code class="command">id:5:initdefault:</code>.
+ </div><div class="para">
+ Finally, <code class="computeroutput">quiet</code> indicates all verbose kernel messages are suppressed at boot time.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-topfiles.html"><strong>Prev</strong>19.2. Top-level Files within the proc File System</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-cpuinfo.html"><strong>Next</strong>19.2.3. /proc/cpuinfo </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-cpuinfo.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-cpuinfo.html
new file mode 100644
index 0000000..362459e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-cpuinfo.html
@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.3. /proc/cpuinfo</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-cmdline.html" title="19.2.2. /proc/cmdline" /><link rel="next" href="s2-proc-crypto.html" title="19.2.4. /proc/crypto" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-cmdline.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hr
ef="s2-proc-crypto.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.3. /proc/cpuinfo" id="s2-proc-cpuinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-cpuinfo">19.2.3. <code class="filename">/proc/cpuinfo</code> </h3></div></div></div><a id="id576629" class="indexterm"></a><div class="para">
+ This virtual file identifies the type of processor used by your system. The following is an example of the output typical of <code class="filename">/proc/cpuinfo</code>:
+ </div><pre class="screen">
+processor : 0
+vendor_id : GenuineIntel
+cpu family : 15
+model : 2
+model name : Intel(R) Xeon(TM) CPU 2.40GHz
+stepping : 7 cpu
+MHz : 2392.371
+cache size : 512 KB
+physical id : 0
+siblings : 2
+runqueue : 0
+fdiv_bug : no
+hlt_bug : no
+f00f_bug : no
+coma_bug : no
+fpu : yes
+fpu_exception : yes
+cpuid level : 2
+wp : yes
+flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
+bogomips : 4771.02
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">processor</code> — Provides each processor with an identifying number. On systems that have one processor, only a <code class="computeroutput">0</code> is present.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu family</code> — Authoritatively identifies the type of processor in the system. For an Intel-based system, place the number in front of "86" to determine the value. This is particularly helpful for those attempting to identify the architecture of an older system such as a 586, 486, or 386. Because some RPM packages are compiled for each of these particular architectures, this value also helps users determine which packages to install.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">model name</code> — Displays the common name of the processor, including its project name.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu MHz</code> — Shows the precise speed in megahertz for the processor to the thousandths decimal place.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">cache size</code> — Displays the amount of level 2 memory cache available to the processor.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">siblings</code> — Displays the number of sibling CPUs on the same physical CPU for architectures which use hyper-threading.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">flags</code> — Defines a number of different qualities about the processor, such as the presence of a floating point unit (FPU) and the ability to process MMX instructions.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-cmdline.html"><strong>Prev</strong>19.2.2. /proc/cmdline </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-crypto.html"><strong>Next</strong>19.2.4. /proc/crypto </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-crypto.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-crypto.html
new file mode 100644
index 0000000..adbeb6d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-crypto.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.4. /proc/crypto</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-cpuinfo.html" title="19.2.3. /proc/cpuinfo" /><link rel="next" href="s2-proc-devices.html" title="19.2.5. /proc/devices" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-cpuinfo.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n"
href="s2-proc-devices.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.4. /proc/crypto" id="s2-proc-crypto"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-crypto">19.2.4. <code class="filename">/proc/crypto</code> </h3></div></div></div><a id="id653472" class="indexterm"></a><div class="para">
+ This file lists all installed cryptographic ciphers used by the Linux kernel, including additional details for each. A sample <code class="filename">/proc/crypto</code> file looks like the following:
+ </div><pre class="screen">
+name : sha1
+module : kernel
+type : digest
+blocksize : 64
+digestsize : 20
+name : md5
+module : md5
+type : digest
+blocksize : 64
+digestsize : 16
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-cpuinfo.html"><strong>Prev</strong>19.2.3. /proc/cpuinfo </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-devices.html"><strong>Next</strong>19.2.5. /proc/devices </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-devices.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-devices.html
new file mode 100644
index 0000000..e4009cf
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-devices.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.5. /proc/devices</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-crypto.html" title="19.2.4. /proc/crypto" /><link rel="next" href="s2-proc-dma.html" title="19.2.6. /proc/dma" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-crypto.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-pr
oc-dma.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.5. /proc/devices" id="s2-proc-devices"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-devices">19.2.5. <code class="filename">/proc/devices</code> </h3></div></div></div><a id="id653522" class="indexterm"></a><a id="id653548" class="indexterm"></a><a id="id653573" class="indexterm"></a><a id="id718632" class="indexterm"></a><a id="id718650" class="indexterm"></a><a id="id718667" class="indexterm"></a><div class="para">
+ This file displays the various character and block devices currently configured (not including devices whose modules are not loaded). Below is a sample output from this file:
+ </div><pre class="screen">
+Character devices:
+ 1 mem
+ 4 /dev/vc/0
+ 4 tty
+ 4 ttyS
+ 5 /dev/tty
+ 5 /dev/console
+ 5 /dev/ptmx
+ 7 vcs
+ 10 misc
+ 13 input
+ 29 fb
+ 36 netlink
+ 128 ptm
+ 136 pts
+ 180 usb
+
+Block devices:
+ 1 ramdisk
+ 3 ide0
+ 9 md
+ 22 ide1
+ 253 device-mapper
+ 254 mdp
+</pre><div class="para">
+ The output from <code class="filename">/proc/devices</code> includes the major number and name of the device, and is broken into two major sections: <code class="computeroutput">Character devices</code> and <code class="computeroutput">Block devices</code>.
+ </div><div class="para">
+ <em class="firstterm">Character devices</em> are similar to <em class="firstterm">block devices</em>, except for two basic differences:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ Character devices do not require buffering. Block devices have a buffer available, allowing them to order requests before addressing them. This is important for devices designed to store information — such as hard drives — because the ability to order the information before writing it to the device allows it to be placed in a more efficient order.
+ </div></li><li class="listitem"><div class="para">
+ Character devices send data with no preconfigured size. Block devices can send and receive information in blocks of a size configured per device.
+ </div></li></ol></div><div class="para">
+ For more information about devices refer to the following installed documentation:
+ </div><pre class="screen">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/devices.txt</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-crypto.html"><strong>Prev</strong>19.2.4. /proc/crypto </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dma.html"><strong>Next</strong>19.2.6. /proc/dma </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-bus.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-bus.html
new file mode 100644
index 0000000..47aecc4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-bus.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.2. /proc/bus/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="next" href="s2-proc-pci.html" title="19.3.3. /proc/bus/pci" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-directories.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hr
ef="s2-proc-pci.html"><strong>Next</strong></a></li></ul><div class="section" title="19.3.2. /proc/bus/" id="s2-proc-dir-bus"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-bus">19.3.2. <code class="filename">/proc/bus/</code> </h3></div></div></div><a id="id823113" class="indexterm"></a><div class="para">
+ This directory contains information specific to the various buses available on the system. For example, on a standard system containing PCI and USB buses, current data on each of these buses is available within a subdirectory within <code class="filename">/proc/bus/</code> by the same name, such as <code class="filename">/proc/bus/pci/</code>.
+ </div><div class="para">
+ The subdirectories and files available within <code class="filename">/proc/bus/</code> vary depending on the devices connected to the system. However, each bus type has at least one directory. Within these bus directories are normally at least one subdirectory with a numerical name, such as <code class="filename">001</code>, which contain binary files.
+ </div><div class="para">
+ For example, the <code class="filename">/proc/bus/usb/</code> subdirectory contains files that track the various devices on any USB buses, as well as the drivers required for them. The following is a sample listing of a <code class="filename">/proc/bus/usb/</code> directory:
+ </div><pre class="screen">
+total 0 dr-xr-xr-x 1 root root 0 May 3 16:25 001
+-r--r--r-- 1 root root 0 May 3 16:25 devices
+-r--r--r-- 1 root root 0 May 3 16:25 drivers
+</pre><div class="para">
+ The <code class="filename">/proc/bus/usb/001/</code> directory contains all devices on the first USB bus and the <code class="filename">devices</code> file identifies the USB root hub on the motherboard.
+ </div><div class="para">
+ The following is a example of a <code class="filename">/proc/bus/usb/devices</code> file:
+ </div><pre class="screen">
+T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
+B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
+D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
+P: Vendor=0000 ProdID=0000 Rev= 0.00
+S: Product=USB UHCI Root Hub
+S: SerialNumber=d400
+C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
+I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
+E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-proc-directories.html"><strong>Prev</strong>19.3. Directories within /proc/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-pci.html"><strong>Next</strong>19.3.3. /proc/bus/pci </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-driver.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-driver.html
new file mode 100644
index 0000000..e3680c4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-driver.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.4. /proc/driver/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s2-proc-pci.html" title="19.3.3. /proc/bus/pci" /><link rel="next" href="s2-proc-dir-fs.html" title="19.3.5. /proc/fs" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-pci.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-fs.html"><s
trong>Next</strong></a></li></ul><div class="section" title="19.3.4. /proc/driver/" id="s2-proc-dir-driver"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-driver">19.3.4. <code class="filename">/proc/driver/</code> </h3></div></div></div><a id="id579788" class="indexterm"></a><div class="para">
+ This directory contains information for specific drivers in use by the kernel.
+ </div><div class="para">
+ A common file found here is <code class="filename">rtc</code> which provides output from the driver for the system's <em class="firstterm">Real Time Clock (RTC)</em>, the device that keeps the time while the system is switched off. Sample output from <code class="filename">/proc/driver/rtc</code> looks like the following:
+ </div><pre class="screen">
+rtc_time : 16:21:00
+rtc_date : 2004-08-31
+rtc_epoch : 1900
+alarm : 21:16:27
+DST_enable : no
+BCD : yes
+24hr : yes
+square_wave : no
+alarm_IRQ : no
+update_IRQ : no
+periodic_IRQ : no
+periodic_freq : 1024
+batt_status : okay
+</pre><div class="para">
+ For more information about the RTC, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/rtc.txt</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-pci.html"><strong>Prev</strong>19.3.3. /proc/bus/pci </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-fs.html"><strong>Next</strong>19.3.5. /proc/fs </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-fs.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-fs.html
new file mode 100644
index 0000000..33dcc9d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-fs.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.5. /proc/fs</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-driver.html" title="19.3.4. /proc/driver/" /><link rel="next" href="s2-proc-dir-irq.html" title="19.3.6. /proc/irq/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-driver.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-pro
c-dir-irq.html"><strong>Next</strong></a></li></ul><div class="section" title="19.3.5. /proc/fs" id="s2-proc-dir-fs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-fs">19.3.5. <code class="filename">/proc/fs</code> </h3></div></div></div><a id="id687142" class="indexterm"></a><div class="para">
+ This directory shows which file systems are exported. If running an NFS server, typing <code class="command">cat /proc/fs/nfsd/exports</code> displays the file systems being shared and the permissions granted for those file systems. For more on file system sharing with NFS, refer to the <em class="citetitle">Network File System (NFS)</em> chapter of the <em class="citetitle">Storage Administration Guide</em>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-driver.html"><strong>Prev</strong>19.3.4. /proc/driver/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-irq.html"><strong>Next</strong>19.3.6. /proc/irq/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-irq.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-irq.html
new file mode 100644
index 0000000..df7b8fe
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-irq.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.6. /proc/irq/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-fs.html" title="19.3.5. /proc/fs" /><link rel="next" href="s2-proc-dir-net.html" title="19.3.7. /proc/net/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-fs.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-net.htm
l"><strong>Next</strong></a></li></ul><div class="section" title="19.3.6. /proc/irq/" id="s2-proc-dir-irq"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-irq">19.3.6. <code class="filename">/proc/irq/</code> </h3></div></div></div><a id="id687199" class="indexterm"></a><div class="para">
+ This directory is used to set IRQ to CPU affinity, which allows the system to connect a particular IRQ to only one CPU. Alternatively, it can exclude a CPU from handling any IRQs.
+ </div><div class="para">
+ Each IRQ has its own directory, allowing for the individual configuration of each IRQ. The <code class="filename">/proc/irq/prof_cpu_mask</code> file is a bitmask that contains the default values for the <code class="filename">smp_affinity</code> file in the IRQ directory. The values in <code class="filename">smp_affinity</code> specify which CPUs handle that particular IRQ.
+ </div><div class="para">
+ For more information about the <code class="filename">/proc/irq/</code> directory, refer to the following installed documentation:
+ </div><pre class="screen">
+/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-fs.html"><strong>Prev</strong>19.3.5. /proc/fs </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-net.html"><strong>Next</strong>19.3.7. /proc/net/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-net.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-net.html
new file mode 100644
index 0000000..aee46ed
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-net.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.7. /proc/net/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-irq.html" title="19.3.6. /proc/irq/" /><link rel="next" href="s2-proc-dir-scsi.html" title="19.3.8. /proc/scsi/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-irq.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-s
csi.html"><strong>Next</strong></a></li></ul><div class="section" title="19.3.7. /proc/net/" id="s2-proc-dir-net"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-net">19.3.7. <code class="filename">/proc/net/</code> </h3></div></div></div><a id="id687274" class="indexterm"></a><div class="para">
+ This directory provides a comprehensive look at various networking parameters and statistics. Each directory and virtual file within this directory describes aspects of the system's network configuration. Below is a partial list of the <code class="filename">/proc/net/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">arp</code> — Lists the kernel's ARP table. This file is particularly useful for connecting a hardware address to an IP address on a system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">atm/</code> directory — The files within this directory contain <em class="firstterm">Asynchronous Transfer Mode (ATM)</em> settings and statistics. This directory is primarily used with ATM networking and ADSL cards.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dev</code> — Lists the various network devices configured on the system, complete with transmit and receive statistics. This file displays the number of bytes each interface has sent and received, the number of packets inbound and outbound, the number of errors seen, the number of packets dropped, and more.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dev_mcast</code> — Lists Layer2 multicast groups on which each device is listening.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">igmp</code> — Lists the IP multicast addresses which this system joined.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_conntrack</code> — Lists tracked network connections for machines that are forwarding IP connections.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_tables_names</code> — Lists the types of <code class="command">iptables</code> in use. This file is only present if <code class="command">iptables</code> is active on the system and contains one or more of the following values: <code class="filename">filter</code>, <code class="filename">mangle</code>, or <code class="filename">nat</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_mr_cache</code> — Lists the multicast routing cache.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_mr_vif</code> — Lists multicast virtual interfaces.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">netstat</code> — Contains a broad yet detailed collection of networking statistics, including TCP timeouts, SYN cookies sent and received, and much more.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">psched</code> — Lists global packet scheduler parameters.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">raw</code> — Lists raw device statistics.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">route</code> — Lists the kernel's routing table.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rt_cache</code> — Contains the current routing cache.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">snmp</code> — List of Simple Network Management Protocol (SNMP) data for various networking protocols in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sockstat</code> — Provides socket statistics.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp</code> — Contains detailed TCP socket information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tr_rif</code> — Lists the token ring RIF routing table.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">udp</code> — Contains detailed UDP socket information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">unix</code> — Lists UNIX domain sockets currently in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wireless</code> — Lists wireless interface data.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-irq.html"><strong>Prev</strong>19.3.6. /proc/irq/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-scsi.html"><strong>Next</strong>19.3.8. /proc/scsi/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-scsi.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-scsi.html
new file mode 100644
index 0000000..0787b5a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-scsi.html
@@ -0,0 +1,97 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.8. /proc/scsi/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-net.html" title="19.3.7. /proc/net/" /><link rel="next" href="s2-proc-dir-sys.html" title="19.3.9. /proc/sys/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-net.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-sys
.html"><strong>Next</strong></a></li></ul><div class="section" title="19.3.8. /proc/scsi/" id="s2-proc-dir-scsi"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-scsi">19.3.8. <code class="filename">/proc/scsi/</code> </h3></div></div></div><a id="id479804" class="indexterm"></a><div class="para">
+ The primary file in this directory is <code class="filename">/proc/scsi/scsi</code>, which contains a list of every recognized SCSI device. From this listing, the type of device, as well as the model name, vendor, SCSI channel and ID data is available.
+ </div><div class="para">
+ For example, if a system contains a SCSI CD-ROM, a tape drive, a hard drive, and a RAID controller, this file looks similar to the following:
+ </div><pre class="screen">
+Attached devices:
+Host: scsi1
+Channel: 00
+Id: 05
+Lun: 00
+Vendor: NEC
+Model: CD-ROM DRIVE:466
+Rev: 1.06
+Type: CD-ROM
+ANSI SCSI revision: 02
+Host: scsi1
+Channel: 00
+Id: 06
+Lun: 00
+Vendor: ARCHIVE
+Model: Python 04106-XXX
+Rev: 7350
+Type: Sequential-Access
+ANSI SCSI revision: 02
+Host: scsi2
+Channel: 00
+Id: 06
+Lun: 00
+Vendor: DELL
+Model: 1x6 U2W SCSI BP
+Rev: 5.35
+Type: Processor
+ANSI SCSI revision: 02
+Host: scsi2
+Channel: 02
+Id: 00
+Lun: 00
+Vendor: MegaRAID
+Model: LD0 RAID5 34556R
+Rev: 1.01
+Type: Direct-Access
+ANSI SCSI revision: 02
+</pre><div class="para">
+ Each SCSI driver used by the system has its own directory within <code class="filename">/proc/scsi/</code>, which contains files specific to each SCSI controller using that driver. From the previous example, <code class="filename">aic7xxx/</code> and <code class="filename">megaraid/</code> directories are present, since two drivers are in use. The files in each of the directories typically contain an I/O address range, IRQ information, and statistics for the SCSI controller using that driver. Each controller can report a different type and amount of information. The Adaptec AIC-7880 Ultra SCSI host adapter's file in this example system produces the following output:
+ </div><pre class="screen">
+Adaptec AIC7xxx driver version: 5.1.20/3.2.4
+Compile Options:
+TCQ Enabled By Default : Disabled
+AIC7XXX_PROC_STATS : Enabled
+AIC7XXX_RESET_DELAY : 5
+Adapter Configuration:
+SCSI Adapter: Adaptec AIC-7880 Ultra SCSI host adapter
+Ultra Narrow Controller PCI MMAPed
+I/O Base: 0xfcffe000
+Adapter SEEPROM Config: SEEPROM found and used.
+Adaptec SCSI BIOS: Enabled
+IRQ: 30
+SCBs: Active 0, Max Active 1, Allocated 15, HW 16, Page 255
+Interrupts: 33726
+BIOS Control Word: 0x18a6
+Adapter Control Word: 0x1c5f
+Extended Translation: Enabled
+Disconnect Enable Flags: 0x00ff
+Ultra Enable Flags: 0x0020
+Tag Queue Enable Flags: 0x0000
+Ordered Queue Tag Flags: 0x0000
+Default Tag Queue Depth: 8
+Tagged Queue By Device array for aic7xxx
+host instance 1: {255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255}
+Actual queue depth per device for aic7xxx host instance 1: {1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}
+Statistics:
+
+(scsi1:0:5:0) Device using Narrow/Sync transfers at 20.0 MByte/sec, offset 15
+Transinfo settings: current(12/15/0/0), goal(12/15/0/0), user(12/15/0/0)
+Total transfers 0 (0 reads and 0 writes)
+ < 2K 2K+ 4K+ 8K+ 16K+ 32K+ 64K+ 128K+
+Reads: 0 0 0 0 0 0 0 0
+Writes: 0 0 0 0 0 0 0 0
+
+(scsi1:0:6:0) Device using Narrow/Sync transfers at 10.0 MByte/sec, offset 15
+Transinfo settings: current(25/15/0/0), goal(12/15/0/0), user(12/15/0/0)
+Total transfers 132 (0 reads and 132 writes)
+ < 2K 2K+ 4K+ 8K+ 16K+ 32K+ 64K+ 128K+
+Reads: 0 0 0 0 0 0 0 0
+Writes: 0 0 0 1 131 0 0 0
+</pre><div class="para">
+ This output reveals the transfer speed to the SCSI devices connected to the controller based on channel ID, as well as detailed statistics concerning the amount and sizes of files read or written by that device. For example, this controller is communicating with the CD-ROM at 20 megabytes per second, while the tape drive is only communicating at 10 megabytes per second.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-net.html"><strong>Prev</strong>19.3.7. /proc/net/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-sys.html"><strong>Next</strong>19.3.9. /proc/sys/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-sys.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-sys.html
new file mode 100644
index 0000000..3649fe9
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-sys.html
@@ -0,0 +1,333 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.9. /proc/sys/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-scsi.html" title="19.3.8. /proc/scsi/" /><link rel="next" href="s2-proc-dir-sysvipc.html" title="19.3.10. /proc/sysvipc/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-scsi.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-
proc-dir-sysvipc.html"><strong>Next</strong></a></li></ul><div class="section" title="19.3.9. /proc/sys/" id="s2-proc-dir-sys"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-sys">19.3.9. <code class="filename">/proc/sys/</code> </h3></div></div></div><a id="id479914" class="indexterm"></a><a id="id479936" class="indexterm"></a><a id="id479951" class="indexterm"></a><a id="id479982" class="indexterm"></a><a id="id480000" class="indexterm"></a><a id="id480015" class="indexterm"></a><div class="para">
+ The <code class="filename">/proc/sys/</code> directory is different from others in <code class="filename">/proc/</code> because it not only provides information about the system but also allows the system administrator to immediately enable and disable kernel features.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Use caution when changing settings on a production system using the various files in the <code class="filename">/proc/sys/</code> directory. Changing the wrong setting may render the kernel unstable, requiring a system reboot.
+ </div><div class="para">
+ For this reason, be sure the options are valid for that file before attempting to change any value in <code class="filename">/proc/sys/</code>.
+ </div></div></div><div class="para">
+ A good way to determine if a particular file can be configured, or if it is only designed to provide information, is to list it with the <code class="option">-l</code> option at the shell prompt. If the file is writable, it may be used to configure the kernel. For example, a partial listing of <code class="filename">/proc/sys/fs</code> looks like the following:
+ </div><pre class="screen">
+-r--r--r-- 1 root root 0 May 10 16:14 dentry-state
+-rw-r--r-- 1 root root 0 May 10 16:14 dir-notify-enable
+-rw-r--r-- 1 root root 0 May 10 16:14 file-max
+-r--r--r-- 1 root root 0 May 10 16:14 file-nr
+</pre><div class="para">
+ In this listing, the files <code class="filename">dir-notify-enable</code> and <code class="filename">file-max</code> can be written to and, therefore, can be used to configure the kernel. The other files only provide feedback on current settings.
+ </div><div class="para">
+ Changing a value within a <code class="filename">/proc/sys/</code> file is done by echoing the new value into the file. For example, to enable the System Request Key on a running kernel, type the command:
+ </div><pre class="screen">
+echo 1 > /proc/sys/kernel/sysrq
+</pre><div class="para">
+ This changes the value for <code class="filename">sysrq</code> from <code class="computeroutput">0</code> (off) to <code class="computeroutput">1</code> (on).
+ </div><div class="para">
+ A few <code class="filename">/proc/sys/</code> configuration files contain more than one value. To correctly send new values to them, place a space character between each value passed with the <code class="command">echo</code> command, such as is done in this example:
+ </div><pre class="screen">
+echo 4 2 45 > /proc/sys/kernel/acct
+</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Any configuration changes made using the <code class="command">echo</code> command disappear when the system is restarted. To make configuration changes take effect after the system is rebooted, refer to <a class="xref" href="s1-proc-sysctl.html" title="19.4. Using the sysctl Command">Section 19.4, “Using the <code class="command">sysctl</code> Command”</a>.
+ </div></div></div><div class="para">
+ The <code class="filename">/proc/sys/</code> directory contains several subdirectories controlling different aspects of a running kernel.
+ </div><div class="section" title="19.3.9.1. /proc/sys/dev/" id="s3-proc-sys-dev"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-sys-dev">19.3.9.1. <code class="filename">/proc/sys/dev/</code> </h4></div></div></div><a id="id521378" class="indexterm"></a><div class="para">
+ This directory provides parameters for particular devices on the system. Most systems have at least two directories, <code class="filename">cdrom/</code> and <code class="filename">raid/</code>. Customized kernels can have other directories, such as <code class="filename">parport/</code>, which provides the ability to share one parallel port between multiple device drivers.
+ </div><div class="para">
+ The <code class="filename">cdrom/</code> directory contains a file called <code class="filename">info</code>, which reveals a number of important CD-ROM parameters:
+ </div><pre class="screen">
+CD-ROM information, Id: cdrom.c 3.20 2003/12/17
+drive name: hdc
+drive speed: 48
+drive # of slots: 1
+Can close tray: 1
+Can open tray: 1
+Can lock tray: 1
+Can change speed: 1
+Can select disk: 0
+Can read multisession: 1
+Can read MCN: 1
+Reports media changed: 1
+Can play audio: 1
+Can write CD-R: 0
+Can write CD-RW: 0
+Can read DVD: 0
+Can write DVD-R: 0
+Can write DVD-RAM: 0
+Can read MRW: 0
+Can write MRW: 0
+Can write RAM: 0
+</pre><div class="para">
+ This file can be quickly scanned to discover the qualities of an unknown CD-ROM. If multiple CD-ROMs are available on a system, each device is given its own column of information.
+ </div><div class="para">
+ Various files in <code class="filename">/proc/sys/dev/cdrom</code>, such as <code class="filename">autoclose</code> and <code class="filename">checkmedia</code>, can be used to control the system's CD-ROM. Use the <code class="command">echo</code> command to enable or disable these features.
+ </div><div class="para">
+ If RAID support is compiled into the kernel, a <code class="filename">/proc/sys/dev/raid/</code> directory becomes available with at least two files in it: <code class="filename">speed_limit_min</code> and <code class="filename">speed_limit_max</code>. These settings determine the acceleration of RAID devices for I/O intensive tasks, such as resyncing the disks.
+ </div></div><div class="section" title="19.3.9.2. /proc/sys/fs/" id="s3-proc-sys-fs"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-sys-fs">19.3.9.2. <code class="filename">/proc/sys/fs/</code> </h4></div></div></div><a id="id715111" class="indexterm"></a><div class="para">
+ This directory contains an array of options and information concerning various aspects of the file system, including quota, file handle, inode, and dentry information.
+ </div><div class="para">
+ The <code class="filename">binfmt_misc/</code> directory is used to provide kernel support for miscellaneous binary formats.
+ </div><div class="para">
+ The important files in <code class="filename">/proc/sys/fs/</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">dentry-state</code> — Provides the status of the directory cache. The file looks similar to the following:
+ </div><pre class="screen">
+57411 52939 45 0 0 0
+</pre><div class="para">
+ The first number reveals the total number of directory cache entries, while the second number displays the number of unused entries. The third number tells the number of seconds between when a directory has been freed and when it can be reclaimed, and the fourth measures the pages currently requested by the system. The last two numbers are not used and display only zeros.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">file-max</code> — Lists the maximum number of file handles that the kernel allocates. Raising the value in this file can resolve errors caused by a lack of available file handles.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">file-nr</code> — Lists the number of allocated file handles, used file handles, and the maximum number of file handles.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overflowgid</code> and <code class="filename">overflowuid</code> — Defines the fixed group ID and user ID, respectively, for use with file systems that only support 16-bit group and user IDs.
+ </div></li></ul></div></div><div class="section" title="19.3.9.3. /proc/sys/kernel/" id="s3-proc-sys-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-sys-kernel">19.3.9.3. <code class="filename">/proc/sys/kernel/</code> </h4></div></div></div><a id="id715259" class="indexterm"></a><a id="id715289" class="indexterm"></a><a id="id505759" class="indexterm"></a><a id="id505778" class="indexterm"></a><a id="id505796" class="indexterm"></a><div class="para">
+ This directory contains a variety of different configuration files that directly affect the operation of the kernel. Some of the most important files include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">acct</code> — Controls the suspension of process accounting based on the percentage of free space available on the file system containing the log. By default, the file looks like the following:
+ </div><pre class="screen">
+4 2 30
+</pre><div class="para">
+ The first value dictates the percentage of free space required for logging to resume, while the second value sets the threshold percentage of free space when logging is suspended. The third value sets the interval, in seconds, that the kernel polls the file system to see if logging should be suspended or resumed.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ctrl-alt-del</code> — Controls whether <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>Delete</strong></span> gracefully restarts the computer using <code class="command">init</code> (<code class="computeroutput">0</code>) or forces an immediate reboot without syncing the dirty buffers to disk (<code class="computeroutput">1</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">domainname</code> — Configures the system domain name, such as <code class="computeroutput">example.com</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">exec-shield</code> — Configures the Exec Shield feature of the kernel. Exec Shield provides protection against certain types of buffer overflow attacks.
+ </div><div class="para">
+ There are two possible values for this virtual file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">0</code> — Disables Exec Shield.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">1</code> — Enables Exec Shield. This is the default value.
+ </div></li></ul></div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ If a system is running security-sensitive applications that were started while Exec Shield was disabled, these applications must be restarted when Exec Shield is enabled in order for Exec Shield to take effect.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="filename">hostname</code> — Configures the system hostname, such as <code class="computeroutput">www.example.com</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">hotplug</code> — Configures the utility to be used when a configuration change is detected by the system. This is primarily used with USB and Cardbus PCI. The default value of <code class="computeroutput">/sbin/hotplug</code> should not be changed unless testing a new program to fulfill this role.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">modprobe</code> — Sets the location of the program used to load kernel modules. The default value is <code class="computeroutput">/sbin/modprobe</code> which means <code class="command">kmod</code> calls it to load the module when a kernel thread calls <code class="command">kmod</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmax</code> — Sets the maximum size of any message sent from one process to another and is set to <code class="computeroutput">8192</code> bytes by default. Be careful when raising this value, as queued messages between processes are stored in non-swappable kernel memory. Any increase in <code class="filename">msgmax</code> would increase RAM requirements for the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmnb</code> — Sets the maximum number of bytes in a single message queue. The default is <code class="computeroutput">16384</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">msgmni</code> — Sets the maximum number of message queue identifiers. The default is <code class="computeroutput">4008</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">osrelease</code> — Lists the Linux kernel release number. This file can only be altered by changing the kernel source and recompiling.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ostype</code> — Displays the type of operating system. By default, this file is set to <code class="computeroutput">Linux</code>, and this value can only be changed by changing the kernel source and recompiling.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overflowgid</code> and <code class="filename">overflowuid</code> — Defines the fixed group ID and user ID, respectively, for use with system calls on architectures that only support 16-bit group and user IDs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">panic</code> — Defines the number of seconds the kernel postpones rebooting when the system experiences a kernel panic. By default, the value is set to <code class="computeroutput">0</code>, which disables automatic rebooting after a panic.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">printk</code> — This file controls a variety of settings related to printing or logging error messages. Each error message reported by the kernel has a <em class="firstterm">loglevel</em> associated with it that defines the importance of the message. The loglevel values break down in this order:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">0</code> — Kernel emergency. The system is unusable.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">1</code> — Kernel alert. Action must be taken immediately.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">2</code> — Condition of the kernel is considered critical.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">3</code> — General kernel error condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">4</code> — General kernel warning condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">5</code> — Kernel notice of a normal but significant condition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">6</code> — Kernel informational message.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">7</code> — Kernel debug-level messages.
+ </div></li></ul></div><div class="para">
+ Four values are found in the <code class="filename">printk</code> file:
+ </div><pre class="screen">
+6 4 1 7
+</pre><div class="para">
+ Each of these values defines a different rule for dealing with error messages. The first value, called the <em class="firstterm">console loglevel</em>, defines the lowest priority of messages printed to the console. (Note that, the lower the priority, the higher the loglevel number.) The second value sets the default loglevel for messages without an explicit loglevel attached to them. The third value sets the lowest possible loglevel configuration for the console loglevel. The last value sets the default value for the console loglevel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">random/</code> directory — Lists a number of values related to generating random numbers for the kernel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sem</code> — Configures <em class="firstterm">semaphore</em> settings within the kernel. A semaphore is a System V IPC object that is used to control utilization of a particular process.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmall</code> — Sets the total amount of shared memory that can be used at one time on the system, in bytes. By default, this value is <code class="computeroutput">2097152</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmmax</code> — Sets the largest shared memory segment size allowed by the kernel, in bytes. By default, this value is <code class="computeroutput">33554432</code>. However, the kernel supports much larger values than this.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">shmmni</code> — Sets the maximum number of shared memory segments for the whole system, in bytes. By default, this value is <code class="computeroutput">4096</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">sysrq</code> — Activates the System Request Key, if this value is set to anything other than zero (<code class="computeroutput">0</code>), the default.
+ </div><div class="para">
+ The System Request Key allows immediate input to the kernel through simple key combinations. For example, the System Request Key can be used to immediately shut down or restart a system, sync all mounted file systems, or dump important information to the console. To initiate a System Request Key, type <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>SysRq</strong></span>+<span class="keycap"><strong> <em class="replaceable"><code>system request code</code></em> </strong></span> . Replace <em class="replaceable"><code>system request code</code></em> with one of the following system request codes:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">r</code> — Disables raw mode for the keyboard and sets it to XLATE (a limited keyboard mode which does not recognize modifiers such as <span class="keycap"><strong>Alt</strong></span>, <span class="keycap"><strong>Ctrl</strong></span>, or <span class="keycap"><strong>Shift</strong></span> for all keys).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">k</code> — Kills all processes active in a virtual console. Also called <em class="firstterm">Secure Access Key</em> (<em class="firstterm">SAK</em>), it is often used to verify that the login prompt is spawned from <code class="command">init</code> and not a trojan copy designed to capture usernames and passwords.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">b</code> — Reboots the kernel without first unmounting file systems or syncing disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">c</code> — Crashes the system without first unmounting file systems or syncing disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">o</code> — Shuts off the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">s</code> — Attempts to sync disks attached to the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">u</code> — Attempts to unmount and remount all file systems as read-only.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">p</code> — Outputs all flags and registers to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">t</code> — Outputs a list of processes to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">m</code> — Outputs memory statistics to the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">0</code> through <code class="command">9</code> — Sets the log level for the console.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">e</code> — Kills all processes except <code class="command">init</code> using SIGTERM.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">i</code> — Kills all processes except <code class="command">init</code> using SIGKILL.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">l</code> — Kills all processes using SIGKILL (including <code class="command">init</code>). <span class="emphasis"><em>The system is unusable after issuing this System Request Key code.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">h</code> — Displays help text.
+ </div></li></ul></div><div class="para">
+ This feature is most beneficial when using a development kernel or when experiencing system freezes.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ The System Request Key feature is considered a security risk because an unattended console provides an attacker with access to the system. For this reason, it is turned off by default.
+ </div></div></div><div class="para">
+ Refer to <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/sysrq.txt</code> for more information about the System Request Key.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tainted</code> — Indicates whether a non-GPL module is loaded.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">0</code> — No non-GPL modules are loaded.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">1</code> — At least one module without a GPL license (including modules with no license) is loaded.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">2</code> — At least one module was force-loaded with the command <code class="command">insmod -f</code>.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="filename">threads-max</code> — Sets the maximum number of threads to be used by the kernel, with a default value of <code class="computeroutput">2048</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">version</code> — Displays the date and time the kernel was last compiled. The first field in this file, such as <code class="computeroutput">#3</code>, relates to the number of times a kernel was built from the source base.
+ </div></li></ul></div></div><div class="section" title="19.3.9.4. /proc/sys/net/" id="s3-proc-sys-net"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-sys-net">19.3.9.4. <code class="filename">/proc/sys/net/</code> </h4></div></div></div><a id="id427770" class="indexterm"></a><a id="id427800" class="indexterm"></a><a id="id427815" class="indexterm"></a><a id="id427829" class="indexterm"></a><div class="para">
+ This directory contains subdirectories concerning various networking topics. Various configurations at the time of kernel compilation make different directories available here, such as <code class="filename">ethernet/</code>, <code class="filename">ipv4/</code>, <code class="filename">ipx/</code>, and <code class="filename">ipv6/</code>. By altering the files within these directories, system administrators are able to adjust the network configuration on a running system.
+ </div><div class="para">
+ Given the wide variety of possible networking options available with Linux, only the most common <code class="filename">/proc/sys/net/</code> directories are discussed.
+ </div><div class="para">
+ The <code class="filename">/proc/sys/net/core/</code> directory contains a variety of settings that control the interaction between the kernel and networking layers. The most important of these files are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">message_burst</code> — Sets the amount of time in tenths of a second required to write a new warning message. This setting is used to mitigate <em class="firstterm">Denial of Service</em> (<em class="firstterm">DoS</em>) attacks. The default setting is <code class="computeroutput">10</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">message_cost</code> — Sets a cost on every warning message. The higher the value of this file (default of <code class="computeroutput">5</code>), the more likely the warning message is ignored. This setting is used to mitigate DoS attacks.
+ </div><div class="para">
+ The idea of a DoS attack is to bombard the targeted system with requests that generate errors and fill up disk partitions with log files or require all of the system's resources to handle the error logging. The settings in <code class="filename">message_burst</code> and <code class="filename">message_cost</code> are designed to be modified based on the system's acceptable risk versus the need for comprehensive logging.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">netdev_max_backlog</code> — Sets the maximum number of packets allowed to queue when a particular interface receives packets faster than the kernel can process them. The default value for this file is <code class="computeroutput">1000</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">optmem_max</code> — Configures the maximum ancillary buffer size allowed per socket.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rmem_default</code> — Sets the receive socket buffer default size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">rmem_max</code> — Sets the receive socket buffer maximum size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wmem_default</code> — Sets the send socket buffer default size in bytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">wmem_max</code> — Sets the send socket buffer maximum size in bytes.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">/proc/sys/net/ipv4/</code> directory contains additional networking settings. Many of these settings, used in conjunction with one another, are useful in preventing attacks on the system or when using the system to act as a router.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ An erroneous change to these files may affect remote connectivity to the system.
+ </div></div></div><div class="para">
+ The following is a list of some of the more important files within the <code class="filename">/proc/sys/net/ipv4/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">icmp_echo_ignore_all</code> and <code class="filename">icmp_echo_ignore_broadcasts</code> — Allows the kernel to ignore ICMP ECHO packets from every host or only those originating from broadcast and multicast addresses, respectively. A value of <code class="computeroutput">0</code> allows the kernel to respond, while a value of <code class="computeroutput">1</code> ignores the packets.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_default_ttl</code> — Sets the default <em class="firstterm">Time To Live (TTL)</em>, which limits the number of hops a packet may make before reaching its destination. Increasing this value can diminish system performance.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_forward</code> — Permits interfaces on the system to forward packets to one other. By default, this file is set to <code class="computeroutput">0</code>. Setting this file to <code class="computeroutput">1</code> enables network packet forwarding.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">ip_local_port_range</code> — Specifies the range of ports to be used by TCP or UDP when a local port is needed. The first number is the lowest port to be used and the second number specifies the highest port. Any systems that expect to require more ports than the default 1024 to 4999 should use a range from 32768 to 61000.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_syn_retries</code> — Provides a limit on the number of times the system re-transmits a SYN packet when attempting to make a connection.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_retries1</code> — Sets the number of permitted re-transmissions attempting to answer an incoming connection. Default of <code class="computeroutput">3</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">tcp_retries2</code> — Sets the number of permitted re-transmissions of TCP packets. Default of <code class="computeroutput">15</code>.
+ </div></li></ul></div><div class="para">
+ The file called
+ </div><pre class="screen">
+<code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/networking/ip-sysctl.txt</code>
+</pre><div class="para">
+ contains a complete list of files and options available in the <code class="filename">/proc/sys/net/ipv4/</code> directory.
+ </div><div class="para">
+ A number of other directories exist within the <code class="filename">/proc/sys/net/ipv4/</code> directory and each covers a different aspect of the network stack. The <code class="filename">/proc/sys/net/ipv4/conf/</code> directory allows each system interface to be configured in different ways, including the use of default settings for unconfigured devices (in the <code class="filename">/proc/sys/net/ipv4/conf/default/</code> subdirectory) and settings that override all special configurations (in the <code class="filename">/proc/sys/net/ipv4/conf/all/</code> subdirectory).
+ </div><div class="para">
+ The <code class="filename">/proc/sys/net/ipv4/neigh/</code> directory contains settings for communicating with a host directly connected to the system (called a network neighbor) and also contains different settings for systems more than one hop away.
+ </div><div class="para">
+ Routing over IPV4 also has its own directory, <code class="filename">/proc/sys/net/ipv4/route/</code>. Unlike <code class="filename">conf/</code> and <code class="filename">neigh/</code>, the <code class="filename">/proc/sys/net/ipv4/route/</code> directory contains specifications that apply to routing with any interfaces on the system. Many of these settings, such as <code class="filename">max_size</code>, <code class="filename">max_delay</code>, and <code class="filename">min_delay</code>, relate to controlling the size of the routing cache. To clear the routing cache, write any value to the <code class="filename">flush</code> file.
+ </div><div class="para">
+ Additional information about these directories and the possible values for their configuration files can be found in:
+ </div><pre class="screen">
+/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/filesystems/proc.txt
+</pre></div><div class="section" title="19.3.9.5. /proc/sys/vm/" id="s3-proc-sys-vm"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-proc-sys-vm">19.3.9.5. <code class="filename">/proc/sys/vm/</code> </h4></div></div></div><a id="id718426" class="indexterm"></a><a id="id718456" class="indexterm"></a><a id="id718471" class="indexterm"></a><div class="para">
+ This directory facilitates the configuration of the Linux kernel's virtual memory (VM) subsystem. The kernel makes extensive and intelligent use of virtual memory, which is commonly referred to as swap space.
+ </div><div class="para">
+ The following files are commonly found in the <code class="filename">/proc/sys/vm/</code> directory:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">block_dump</code> — Configures block I/O debugging when enabled. All read/write and block dirtying operations done to files are logged accordingly. This can be useful if diagnosing disk spin up and spin downs for laptop battery conservation. All output when <code class="filename">block_dump</code> is enabled can be retrieved via <code class="command">dmesg</code>. The default value is <code class="computeroutput">0</code>.
+ </div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ If <code class="filename">block_dump</code> is enabled at the same time as kernel debugging, it is prudent to stop the <code class="command">klogd</code> daemon, as it generates erroneous disk activity caused by <code class="filename">block_dump</code>.
+ </div></div></div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_background_ratio</code> — Starts background writeback of dirty data at this percentage of total memory, via a pdflush daemon. The default value is <code class="command">10</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_expire_centisecs</code> — Defines when dirty in-memory data is old enough to be eligible for writeout. Data which has been dirty in-memory for longer than this interval is written out next time a pdflush daemon wakes up. The default value is <code class="command">3000</code>, expressed in hundredths of a second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_ratio</code> — Starts active writeback of dirty data at this percentage of total memory for the generator of dirty data, via pdflush. The default value is <code class="command">20</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">dirty_writeback_centisecs</code> — Defines the interval between pdflush daemon wakeups, which periodically writes dirty in-memory data out to disk. The default value is <code class="command">500</code>, expressed in hundredths of a second.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">laptop_mode</code> — Minimizes the number of times that a hard disk needs to spin up by keeping the disk spun down for as long as possible, therefore conserving battery power on laptops. This increases efficiency by combining all future I/O processes together, reducing the frequency of spin ups. The default value is <code class="computeroutput">0</code>, but is automatically enabled in case a battery on a laptop is used.
+ </div><div class="para">
+ This value is controlled automatically by the acpid daemon once a user is notified battery power is enabled. No user modifications or interactions are necessary if the laptop supports the ACPI (Advanced Configuration and Power Interface) specification.
+ </div><div class="para">
+ For more information, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/laptop-mode.txt</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">max_map_count</code> — Configures the maximum number of memory map areas a process may have. In most cases, the default value of <code class="computeroutput">65536</code> is appropriate.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">min_free_kbytes</code> — Forces the Linux VM (virtual memory manager) to keep a minimum number of kilobytes free. The VM uses this number to compute a <code class="filename">pages_min</code> value for each <code class="filename">lowmem</code> zone in the system. The default value is in respect to the total memory on the machine.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nr_hugepages</code> — Indicates the current number of configured <code class="filename">hugetlb</code> pages in the kernel.
+ </div><div class="para">
+ For more information, refer to the following installed documentation:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/vm/hugetlbpage.txt</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">nr_pdflush_threads</code> — Indicates the number of pdflush daemons that are currently running. This file is read-only, and should not be changed by the user. Under heavy I/O loads, the default value of two is increased by the kernel.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">overcommit_memory</code> — Configures the conditions under which a large memory request is accepted or denied. The following three modes are available:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">0</code> — The kernel performs heuristic memory over commit handling by estimating the amount of memory available and failing requests that are blatantly invalid. Unfortunately, since memory is allocated using a heuristic rather than a precise algorithm, this setting can sometimes allow available memory on the system to be overloaded. This is the default setting.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">1</code> — The kernel performs no memory over commit handling. Under this setting, the potential for memory overload is increased, but so is performance for memory intensive tasks (such as those executed by some scientific software).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">2</code> — The kernel fails requests for memory that add up to all of swap plus the percent of physical RAM specified in <code class="filename">/proc/sys/vm/overcommit_ratio</code>. This setting is best for those who desire less risk of memory overcommitment.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This setting is only recommended for systems with swap areas larger than physical memory.
+ </div></div></div></li></ul></div></li><li class="listitem"><div class="para">
+ <code class="filename">overcommit_ratio</code> — Specifies the percentage of physical RAM considered when <code class="filename">/proc/sys/vm/overcommit_memory</code> is set to <code class="command">2</code>. The default value is <code class="command">50</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">page-cluster</code> — Sets the number of pages read in a single attempt. The default value of <code class="computeroutput">3</code>, which actually relates to 16 pages, is appropriate for most systems.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">swappiness</code> — Determines how much a machine should swap. The higher the value, the more swapping occurs. The default value, as a percentage, is set to <code class="computeroutput">60</code>.
+ </div></li></ul></div><div class="para">
+ All kernel-based documentation can be found in the following locally installed location:
+ </div><div class="para">
+ <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code>kernel_version</code></em>/Documentation/</code>, which contains additional information.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-scsi.html"><strong>Prev</strong>19.3.8. /proc/scsi/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-sysvipc.html"><strong>Next</strong>19.3.10. /proc/sysvipc/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-sysvipc.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-sysvipc.html
new file mode 100644
index 0000000..0c94923
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dir-sysvipc.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.10. /proc/sysvipc/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-sys.html" title="19.3.9. /proc/sys/" /><link rel="next" href="s2-proc-tty.html" title="19.3.11. /proc/tty/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-sys.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-tty.html">
<strong>Next</strong></a></li></ul><div class="section" title="19.3.10. /proc/sysvipc/" id="s2-proc-dir-sysvipc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dir-sysvipc">19.3.10. <code class="filename">/proc/sysvipc/</code> </h3></div></div></div><a id="id541866" class="indexterm"></a><div class="para">
+ This directory contains information about System V IPC resources. The files in this directory relate to System V IPC calls for messages (<code class="filename">msg</code>), semaphores (<code class="filename">sem</code>), and shared memory (<code class="filename">shm</code>).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-sys.html"><strong>Prev</strong>19.3.9. /proc/sys/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-tty.html"><strong>Next</strong>19.3.11. /proc/tty/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dma.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dma.html
new file mode 100644
index 0000000..0161a08
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-dma.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.6. /proc/dma</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-devices.html" title="19.2.5. /proc/devices" /><link rel="next" href="s2-proc-execdomains.html" title="19.2.7. /proc/execdomains" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-devices.html"><strong>Prev</strong></a></li><li class="next"><a access
key="n" href="s2-proc-execdomains.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.6. /proc/dma" id="s2-proc-dma"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-dma">19.2.6. <code class="filename">/proc/dma</code> </h3></div></div></div><a id="id718773" class="indexterm"></a><div class="para">
+ This file contains a list of the registered ISA DMA channels in use. A sample <code class="filename">/proc/dma</code> files looks like the following:
+ </div><pre class="screen">
+4: cascade
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-devices.html"><strong>Prev</strong>19.2.5. /proc/devices </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-execdomains.html"><strong>Next</strong>19.2.7. /proc/execdomains </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-execdomains.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-execdomains.html
new file mode 100644
index 0000000..f3d2b04
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-execdomains.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.7. /proc/execdomains</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-dma.html" title="19.2.6. /proc/dma" /><link rel="next" href="s2-proc-fb.html" title="19.2.8. /proc/fb" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dma.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-fb.html"
><strong>Next</strong></a></li></ul><div class="section" title="19.2.7. /proc/execdomains" id="s2-proc-execdomains"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-execdomains">19.2.7. <code class="filename">/proc/execdomains</code> </h3></div></div></div><a id="id718820" class="indexterm"></a><a id="id718841" class="indexterm"></a><a id="id460270" class="indexterm"></a><div class="para">
+ This file lists the <em class="firstterm">execution domains</em> currently supported by the Linux kernel, along with the range of personalities they support.
+ </div><pre class="screen">
+0-0 Linux [kernel]
+</pre><div class="para">
+ Think of execution domains as the "personality" for an operating system. Because other binary formats, such as Solaris, UnixWare, and FreeBSD, can be used with Linux, programmers can change the way the operating system treats system calls from these binaries by changing the personality of the task. Except for the <code class="computeroutput">PER_LINUX</code> execution domain, different personalities can be implemented as dynamically loadable modules.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dma.html"><strong>Prev</strong>19.2.6. /proc/dma </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-fb.html"><strong>Next</strong>19.2.8. /proc/fb </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-fb.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-fb.html
new file mode 100644
index 0000000..ea10691
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-fb.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.8. /proc/fb</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-execdomains.html" title="19.2.7. /proc/execdomains" /><link rel="next" href="s2-proc-filesystems.html" title="19.2.9. /proc/filesystems" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-execdomains.html"><strong>Prev</strong></a></li><li class="nex
t"><a accesskey="n" href="s2-proc-filesystems.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.8. /proc/fb" id="s2-proc-fb"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-fb">19.2.8. <code class="filename">/proc/fb</code> </h3></div></div></div><a id="id460319" class="indexterm"></a><a id="id460341" class="indexterm"></a><div class="para">
+ This file contains a list of frame buffer devices, with the frame buffer device number and the driver that controls it. Typical output of <code class="filename">/proc/fb</code> for systems which contain frame buffer devices looks similar to the following:
+ </div><pre class="screen">
+0 VESA VGA
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-execdomains.html"><strong>Prev</strong>19.2.7. /proc/execdomains </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-filesystems.html"><strong>Next</strong>19.2.9. /proc/filesystems </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-filesystems.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-filesystems.html
new file mode 100644
index 0000000..482155c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-filesystems.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.9. /proc/filesystems</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-fb.html" title="19.2.8. /proc/fb" /><link rel="next" href="s2-proc-interrupts.html" title="19.2.10. /proc/interrupts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-fb.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2
-proc-interrupts.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.9. /proc/filesystems" id="s2-proc-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-filesystems">19.2.9. <code class="filename">/proc/filesystems</code> </h3></div></div></div><a id="id460385" class="indexterm"></a><div class="para">
+ This file displays a list of the file system types currently supported by the kernel. Sample output from a generic <code class="filename">/proc/filesystems</code> file looks similar to the following:
+ </div><pre class="screen">
+nodev sysfs
+nodev rootfs
+nodev bdev
+nodev proc
+nodev sockfs
+nodev binfmt_misc
+nodev usbfs
+nodev usbdevfs
+nodev futexfs
+nodev tmpfs
+nodev pipefs
+nodev eventpollfs
+nodev devpts
+ ext2
+nodev ramfs
+nodev hugetlbfs
+ iso9660
+nodev mqueue
+ ext3
+nodev rpc_pipefs
+nodev autofs
+</pre><div class="para">
+ The first column signifies whether the file system is mounted on a block device. Those beginning with <code class="computeroutput">nodev</code> are not mounted on a device. The second column lists the names of the file systems supported.
+ </div><div class="para">
+ The <code class="command">mount</code> command cycles through the file systems listed here when one is not specified as an argument.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-fb.html"><strong>Prev</strong>19.2.8. /proc/fb </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-interrupts.html"><strong>Next</strong>19.2.10. /proc/interrupts </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-interrupts.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-interrupts.html
new file mode 100644
index 0000000..94faa9d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-interrupts.html
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.10. /proc/interrupts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-filesystems.html" title="19.2.9. /proc/filesystems" /><link rel="next" href="s2-proc-iomem.html" title="19.2.11. /proc/iomem" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-filesystems.html"><strong>Prev</strong></a></li><li class="next"><a acces
skey="n" href="s2-proc-iomem.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.10. /proc/interrupts" id="s2-proc-interrupts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-interrupts">19.2.10. <code class="filename">/proc/interrupts</code> </h3></div></div></div><a id="id460452" class="indexterm"></a><div class="para">
+ This file records the number of interrupts per IRQ on the x86 architecture. A standard <code class="filename">/proc/interrupts</code> looks similar to the following:
+ </div><pre class="screen">
+ CPU0
+ 0: 80448940 XT-PIC timer
+ 1: 174412 XT-PIC keyboard
+ 2: 0 XT-PIC cascade
+ 8: 1 XT-PIC rtc
+ 10: 410964 XT-PIC eth0
+ 12: 60330 XT-PIC PS/2 Mouse
+ 14: 1314121 XT-PIC ide0
+ 15: 5195422 XT-PIC ide1
+NMI: 0
+ERR: 0
+</pre><div class="para">
+ For a multi-processor machine, this file may look slightly different:
+ </div><pre class="screen">
+ CPU0 CPU1
+ 0: 1366814704 0 XT-PIC timer
+ 1: 128 340 IO-APIC-edge keyboard
+ 2: 0 0 XT-PIC cascade
+ 8: 0 1 IO-APIC-edge rtc
+ 12: 5323 5793 IO-APIC-edge PS/2 Mouse
+ 13: 1 0 XT-PIC fpu
+ 16: 11184294 15940594 IO-APIC-level Intel EtherExpress Pro 10/100 Ethernet
+ 20: 8450043 11120093 IO-APIC-level megaraid
+ 30: 10432 10722 IO-APIC-level aic7xxx
+ 31: 23 22 IO-APIC-level aic7xxx
+NMI: 0
+ERR: 0
+</pre><div class="para">
+ The first column refers to the IRQ number. Each CPU in the system has its own column and its own number of interrupts per IRQ. The next column reports the type of interrupt, and the last column contains the name of the device that is located at that IRQ.
+ </div><div class="para">
+ Each of the types of interrupts seen in this file, which are architecture-specific, mean something different. For x86 machines, the following values are common:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">XT-PIC</code> — This is the old AT computer interrupts.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">IO-APIC-edge</code> — The voltage signal on this interrupt transitions from low to high, creating an <span class="emphasis"><em>edge</em></span>, where the interrupt occurs and is only signaled once. This kind of interrupt, as well as the <code class="computeroutput">IO-APIC-level</code> interrupt, are only seen on systems with processors from the 586 family and higher.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">IO-APIC-level</code> — Generates interrupts when its voltage signal is high until the signal is low again.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-filesystems.html"><strong>Prev</strong>19.2.9. /proc/filesystems </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-iomem.html"><strong>Next</strong>19.2.11. /proc/iomem </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-iomem.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-iomem.html
new file mode 100644
index 0000000..669fd8b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-iomem.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.11. /proc/iomem</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-interrupts.html" title="19.2.10. /proc/interrupts" /><link rel="next" href="s2-proc-ioports.html" title="19.2.12. /proc/ioports" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-interrupts.html"><strong>Prev</strong></a></li><li class="next"><a acc
esskey="n" href="s2-proc-ioports.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.11. /proc/iomem" id="s2-proc-iomem"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-iomem">19.2.11. <code class="filename">/proc/iomem</code> </h3></div></div></div><a id="id620062" class="indexterm"></a><div class="para">
+ This file shows you the current map of the system's memory for each physical device:
+ </div><pre class="screen">
+00000000-0009fbff : System RAM
+0009fc00-0009ffff : reserved
+000a0000-000bffff : Video RAM area
+000c0000-000c7fff : Video ROM
+000f0000-000fffff : System ROM
+00100000-07ffffff : System RAM
+00100000-00291ba8 : Kernel code
+00291ba9-002e09cb : Kernel data
+e0000000-e3ffffff : VIA Technologies, Inc. VT82C597 [Apollo VP3] e4000000-e7ffffff : PCI Bus #01
+e4000000-e4003fff : Matrox Graphics, Inc. MGA G200 AGP
+e5000000-e57fffff : Matrox Graphics, Inc. MGA G200 AGP
+e8000000-e8ffffff : PCI Bus #01
+e8000000-e8ffffff : Matrox Graphics, Inc. MGA G200 AGP
+ea000000-ea00007f : Digital Equipment Corporation DECchip 21140 [FasterNet]
+ea000000-ea00007f : tulip ffff0000-ffffffff : reserved
+</pre><div class="para">
+ The first column displays the memory registers used by each of the different types of memory. The second column lists the kind of memory located within those registers and displays which memory registers are used by the kernel within the system RAM or, if the network interface card has multiple Ethernet ports, the memory registers assigned for each port.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-interrupts.html"><strong>Prev</strong>19.2.10. /proc/interrupts </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-ioports.html"><strong>Next</strong>19.2.12. /proc/ioports </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-ioports.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-ioports.html
new file mode 100644
index 0000000..7d72a93
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-ioports.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.12. /proc/ioports</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-iomem.html" title="19.2.11. /proc/iomem" /><link rel="next" href="s2-proc-kcore.html" title="19.2.13. /proc/kcore" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-iomem.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2
-proc-kcore.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.12. /proc/ioports" id="s2-proc-ioports"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-ioports">19.2.12. <code class="filename">/proc/ioports</code> </h3></div></div></div><a id="id620120" class="indexterm"></a><div class="para">
+ The output of <code class="filename">/proc/ioports</code> provides a list of currently registered port regions used for input or output communication with a device. This file can be quite long. The following is a partial listing:
+ </div><pre class="screen">
+0000-001f : dma1
+0020-003f : pic1
+0040-005f : timer
+0060-006f : keyboard
+0070-007f : rtc
+0080-008f : dma page reg
+00a0-00bf : pic2
+00c0-00df : dma2
+00f0-00ff : fpu
+0170-0177 : ide1
+01f0-01f7 : ide0
+02f8-02ff : serial(auto)
+0376-0376 : ide1
+03c0-03df : vga+
+03f6-03f6 : ide0
+03f8-03ff : serial(auto)
+0cf8-0cff : PCI conf1
+d000-dfff : PCI Bus #01
+e000-e00f : VIA Technologies, Inc. Bus Master IDE
+e000-e007 : ide0
+e008-e00f : ide1
+e800-e87f : Digital Equipment Corporation DECchip 21140 [FasterNet]
+e800-e87f : tulip
+</pre><div class="para">
+ The first column gives the I/O port address range reserved for the device listed in the second column.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-iomem.html"><strong>Prev</strong>19.2.11. /proc/iomem </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-kcore.html"><strong>Next</strong>19.2.13. /proc/kcore </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-kcore.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-kcore.html
new file mode 100644
index 0000000..c27828b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-kcore.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.13. /proc/kcore</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-ioports.html" title="19.2.12. /proc/ioports" /><link rel="next" href="s2-proc-kmsg.html" title="19.2.14. /proc/kmsg" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-ioports.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href
="s2-proc-kmsg.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.13. /proc/kcore" id="s2-proc-kcore"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-kcore">19.2.13. <code class="filename">/proc/kcore</code> </h3></div></div></div><a id="id620179" class="indexterm"></a><div class="para">
+ This file represents the physical memory of the system and is stored in the core file format. Unlike most <code class="filename">/proc/</code> files, <code class="filename">kcore</code> displays a size. This value is given in bytes and is equal to the size of the physical memory (RAM) used plus 4 KB.
+ </div><div class="para">
+ The contents of this file are designed to be examined by a debugger, such as <code class="command">gdb</code>, and is not human readable.
+ </div><div class="warning" title="Caution"><div class="admonition_header"><h2>Caution</h2></div><div class="admonition"><div class="para">
+ Do not view the <code class="filename">/proc/kcore</code> virtual file. The contents of the file scramble text output on the terminal. If this file is accidentally viewed, press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>C</strong></span> to stop the process and then type <code class="command">reset</code> to bring back the command line prompt.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-ioports.html"><strong>Prev</strong>19.2.12. /proc/ioports </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-kmsg.html"><strong>Next</strong>19.2.14. /proc/kmsg </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-kmsg.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-kmsg.html
new file mode 100644
index 0000000..628df9e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-kmsg.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.14. /proc/kmsg</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-kcore.html" title="19.2.13. /proc/kcore" /><link rel="next" href="s2-proc-loadavg.html" title="19.2.15. /proc/loadavg" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-kcore.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href
="s2-proc-loadavg.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.14. /proc/kmsg" id="s2-proc-kmsg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-kmsg">19.2.14. <code class="filename">/proc/kmsg</code> </h3></div></div></div><a id="id740356" class="indexterm"></a><div class="para">
+ This file is used to hold messages generated by the kernel. These messages are then picked up by other programs, such as <code class="command">/sbin/klogd</code> or <code class="command">/bin/dmesg</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-kcore.html"><strong>Prev</strong>19.2.13. /proc/kcore </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-loadavg.html"><strong>Next</strong>19.2.15. /proc/loadavg </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-loadavg.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-loadavg.html
new file mode 100644
index 0000000..9f5b379
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-loadavg.html
@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.15. /proc/loadavg</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-kmsg.html" title="19.2.14. /proc/kmsg" /><link rel="next" href="s2-proc-locks.html" title="19.2.16. /proc/locks" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-kmsg.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-pr
oc-locks.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.15. /proc/loadavg" id="s2-proc-loadavg"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-loadavg">19.2.15. <code class="filename">/proc/loadavg</code> </h3></div></div></div><a id="id740407" class="indexterm"></a><div class="para">
+ This file provides a look at the load average in regard to both the CPU and IO over time, as well as additional data used by <code class="command">uptime</code> and other commands. A sample <code class="filename">/proc/loadavg</code> file looks similar to the following:
+ </div><pre class="screen">
+0.20 0.18 0.12 1/80 11206
+</pre><div class="para">
+ The first three columns measure CPU and IO utilization of the last one, five, and 15 minute periods. The fourth column shows the number of currently running processes and the total number of processes. The last column displays the last process ID used.
+ </div><div class="para">
+ In addition, load average also refers to the number of processes ready to run (i.e. in the run queue, waiting for a CPU share.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-kmsg.html"><strong>Prev</strong>19.2.14. /proc/kmsg </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-locks.html"><strong>Next</strong>19.2.16. /proc/locks </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-locks.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-locks.html
new file mode 100644
index 0000000..130797e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-locks.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.16. /proc/locks</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-loadavg.html" title="19.2.15. /proc/loadavg" /><link rel="next" href="s2-proc-mdstat.html" title="19.2.17. /proc/mdstat" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-loadavg.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n"
href="s2-proc-mdstat.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.16. /proc/locks" id="s2-proc-locks"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-locks">19.2.16. <code class="filename">/proc/locks</code> </h3></div></div></div><a id="id740474" class="indexterm"></a><div class="para">
+ This file displays the files currently locked by the kernel. The contents of this file contain internal kernel debugging data and can vary tremendously, depending on the use of the system. A sample <code class="filename">/proc/locks</code> file for a lightly loaded system looks similar to the following:
+ </div><pre class="screen">
+1: POSIX ADVISORY WRITE 3568 fd:00:2531452 0 EOF
+2: FLOCK ADVISORY WRITE 3517 fd:00:2531448 0 EOF
+3: POSIX ADVISORY WRITE 3452 fd:00:2531442 0 EOF
+4: POSIX ADVISORY WRITE 3443 fd:00:2531440 0 EOF
+5: POSIX ADVISORY WRITE 3326 fd:00:2531430 0 EOF
+6: POSIX ADVISORY WRITE 3175 fd:00:2531425 0 EOF
+7: POSIX ADVISORY WRITE 3056 fd:00:2548663 0 EOF
+</pre><div class="para">
+ Each lock has its own line which starts with a unique number. The second column refers to the class of lock used, with <code class="computeroutput">FLOCK</code> signifying the older-style UNIX file locks from a <code class="command">flock</code> system call and <code class="computeroutput">POSIX</code> representing the newer POSIX locks from the <code class="command">lockf</code> system call.
+ </div><div class="para">
+ The third column can have two values: <code class="computeroutput">ADVISORY</code> or <code class="computeroutput">MANDATORY</code>. <code class="computeroutput">ADVISORY</code> means that the lock does not prevent other people from accessing the data; it only prevents other attempts to lock it. <code class="computeroutput">MANDATORY</code> means that no other access to the data is permitted while the lock is held. The fourth column reveals whether the lock is allowing the holder <code class="computeroutput">READ</code> or <code class="computeroutput">WRITE</code> access to the file. The fifth column shows the ID of the process holding the lock. The sixth column shows the ID of the file being locked, in the format of <code class="computeroutput"><em class="replaceable"><code>MAJOR-DEVICE</code></em>:<em class="replaceable"><code>MINOR-DEVICE</code></em>:<em class="replaceable"><code>INODE-NUMBER</code></em> </code>. The seventh and eighth column shows the start and end o
f the file's locked region.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-loadavg.html"><strong>Prev</strong>19.2.15. /proc/loadavg </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-mdstat.html"><strong>Next</strong>19.2.17. /proc/mdstat </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-mdstat.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-mdstat.html
new file mode 100644
index 0000000..8eeb534
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-mdstat.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.17. /proc/mdstat</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-locks.html" title="19.2.16. /proc/locks" /><link rel="next" href="s2-proc-meminfo.html" title="19.2.18. /proc/meminfo" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-locks.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href
="s2-proc-meminfo.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.17. /proc/mdstat" id="s2-proc-mdstat"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-mdstat">19.2.17. <code class="filename">/proc/mdstat</code> </h3></div></div></div><a id="id494866" class="indexterm"></a><div class="para">
+ This file contains the current information for multiple-disk, RAID configurations. If the system does not contain such a configuration, then <code class="filename">/proc/mdstat</code> looks similar to the following:
+ </div><pre class="screen">
+Personalities : read_ahead not set unused devices: <none>
+</pre><div class="para">
+ This file remains in the same state as seen above unless a software RAID or <code class="filename">md</code> device is present. In that case, view <code class="filename">/proc/mdstat</code> to find the current status of <code class="filename">md<em class="replaceable"><code>X</code></em> </code> RAID devices.
+ </div><div class="para">
+ The <code class="filename">/proc/mdstat</code> file below shows a system with its <code class="filename">md0</code> configured as a RAID 1 device, while it is currently re-syncing the disks:
+ </div><pre class="screen">
+Personalities : [linear] [raid1] read_ahead 1024 sectors
+md0: active raid1 sda2[1] sdb2[0] 9940 blocks [2/2] [UU] resync=1% finish=12.3min algorithm 2 [3/3] [UUU]
+unused devices: <none>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-locks.html"><strong>Prev</strong>19.2.16. /proc/locks </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-meminfo.html"><strong>Next</strong>19.2.18. /proc/meminfo </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-meminfo.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-meminfo.html
new file mode 100644
index 0000000..373b053
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-meminfo.html
@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.18. /proc/meminfo</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-mdstat.html" title="19.2.17. /proc/mdstat" /><link rel="next" href="s2-proc-misc.html" title="19.2.19. /proc/misc" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-mdstat.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s
2-proc-misc.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.18. /proc/meminfo" id="s2-proc-meminfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-meminfo">19.2.18. <code class="filename">/proc/meminfo</code> </h3></div></div></div><a id="id494953" class="indexterm"></a><div class="para">
+ This is one of the more commonly used files in the <code class="filename">/proc/</code> directory, as it reports a large amount of valuable information about the systems RAM usage.
+ </div><div class="para">
+ The following sample <code class="filename">/proc/meminfo</code> virtual file is from a system with 256 MB of RAM and 512 MB of swap space:
+ </div><pre class="screen">
+MemTotal: 255908 kB
+MemFree: 69936 kB
+Buffers: 15812 kB
+Cached: 115124 kB
+SwapCached: 0 kB
+Active: 92700 kB
+Inactive: 63792 kB
+HighTotal: 0 kB
+HighFree: 0 kB
+LowTotal: 255908 kB
+LowFree: 69936 kB
+SwapTotal: 524280 kB
+SwapFree: 524280 kB
+Dirty: 4 kB
+Writeback: 0 kB
+Mapped: 42236 kB
+Slab: 25912 kB
+Committed_AS: 118680 kB
+PageTables: 1236 kB
+VmallocTotal: 3874808 kB
+VmallocUsed: 1416 kB
+VmallocChunk: 3872908 kB
+HugePages_Total: 0
+HugePages_Free: 0
+Hugepagesize: 4096 kB
+</pre><div class="para">
+ Much of the information here is used by the <code class="command">free</code>, <code class="command">top</code>, and <code class="command">ps</code> commands. In fact, the output of the <code class="command">free</code> command is similar in appearance to the contents and structure of <code class="filename">/proc/meminfo</code>. But by looking directly at <code class="filename">/proc/meminfo</code>, more details are revealed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">MemTotal</code> — Total amount of physical RAM, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">MemFree</code> — The amount of physical RAM, in kilobytes, left unused by the system.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Buffers</code> — The amount of physical RAM, in kilobytes, used for file buffers.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Cached</code> — The amount of physical RAM, in kilobytes, used as cache memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapCached</code> — The amount of swap, in kilobytes, used as cache memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Active</code> — The total amount of buffer or page cache memory, in kilobytes, that is in active use. This is memory that has been recently used and is usually not reclaimed for other purposes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Inactive</code> — The total amount of buffer or page cache memory, in kilobytes, that are free and available. This is memory that has not been recently used and can be reclaimed for other purposes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HighTotal</code> and <code class="computeroutput">HighFree</code> — The total and free amount of memory, in kilobytes, that is not directly mapped into kernel space. The <code class="computeroutput">HighTotal</code> value can vary based on the type of kernel used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">LowTotal</code> and <code class="computeroutput">LowFree</code> — The total and free amount of memory, in kilobytes, that is directly mapped into kernel space. The <code class="computeroutput">LowTotal</code> value can vary based on the type of kernel used.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapTotal</code> — The total amount of swap available, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SwapFree</code> — The total amount of swap free, in kilobytes.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Dirty</code> — The total amount of memory, in kilobytes, waiting to be written back to the disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Writeback</code> — The total amount of memory, in kilobytes, actively being written back to the disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Mapped</code> — The total amount of memory, in kilobytes, which have been used to map devices, files, or libraries using the <code class="command">mmap</code> command.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Slab</code> — The total amount of memory, in kilobytes, used by the kernel to cache data structures for its own use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Committed_AS</code> — The total amount of memory, in kilobytes, estimated to complete the workload. This value represents the worst case scenario value, and also includes swap memory.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">PageTables</code> — The total amount of memory, in kilobytes, dedicated to the lowest page table level.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocTotal</code> — The total amount of memory, in kilobytes, of total allocated virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocUsed</code> — The total amount of memory, in kilobytes, of used virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">VMallocChunk</code> — The largest contiguous block of memory, in kilobytes, of available virtual address space.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HugePages_Total</code> — The total number of hugepages for the system. The number is derived by dividing <code class="computeroutput">Hugepagesize</code> by the megabytes set aside for hugepages specified in <code class="filename">/proc/sys/vm/hugetlb_pool</code>. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">HugePages_Free</code> — The total number of hugepages available for the system. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">Hugepagesize</code> — The size for each hugepages unit in kilobytes. By default, the value is 4096 KB on uniprocessor kernels for 32 bit architectures. For SMP, hugemem kernels, and AMD64, the default is 2048 KB. For Itanium architectures, the default is 262144 KB. <span class="emphasis"><em>This statistic only appears on the x86, Itanium, and AMD64 architectures.</em></span>
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-mdstat.html"><strong>Prev</strong>19.2.17. /proc/mdstat </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-misc.html"><strong>Next</strong>19.2.19. /proc/misc </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-misc.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-misc.html
new file mode 100644
index 0000000..ecdeaef
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-misc.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.19. /proc/misc</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-meminfo.html" title="19.2.18. /proc/meminfo" /><link rel="next" href="s2-proc-modules.html" title="19.2.20. /proc/modules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-meminfo.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n
" href="s2-proc-modules.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.19. /proc/misc" id="s2-proc-misc"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-misc">19.2.19. <code class="filename">/proc/misc</code> </h3></div></div></div><a id="id684611" class="indexterm"></a><div class="para">
+ This file lists miscellaneous drivers registered on the miscellaneous major device, which is device number 10:
+ </div><pre class="screen">
+63 device-mapper 175 agpgart 135 rtc 134 apm_bios
+</pre><div class="para">
+ The first column is the minor number of each device, while the second column shows the driver in use.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-meminfo.html"><strong>Prev</strong>19.2.18. /proc/meminfo </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-modules.html"><strong>Next</strong>19.2.20. /proc/modules </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-modules.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-modules.html
new file mode 100644
index 0000000..32a62a7
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-modules.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.20. /proc/modules</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-misc.html" title="19.2.19. /proc/misc" /><link rel="next" href="s2-proc-mounts.html" title="19.2.21. /proc/mounts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-misc.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-
proc-mounts.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.20. /proc/modules" id="s2-proc-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-modules">19.2.20. <code class="filename">/proc/modules</code> </h3></div></div></div><a id="id684662" class="indexterm"></a><div class="para">
+ This file displays a list of all modules loaded into the kernel. Its contents vary based on the configuration and use of your system, but it should be organized in a similar manner to this sample <code class="filename">/proc/modules</code> file output:
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ This example has been reformatted into a readable format. Most of this information can also be viewed via the <code class="command">/sbin/lsmod</code> command.
+ </div></div></div><pre class="screen">
+nfs 170109 0 - Live 0x129b0000
+lockd 51593 1 nfs, Live 0x128b0000
+nls_utf8 1729 0 - Live 0x12830000
+vfat 12097 0 - Live 0x12823000
+fat 38881 1 vfat, Live 0x1287b000
+autofs4 20293 2 - Live 0x1284f000
+sunrpc 140453 3 nfs,lockd, Live 0x12954000
+3c59x 33257 0 - Live 0x12871000
+uhci_hcd 28377 0 - Live 0x12869000
+md5 3777 1 - Live 0x1282c000
+ipv6 211845 16 - Live 0x128de000
+ext3 92585 2 - Live 0x12886000
+jbd 65625 1 ext3, Live 0x12857000
+dm_mod 46677 3 - Live 0x12833000
+</pre><div class="para">
+ The first column contains the name of the module.
+ </div><div class="para">
+ The second column refers to the memory size of the module, in bytes.
+ </div><div class="para">
+ The third column lists how many instances of the module are currently loaded. A value of zero represents an unloaded module.
+ </div><div class="para">
+ The fourth column states if the module depends upon another module to be present in order to function, and lists those other modules.
+ </div><div class="para">
+ The fifth column lists what load state the module is in: <code class="command">Live</code>, <code class="command">Loading</code>, or <code class="command">Unloading</code> are the only possible values.
+ </div><div class="para">
+ The sixth column lists the current kernel memory offset for the loaded module. This information can be useful for debugging purposes, or for profiling tools such as <code class="filename">oprofile</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-misc.html"><strong>Prev</strong>19.2.19. /proc/misc </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-mounts.html"><strong>Next</strong>19.2.21. /proc/mounts </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-mounts.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-mounts.html
new file mode 100644
index 0000000..d8a821f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-mounts.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.21. /proc/mounts</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-modules.html" title="19.2.20. /proc/modules" /><link rel="next" href="s2-proc-mtrr.html" title="19.2.22. /proc/mtrr" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-modules.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href
="s2-proc-mtrr.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.21. /proc/mounts" id="s2-proc-mounts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-mounts">19.2.21. <code class="filename">/proc/mounts</code> </h3></div></div></div><a id="id763310" class="indexterm"></a><div class="para">
+ This file provides a list of all mounts in use by the system:
+ </div><pre class="screen">
+rootfs / rootfs rw 0 0
+/proc /proc proc rw,nodiratime 0 0 none
+/dev ramfs rw 0 0
+/dev/mapper/VolGroup00-LogVol00 / ext3 rw 0 0
+none /dev ramfs rw 0 0
+/proc /proc proc rw,nodiratime 0 0
+/sys /sys sysfs rw 0 0
+none /dev/pts devpts rw 0 0
+usbdevfs /proc/bus/usb usbdevfs rw 0 0
+/dev/hda1 /boot ext3 rw 0 0
+none /dev/shm tmpfs rw 0 0
+none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
+sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
+</pre><div class="para">
+ The output found here is similar to the contents of <code class="filename">/etc/mtab</code>, except that <code class="filename">/proc/mounts</code> is more up-to-date.
+ </div><div class="para">
+ The first column specifies the device that is mounted, the second column reveals the mount point, and the third column tells the file system type, and the fourth column tells you if it is mounted read-only (<code class="computeroutput">ro</code>) or read-write (<code class="computeroutput">rw</code>). The fifth and sixth columns are dummy values designed to match the format used in <code class="filename">/etc/mtab</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-modules.html"><strong>Prev</strong>19.2.20. /proc/modules </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-mtrr.html"><strong>Next</strong>19.2.22. /proc/mtrr </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-mtrr.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-mtrr.html
new file mode 100644
index 0000000..de66424
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-mtrr.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.22. /proc/mtrr</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-mounts.html" title="19.2.21. /proc/mounts" /><link rel="next" href="s2-proc-partitions.html" title="19.2.23. /proc/partitions" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-mounts.html"><strong>Prev</strong></a></li><li class="next"><a accesskey
="n" href="s2-proc-partitions.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.22. /proc/mtrr" id="s2-proc-mtrr"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-mtrr">19.2.22. <code class="filename">/proc/mtrr</code> </h3></div></div></div><a id="id763391" class="indexterm"></a><div class="para">
+ This file refers to the current Memory Type Range Registers (MTRRs) in use with the system. If the system architecture supports MTRRs, then the <code class="filename">/proc/mtrr</code> file may look similar to the following:
+ </div><pre class="screen">
+reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
+reg01: base=0xe8000000 (3712MB), size= 32MB: write-combining, count=1
+</pre><div class="para">
+ MTRRs are used with the Intel P6 family of processors (Pentium II and higher) and control processor access to memory ranges. When using a video card on a PCI or AGP bus, a properly configured <code class="filename">/proc/mtrr</code> file can increase performance more than 150%.
+ </div><div class="para">
+ Most of the time, this value is properly configured by default. More information on manually configuring this file can be found locally at the following location:
+ </div><pre class="screen">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/<em class="replaceable"><code><arch></code></em>/mtrr.txt</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-mounts.html"><strong>Prev</strong>19.2.21. /proc/mounts </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-partitions.html"><strong>Next</strong>19.2.23. /proc/partitions </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-partitions.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-partitions.html
new file mode 100644
index 0000000..a2598e8
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-partitions.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.23. /proc/partitions</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-mtrr.html" title="19.2.22. /proc/mtrr" /><link rel="next" href="s2-proc-slabinfo.html" title="19.2.24. /proc/slabinfo" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-mtrr.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href=
"s2-proc-slabinfo.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.23. /proc/partitions" id="s2-proc-partitions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-partitions">19.2.23. <code class="filename">/proc/partitions</code> </h3></div></div></div><a id="id763469" class="indexterm"></a><div class="para">
+ This file contains partition block allocation information. A sampling of this file from a basic system looks similar to the following:
+ </div><pre class="screen">
+major minor #blocks name
+ 3 0 19531250 hda
+ 3 1 104391 hda1
+ 3 2 19422585 hda2
+253 0 22708224 dm-0
+253 1 524288 dm-1
+</pre><div class="para">
+ Most of the information here is of little importance to the user, except for the following columns:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">major</code> — The major number of the device with this partition. The major number in the <code class="filename">/proc/partitions</code>, (<code class="computeroutput">3</code>), corresponds with the block device <code class="computeroutput">ide0</code>, in <code class="filename">/proc/devices</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">minor</code> — The minor number of the device with this partition. This serves to separate the partitions into different physical devices and relates to the number at the end of the name of the partition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">#blocks</code> — Lists the number of physical disk blocks contained in a particular partition.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">name</code> — The name of the partition.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-mtrr.html"><strong>Prev</strong>19.2.22. /proc/mtrr </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-slabinfo.html"><strong>Next</strong>19.2.24. /proc/slabinfo </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-pci.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-pci.html
new file mode 100644
index 0000000..55f6e9e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-pci.html
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.3. /proc/bus/pci</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-bus.html" title="19.3.2. /proc/bus/" /><link rel="next" href="s2-proc-dir-driver.html" title="19.3.4. /proc/driver/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-bus.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-d
ir-driver.html"><strong>Next</strong></a></li></ul><div class="section" title="19.3.3. /proc/bus/pci" id="s2-proc-pci"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-pci">19.3.3. <code class="filename">/proc/bus/pci</code> </h3></div></div></div><a id="id579660" class="indexterm"></a><a id="id579690" class="indexterm"></a><div class="para">
+ Later versions of the 2.6 Linux kernel have obsoleted the <code class="filename">/proc/pci</code> directory in favor of the <code class="filename">/proc/bus/pci</code> directory. Although you can get a list of all PCI devices present on the system using the command <code class="command">cat /proc/bus/pci/devices</code>, the output is difficult to read and interpret.
+ </div><div class="para">
+ For a human-readable list of PCI devices, run the following command:
+ </div><pre class="screen">~]# <code class="command">/sbin/lspci -vb</code>
+00:00.0 Host bridge: Intel Corporation 82X38/X48 Express DRAM Controller
+ Subsystem: Hewlett-Packard Company Device 1308
+ Flags: bus master, fast devsel, latency 0
+ Capabilities: [e0] Vendor Specific Information <?>
+ Kernel driver in use: x38_edac
+ Kernel modules: x38_edac
+
+00:01.0 PCI bridge: Intel Corporation 82X38/X48 Express Host-Primary PCI Express Bridge (prog-if 00 [Normal decode])
+ Flags: bus master, fast devsel, latency 0
+ Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
+ I/O behind bridge: 00001000-00001fff
+ Memory behind bridge: f0000000-f2ffffff
+ Capabilities: [88] Subsystem: Hewlett-Packard Company Device 1308
+ Capabilities: [80] Power Management version 3
+ Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
+ Capabilities: [a0] Express Root Port (Slot+), MSI 00
+ Capabilities: [100] Virtual Channel <?>
+ Capabilities: [140] Root Complex Link <?>
+ Kernel driver in use: pcieport
+ Kernel modules: shpchp
+
+00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) (prog-if 00 [UHCI])
+ Subsystem: Hewlett-Packard Company Device 1308
+ Flags: bus master, medium devsel, latency 0, IRQ 5
+ I/O ports at 2100
+ Capabilities: [50] PCI Advanced Features
+ Kernel driver in use: uhci_hcd
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em>
+</pre><div class="para">
+ The output is a sorted list of all IRQ numbers and addresses as seen by the cards on the PCI bus instead of as seen by the kernel. Beyond providing the name and version of the device, this list also gives detailed IRQ information so an administrator can quickly look for conflicts.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-bus.html"><strong>Prev</strong>19.3.2. /proc/bus/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-dir-driver.html"><strong>Next</strong>19.3.4. /proc/driver/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-pid.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-pid.html
new file mode 100644
index 0000000..cc502ff
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-pid.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.12. /proc/PID/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s2-proc-tty.html" title="19.3.11. /proc/tty/" /><link rel="next" href="s1-proc-sysctl.html" title="19.4. Using the sysctl Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-tty.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-proc-sysc
tl.html"><strong>Next</strong></a></li></ul><div class="section" title="19.3.12. /proc/PID/" id="s2-proc-pid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-pid">19.3.12. <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> </h3></div></div></div><a id="id555677" class="indexterm"></a><div class="para">
+ Out of Memory (OOM) refers to a computing state where all available memory, including swap space, has been allocated. When this situation occurs, it will cause the system to panic and stop functioning as expected. There is a switch that controls OOM behavior in <code class="filename">/proc/sys/vm/panic_on_oom</code>. When set to <code class="filename">1</code> the kernel will panic on OOM. A setting of <code class="filename">0</code> instructs the kernel to call a function named <code class="filename">oom_killer</code> on an OOM. Usually, <code class="filename">oom_killer</code> can kill rogue processes and the system will survive.
+ </div><div class="para">
+ The easiest way to change this is to echo the new value to <code class="filename">/proc/sys/vm/panic_on_oom</code>.
+ </div><pre class="screen">
+# cat /proc/sys/vm/panic_on_oom
+1
+
+# echo 0 > /proc/sys/vm/panic_on_oom
+
+# cat /proc/sys/vm/panic_on_oom
+0
+</pre><div class="para">
+ It is also possible to prioritize which processes get killed by adjusting the <code class="filename">oom_killer</code> score. In <code class="filename">/proc/<em class="replaceable"><code>PID</code></em>/</code> there are two tools labelled <code class="filename">oom_adj</code> and <code class="filename">oom_score</code>. Valid scores for <code class="filename">oom_adj</code> are in the range -16 to +15. To see the current <code class="filename">oom_killer</code> score, view the <code class="filename">oom_score</code> for the process. <code class="filename">oom_killer</code> will kill processes with the highest scores first.
+ </div><div class="para">
+ This example adjusts the oom_score of a process with a <em class="replaceable"><code>PID</code></em> of 12465 to make it less likely that <code class="filename">oom_killer</code> will kill it.
+ </div><pre class="screen">
+# cat /proc/12465/oom_score
+79872
+
+# echo -5 > /proc/12465/oom_adj
+
+# cat /proc/12465/oom_score
+78
+</pre><div class="para">
+ There is also a special value of -17, which disables <code class="filename">oom_killer</code> for that process. In the example below, <code class="filename">oom_score</code> returns a value of 0, indicating that this process would not be killed.
+ </div><pre class="screen">
+# cat /proc/12465/oom_score
+78
+
+# echo -17 > /proc/12465/oom_adj
+
+# cat /proc/12465/oom_score
+0
+</pre><div class="para">
+ A function called <code class="filename">badness()</code> is used to determine the actual score for each process. This is done by adding up 'points' for each examined process. The process scoring is done in the following way:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ The basis of each process's score is its memory size.
+ </div></li><li class="listitem"><div class="para">
+ The memory size of any of the process's children (not including a kernel thread) is also added to the score
+ </div></li><li class="listitem"><div class="para">
+ The process's score is increased for 'niced' processes and decreased for long running processes.
+ </div></li><li class="listitem"><div class="para">
+ Processes with the <code class="filename">CAP_SYS_ADMIN</code> and <code class="filename">CAP_SYS_RAWIO</code> capabilities have their scores reduced.
+ </div></li><li class="listitem"><div class="para">
+ The final score is then bitshifted by the value saved in the <code class="filename">oom_adj</code> file.
+ </div></li></ol></div><div class="para">
+ Thus, a process with the highest <code class="filename">oom_score</code> value will most probably be a non-priviliged, recently started process that, along with its children, uses a large amount of memory, has been 'niced', and handles no raw I/O.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-tty.html"><strong>Prev</strong>19.3.11. /proc/tty/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-proc-sysctl.html"><strong>Next</strong>19.4. Using the sysctl Command</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-slabinfo.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-slabinfo.html
new file mode 100644
index 0000000..6de7902
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-slabinfo.html
@@ -0,0 +1,67 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.24. /proc/slabinfo</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-partitions.html" title="19.2.23. /proc/partitions" /><link rel="next" href="s2-proc-stat.html" title="19.2.25. /proc/stat" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-partitions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey
="n" href="s2-proc-stat.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.24. /proc/slabinfo" id="s2-proc-slabinfo"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-slabinfo">19.2.24. <code class="filename">/proc/slabinfo</code> </h3></div></div></div><a id="id522189" class="indexterm"></a><a id="id522212" class="indexterm"></a><div class="para">
+ This file gives full information about memory usage on the <em class="firstterm">slab</em> level. Linux kernels greater than version 2.2 use <em class="firstterm">slab pools</em> to manage memory above the page level. Commonly used objects have their own slab pools.
+ </div><div class="para">
+ Instead of parsing the highly verbose <code class="filename">/proc/slabinfo</code> file manually, the <code class="filename">/usr/bin/slabtop</code> program displays kernel slab cache information in real time. This program allows for custom configurations, including column sorting and screen refreshing.
+ </div><div class="para">
+ A sample screen shot of <code class="filename">/usr/bin/slabtop</code> usually looks like the following example:
+ </div><pre class="screen">
+Active / Total Objects (% used) : 133629 / 147300 (90.7%)
+Active / Total Slabs (% used) : 11492 / 11493 (100.0%)
+Active / Total Caches (% used) : 77 / 121 (63.6%)
+Active / Total Size (% used) : 41739.83K / 44081.89K (94.7%)
+Minimum / Average / Maximum Object : 0.01K / 0.30K / 128.00K
+OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
+44814 43159 96% 0.62K 7469 6 29876K ext3_inode_cache
+36900 34614 93% 0.05K 492 75 1968K buffer_head
+35213 33124 94% 0.16K 1531 23 6124K dentry_cache
+7364 6463 87% 0.27K 526 14 2104K radix_tree_node
+2585 1781 68% 0.08K 55 47 220K vm_area_struct
+2263 2116 93% 0.12K 73 31 292K size-128
+1904 1125 59% 0.03K 16 119 64K size-32
+1666 768 46% 0.03K 14 119 56K anon_vma
+1512 1482 98% 0.44K 168 9 672K inode_cache
+1464 1040 71% 0.06K 24 61 96K size-64
+1320 820 62% 0.19K 66 20 264K filp
+678 587 86% 0.02K 3 226 12K dm_io
+678 587 86% 0.02K 3 226 12K dm_tio
+576 574 99% 0.47K 72 8 288K proc_inode_cache
+528 514 97% 0.50K 66 8 264K size-512
+492 372 75% 0.09K 12 41 48K bio
+465 314 67% 0.25K 31 15 124K size-256
+452 331 73% 0.02K 2 226 8K biovec-1
+420 420 100% 0.19K 21 20 84K skbuff_head_cache
+305 256 83% 0.06K 5 61 20K biovec-4
+290 4 1% 0.01K 1 290 4K revoke_table
+264 264 100% 4.00K 264 1 1056K size-4096
+260 256 98% 0.19K 13 20 52K biovec-16
+260 256 98% 0.75K 52 5 208K biovec-64
+</pre><div class="para">
+ Some of the more commonly used statistics in <code class="filename">/proc/slabinfo</code> that are included into <code class="filename">/usr/bin/slabtop</code> include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJS</code> — The total number of objects (memory blocks), including those in use (allocated), and some spares not in use.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">ACTIVE</code> — The number of objects (memory blocks) that are in use (allocated).
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">USE</code> — Percentage of total objects that are active. ((ACTIVE/OBJS)(100))
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJ SIZE</code> — The size of the objects.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">SLABS</code> — The total number of slabs.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">OBJ/SLAB</code> — The number of objects that fit into a slab.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">CACHE SIZE</code> — The cache size of the slab.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">NAME</code> — The name of the slab.
+ </div></li></ul></div><div class="para">
+ For more information on the <code class="filename">/usr/bin/slabtop</code> program, refer to the <code class="filename">slabtop</code> man page.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-partitions.html"><strong>Prev</strong>19.2.23. /proc/partitions </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-stat.html"><strong>Next</strong>19.2.25. /proc/stat </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-stat.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-stat.html
new file mode 100644
index 0000000..d0c8f00
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-stat.html
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.25. /proc/stat</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-slabinfo.html" title="19.2.24. /proc/slabinfo" /><link rel="next" href="s2-proc-swaps.html" title="19.2.26. /proc/swaps" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-slabinfo.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n"
href="s2-proc-swaps.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.25. /proc/stat" id="s2-proc-stat"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-stat">19.2.25. <code class="filename">/proc/stat</code> </h3></div></div></div><a id="id479413" class="indexterm"></a><a id="id479436" class="indexterm"></a><a id="id479450" class="indexterm"></a><div class="para">
+ This file keeps track of a variety of different statistics about the system since it was last restarted. The contents of <code class="filename">/proc/stat</code>, which can be quite long, usually begins like the following example:
+ </div><pre class="screen">
+cpu 259246 7001 60190 34250993 137517 772 0
+cpu0 259246 7001 60190 34250993 137517 772 0
+intr 354133732 347209999 2272 0 4 4 0 0 3 1 1249247 0 0 80143 0 422626 5169433
+ctxt 12547729
+btime 1093631447
+processes 130523
+procs_running 1
+procs_blocked 0
+preempt 5651840
+cpu 209841 1554 21720 118519346 72939 154 27168
+cpu0 42536 798 4841 14790880 14778 124 3117
+cpu1 24184 569 3875 14794524 30209 29 3130
+cpu2 28616 11 2182 14818198 4020 1 3493
+cpu3 35350 6 2942 14811519 3045 0 3659
+cpu4 18209 135 2263 14820076 12465 0 3373
+cpu5 20795 35 1866 14825701 4508 0 3615
+cpu6 21607 0 2201 14827053 2325 0 3334
+cpu7 18544 0 1550 14831395 1589 0 3447
+intr 15239682 14857833 6 0 6 6 0 5 0 1 0 0 0 29 0 2 0 0 0 0 0 0 0 94982 0 286812
+ctxt 4209609
+btime 1078711415
+processes 21905
+procs_running 1
+procs_blocked 0
+</pre><div class="para">
+ Some of the more commonly used statistics include:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">cpu</code> — Measures the number of <em class="firstterm">jiffies</em> (1/100 of a second for x86 systems) that the system has been in user mode, user mode with low priority (nice), system mode, idle task, I/O wait, IRQ (hardirq), and softirq respectively. The IRQ (hardirq) is the direct response to a hardware event. The IRQ takes minimal work for queuing the "heavy" work up for the softirq to execute. The softirq runs at a lower priority than the IRQ and therefore may be interrupted more frequently. The total for all CPUs is given at the top, while each individual CPU is listed below with its own statistics. The following example is a 4-way Intel Pentium Xeon configuration with multi-threading enabled, therefore showing four physical processors and four virtual processors totaling eight processors.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">page</code> — The number of memory pages the system has written in and out to disk.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">swap</code> — The number of swap pages the system has brought in and out.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">intr</code> — The number of interrupts the system has experienced.
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">btime</code> — The boot time, measured in the number of seconds since January 1, 1970, otherwise known as the <em class="firstterm">epoch</em>.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-slabinfo.html"><strong>Prev</strong>19.2.24. /proc/slabinfo </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-swaps.html"><strong>Next</strong>19.2.26. /proc/swaps </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-swaps.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-swaps.html
new file mode 100644
index 0000000..e9d21e4
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-swaps.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.26. /proc/swaps</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-stat.html" title="19.2.25. /proc/stat" /><link rel="next" href="s2-proc-sysrq-trigger.html" title="19.2.27. /proc/sysrq-trigger" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-stat.html"><strong>Prev</strong></a></li><li class="next"><a accesskey
="n" href="s2-proc-sysrq-trigger.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.26. /proc/swaps" id="s2-proc-swaps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-swaps">19.2.26. <code class="filename">/proc/swaps</code> </h3></div></div></div><a id="id479587" class="indexterm"></a><div class="para">
+ This file measures swap space and its utilization. For a system with only one swap partition, the output of <code class="filename">/proc/swaps</code> may look similar to the following:
+ </div><pre class="screen">
+Filename Type Size Used Priority
+/dev/mapper/VolGroup00-LogVol01 partition 524280 0 -1
+</pre><div class="para">
+ While some of this information can be found in other files in the <code class="filename">/proc/</code> directory, <code class="filename">/proc/swap</code> provides a snapshot of every swap file name, the type of swap space, the total size, and the amount of space in use (in kilobytes). The priority column is useful when multiple swap files are in use. The lower the priority, the more likely the swap file is to be used.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-stat.html"><strong>Prev</strong>19.2.25. /proc/stat </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-sysrq-trigger.html"><strong>Next</strong>19.2.27. /proc/sysrq-trigger </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-sysrq-trigger.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-sysrq-trigger.html
new file mode 100644
index 0000000..fbb5d75
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-sysrq-trigger.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.27. /proc/sysrq-trigger</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-swaps.html" title="19.2.26. /proc/swaps" /><link rel="next" href="s2-proc-uptime.html" title="19.2.28. /proc/uptime" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-swaps.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="
s2-proc-uptime.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.27. /proc/sysrq-trigger" id="s2-proc-sysrq-trigger"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-sysrq-trigger">19.2.27. <code class="filename">/proc/sysrq-trigger</code> </h3></div></div></div><a id="id635231" class="indexterm"></a><div class="para">
+ Using the <code class="command">echo</code> command to write to this file, a remote root user can execute most System Request Key commands remotely as if at the local terminal. To <code class="command">echo</code> values to this file, the <code class="filename">/proc/sys/kernel/sysrq</code> must be set to a value other than <code class="computeroutput">0</code>. For more information about the System Request Key, refer to <a class="xref" href="s2-proc-dir-sys.html#s3-proc-sys-kernel" title="19.3.9.3. /proc/sys/kernel/">Section 19.3.9.3, “ <code class="filename">/proc/sys/kernel/</code> ”</a>.
+ </div><div class="para">
+ Although it is possible to write to this file, it cannot be read, even by the root user.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-swaps.html"><strong>Prev</strong>19.2.26. /proc/swaps </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-uptime.html"><strong>Next</strong>19.2.28. /proc/uptime </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-tty.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-tty.html
new file mode 100644
index 0000000..fbcb1c8
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-tty.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.3.11. /proc/tty/</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /><link rel="prev" href="s2-proc-dir-sysvipc.html" title="19.3.10. /proc/sysvipc/" /><link rel="next" href="s2-proc-pid.html" title="19.3.12. /proc/PID/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-sysvipc.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-pr
oc-pid.html"><strong>Next</strong></a></li></ul><div class="section" title="19.3.11. /proc/tty/" id="s2-proc-tty"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-tty">19.3.11. <code class="filename">/proc/tty/</code> </h3></div></div></div><a id="id541921" class="indexterm"></a><div class="para">
+ This directory contains information about the available and currently used <em class="firstterm">tty devices</em> on the system. Originally called <em class="firstterm">teletype devices</em>, any character-based data terminals are called tty devices.
+ </div><div class="para">
+ In Linux, there are three different kinds of tty devices. <em class="firstterm">Serial devices</em> are used with serial connections, such as over a modem or using a serial cable. <em class="firstterm">Virtual terminals</em> create the common console connection, such as the virtual consoles available when pressing <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong><F-key></strong></span> at the system console. <em class="firstterm">Pseudo terminals</em> create a two-way communication that is used by some higher level applications, such as XFree86. The <code class="filename">drivers</code> file is a list of the current tty devices in use, as in the following example:
+ </div><pre class="screen">
+serial /dev/cua 5 64-127 serial:callout
+serial /dev/ttyS 4 64-127 serial
+pty_slave /dev/pts 136 0-255 pty:slave
+pty_master /dev/ptm 128 0-255 pty:master
+pty_slave /dev/ttyp 3 0-255 pty:slave
+pty_master /dev/pty 2 0-255 pty:master
+/dev/vc/0 /dev/vc/0 4 0 system:vtmaster
+/dev/ptmx /dev/ptmx 5 2 system
+/dev/console /dev/console 5 1 system:console
+/dev/tty /dev/tty 5 0 system:/dev/tty
+unknown /dev/vc/%d 4 1-63 console
+</pre><div class="para">
+ The <code class="filename">/proc/tty/driver/serial</code> file lists the usage statistics and status of each of the serial tty lines.
+ </div><div class="para">
+ In order for tty devices to be used as network devices, the Linux kernel enforces <em class="firstterm">line discipline</em> on the device. This allows the driver to place a specific type of header with every block of data transmitted over the device, making it possible for the remote end of the connection to a block of data as just one in a stream of data blocks. SLIP and PPP are common line disciplines, and each are commonly used to connect systems to one other over a serial link.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-dir-sysvipc.html"><strong>Prev</strong>19.3.10. /proc/sysvipc/ </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-pid.html"><strong>Next</strong>19.3.12. /proc/PID/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-uptime.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-uptime.html
new file mode 100644
index 0000000..b2d7cb8
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-uptime.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.28. /proc/uptime</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-sysrq-trigger.html" title="19.2.27. /proc/sysrq-trigger" /><link rel="next" href="s2-proc-version.html" title="19.2.29. /proc/version" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-sysrq-trigger.html"><strong>Prev</strong></a></li><li class="nex
t"><a accesskey="n" href="s2-proc-version.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.28. /proc/uptime" id="s2-proc-uptime"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-uptime">19.2.28. <code class="filename">/proc/uptime</code> </h3></div></div></div><a id="id635299" class="indexterm"></a><div class="para">
+ This file contains information detailing how long the system has been on since its last restart. The output of <code class="filename">/proc/uptime</code> is quite minimal:
+ </div><pre class="screen">
+350735.47 234388.90
+</pre><div class="para">
+ The first number is the total number of seconds the system has been up. The second number is how much of that time the machine has spent idle, in seconds.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-sysrq-trigger.html"><strong>Prev</strong>19.2.27. /proc/sysrq-trigger </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-proc-version.html"><strong>Next</strong>19.2.29. /proc/version </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-version.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-version.html
new file mode 100644
index 0000000..3eefd24
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-proc-version.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.29. /proc/version</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-proc-topfiles.html" title="19.2. Top-level Files within the proc File System" /><link rel="prev" href="s2-proc-uptime.html" title="19.2.28. /proc/uptime" /><link rel="next" href="s1-proc-directories.html" title="19.3. Directories within /proc/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-uptime.html"><strong>Prev</strong></a></li><li class="next"><a acc
esskey="n" href="s1-proc-directories.html"><strong>Next</strong></a></li></ul><div class="section" title="19.2.29. /proc/version" id="s2-proc-version"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-proc-version">19.2.29. <code class="filename">/proc/version</code> </h3></div></div></div><a id="id635355" class="indexterm"></a><div class="para">
+ This file specifies the version of the Linux kernel, the version of <code class="command">gcc</code> used to compile the kernel, and the time of kernel compilation. It also contains the kernel compiler's user name (in parentheses).
+ </div><pre class="screen">
+Linux version 2.6.8-1.523 (user at foo.redhat.com) (gcc version 3.4.1 20040714 \ (Red Hat Enterprise Linux 3.4.1-7)) #1 Mon Aug 16 13:27:03 EDT 2004
+</pre><div class="para">
+ This information is used for a variety of purposes, including the version data presented when a user logs in.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-proc-uptime.html"><strong>Prev</strong>19.2.28. /proc/uptime </a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-proc-directories.html"><strong>Next</strong>19.3. Directories within /proc/ </a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-redhat-config-users-process.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-redhat-config-users-process.html
new file mode 100644
index 0000000..5cd38da
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-redhat-config-users-process.html
@@ -0,0 +1,81 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.2.2. Explaining the Process</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-users-tools.html" title="15.2. User and Group Management Tools" /><link rel="prev" href="s1-users-tools.html" title="15.2. User and Group Management Tools" /><link rel="next" href="s1-users-groups-standard-users.html" title="15.3. Standard Users" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-tools.html"><strong>Prev</strong></a></li><li class="next"><a ac
cesskey="n" href="s1-users-groups-standard-users.html"><strong>Next</strong></a></li></ul><div class="section" title="15.2.2. Explaining the Process" id="s2-redhat-config-users-process"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-redhat-config-users-process">15.2.2. Explaining the Process</h3></div></div></div><div class="para">
+ The following steps illustrate what happens if the command <code class="command">useradd juan</code> is issued on a system that has shadow passwords enabled:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ A new line for <code class="computeroutput">juan</code> is created in <code class="filename">/etc/passwd</code>.
+<pre class="screen"><code class="code">juan:x:501:501::/home/juan:/bin/bash</code>
+</pre>
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ It begins with the username <code class="computeroutput">juan</code>.
+ </div></li><li class="listitem"><div class="para">
+ There is an <code class="computeroutput">x</code> for the password field indicating that the system is using shadow passwords.
+ </div></li><li class="listitem"><div class="para">
+ A UID greater than 499 is created. Under Fedora. UIDs and GIDs below 500 are reserved for system use. These should not be assigned to users.
+ </div></li><li class="listitem"><div class="para">
+ A GID greater than 499 is created.
+ </div></li><li class="listitem"><div class="para">
+ The optional GECOS information is left blank.
+ </div></li><li class="listitem"><div class="para">
+ The home directory for <code class="computeroutput">juan</code> is set to <code class="filename">/home/juan/</code>.
+ </div></li><li class="listitem"><div class="para">
+ The default shell is set to <code class="command">/bin/bash</code>.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ A new line for <code class="computeroutput">juan</code> is created in <code class="filename">/etc/shadow</code>.
+<pre class="screen"><code class="code">juan:!!:14798:0:99999:7:::</code>
+</pre>
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ It begins with the username <code class="computeroutput">juan</code>.
+ </div></li><li class="listitem"><div class="para">
+ Two exclamation points (<code class="computeroutput">!!</code>) appear in the password field of the <code class="filename">/etc/shadow</code> file, which locks the account.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If an encrypted password is passed using the <code class="option">-p</code> flag, it is placed in the <code class="filename">/etc/shadow</code> file on the new line for the user.
+ </div></div></div></li><li class="listitem"><div class="para">
+ The password is set to never expire.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ A new line for a group named <code class="computeroutput">juan</code> is created in <code class="filename">/etc/group</code>.
+<pre class="screen"><code class="code">juan:x:501:</code>
+</pre>
+ A group with the same name as a user is called a <em class="firstterm">user private group</em>. For more information on user private groups, refer to <a class="xref" href="Users_and_Groups.html#s2-redhat-config-users-user-new" title="15.1.1. Adding a New User">Section 15.1.1, “Adding a New User”</a>.
+ </div><div class="para">
+ The line created in <code class="filename">/etc/group</code> has the following characteristics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ It begins with the group name <code class="computeroutput">juan</code>.
+ </div></li><li class="listitem"><div class="para">
+ An <code class="computeroutput">x</code> appears in the password field indicating that the system is using shadow group passwords.
+ </div></li><li class="listitem"><div class="para">
+ The GID matches the one listed for user <code class="computeroutput">juan</code> in <code class="filename">/etc/passwd</code>.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ A new line for a group named <code class="computeroutput">juan</code> is created in <code class="filename">/etc/gshadow</code>.
+<pre class="screen"><code class="code">juan:!::</code>
+</pre>
+ The line has the following characteristics:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ It begins with the group name <code class="computeroutput">juan</code>.
+ </div></li><li class="listitem"><div class="para">
+ An exclamation point (<code class="computeroutput">!</code>) appears in the password field of the <code class="filename">/etc/gshadow</code> file, which locks the group.
+ </div></li><li class="listitem"><div class="para">
+ All other fields are blank.
+ </div></li></ul></div></li><li class="listitem"><div class="para">
+ A directory for user <code class="computeroutput">juan</code> is created in the <code class="filename">/home/</code> directory.
+<pre class="screen"><code class="code">ls -l /home</code>
+ <code class="code">drwx------. 4 juan juan 4096 Jul 9 14:55 juan</code>
+</pre>
+ This directory is owned by user <code class="computeroutput">juan</code> and group <code class="computeroutput">juan</code>. It has <span class="emphasis"><em>read</em></span>, <span class="emphasis"><em>write</em></span>, and <span class="emphasis"><em>execute</em></span> privileges <span class="emphasis"><em>only</em></span> for the user <code class="computeroutput">juan</code>. All other permissions are denied.
+ </div></li><li class="listitem"><div class="para">
+ The files within the <code class="filename">/etc/skel/</code> directory (which contain default user settings) are copied into the new <code class="filename">/home/juan/</code> directory.
+<pre class="screen"><code class="code"></code>
+</pre>
+
+ </div></li></ol></div><div class="para">
+ At this point, a locked account called <code class="computeroutput">juan</code> exists on the system. To activate it, the administrator must next assign a password to the account using the <code class="command">passwd</code> command and, optionally, set password aging guidelines.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-tools.html"><strong>Prev</strong>15.2. User and Group Management Tools</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-users-groups-standard-users.html"><strong>Next</strong>15.3. Standard Users</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-freshening.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-freshening.html
new file mode 100644
index 0000000..5b26513
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-freshening.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.5. Freshening</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-rpm-using.html" title="3.2. Using RPM" /><link rel="prev" href="s2-rpm-uninstalling.html" title="3.2.4. Uninstalling" /><link rel="next" href="s2-rpm-querying.html" title="3.2.6. Querying" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-uninstalling.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-querying.html"><strong>Next<
/strong></a></li></ul><div class="section" title="3.2.5. Freshening" id="s2-rpm-freshening"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-freshening">3.2.5. Freshening</h3></div></div></div><a id="id714977" class="indexterm"></a><a id="id732340" class="indexterm"></a><div class="para">
+ Freshening is similar to upgrading, except that only existent packages are upgraded. Type the following command at a shell prompt:
+ </div><pre class="screen">
+<code class="command">rpm -Fvh foo-2.0-1.fc14.x86_64.rpm</code>
+</pre><div class="para">
+ RPM's freshen option checks the versions of the packages specified on the command line against the versions of packages that have already been installed on your system. When a newer version of an already-installed package is processed by RPM's freshen option, it is upgraded to the newer version. However, RPM's freshen option does not install a package if no previously-installed package of the same name exists. This differs from RPM's upgrade option, as an upgrade <span class="emphasis"><em>does</em></span> install packages whether or not an older version of the package was already installed.
+ </div><div class="para">
+ Freshening works for single packages or package groups. If you have just downloaded a large number of different packages, and you only want to upgrade those packages that are already installed on your system, freshening does the job. Thus, you do not have to delete any unwanted packages from the group that you downloaded before using RPM.
+ </div><div class="para">
+ In this case, issue the following with the <code class="filename">*.rpm</code> glob:
+ </div><pre class="screen">
+<code class="command">rpm -Fvh *.rpm</code>
+</pre><div class="para">
+ RPM then automatically upgrades only those packages that are already installed.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-uninstalling.html"><strong>Prev</strong>3.2.4. Uninstalling</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-querying.html"><strong>Next</strong>3.2.6. Querying</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-querying.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-querying.html
new file mode 100644
index 0000000..ea6ba9a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-querying.html
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.6. Querying</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-rpm-using.html" title="3.2. Using RPM" /><link rel="prev" href="s2-rpm-freshening.html" title="3.2.5. Freshening" /><link rel="next" href="s2-rpm-verifying.html" title="3.2.7. Verifying" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-freshening.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-verifying.html"><strong>Next</st
rong></a></li></ul><div class="section" title="3.2.6. Querying" id="s2-rpm-querying"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-querying">3.2.6. Querying</h3></div></div></div><a id="id851967" class="indexterm"></a><a id="id851979" class="indexterm"></a><div class="para">
+ The RPM database stores information about all RPM packages installed in your system. It is stored in the directory <code class="filename">/var/lib/rpm/</code>, and is used to query what packages are installed, what versions each package is, and to calculate any changes to any files in the package since installation, among other use cases.
+ </div><div class="para">
+ To query this database, use the <code class="command">-q</code> option. The <code class="command">rpm -q <em class="replaceable"><code>package name</code></em> </code> command displays the package name, version, and release number of the installed package <em class="replaceable"><code><package_name></code></em>. For example, using <code class="command">rpm -q tree</code> to query installed package <code class="filename">tree</code> might generate the following output:
+ </div><pre class="screen">tree-1.5.2.2-4.fc14.x86_64</pre><div class="para">
+ You can also use the following <span class="emphasis"><em>Package Selection Options</em></span> (which is a subheading in the RPM man page: see <code class="command">man rpm</code> for details) to further refine or qualify your query:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-a</code> — queries all currently installed packages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-f <code class="filename"><em class="replaceable"><code><file_name></code></em> </code> </code> — queries the RPM database for which package owns <code class="filename"><em class="replaceable"><code><file_name></code></em> </code>. Specify the absolute path of the file (for example, <code class="command">rpm -qf <code class="filename">/bin/ls</code> </code> instead of <code class="command">rpm -qf ls</code>).
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-p <code class="filename"><em class="replaceable"><code><package_file></code></em> </code> </code> — queries the uninstalled package <code class="filename"><em class="replaceable"><code><package_file></code></em> </code>.
+ </div></li></ul></div><div class="para">
+ There are a number of ways to specify what information to display about queried packages. The following options are used to select the type of information for which you are searching. These are called the <span class="emphasis"><em>Package Query Options</em></span>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">-i</code> displays package information including name, description, release, size, build date, install date, vendor, and other miscellaneous information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-l</code> displays the list of files that the package contains.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-s</code> displays the state of all the files in the package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-d</code> displays a list of files marked as documentation (man pages, info pages, READMEs, etc.) in the package.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">-c</code> displays a list of files marked as configuration files. These are the files you edit after installation to adapt and customize the package to your system (for example, <code class="filename">sendmail.cf</code>, <code class="filename">passwd</code>, <code class="filename">inittab</code>, etc.).
+ </div></li></ul></div><div class="para">
+ For options that display lists of files, add <code class="command">-v</code> to the command to display the lists in a familiar <code class="command">ls -l</code> format.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-freshening.html"><strong>Prev</strong>3.2.5. Freshening</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-verifying.html"><strong>Next</strong>3.2.7. Verifying</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-related-books.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-related-books.html
new file mode 100644
index 0000000..b63286c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-related-books.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.5.3. Related Books</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-rpm-additional-resources.html" title="3.5. Additional Resources" /><link rel="prev" href="s2-rpm-useful-websites.html" title="3.5.2. Useful Websites" /><link rel="next" href="pt-network-related-config.html" title="Part II. Network-Related Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-useful-websites.html"><strong>Prev</strong></a></li><li cl
ass="next"><a accesskey="n" href="pt-network-related-config.html"><strong>Next</strong></a></li></ul><div class="section" title="3.5.3. Related Books" id="s2-rpm-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-related-books">3.5.3. Related Books</h3></div></div></div><a id="id564902" class="indexterm"></a><a id="id838454" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <em class="citetitle">Maximum RPM</em> — <a href="http://www.redhat.com/docs/books/max-rpm/">http://www.redhat.com/docs/books/max-rpm/</a> </span></dt><dd><div class="para">
+ The <em class="citetitle">Maximum RPM</em> book, which you can read online or download in HTML or PDF, covers everything from general RPM usage to building your own RPMs to programming with rpmlib.
+ </div></dd><dt class="varlistentry"><span class="term"> <em class="citetitle">Red Hat RPM Guide</em> — <a href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html">http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html</a> </span></dt><dd><div class="para">
+ The <em class="citetitle">Red Hat RPM Guide</em> by Eric Foster-Johnson is an excellent resource on all details of the RPM package format and the RPM package management utility.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-useful-websites.html"><strong>Prev</strong>3.5.2. Useful Websites</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pt-network-related-config.html"><strong>Next</strong>Part II. Network-Related Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-uninstalling.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-uninstalling.html
new file mode 100644
index 0000000..f5f87ec
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-uninstalling.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.4. Uninstalling</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-rpm-using.html" title="3.2. Using RPM" /><link rel="prev" href="sec-Configuration_File_Changes.html" title="3.2.3. Configuration File Changes" /><link rel="next" href="s2-rpm-freshening.html" title="3.2.5. Freshening" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuration_File_Changes.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" h
ref="s2-rpm-freshening.html"><strong>Next</strong></a></li></ul><div class="section" title="3.2.4. Uninstalling" id="s2-rpm-uninstalling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-uninstalling">3.2.4. Uninstalling</h3></div></div></div><a id="id721358" class="indexterm"></a><a id="id584317" class="indexterm"></a><a id="id584329" class="indexterm"></a><a id="id584345" class="indexterm"></a><div class="para">
+ Uninstalling a package is just as simple as installing one. Type the following command at a shell prompt:
+ </div><pre class="screen">rpm -e foo</pre><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Notice that we used the package <span class="emphasis"><em>name</em></span> <code class="filename">foo</code>, not the name of the original package <span class="emphasis"><em>file</em></span>, <code class="filename">foo-1.0-1.fc14.x86_64</code>. If you attempt to uninstall a package using the <code class="command">rpm -e</code> command and the original full file name, you will receive a package name error.
+ </div></div></div><div class="para">
+ You can encounter dependency errors when uninstalling a package if another installed package depends on the one you are trying to remove. For example:
+ </div><pre class="screen">
+<code class="command">rpm -e ghostscript</code>
+error: Failed dependencies:
+ libgs.so.8()(64bit) is needed by (installed) libspectre-0.2.2-3.fc14.x86_64
+ libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc14.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc14.x86_64
+ ghostscript is needed by (installed) printer-filters-1.1-4.fc14.noarch</pre><div class="para">
+ Similar to how we searched for a shared object library (i.e. a <code class="filename"><em class="replaceable"><code><library_name></code></em>.so.<em class="replaceable"><code><number></code></em> </code> file) in <a class="xref" href="sec-Installing_and_Upgrading.html#s3-rpm-unresolved-dependency" title="3.2.2.3. Unresolved Dependency">Section 3.2.2.3, “Unresolved Dependency”</a>, we can search for a 64-bit shared object library using this exact syntax (and making sure to quote the file name):
+ </div><pre class="screen">~]# <code class="command">rpm -q --whatprovides "libgs.so.8()(64bit)"</code>
+ghostscript-8.70-1.fc14.x86_64</pre><div class="warning" title="Warning: Forcing Package Installation" id="warning-uninstall-Warning-Forcing_Package_Installation"><div class="admonition_header"><h2>Warning: Forcing Package Installation</h2></div><div class="admonition"><div class="para">
+ Although we can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to remove a package that gives us a <code class="computeroutput">Failed dependencies</code> error (using the <code class="option">--nodeps</code> option), this is <span class="emphasis"><em>not</em></span> recommended, and may cause harm to other installed applications. Installing or removing packages with <code class="command">rpm --nodeps</code> can cause applications to misbehave and/or crash, and can cause serious package management problems or, possibly, system failure. For these reasons, it is best to heed such warnings; the package manager—whether <span class="application"><strong>RPM</strong></span>, <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span>—shows us these warnings and suggests possible fixes because accounting for dependencies is critical. The <span class="application"><strong>Yum</strong><
/span> package manager can perform dependency resolution and fetch dependencies from online repositories, making it safer, easier and smarter than forcing <code class="command">rpm</code> to carry out actions without regard to resolving dependencies.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuration_File_Changes.html"><strong>Prev</strong>3.2.3. Configuration File Changes</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-freshening.html"><strong>Next</strong>3.2.5. Freshening</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-useful-websites.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-useful-websites.html
new file mode 100644
index 0000000..cd2749f
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-useful-websites.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.5.2. Useful Websites</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-rpm-additional-resources.html" title="3.5. Additional Resources" /><link rel="prev" href="s1-rpm-additional-resources.html" title="3.5. Additional Resources" /><link rel="next" href="s2-rpm-related-books.html" title="3.5.3. Related Books" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-additional-resources.html"><strong>Prev</strong></a></li><li class="next">
<a accesskey="n" href="s2-rpm-related-books.html"><strong>Next</strong></a></li></ul><div class="section" title="3.5.2. Useful Websites" id="s2-rpm-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-useful-websites">3.5.2. Useful Websites</h3></div></div></div><div class="itemizedlist"><a id="id672567" class="indexterm"></a><ul><li class="listitem"><div class="para">
+ The RPM website — <a href="http://www.rpm.org/">http://www.rpm.org/</a>
+ </div></li><li class="listitem"><div class="para">
+ The RPM mailing list can be subscribed to, and its archives read from, here — <a href="http://www.redhat.com/mailman/listinfo/rpm-list/">https://lists.rpm.org/mailman/listinfo/rpm-list</a>
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-additional-resources.html"><strong>Prev</strong>3.5. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-related-books.html"><strong>Next</strong>3.5.3. Related Books</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-verifying.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-verifying.html
new file mode 100644
index 0000000..d102dfc
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-rpm-verifying.html
@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.7. Verifying</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-rpm-using.html" title="3.2. Using RPM" /><link rel="prev" href="s2-rpm-querying.html" title="3.2.6. Querying" /><link rel="next" href="s1-check-rpm-sig.html" title="3.3. Checking a Package's Signature" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-querying.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-check-rpm-sig.html"><st
rong>Next</strong></a></li></ul><div class="section" title="3.2.7. Verifying" id="s2-rpm-verifying"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-rpm-verifying">3.2.7. Verifying</h3></div></div></div><a id="id649294" class="indexterm"></a><a id="id739318" class="indexterm"></a><div class="para">
+ Verifying a package compares information about files installed from a package with the same information from the original package. Among other things, verifying compares the file size, MD5 sum, permissions, type, owner, and group of each file.
+ </div><div class="para">
+ The command <code class="command">rpm -V</code> verifies a package. You can use any of the <span class="emphasis"><em>Verify Options</em></span> listed for querying to specify the packages you wish to verify. A simple use of verifying is <code class="command">rpm -V tree</code>, which verifies that all the files in the <code class="command">tree</code> package are as they were when they were originally installed. For example:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To verify a package containing a particular file:
+ </div><pre class="screen">
+<code class="command">rpm -Vf /usr/bin/tree</code>
+</pre><div class="para">
+ In this example, <code class="filename">/usr/bin/tree</code> is the absolute path to the file used to query a package.
+ </div></li><li class="listitem"><div class="para">
+ To verify ALL installed packages throughout the system (which will take some time):
+ </div><pre class="screen">
+<code class="command">rpm -Va</code>
+</pre></li><li class="listitem"><div class="para">
+ To verify an installed package against an RPM package file:
+ </div><pre class="screen">
+<code class="command">rpm -Vp tree-1.5.2.2-4.fc14.x86_64.rpm</code>
+</pre><div class="para">
+ This command can be useful if you suspect that your RPM database is corrupt.
+ </div></li></ul></div><div class="para">
+ If everything verified properly, there is no output. If there are any discrepancies, they are displayed. The format of the output is a string of eight characters (a "<code class="computeroutput">c</code>" denotes a configuration file) and then the file name. Each of the eight characters denotes the result of a comparison of one attribute of the file to the value of that attribute recorded in the RPM database. A single period (<code class="computeroutput">.</code>) means the test passed. The following characters denote specific discrepancies:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="computeroutput">5</code> — MD5 checksum
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">S</code> — file size
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">L</code> — symbolic link
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">T</code> — file modification time
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">D</code> — device
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">U</code> — user
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">G</code> — group
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">M</code> — mode (includes permissions and file type)
+ </div></li><li class="listitem"><div class="para">
+ <code class="computeroutput">?</code> — unreadable file (file permission errors, for example)
+ </div></li></ul></div><div class="para">
+ If you see any output, use your best judgment to determine if you should remove the package, reinstall it, or fix the problem in another way.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-querying.html"><strong>Prev</strong>3.2.6. Querying</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-check-rpm-sig.html"><strong>Next</strong>3.3. Checking a Package's Signature</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-services-additional-resources-books.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-services-additional-resources-books.html
new file mode 100644
index 0000000..3a662a2
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-services-additional-resources-books.html
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.4.2. Related Books</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-services-additional-resources.html" title="7.4. Additional Resources" /><link rel="prev" href="s1-services-additional-resources.html" title="7.4. Additional Resources" /><link rel="next" href="ch-Authentication_Configuration.html" title="Chapter 8. Authentication Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-services-additional-resources.html"><
strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Authentication_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="7.4.2. Related Books" id="s2-services-additional-resources-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-additional-resources-books">7.4.2. Related Books</h3></div></div></div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a href="http://docs.fedoraproject.org/en-US/Fedora/14/html/Security_Guide/index.html"><em class="citetitle">Security Guide</em></a> </span></dt><dd><div class="para">
+ A guide to securing Fedora. It contains valuable information on how to set up the firewall, as well as the configuration of <span class="application"><strong>SELinux</strong></span>.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-services-additional-resources.html"><strong>Prev</strong>7.4. Additional Resources</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Authentication_Configuration.html"><strong>Next</strong>Chapter 8. Authentication Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-services-chkconfig.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-services-chkconfig.html
new file mode 100644
index 0000000..81dc437
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-services-chkconfig.html
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.3. Using the chkconfig Utility</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-services-configuring.html" title="7.2. Configuring the Services" /><link rel="prev" href="s2-services-ntsysv.html" title="7.2.2. Using the ntsysv Utility" /><link rel="next" href="s1-services-running.html" title="7.3. Running the Services" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-services-ntsysv.html"><strong>Prev</strong></a></li><li class="next"><a acces
skey="n" href="s1-services-running.html"><strong>Next</strong></a></li></ul><div class="section" title="7.2.3. Using the chkconfig Utility" id="s2-services-chkconfig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-chkconfig">7.2.3. Using the <code class="command">chkconfig</code> Utility</h3></div></div></div><a id="id451176" class="indexterm"></a><a id="id451194" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>chkconfig</strong></span> utility is a command line application to configure which services are to be started in selected runlevels. It also allows you to list all available services along with their current setting. Note that with the exception of listing, you must have superuser privileges to use this command. To obtain them, log in as root by typing:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="section" title="7.2.3.1. Listing the Services" id="s3-services-chkconfig-listing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-chkconfig-listing">7.2.3.1. Listing the Services</h4></div></div></div><div class="para">
+ To display a list of system services (i.e., both the services from the <code class="filename">/etc/rc.d/init.d/</code> directory, and the services controlled by <span class="application"><strong>xinetd</strong></span>), either type <code class="command">chkconfig --list</code>, or use <code class="command">chkconfig</code> with no additional arguments. You should be presented with an output similar to this:
+ </div><div class="example" title="Example 7.1. Listing the services" id="ex-services-chkconfig-listing-all"><h6>Example 7.1. Listing the services</h6><div class="example-contents"><pre class="screen">~]# <code class="command">chkconfig --list</code>
+NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off
+abrtd 0:off 1:off 2:off 3:on 4:off 5:on 6:off
+acpid 0:off 1:off 2:on 3:on 4:on 5:on 6:off
+anamon 0:off 1:off 2:off 3:off 4:off 5:off 6:off
+atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
+auditd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
+avahi-daemon 0:off 1:off 2:off 3:on 4:on 5:on 6:off
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+wpa_supplicant 0:off 1:off 2:off 3:off 4:off 5:off 6:off
+
+xinetd based services:
+ chargen-dgram: off
+ chargen-stream: off
+ cvs: off
+ daytime-dgram: off
+ daytime-stream: off
+ discard-dgram: off
+<span class="emphasis"><em>... several lines omitted ...</em></span>
+ time-stream: off</pre></div></div><br class="example-break" /><div class="para">
+ As you can see, each line consists of the name of the service followed by its status (<span class="emphasis"><em>on</em></span> or <span class="emphasis"><em>off</em></span>) for each of the seven numbered runlevels. For example, in the listing above, <span class="application"><strong>NetworkManager</strong></span> is enabled for runlevel 2, 3, 4, and 5, while <span class="application"><strong>abrtd</strong></span> runs in runlevel 3 and 5. The <span class="application"><strong>xinetd</strong></span> based services are listed at the end, being either <span class="emphasis"><em>on</em></span>, or <span class="emphasis"><em>off</em></span>.
+ </div><div class="para">
+ To display the current settings for selected service only, use <code class="command">chkconfig --list</code> followed by the name of the service:
+ </div><div class="example" title="Example 7.2. Listing a single service" id="ex-services-chkconfig-listing-single"><h6>Example 7.2. Listing a single service</h6><div class="example-contents"><pre class="screen">~]# <code class="command">chkconfig --list sshd</code>
+sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off</pre></div></div><br class="example-break" /><div class="para">
+ You can also use <code class="command">chkconfig --list <em class="replaceable"><code><service></code></em></code> to display the status of a service that is managed by <span class="application"><strong>xinetd</strong></span>. In that case, the output will simply contain the information whether the service is enabled or disabled:
+ </div><div class="example" title="Example 7.3. Listing a service that is managed by xinetd" id="ex-services-chkconfig-listing-xinetd"><h6>Example 7.3. Listing a service that is managed by <span class="application">xinetd</span></h6><div class="example-contents"><pre class="screen">~]# <code class="command">chkconfig --list rsync</code>
+rsync off</pre></div></div><br class="example-break" /></div><div class="section" title="7.2.3.2. Enabling the Service" id="s3-services-chkconfig-enabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-chkconfig-enabling">7.2.3.2. Enabling the Service</h4></div></div></div><div class="para">
+ To enable the service for runlevels 2, 3, 4, and 5 at the same time, type <code class="command">chkconfig <em class="replaceable"><code><service></code></em> on</code>. For instance:
+ </div><pre class="screen">~]# <code class="command">chkconfig httpd on</code></pre><div class="para">
+ To enable the service for certain runlevels only, add the <code class="option">--level</code> option followed by the string of numbers from 0 to 6 representing each runlevel in which you want the service to run. For example, to enable the <span class="application"><strong>abrtd</strong></span> for runlevels 3 and 5, type:
+ </div><pre class="screen">~]# <code class="command">chkconfig abrtd on --level 35</code></pre><div class="para">
+ The service will be started the next time you enter one of these runlevels. If you need to start the service immediately, use the <code class="command">service</code> command as described in <a class="xref" href="s1-services-running.html#s3-services-running-running" title="7.3.1.1. Running the Service">Section 7.3.1.1, “Running the Service”</a>.
+ </div><div class="para">
+ To enable the service that is managed by <span class="application"><strong>xinetd</strong></span>, use <code class="command">chkconfig <em class="replaceable"><code><service></code></em> on</code> only, as the <code class="option">--level</code> option is not allowed:
+ </div><pre class="screen">~]# <code class="command">chkconfig rsync on</code></pre><div class="para">
+ If the <span class="application"><strong>xinetd</strong></span> daemon is running, the service is immediately enabled without having to restart the daemon manually.
+ </div></div><div class="section" title="7.2.3.3. Disabling the Service" id="s3-services-chkconfig-disabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-chkconfig-disabling">7.2.3.3. Disabling the Service</h4></div></div></div><div class="para">
+ To disable the service for runlevels 2, 3, 4, and 5 at the same time, type <code class="command">chkconfig <em class="replaceable"><code><service></code></em> off</code>. For instance:
+ </div><pre class="screen">~]# <code class="command">chkconfig httpd off</code></pre><div class="para">
+ To disable the service for certain runlevels only, add the <code class="option">--level</code> option followed by the string of numbers from 0 to 6 representing each runlevel in which you do <span class="emphasis"><em>not</em></span> want the service to run. For example, to disable the <span class="application"><strong>abrtd</strong></span> for runlevels 2 and 4, type:
+ </div><pre class="screen">~]# <code class="command">chkconfig abrtd off --level 24</code></pre><div class="para">
+ The service will be stopped the next time you enter one of these runlevels. If you need to stop the service immediately, use the <code class="command">service</code> command as described in <a class="xref" href="s1-services-running.html#s3-services-running-stopping" title="7.3.1.2. Stopping the Service">Section 7.3.1.2, “Stopping the Service”</a>.
+ </div><div class="para">
+ To disable the service that is managed by <span class="application"><strong>xinetd</strong></span>, use <code class="command">chkconfig <em class="replaceable"><code><service></code></em> off</code> only, as the <code class="option">--level</code> option is not allowed:
+ </div><pre class="screen">~]# <code class="command">chkconfig rsync off</code></pre><div class="para">
+ If the <span class="application"><strong>xinetd</strong></span> daemon is running, the service is immediately disabled without having to restart the daemon manually.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-services-ntsysv.html"><strong>Prev</strong>7.2.2. Using the ntsysv Utility</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-services-running.html"><strong>Next</strong>7.3. Running the Services</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-services-ntsysv.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-services-ntsysv.html
new file mode 100644
index 0000000..cc60616
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-services-ntsysv.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>7.2.2. Using the ntsysv Utility</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-services-configuring.html" title="7.2. Configuring the Services" /><link rel="prev" href="s1-services-configuring.html" title="7.2. Configuring the Services" /><link rel="next" href="s2-services-chkconfig.html" title="7.2.3. Using the chkconfig Utility" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-services-configuring.html"><strong>Prev</strong></a></li><li cl
ass="next"><a accesskey="n" href="s2-services-chkconfig.html"><strong>Next</strong></a></li></ul><div class="section" title="7.2.2. Using the ntsysv Utility" id="s2-services-ntsysv"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-services-ntsysv">7.2.2. Using the <span class="application"><strong>ntsysv</strong></span> Utility</h3></div></div></div><a id="id536957" class="indexterm"></a><a id="id536975" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>ntsysv</strong></span> utility is a command line application with a simple text user interface to configure which services are to be started in selected runlevels. Note that in order to use the utility, you must obtain superuser privileges first:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="para">
+ To start the utility, type the following command:
+ </div><pre class="screen">~]# <code class="command">ntsysv</code></pre><div class="figure" title="Figure 7.3. The ntsysv utility" id="fig-ntsysv"><div class="figure-contents"><div class="mediaobject"><img src="images/controlling-access-to-services-ntsysv.png" alt="The ntsysv utility" /><div class="longdesc"><div class="para">
+ The <span class="application"><strong>ntsysv</strong></span> utility
+ </div></div></div></div><h6>Figure 7.3. The <span class="application">ntsysv</span> utility</h6></div><br class="figure-break" /><div class="para">
+ The utility displays the list of available services (i.e., the services from the <code class="filename">/etc/rc.d/init.d/</code> directory) along with their current status and a description obtainable by pressing <span class="keycap"><strong>F1</strong></span>. See <a class="xref" href="s2-services-ntsysv.html#tab-services-ntsysv-states" title="Table 7.3. Possible Service States">Table 7.3, “Possible Service States”</a> for a list of used symbols and an explanation of their meaning.
+ </div><div class="table" title="Table 7.3. Possible Service States" id="tab-services-ntsysv-states"><h6>Table 7.3. Possible Service States</h6><div class="table-contents"><table summary="Possible Service States" border="1"><colgroup><col width="14%" /><col width="86%" /></colgroup><thead><tr><th>
+ Symbol
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <span class="guilabel"><strong>[*]</strong></span>
+ </td><td>
+ The service is enabled.
+ </td></tr><tr><td>
+ <span class="guilabel"><strong>[ ]</strong></span>
+ </td><td>
+ The service is disabled.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" title="7.2.2.1. Enabling the Service" id="s3-services-ntsysv-enabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-ntsysv-enabling">7.2.2.1. Enabling the Service</h4></div></div></div><div class="para">
+ To enable a service, navigate through the list using the <span class="keycap"><strong>Up</strong></span> and <span class="keycap"><strong>Down</strong></span> arrows keys, and select it with the <span class="keycap"><strong>Spacebar</strong></span>. An asterisk (<span class="guilabel"><strong>*</strong></span>) should appear in the brackets. Once you are done, use <span class="keycap"><strong>Tab</strong></span> to navigate to the <span class="guibutton"><strong>Ok</strong></span> button, and confirm the changes by pressing <span class="keycap"><strong>Enter</strong></span>.
+ </div><div class="para">
+ Please, keep in mind that <span class="application"><strong>ntsysv</strong></span> does not actually run the service. If you need to start the service immediately, use the <code class="command">service</code> command as described in <a class="xref" href="s1-services-running.html#s3-services-running-running" title="7.3.1.1. Running the Service">Section 7.3.1.1, “Running the Service”</a>.
+ </div></div><div class="section" title="7.2.2.2. Disabling the Service" id="s3-services-ntsysv-disabling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-ntsysv-disabling">7.2.2.2. Disabling the Service</h4></div></div></div><div class="para">
+ To disable a service, navigate through the list using the <span class="keycap"><strong>Up</strong></span> and <span class="keycap"><strong>Down</strong></span> arrows keys, and toggle its status with the <span class="keycap"><strong>Spacebar</strong></span>. An asterisk (<span class="guilabel"><strong>*</strong></span>) in the brackets should disappear. Once you are done, use <span class="keycap"><strong>Tab</strong></span> to navigate to the <span class="guibutton"><strong>Ok</strong></span> button, and confirm the changes by pressing <span class="keycap"><strong>Enter</strong></span>.
+ </div><div class="para">
+ Please, keep in mind that <span class="application"><strong>ntsysv</strong></span> does not actually stop the service. If you need to stop the service immediately, use the <code class="command">service</code> command as described in <a class="xref" href="s1-services-running.html#s3-services-running-stopping" title="7.3.1.2. Stopping the Service">Section 7.3.1.2, “Stopping the Service”</a>.
+ </div></div><div class="section" title="7.2.2.3. Selecting the Runlevels" id="s3-services-ntsysv-selecting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-services-ntsysv-selecting">7.2.2.3. Selecting the Runlevels</h4></div></div></div><div class="para">
+ By default, the <span class="application"><strong>ntsysv</strong></span> utility affects the current runlevel only. To enable or disable services for other runlevels, run the command with the additional <code class="option">--level</code> option followed by the string of numbers from 0 to 6 representing each runlevel you want to configure. For example, to configure runlevels 3 and 5, type:
+ </div><pre class="screen">~]# <code class="command">ntsysv --level 35</code></pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-services-configuring.html"><strong>Prev</strong>7.2. Configuring the Services</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-services-chkconfig.html"><strong>Next</strong>7.2.3. Using the chkconfig Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-beyondshell-tcpip.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-beyondshell-tcpip.html
new file mode 100644
index 0000000..0d5ea64
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-beyondshell-tcpip.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.4.2. Port Forwarding</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-beyondshell.html" title="9.4. More Than a Secure Shell" /><link rel="prev" href="s1-ssh-beyondshell.html" title="9.4. More Than a Secure Shell" /><link rel="next" href="s1-openssh-additional-resources.html" title="9.5. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ssh-beyondshell.html"><strong>Prev</strong></a></li><li class="next"><a
accesskey="n" href="s1-openssh-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="9.4.2. Port Forwarding" id="s2-ssh-beyondshell-tcpip"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-beyondshell-tcpip">9.4.2. Port Forwarding</h3></div></div></div><a id="id617883" class="indexterm"></a><div class="para">
+ SSH can secure otherwise insecure <code class="systemitem">TCP/IP</code> protocols via port forwarding. When using this technique, the SSH server becomes an encrypted conduit to the SSH client.
+ </div><div class="para">
+ Port forwarding works by mapping a local port on the client to a remote port on the server. SSH can map any port from the server to any port on the client. Port numbers do not need to match for this technique to work.
+ </div><div class="note" title="Note: Using Reserved Port Numbers"><div class="admonition_header"><h2>Note: Using Reserved Port Numbers</h2></div><div class="admonition"><div class="para">
+ Setting up port forwarding to listen on ports below 1024 requires root level access.
+ </div></div></div><div class="para">
+ To create a TCP/IP port forwarding channel which listens for connections on the <code class="systemitem">localhost</code>, use a command in the following form:
+ </div><pre class="screen"><code class="command">ssh -L <em class="replaceable"><code>local-port</code></em>:<em class="replaceable"><code>remote-hostname</code></em>:<em class="replaceable"><code>remote-port</code></em> <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em></code></pre><div class="para">
+ For example, to check email on a server called <code class="systemitem">mail.example.com</code> using <code class="systemitem">POP3</code> through an encrypted connection, use the following command:
+ </div><pre class="screen">~]$ <code class="command">ssh -L 1100:mail.example.com:110 mail.example.com</code></pre><div class="para">
+ Once the port forwarding channel is in place between the client machine and the mail server, direct a POP3 mail client to use port <code class="literal">1100</code> on the <code class="systemitem">localhost</code> to check for new email. Any requests sent to port <code class="literal">1100</code> on the client system will be directed securely to the <code class="systemitem">mail.example.com</code> server.
+ </div><div class="para">
+ If <code class="systemitem">mail.example.com</code> is not running an SSH server, but another machine on the same network is, SSH can still be used to secure part of the connection. However, a slightly different command is necessary:
+ </div><pre class="screen">~]$ <code class="command">ssh -L 1100:mail.example.com:110 other.example.com</code></pre><div class="para">
+ In this example, POP3 requests from port <code class="literal">1100</code> on the client machine are forwarded through the SSH connection on port <code class="literal">22</code> to the SSH server, <code class="systemitem">other.example.com</code>. Then, <code class="systemitem">other.example.com</code> connects to port <code class="literal">110</code> on <code class="systemitem">mail.example.com</code> to check for new email. Note that when using this technique, only the connection between the client system and <code class="systemitem">other.example.com</code> SSH server is secure.
+ </div><div class="para">
+ Port forwarding can also be used to get information securely through network firewalls. If the firewall is configured to allow SSH traffic via its standard port (that is, port 22) but blocks access to other ports, a connection between two hosts using the blocked ports is still possible by redirecting their communication over an established SSH connection.
+ </div><div class="important" title="Important: A Connection Is Only as Secure as a Client System"><div class="admonition_header"><h2>Important: A Connection Is Only as Secure as a Client System</h2></div><div class="admonition"><div class="para">
+ Using port forwarding to forward connections in this manner allows any user on the client system to connect to that service. If the client system becomes compromised, the attacker also has access to forwarded services.
+ </div><div class="para">
+ System administrators concerned about port forwarding can disable this functionality on the server by specifying a <code class="option">No</code> parameter for the <code class="option">AllowTcpForwarding</code> line in <code class="filename">/etc/ssh/sshd_config</code> and restarting the <code class="command">sshd</code> service.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ssh-beyondshell.html"><strong>Prev</strong>9.4. More Than a Secure Shell</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-openssh-additional-resources.html"><strong>Next</strong>9.5. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-clients-scp.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-clients-scp.html
new file mode 100644
index 0000000..722ac02
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-clients-scp.html
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3.2. Using the scp Utility</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-clients.html" title="9.3. OpenSSH Clients" /><link rel="prev" href="s1-ssh-clients.html" title="9.3. OpenSSH Clients" /><link rel="next" href="s2-ssh-clients-sftp.html" title="9.3.3. Using the sftp Utility" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ssh-clients.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-ssh-clients-sft
p.html"><strong>Next</strong></a></li></ul><div class="section" title="9.3.2. Using the scp Utility" id="s2-ssh-clients-scp"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-clients-scp">9.3.2. Using the <code class="command">scp</code> Utility</h3></div></div></div><a id="id785029" class="indexterm"></a><a id="id471642" class="indexterm"></a><a id="id471662" class="indexterm"></a><div class="para">
+ <code class="command">scp</code> can be used to transfer files between machines over a secure, encrypted connection. In its design, it is very similar to <code class="command">rcp</code>.
+ </div><div class="para">
+ To transfer a local file to a remote system, use a command in the following form:
+ </div><pre class="screen"><code class="command">scp <em class="replaceable"><code>localfile</code></em> <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em>:<em class="replaceable"><code>remotefile</code></em></code></pre><div class="para">
+ For example, if you want to transfer <code class="filename">taglist.vim</code> to a remote machine named <code class="systemitem">penguin.example.com</code>, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">scp taglist.vim john at penguin.example.com:.vim/plugin/taglist.vim</code>
+john at penguin.example.com's password:
+taglist.vim 100% 144KB 144.5KB/s 00:00</pre><div class="para">
+ Multiple files can be specified at once. To transfer the contents of <code class="filename">.vim/plugin/</code> to the same directory on the remote machine <code class="systemitem">penguin.example.com</code>, type the following command:
+ </div><pre class="screen">~]$ <code class="command">scp .vim/plugin/* john at penguin.example.com:.vim/plugin/</code>
+john at penguin.example.com's password:
+closetag.vim 100% 13KB 12.6KB/s 00:00
+snippetsEmu.vim 100% 33KB 33.1KB/s 00:00
+taglist.vim 100% 144KB 144.5KB/s 00:00</pre><div class="para">
+ To transfer a remote file to the local system, use the following syntax:
+ </div><pre class="screen"><code class="command">scp <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em>:<em class="replaceable"><code>remotefile</code></em> <em class="replaceable"><code>localfile</code></em></code></pre><div class="para">
+ For instance, to download the <code class="filename">.vimrc</code> configuration file from the remote machine, type:
+ </div><pre class="screen">~]$ <code class="command">scp john at penguin.example.com:.vimrc .vimrc</code>
+john at penguin.example.com's password:
+.vimrc 100% 2233 2.2KB/s 00:00</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ssh-clients.html"><strong>Prev</strong>9.3. OpenSSH Clients</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-ssh-clients-sftp.html"><strong>Next</strong>9.3.3. Using the sftp Utility</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-clients-sftp.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-clients-sftp.html
new file mode 100644
index 0000000..b25e267
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-clients-sftp.html
@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.3.3. Using the sftp Utility</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-clients.html" title="9.3. OpenSSH Clients" /><link rel="prev" href="s2-ssh-clients-scp.html" title="9.3.2. Using the scp Utility" /><link rel="next" href="s1-ssh-beyondshell.html" title="9.4. More Than a Secure Shell" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-clients-scp.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-
ssh-beyondshell.html"><strong>Next</strong></a></li></ul><div class="section" title="9.3.3. Using the sftp Utility" id="s2-ssh-clients-sftp"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-clients-sftp">9.3.3. Using the <code class="command">sftp</code> Utility</h3></div></div></div><a id="id700561" class="indexterm"></a><a id="id700577" class="indexterm"></a><div class="para">
+ The <code class="command">sftp</code> utility can be used to open a secure, interactive FTP session. In its design, it is similar to <code class="command">ftp</code> except that it uses a secure, encrypted connection.
+ </div><div class="para">
+ To connect to a remote system, use a command in the following form:
+ </div><pre class="screen"><code class="command">sftp <em class="replaceable"><code>username</code></em>@<em class="replaceable"><code>hostname</code></em></code></pre><div class="para">
+ For example, to log in to a remote machine named <code class="systemitem">penguin.example.com</code> with <code class="systemitem">john</code> as a username, type:
+ </div><pre class="screen">~]$ <code class="command">sftp john at penguin.example.com</code>
+john at penguin.example.com's password:
+Connected to penguin.example.com.
+sftp></pre><div class="para">
+ After you enter the correct password, you will be presented with a prompt. The <code class="command">sftp</code> utility accepts a set of commands similar to those used by <code class="command">ftp</code> (see <a class="xref" href="s2-ssh-clients-sftp.html#table-ssh-clients-sftp" title="Table 9.3. A selection of available sftp commands">Table 9.3, “A selection of available <code class="command">sftp</code> commands”</a>).
+ </div><div class="table" title="Table 9.3. A selection of available sftp commands" id="table-ssh-clients-sftp"><h6>Table 9.3. A selection of available <code class="command">sftp</code> commands</h6><div class="table-contents"><table summary="A selection of available sftp commands" border="1"><colgroup><col width="38%" /><col width="63%" /></colgroup><thead><tr><th>
+ Command
+ </th><th>
+ Description
+ </th></tr></thead><tbody><tr><td>
+ <code class="command">ls</code> [<em class="replaceable"><code>directory</code></em>]
+ </td><td>
+ List the content of a remote <em class="replaceable"><code>directory</code></em>. If none is supplied, a current working directory is used by default.
+ </td></tr><tr><td>
+ <code class="command">cd</code> <em class="replaceable"><code>directory</code></em>
+ </td><td>
+ Change the remote working directory to <em class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">mkdir</code> <em class="replaceable"><code>directory</code></em>
+ </td><td>
+ Create a remote <em class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">rmdir</code> <em class="replaceable"><code>path</code></em>
+ </td><td>
+ Remove a remote <em class="replaceable"><code>directory</code></em>.
+ </td></tr><tr><td>
+ <code class="command">put</code> <em class="replaceable"><code>localfile</code></em> [<em class="replaceable"><code>remotefile</code></em>]
+ </td><td>
+ Transfer <em class="replaceable"><code>localfile</code></em> to a remote machine.
+ </td></tr><tr><td>
+ <code class="command">get</code> <em class="replaceable"><code>remotefile</code></em> [<em class="replaceable"><code>localfile</code></em>]
+ </td><td>
+ Transfer <em class="replaceable"><code>remotefile</code></em> from a remote machine.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ For a complete list of available commands, refer to the <code class="command">sftp</code> man page.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-clients-scp.html"><strong>Prev</strong>9.3.2. Using the scp Utility</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-ssh-beyondshell.html"><strong>Next</strong>9.4. More Than a Secure Shell</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-keypairs.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-keypairs.html
new file mode 100644
index 0000000..f1bd749
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-keypairs.html
@@ -0,0 +1,150 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2.4. Using a Key-Based Authentication</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-configuration.html" title="9.2. An OpenSSH Configuration" /><link rel="prev" href="s2-ssh-configuration-requiring.html" title="9.2.3. Requiring SSH for Remote Connections" /><link rel="next" href="s1-ssh-clients.html" title="9.3. OpenSSH Clients" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-configuration-requiring.html"><strong>Prev</strong></a></li><l
i class="next"><a accesskey="n" href="s1-ssh-clients.html"><strong>Next</strong></a></li></ul><div class="section" title="9.2.4. Using a Key-Based Authentication" id="s2-ssh-configuration-keypairs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-configuration-keypairs">9.2.4. Using a Key-Based Authentication</h3></div></div></div><a id="id634181" class="indexterm"></a><div class="para">
+ To improve the system security even further, you can enforce the use the key-based authentication by disabling the standard password authentication. To do so, open the <code class="filename">/etc/ssh/sshd_config</code> configuration file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, and change the <code class="option">PasswordAuthentication</code> option as follows:
+ </div><pre class="screen">PasswordAuthentication no</pre><div class="para">
+ To be able to use <code class="command">ssh</code>, <code class="command">scp</code>, or <code class="command">sftp</code> to connect to the server from a client machine, generate an authorization key pair by following the steps below. Note that keys must be generated for each user separately.
+ </div><div class="para">
+ Fedora 14 uses SSH Protocol 2 and RSA keys by default (see <a class="xref" href="ch-OpenSSH.html#s2-ssh-versions" title="9.1.3. Protocol Versions">Section 9.1.3, “Protocol Versions”</a> for more information).
+ </div><div class="important" title="Important: Do Not Generate Key Pairs as root"><div class="admonition_header"><h2>Important: Do Not Generate Key Pairs as root</h2></div><div class="admonition"><div class="para">
+ If you complete the steps as root, only root will be able to use the keys.
+ </div></div></div><div class="note" title="Tip: Backup Your ~/.ssh/ Directory"><div class="admonition_header"><h2>Tip: Backup Your <code class="filename">~/.ssh/</code> Directory</h2></div><div class="admonition"><div class="para">
+ If you reinstall your system and want to keep previously generated key pair, backup the <code class="filename">~/.ssh/</code> directory. After reinstalling, copy it back to your home directory. This process can be done for all users on your system, including root.
+ </div></div></div><div class="section" title="9.2.4.1. Generating Key Pairs" id="s3-ssh-configuration-keypairs-generating"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-ssh-configuration-keypairs-generating">9.2.4.1. Generating Key Pairs</h4></div></div></div><a id="id544934" class="indexterm"></a><a id="id544946" class="indexterm"></a><div class="para">
+ To generate an RSA key pair for version 2 of the SSH protocol, follow these steps:
+ </div><a id="id488044" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Generate an RSA key pair by typing the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">ssh-keygen -t rsa</code>
+Generating public/private rsa key pair.
+Enter file in which to save the key (/home/john/.ssh/id_rsa):</pre></li><li class="step" title="Step 2"><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to confirm the default location (that is, <code class="filename">~/.ssh/id_rsa</code>) for the newly created key.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so. For security reasons, avoid using the same password as you use to log in to your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/id_rsa.
+Your public key has been saved in /home/john/.ssh/id_rsa.pub.
+The key fingerprint is:
+e7:97:c7:e2:0e:f9:0e:fc:c4:d7:cb:e5:31:11:92:14 john at penguin.example.com
+The key's randomart image is:
++--[ RSA 2048]----+
+| E. |
+| . . |
+| o . |
+| . .|
+| S . . |
+| + o o ..|
+| * * +oo|
+| O +..=|
+| o* o.|
++-----------------+</pre></li><li class="step" title="Step 4"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code class="command">chmod 755 ~/.ssh</code></pre></li><li class="step" title="Step 5"><div class="para">
+ Copy the content of <code class="filename">~/.ssh/id_rsa.pub</code> into the <code class="filename">~/.ssh/authorized_keys</code> on the machine to which you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step" title="Step 6"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/authorized_keys</code> file using the following command:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><a id="id603386" class="indexterm"></a><a id="id542196" class="indexterm"></a><div class="para">
+ To generate a DSA key pair for version 2 of the SSH protocol, follow these steps:
+ </div><a id="id542216" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Generate a DSA key pair by typing the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">ssh-keygen -t dsa</code>
+Generating public/private dsa key pair.
+Enter file in which to save the key (/home/john/.ssh/id_dsa):</pre></li><li class="step" title="Step 2"><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to confirm the default location (that is, <code class="filename">~/.ssh/id_dsa</code>) for the newly created key.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so. For security reasons, avoid using the same password as you use to log in to your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/id_dsa.
+Your public key has been saved in /home/john/.ssh/id_dsa.pub.
+The key fingerprint is:
+81:a1:91:a8:9f:e8:c5:66:0d:54:f5:90:cc:bc:cc:27 john at penguin.example.com
+The key's randomart image is:
++--[ DSA 1024]----+
+| .oo*o. |
+| ...o Bo |
+| .. . + o. |
+|. . E o |
+| o..o S |
+|. o= . |
+|. + |
+| . |
+| |
++-----------------+</pre></li><li class="step" title="Step 4"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code class="command">chmod 775 ~/.ssh</code></pre></li><li class="step" title="Step 5"><div class="para">
+ Copy the content of <code class="filename">~/.ssh/id_dsa.pub</code> into the <code class="filename">~/.ssh/authorized_keys</code> on the machine to which you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step" title="Step 6"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/authorized_keys</code> file using the following command:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><a id="id484374" class="indexterm"></a><a id="id484386" class="indexterm"></a><div class="para">
+ To generate an RSA key pair for version 1 of the SSH protocol, follow these steps:
+ </div><a id="id484406" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Generate an RSA key pair by typing the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">ssh-keygen -t rsa1</code>
+Generating public/private rsa1 key pair.
+Enter file in which to save the key (/home/john/.ssh/identity):</pre></li><li class="step" title="Step 2"><div class="para">
+ Press <span class="keycap"><strong>Enter</strong></span> to confirm the default location (that is, <code class="filename">~/.ssh/identity</code>) for the newly created key.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Enter a passphrase, and confirm it by entering it again when prompted to do so. For security reasons, avoid using the same password as you use to log into your account.
+ </div><div class="para">
+ After this, you will be presented with a message similar to this:
+ </div><pre class="screen">Your identification has been saved in /home/john/.ssh/identity.
+Your public key has been saved in /home/john/.ssh/identity.pub.
+The key fingerprint is:
+cb:f6:d5:cb:6e:5f:2b:28:ac:17:0c:e4:62:e4:6f:59 john at penguin.example.com
+The key's randomart image is:
++--[RSA1 2048]----+
+| |
+| . . |
+| o o |
+| + o E |
+| . o S |
+| = + . |
+| . = . o . .|
+| . = o o..o|
+| .o o o=o.|
++-----------------+</pre></li><li class="step" title="Step 4"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/</code> directory:
+ </div><pre class="screen">~]$ <code class="command">chmod 755 ~/.ssh</code></pre></li><li class="step" title="Step 5"><div class="para">
+ Copy the content of <code class="filename">~/.ssh/identity.pub</code> into the <code class="filename">~/.ssh/authorized_keys</code> on the machine to which you want to connect, appending it to its end if the file already exists.
+ </div></li><li class="step" title="Step 6"><div class="para">
+ Change the permissions of the <code class="filename">~/.ssh/authorized_keys</code> file using the following command:
+ </div><pre class="screen">~]$ <code class="command">chmod 644 ~/.ssh/authorized_keys</code></pre></li></ol></div><div class="para">
+ Refer to <a class="xref" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent" title="9.2.4.2. Configuring ssh-agent">Section 9.2.4.2, “Configuring <code class="command">ssh-agent</code>”</a> for information on how to set up your system to remember the passphrase.
+ </div><div class="important" title="Important: Never Share Your Private Key"><div class="admonition_header"><h2>Important: Never Share Your Private Key</h2></div><div class="admonition"><div class="para">
+ The private key is for your personal use only, and it is important that you never give it to anyone.
+ </div></div></div></div><div class="section" title="9.2.4.2. Configuring ssh-agent" id="s3-ssh-configuration-keypairs-agent"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-ssh-configuration-keypairs-agent">9.2.4.2. Configuring <code class="command">ssh-agent</code></h4></div></div></div><a id="id594465" class="indexterm"></a><a id="id699774" class="indexterm"></a><div class="para">
+ To store your passphrase so that you do not have to enter it each time you initiate a connection with a remote machine, you can use the <code class="command">ssh-agent</code> authentication agent. If you are running GNOME, you can configure it to prompt you for your passphrase whenever you log in and remember it during the whole session. Otherwise you can store the passphrase for a certain shell prompt.
+ </div><div class="para">
+ To save your passphrase during your GNOME session, follow these steps:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Make sure you have the <span class="package">openssh-askpass</span> package installed. If not, refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Select <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Startup Applications</strong></span> from the panel. The <span class="application"><strong>Startup Applications Preferences</strong></span> will be started, and the tab containing a list of available startup programs will be shown by default.
+ </div><div class="figure" title="Figure 9.1. Startup Applications Preferences" id="fig-ssh-startup-applications"><div class="figure-contents"><div class="mediaobject"><img src="images/ssh-startup-applications.png" alt="Startup Applications Preferences" /><div class="longdesc"><div class="para">
+ <span class="application"><strong>Startup Applications Preferences</strong></span>
+ </div></div></div></div><h6>Figure 9.1. <span class="application">Startup Applications Preferences</span></h6></div><br class="figure-break" /></li><li class="step" title="Step 3"><div class="para">
+ Click the <span class="guibutton"><strong>Add</strong></span> button on the right, and enter <strong class="userinput"><code>/usr/bin/ssh-add</code></strong> in the <span class="guilabel"><strong>Command</strong></span> field.
+ </div><a id="id823807" class="indexterm"></a><a id="id823823" class="indexterm"></a><div class="figure" title="Figure 9.2. Adding new application" id="fig-ssh-startup-applications-add"><div class="figure-contents"><div class="mediaobject"><img src="images/ssh-startup-applications-add.png" alt="Adding new application" /><div class="longdesc"><div class="para">
+ Adding new application
+ </div></div></div></div><h6>Figure 9.2. Adding new application</h6></div><br class="figure-break" /></li><li class="step" title="Step 4"><div class="para">
+ Click <span class="guibutton"><strong>Add</strong></span> and make sure the check box next to the newly added item is selected.
+ </div><div class="figure" title="Figure 9.3. Enabling the application" id="fig-ssh-startup-applications-check"><div class="figure-contents"><div class="mediaobject"><img src="images/ssh-startup-applications-check.png" alt="Enabling the application" /><div class="longdesc"><div class="para">
+ Enabling the application
+ </div></div></div></div><h6>Figure 9.3. Enabling the application</h6></div><br class="figure-break" /></li><li class="step" title="Step 5"><div class="para">
+ Log out and then log back in. A dialog box will appear prompting you for your passphrase. From this point on, you should not be prompted for a password by <code class="command">ssh</code>, <code class="command">scp</code>, or <code class="command">sftp</code>.
+ </div><div class="figure" title="Figure 9.4. Entering a passphrase" id="fig-ssh-passphrase-prompt"><div class="figure-contents"><div class="mediaobject"><img src="images/ssh-passphrase-prompt.png" alt="Entering a passphrase" /><div class="longdesc"><div class="para">
+ Entering a passphrase
+ </div></div></div></div><h6>Figure 9.4. Entering a passphrase</h6></div><br class="figure-break" /></li></ol></div><div class="para">
+ To save your passphrase for a certain shell prompt, use the following command:
+ </div><pre class="screen">~]$ <code class="command">ssh-add</code>
+Enter passphrase for /home/john/.ssh/id_rsa:</pre><div class="para">
+ Note that when you log out, your passphrase will be forgotten. You must execute the command each time you log in to a virtual console or a terminal window.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-configuration-requiring.html"><strong>Prev</strong>9.2.3. Requiring SSH for Remote Connections</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-ssh-clients.html"><strong>Next</strong>9.3. OpenSSH Clients</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-requiring.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-requiring.html
new file mode 100644
index 0000000..3bac749
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-requiring.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2.3. Requiring SSH for Remote Connections</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-configuration.html" title="9.2. An OpenSSH Configuration" /><link rel="prev" href="s2-ssh-configuration-sshd.html" title="9.2.2. Starting an OpenSSH Server" /><link rel="next" href="s2-ssh-configuration-keypairs.html" title="9.2.4. Using a Key-Based Authentication" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-configuration-sshd.html"><strong>Prev</stro
ng></a></li><li class="next"><a accesskey="n" href="s2-ssh-configuration-keypairs.html"><strong>Next</strong></a></li></ul><div class="section" title="9.2.3. Requiring SSH for Remote Connections" id="s2-ssh-configuration-requiring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-configuration-requiring">9.2.3. Requiring SSH for Remote Connections</h3></div></div></div><a id="id544848" class="indexterm"></a><a id="id550052" class="indexterm"></a><div class="para">
+ For SSH to be truly effective, using insecure connection protocols should be prohibited. Otherwise, a user's password may be protected using SSH for one session, only to be captured later while logging in using Telnet. Some services to disable include <code class="command">telnet</code>, <code class="command">rsh</code>, <code class="command">rlogin</code>, and <code class="command">vsftpd</code>.
+ </div><div class="para">
+ To disable these services, type the following commands at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">chkconfig telnet off</code>
+~]# <code class="command">chkconfig rsh off</code>
+~]# <code class="command">chkconfig rlogin off</code>
+~]# <code class="command">chkconfig vsftpd off</code></pre><div class="para">
+ For more information on runlevels and configuring services in general, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-configuration-sshd.html"><strong>Prev</strong>9.2.2. Starting an OpenSSH Server</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-ssh-configuration-keypairs.html"><strong>Next</strong>9.2.4. Using a Key-Based Authentication</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-sshd.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-sshd.html
new file mode 100644
index 0000000..dbdd2b8
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s2-ssh-configuration-sshd.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>9.2.2. Starting an OpenSSH Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-ssh-configuration.html" title="9.2. An OpenSSH Configuration" /><link rel="prev" href="s1-ssh-configuration.html" title="9.2. An OpenSSH Configuration" /><link rel="next" href="s2-ssh-configuration-requiring.html" title="9.2.3. Requiring SSH for Remote Connections" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ssh-configuration.html"><strong>Prev</strong></a></
li><li class="next"><a accesskey="n" href="s2-ssh-configuration-requiring.html"><strong>Next</strong></a></li></ul><div class="section" title="9.2.2. Starting an OpenSSH Server" id="s2-ssh-configuration-sshd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s2-ssh-configuration-sshd">9.2.2. Starting an OpenSSH Server</h3></div></div></div><a id="id660177" class="indexterm"></a><div class="note" title="Note: Make Sure You Have Relevant Packages Installed"><div class="admonition_header"><h2>Note: Make Sure You Have Relevant Packages Installed</h2></div><div class="admonition"><div class="para">
+ To run an OpenSSH server, you must have the <span class="package">openssh-server</span> and <span class="package">openssh</span> packages installed. Refer to <a class="xref" href="sec-Installing.html" title="1.2.2. Installing">Section 1.2.2, “Installing”</a> for more information on how to install new packages in Fedora.
+ </div></div></div><a id="id788660" class="indexterm"></a><div class="para">
+ To start the <code class="command">sshd</code> daemon, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service sshd start</code></pre><a id="id788691" class="indexterm"></a><div class="para">
+ To stop the running <code class="command">sshd</code> daemon, use the following command:
+ </div><pre class="screen">~]# <code class="command">service sshd stop</code></pre><div class="para">
+ If you want the daemon to start automatically at the boot time, type:
+ </div><pre class="screen">~]# <code class="command">chkconfig sshd on</code></pre><div class="para">
+ This will enable the service for all runlevels. For more configuration options, refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for the detailed information on how to manage services.
+ </div><div class="para">
+ Note that if you reinstall the system, a new set of identification keys will be created. As a result, clients who had connected to the system with any of the OpenSSH tools before the reinstall will see the following message:
+ </div><pre class="screen">@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
+@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
+IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
+Someone could be eavesdropping on you right now (man-in-the-middle attack)!
+It is also possible that the RSA host key has just been changed.</pre><div class="para">
+ To prevent this, you can backup the relevant files from the <code class="filename">/etc/ssh/</code> directory (see <a class="xref" href="s1-ssh-configuration.html#table-ssh-configuration-configs-system" title="Table 9.1. System-wide configuration files">Table 9.1, “System-wide configuration files”</a> for a complete list), and restore them whenever you reinstall the system.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-ssh-configuration.html"><strong>Prev</strong>9.2. An OpenSSH Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-ssh-configuration-requiring.html"><strong>Next</strong>9.2.3. Requiring SSH for Remote Connections</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s3-apache-running-restarting.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s3-apache-running-restarting.html
new file mode 100644
index 0000000..a6e539c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s3-apache-running-restarting.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.2.3. Restarting the Service</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-running.html" title="11.2. Running the httpd Service" /><link rel="prev" href="s2-apache-running-stopping.html" title="11.2.2. Stopping the Service" /><link rel="next" href="s3-apache-running-status.html" title="11.2.4. Checking the Service Status" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-running-stopping.html"><strong>Prev</strong></a></li><
li class="next"><a accesskey="n" href="s3-apache-running-status.html"><strong>Next</strong></a></li></ul><div class="section" title="11.2.3. Restarting the Service" id="s3-apache-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s3-apache-running-restarting">11.2.3. Restarting the Service</h3></div></div></div><a id="id786369" class="indexterm"></a><div class="para">
+ There are three different ways to restart the running <code class="systemitem">httpd</code> service:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ To restart the service completely, type:
+ </div><pre class="screen">~]# <code class="command">service httpd restart</code>
+Stopping httpd: [ OK ]
+Starting httpd: [ OK ]</pre><div class="para">
+ This will stop the running <code class="systemitem">httpd</code> service, and then start it again. Use this command after installing or removing a dynamically loaded module such as PHP.
+ </div></li><li class="listitem"><div class="para">
+ To only reload the configuration, type:
+ </div><pre class="screen">~]# <code class="command">service httpd reload</code></pre><div class="para">
+ This will cause the running <code class="systemitem">httpd</code> service to reload the configuration file. Note that any requests being currently processed will be interrupted, which may cause a client browser to display an error message or render a partial page.
+ </div></li><li class="listitem"><div class="para">
+ To reload the configuration without affecting active requests, type:
+ </div><pre class="screen">~]# <code class="command">service httpd graceful</code></pre><div class="para">
+ This will cause the running <code class="systemitem">httpd</code> service to reload the configuration file. Note that any requests being currently processed will use the old configuration.
+ </div></li></ol></div><div class="para">
+ Alternatively, you can use the <span class="application"><strong>Service Configuration</strong></span> utility as described in <a class="xref" href="s1-services-configuring.html#s3-services-serviceconf-restarting" title="7.2.1.5. Restarting the Running Service">Section 7.2.1.5, “Restarting the Running Service”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-apache-running-stopping.html"><strong>Prev</strong>11.2.2. Stopping the Service</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s3-apache-running-status.html"><strong>Next</strong>11.2.4. Checking the Service Status</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s3-apache-running-status.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s3-apache-running-status.html
new file mode 100644
index 0000000..1628645
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s3-apache-running-status.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>11.2.4. Checking the Service Status</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-apache-running.html" title="11.2. Running the httpd Service" /><link rel="prev" href="s3-apache-running-restarting.html" title="11.2.3. Restarting the Service" /><link rel="next" href="s1-apache-editing.html" title="11.3. Editing the Configuration Files" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s3-apache-running-restarting.html"><strong>Prev</strong></a></li>
<li class="next"><a accesskey="n" href="s1-apache-editing.html"><strong>Next</strong></a></li></ul><div class="section" title="11.2.4. Checking the Service Status" id="s3-apache-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s3-apache-running-status">11.2.4. Checking the Service Status</h3></div></div></div><a id="id585624" class="indexterm"></a><div class="para">
+ To check whether the service is running, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">service httpd status</code>
+httpd (pid 19014) is running...</pre><div class="para">
+ Alternatively, you can use the <span class="application"><strong>Service Configuration</strong></span> utility as described in <a class="xref" href="s1-services-configuring.html#s2-services-serviceconf" title="7.2.1. Using the Service Configuration Utility">Section 7.2.1, “Using the <span class="application"><strong>Service Configuration</strong></span> Utility”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s3-apache-running-restarting.html"><strong>Prev</strong>11.2.3. Restarting the Service</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-apache-editing.html"><strong>Next</strong>11.3. Editing the Configuration Files</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/s3-bind-zone-rr.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/s3-bind-zone-rr.html
new file mode 100644
index 0000000..a336186
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/s3-bind-zone-rr.html
@@ -0,0 +1,130 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>10.3.2. Common Resource Records</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-bind-zone.html" title="10.3. Editing Zone Files" /><link rel="prev" href="s1-bind-zone.html" title="10.3. Editing Zone Files" /><link rel="next" href="s2-bind-zone-comm.html" title="10.3.3. Comment Tags" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-zone.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-zone-comm.html"><st
rong>Next</strong></a></li></ul><div class="section" title="10.3.2. Common Resource Records" id="s3-bind-zone-rr"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="s3-bind-zone-rr">10.3.2. Common Resource Records</h3></div></div></div><div class="para">
+ The following resource records are commonly used in zone files:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <a id="id649360" class="indexterm"></a>
+ <code class="command">A</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Address</em> record specifies an IP address to be assigned to a name. It takes the following form:
+ </div><pre class="screen"><em class="replaceable"><code>hostname</code></em> IN A <em class="replaceable"><code>IP-address</code></em></pre><div class="para">
+ If the <em class="replaceable"><code>hostname</code></em> value is omitted, the record will point to the last specified <em class="replaceable"><code>hostname</code></em>.
+ </div><div class="para">
+ In <a class="xref" href="s3-bind-zone-rr.html#example-bind-zone-rr-a" title="Example 10.10. Using the A resource record">Example 10.10, “Using the <code class="command">A</code> resource record”</a>, the requests for <code class="systemitem">server1.example.com</code> are pointed to <code class="literal">10.0.1.3</code> or <code class="literal">10.0.1.5</code>.
+ </div><div class="example" title="Example 10.10. Using the A resource record" id="example-bind-zone-rr-a"><h6>Example 10.10. Using the <code class="command">A</code> resource record</h6><div class="example-contents"><pre class="screen">server1 IN A 10.0.1.3
+ IN A 10.0.1.5</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id711864" class="indexterm"></a>
+ <code class="command">CNAME</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Canonical Name</em> record maps one name to another. Because of this, this type of record is sometimes referred to as an <em class="firstterm">alias record</em>. It takes the following form:
+ </div><pre class="screen"><em class="replaceable"><code>alias-name</code></em> IN CNAME <em class="replaceable"><code>real-name</code></em></pre><div class="para">
+ <code class="command">CNAME</code> records are most commonly used to point to services that use a common naming scheme, such as <code class="literal">www</code> for Web servers. However, there are multiple restrictions for their usage:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ CNAME records should not point to other CNAME records. This is mainly to avoid possible infinite loops.
+ </div></li><li class="listitem"><div class="para">
+ CNAME records should not contain other resource record types (such as A, NS, MX, etc.). The only exception are DNSSEC related records (that is, RRSIG, NSEC, etc.) when the zone is signed.
+ </div></li><li class="listitem"><div class="para">
+ Other resource record that point to the fully qualified domain name (FQDN) of a host (that is, NS, MX, PTR) should not point to a CNAME record.
+ </div></li></ul></div><div class="para">
+ In <a class="xref" href="s3-bind-zone-rr.html#example-bind-zone-rr-cname" title="Example 10.11. Using the CNAME resource record">Example 10.11, “Using the <code class="command">CNAME</code> resource record”</a>, the <code class="command">A</code> record binds a hostname to an IP address, while the <code class="command">CNAME</code> record points the commonly used <code class="literal">www</code> hostname to it.
+ </div><div class="example" title="Example 10.11. Using the CNAME resource record" id="example-bind-zone-rr-cname"><h6>Example 10.11. Using the <code class="command">CNAME</code> resource record</h6><div class="example-contents"><pre class="screen">server1 IN A 10.0.1.5
+www IN CNAME server1</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id482429" class="indexterm"></a>
+ <code class="command">MX</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Mail Exchange</em> record specifies where the mail sent to a particular namespace controlled by this zone should go. It takes the following form:
+ </div><pre class="screen">IN MX <em class="replaceable"><code>preference-value</code></em> <em class="replaceable"><code>email-server-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>email-server-name</code></em> is a fully qualified domain name (FQDN). The <em class="replaceable"><code>preference-value</code></em> allows numerical ranking of the email servers for a namespace, giving preference to some email systems over others. The <code class="command">MX</code> resource record with the lowest <em class="replaceable"><code>preference-value</code></em> is preferred over the others. However, multiple email servers can possess the same value to distribute email traffic evenly among them.
+ </div><div class="para">
+ In <a class="xref" href="s3-bind-zone-rr.html#example-bind-zone-rr-mx" title="Example 10.12. Using the MX resource record">Example 10.12, “Using the <code class="command">MX</code> resource record”</a>, the first <code class="systemitem">mail.example.com</code> email server is preferred to the <code class="systemitem">mail2.example.com</code> email server when receiving email destined for the <code class="systemitem">example.com</code> domain.
+ </div><div class="example" title="Example 10.12. Using the MX resource record" id="example-bind-zone-rr-mx"><h6>Example 10.12. Using the <code class="command">MX</code> resource record</h6><div class="example-contents"><pre class="screen">example.com. IN MX 10 mail.example.com.
+ IN MX 20 mail2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id503110" class="indexterm"></a>
+ <code class="command">NS</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Nameserver</em> record announces authoritative nameservers for a particular zone. It takes the following form:
+ </div><pre class="screen">IN NS <em class="replaceable"><code>nameserver-name</code></em></pre><div class="para">
+ The <em class="replaceable"><code>nameserver-name</code></em> should be a fully qualified domain name (FQDN). Note that when two nameservers are listed as authoritative for the domain, it is not important whether these nameservers are secondary nameservers, or if one of them is a primary server. They are both still considered authoritative.
+ </div><div class="example" title="Example 10.13. Using the NS resource record" id="example-bind-zone-rr-ns"><h6>Example 10.13. Using the <code class="command">NS</code> resource record</h6><div class="example-contents"><pre class="screen">IN NS dns1.example.com.
+IN NS dns2.example.com.</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="id417362" class="indexterm"></a>
+ <code class="command">PTR</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Pointer</em> record points to another part of the namespace. It takes the following form:
+ </div><pre class="screen"><em class="replaceable"><code>last-IP-digit</code></em> IN PTR <em class="replaceable"><code>FQDN-of-system</code></em></pre><div class="para">
+ The <em class="replaceable"><code>last-IP-digit</code></em> directive is the last number in an IP address, and the <em class="replaceable"><code>FQDN-of-system</code></em> is a fully qualified domain name (FQDN).
+ </div><div class="para">
+ <code class="command">PTR</code> records are primarily used for reverse name resolution, as they point IP addresses back to a particular name. Refer to <a class="xref" href="s2-bind-zone-examples.html#s2-bind-configuration-zone-reverse" title="10.3.4.2. A Reverse Name Resolution Zone File">Section 10.3.4.2, “A Reverse Name Resolution Zone File”</a> for more examples of <code class="command">PTR</code> records in use.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="id728106" class="indexterm"></a>
+ <code class="command">SOA</code> </span></dt><dd><div class="para">
+ The <em class="firstterm">Start of Authority</em> record announces important authoritative information about a namespace to the nameserver. Located after the directives, it is the first resource record in a zone file. It takes the following form:
+ </div><pre class="screen">@ IN SOA <em class="replaceable"><code>primary-name-server</code></em> <em class="replaceable"><code>hostmaster-email</code></em> (
+ <em class="replaceable"><code>serial-number</code></em>
+ <em class="replaceable"><code>time-to-refresh</code></em>
+ <em class="replaceable"><code>time-to-retry</code></em>
+ <em class="replaceable"><code>time-to-expire</code></em>
+ <em class="replaceable"><code>minimum-TTL</code></em> )</pre><div class="para">
+ The directives are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <code class="literal">@</code> symbol places the <code class="command">$ORIGIN</code> directive (or the zone's name if the <code class="command">$ORIGIN</code> directive is not set) as the namespace being defined by this <code class="command">SOA</code> resource record.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>primary-name-server</code></em> directive is the hostname of the primary nameserver that is authoritative for this domain.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>hostmaster-email</code></em> directive is the email of the person to contact about the namespace.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>serial-number</code></em> directive is a numerical value incremented every time the zone file is altered to indicate it is time for the <code class="systemitem">named</code> service to reload the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-refresh</code></em> directive is the numerical value secondary nameservers use to determine how long to wait before asking the primary nameserver if any changes have been made to the zone.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>time-to-retry</code></em> directive is a numerical value used by secondary nameservers to determine the length of time to wait before issuing a refresh request in the event that the primary nameserver is not answering. If the primary server has not replied to a refresh request before the amount of time specified in the <em class="replaceable"><code>time-to-expire</code></em> directive elapses, the secondary servers stop responding as an authority for requests concerning that namespace.
+ </div></li><li class="listitem"><div class="para">
+ In BIND 4 and 8, the <em class="replaceable"><code>minimum-TTL</code></em> directive is the amount of time other nameservers cache the zone's information. In BIND 9, it defines how long negative answers are cached for. Caching of negative answers can be set to a maximum of 3 hours (that is, <code class="option">3H</code>).
+ </div></li></ul></div><div class="para">
+ When configuring BIND, all times are specified in seconds. However, it is possible to use abbreviations when specifying units of time other than seconds, such as minutes (<code class="literal">M</code>), hours (<code class="literal">H</code>), days (<code class="literal">D</code>), and weeks (<code class="literal">W</code>). <a class="xref" href="s3-bind-zone-rr.html#tb-bind-seconds" title="Table 10.6. Seconds compared to other time units">Table 10.6, “Seconds compared to other time units”</a> shows an amount of time in seconds and the equivalent time in another format.
+ </div><div class="table" title="Table 10.6. Seconds compared to other time units" id="tb-bind-seconds"><h6>Table 10.6. Seconds compared to other time units</h6><div class="table-contents"><table summary="Seconds compared to other time units" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th>
+ Seconds
+ </th><th>
+ Other Time Units
+ </th></tr></thead><tbody><tr><td>
+ 60
+ </td><td>
+ <code class="literal">1M</code>
+ </td></tr><tr><td>
+ 1800
+ </td><td>
+ <code class="literal">30M</code>
+ </td></tr><tr><td>
+ 3600
+ </td><td>
+ <code class="literal">1H</code>
+ </td></tr><tr><td>
+ 10800
+ </td><td>
+ <code class="literal">3H</code>
+ </td></tr><tr><td>
+ 21600
+ </td><td>
+ <code class="literal">6H</code>
+ </td></tr><tr><td>
+ 43200
+ </td><td>
+ <code class="literal">12H</code>
+ </td></tr><tr><td>
+ 86400
+ </td><td>
+ <code class="literal">1D</code>
+ </td></tr><tr><td>
+ 259200
+ </td><td>
+ <code class="literal">3D</code>
+ </td></tr><tr><td>
+ 604800
+ </td><td>
+ <code class="literal">1W</code>
+ </td></tr><tr><td>
+ 31536000
+ </td><td>
+ <code class="literal">365D</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" title="Example 10.14. Using the SOA resource record" id="example-bind-zone-rr-soa"><h6>Example 10.14. Using the <code class="command">SOA</code> resource record</h6><div class="example-contents"><pre class="screen">@ IN SOA dns1.example.com. hostmaster.example.com. (
+ 2001062501 ; serial
+ 21600 ; refresh after 6 hours
+ 3600 ; retry after 1 hour
+ 604800 ; expire after 1 week
+ 86400 ) ; minimum TTL of 1 day</pre></div></div><br class="example-break" /></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-bind-zone.html"><strong>Prev</strong>10.3. Editing Zone Files</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-bind-zone-comm.html"><strong>Next</strong>10.3.3. Comment Tags</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Additional_Resources.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Additional_Resources.html
new file mode 100644
index 0000000..049486b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Additional_Resources.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.5. Additional Resources</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-yum.html" title="Chapter 1. Yum" /><link rel="prev" href="sec-Plugin_Descriptions.html" title="1.4.3. Plugin Descriptions" /><link rel="next" href="ch-PackageKit.html" title="Chapter 2. PackageKit" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Plugin_Descriptions.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-PackageKit.html">
<strong>Next</strong></a></li></ul><div class="section" title="1.5. Additional Resources" id="sec-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Additional_Resources">1.5. Additional Resources</h2></div></div></div><a id="id521189" class="indexterm"></a><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> The <span class="application"><strong>Yum</strong></span> home page and wiki — <a href="http://yum.baseurl.org/wiki/Guides">http://yum.baseurl.org/wiki/Guides</a> </span></dt><dd><div class="para">
+ The <code class="literal">Yum Guides</code> section of the wiki contains more <span class="application"><strong>Yum</strong></span> documentation.
+ </div></dd><dt class="varlistentry"><span class="term"> Managing Software with <span class="application"><strong>Yum</strong></span> — <a href="http://docs.fedoraproject.org/en-US/Fedora_Core/5/html-single/Software_Management_Guide/">http://docs.fedoraproject.org/en-US/Fedora_Core/5/html-single/Software_Management_Guide/</a> </span></dt><dd><div class="para">
+ A useful resource that provides additional information about using the <span class="application"><strong>Yum</strong></span> package manager.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Plugin_Descriptions.html"><strong>Prev</strong>1.4.3. Plugin Descriptions</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-PackageKit.html"><strong>Next</strong>Chapter 2. PackageKit</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuration_File_Changes.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuration_File_Changes.html
new file mode 100644
index 0000000..d19e56c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuration_File_Changes.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.3. Configuration File Changes</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-rpm-using.html" title="3.2. Using RPM" /><link rel="prev" href="sec-Installing_and_Upgrading.html" title="3.2.2. Installing and Upgrading" /><link rel="next" href="s2-rpm-uninstalling.html" title="3.2.4. Uninstalling" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_and_Upgrading.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hre
f="s2-rpm-uninstalling.html"><strong>Next</strong></a></li></ul><div class="section" title="3.2.3. Configuration File Changes" id="sec-Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuration_File_Changes">3.2.3. Configuration File Changes</h3></div></div></div><a id="id774199" class="indexterm"></a><a id="id774211" class="indexterm"></a><div class="para">
+ Because RPM performs intelligent upgrading of packages with configuration files
+ <a id="id555879" class="indexterm"></a>
+ , you may see one or the other of the following messages:
+ </div><pre class="screen">saving /etc/foo.conf as /etc/foo.conf.rpmsave</pre><div class="para">
+ This message means that changes you made to the configuration file may not be <span class="emphasis"><em>forward-compatible</em></span> with the new configuration file in the package, so RPM saved your original file and installed a new one. You should investigate the differences between the two configuration files and resolve them as soon as possible, to ensure that your system continues to function properly.
+ </div><div class="para">
+ Alternatively, RPM may save the package's <span class="emphasis"><em>new</em></span> configuration file as, for example, <code class="filename">foo.conf.rpmnew</code>, and leave the configuration file you modified untouched. You should still resolve any conflicts between your modified configuration file and the new one, usually by merging changes from the old one to the new one with a <code class="command">diff</code> program.
+ </div><div class="para">
+ If you attempt to upgrade to a package with an <span class="emphasis"><em>older</em></span> version number (that is, if a higher version of the package is already installed), the output is similar to the following:
+ </div><pre class="screen">package foo-2.0-1.fc14.x86_64.rpm (which is newer than foo-1.0-1) is already installed</pre><div class="para">
+ To force RPM to upgrade anyway, use the <code class="command">--oldpackage</code> option:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --oldpackage foo-1.0-1.fc14.x86_64.rpm</code>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_and_Upgrading.html"><strong>Prev</strong>3.2.2. Installing and Upgrading</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-uninstalling.html"><strong>Next</strong>3.2.4. Uninstalling</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuring_Connection_Settings.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuring_Connection_Settings.html
new file mode 100644
index 0000000..dac7488
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuring_Connection_Settings.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.3. Configuring Connection Settings</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Network_Configuration.html" title="Chapter 5. Network Configuration" /><link rel="prev" href="sec-User_and_System_Connections.html" title="5.2.4. User and System Connections" /><link rel="next" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Us
er_and_System_Connections.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html"><strong>Next</strong></a></li></ul><div class="section" title="5.3. Configuring Connection Settings" id="sec-Configuring_Connection_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Configuring_Connection_Settings">5.3. Configuring Connection Settings</h2></div></div></div><div class="section" title="5.3.1. Configuring IPv4 Settings" id="sec-Configuring_IPv4_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_IPv4_Settings">5.3.1. Configuring IPv4 Settings</h3></div></div></div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-IPv4_Settings.png" align="middle" /><div class="caption"><div class="para">
+ Editing the IPv4 Settings Tab
+ </div></div></div><div class="para">
+ The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab allows you to configure the method by which you connect to the Internet and enter IP address, route, and DNS information as required. The <span class="guilabel"><strong>IPv4 Settings</strong></span> tab is available when you create and modify one of the following connection types: wired, wireless, mobile broadband, VPN or DSL.
+ </div><div class="para">
+ If you are using DHCP to obtain a dynamic IP address from a DHCP server, you can simply set <span class="guilabel"><strong>Method</strong></span> to <span class="guimenuitem"><strong>Automatic (DHCP)</strong></span>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-User_and_System_Connections.html"><strong>Prev</strong>5.2.4. User and System Connections</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html"><strong>Next</strong>Chapter 6. Dynamic Host Configuration Protocol (D...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuring_New_and_Editing_Existing_Connections.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuring_New_and_Editing_Existing_Connections.html
new file mode 100644
index 0000000..56d8596
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuring_New_and_Editing_Existing_Connections.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2.2. Configuring New and Editing Existing Connections</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Interacting_with_NetworkManager.html" title="5.2. Interacting with NetworkManager" /><link rel="prev" href="sec-Interacting_with_NetworkManager.html" title="5.2. Interacting with NetworkManager" /><link rel="next" href="sec-Connecting_to_a_Network_Automatically.html" title="5.2.3. Connecting to a Network Automatically" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href
="sec-Interacting_with_NetworkManager.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Connecting_to_a_Network_Automatically.html"><strong>Next</strong></a></li></ul><div class="section" title="5.2.2. Configuring New and Editing Existing Connections" id="sec-Configuring_New_and_Editing_Existing_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Configuring_New_and_Editing_Existing_Connections">5.2.2. Configuring New and Editing Existing Connections</h3></div></div></div><div class="para">
+ Next, right-click on the <span class="application"><strong>NetworkManager</strong></span> applet to open its context menu, which is the main point of entry for interacting with <span class="application"><strong>NetworkManager</strong></span> to configure connections.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-right-click_menu.png" align="middle" /><div class="caption"><div class="para">
+ The NetworkManager applet's context menu
+ </div></div></div><div class="para">
+ Ensure that the <span class="guilabel"><strong>Enable Networking</strong></span> box is checked. if the system has detected a wireless card, then you will also see an <span class="guilabel"><strong>Enable Wireless</strong></span> menu option. Check the <span class="guilabel"><strong>Enable Wireless</strong></span> checkbox as well. <span class="application"><strong>NetworkManager</strong></span> notifies you of network connection status changes if you check the <span class="guilabel"><strong>Enable Notifications</strong></span> box. Clicking the <span class="guilabel"><strong>Connection Information</strong></span> entry presents an informative <span class="guilabel"><strong>Connection Information</strong></span> window that lists the connection type and interface, your IP address and routing details, and so on. Useful network information is thus always two clicks away.
+ </div><div class="para">
+ Finally, clicking on <span class="guilabel"><strong>Edit Connections</strong></span> opens the <span class="guilabel"><strong>Network Connections</strong></span> window, from where you can perform most of your network configuration tasks. Note that this window can also be opened by running, as a normal user:
+ </div><pre class="screen">~]$ <code class="command">nm-connection-editor &</code>
+</pre><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Network_Connections.png" align="middle" width="444" /><div class="caption"><div class="para">
+ Configure networks using the Network Connections window
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Interacting_with_NetworkManager.html"><strong>Prev</strong>5.2. Interacting with NetworkManager</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Connecting_to_a_Network_Automatically.html"><strong>Next</strong>5.2.3. Connecting to a Network Automatically</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.html
new file mode 100644
index 0000000..12be472
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Configuring_Yum_and_Yum_Repositories.html
@@ -0,0 +1,112 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3. Configuring Yum and Yum Repositories</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-yum.html" title="Chapter 1. Yum" /><link rel="prev" href="sec-Removing.html" title="1.2.3. Removing" /><link rel="next" href="sec-Setting_repository_Options.html" title="1.3.2. Setting [repository] Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Removing.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Setting_repository_
Options.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3. Configuring Yum and Yum Repositories" id="sec-Configuring_Yum_and_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Configuring_Yum_and_Yum_Repositories">1.3. Configuring Yum and Yum Repositories</h2></div></div></div><a id="id584512" class="indexterm"></a><a id="id584524" class="indexterm"></a><div class="para">
+ This section shows you how to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ set global <span class="application"><strong>Yum</strong></span> options by editing the <code class="literal">[main]</code> section of the <code class="filename">/etc/yum.conf</code> configuration file;
+ </div></li><li class="listitem"><div class="para">
+ set options for individual repositories by editing the [<em class="replaceable"><code>repository</code></em>] sections in <code class="filename">/etc/yum.conf</code> and <em class="replaceable"><code>.repo</code></em> files in the <code class="filename">/etc/yum.repos.d/</code> directory;
+ </div></li><li class="listitem"><div class="para">
+ use <span class="application"><strong>Yum</strong></span> variables in <code class="filename">/etc/yum.conf</code> and files in <code class="filename">/etc/yum.repos.d/</code>so that dynamic version and architecture values are handled correctly; and,
+ </div></li><li class="listitem"><div class="para">
+ set up your own custom <span class="application"><strong>Yum</strong></span> repository.
+ </div></li></ul></div><div class="para">
+ The <code class="filename">/etc/yum.conf</code> configuration file contains one mandatory <code class="literal">[main]</code> section under which you can set <span class="application"><strong>Yum</strong></span> options. The values that you define in the <code class="literal">[main]</code> section of <code class="filename">yum.conf</code> have global effect, and may override values set any individual [<em class="replaceable"><code>repository</code></em>] sections. You can also add [<em class="replaceable"><code>repository</code></em>] sections to <code class="filename">/etc/yum.conf</code>; however, best practice is to define individual repositories in new or existing <code class="filename">.repo</code> files in the <code class="filename">/etc/yum.repos.d/</code>directory. Refer to <a class="xref" href="sec-Setting_repository_Options.html" title="1.3.2. Setting [repository] Options">Section 1.3.2, “Setting [repository] Options”</a> if you need to add or edit reposit
ory-specific information.
+ </div><div class="section" title="1.3.1. Setting [main] Options" id="sec-Setting_main_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Setting_main_Options">1.3.1. Setting [main] Options</h3></div></div></div><a id="id696557" class="indexterm"></a><div class="para">
+ The <code class="filename">/etc/yum.conf</code> configuration file contains exactly one <code class="literal">[main]</code> section. You can add many additional options under the <code class="literal">[main]</code> section heading in <code class="filename">/etc/yum.conf</code>. Some of the key-value pairs in the <code class="literal">[main]</code> section affect how <code class="command">yum</code> operates; others affect how <span class="application"><strong>Yum</strong></span> treats repositories. The best source of information for all <span class="application"><strong>Yum</strong></span> options is in the <code class="literal">[main] OPTIONS</code> and <code class="literal">[repository] OPTIONS</code> sections of <code class="command">man yum.conf</code>.
+ </div><div class="para">
+ Here is a sample <code class="filename">/etc/yum.conf</code> configuration file:
+ </div><pre class="screen">
+[main]
+cachedir=/var/cache/yum/$basearch/$releasever
+keepcache=0
+debuglevel=2
+logfile=/var/log/yum.log
+exactarch=1
+obsoletes=1
+gpgcheck=1
+plugins=1
+installonly_limit=3
+<em class="lineannotation"><span class="lineannotation">[comments abridged]</span></em>
+# PUT YOUR REPOS HERE OR IN separate files named file.repo
+# in /etc/yum.repos.d
+</pre><div class="para">
+ Here is a list of the most commonly-used options in the <code class="literal">[main]</code> section, and descriptions for each:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">assumeyes=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — <code class="command">yum</code> should prompt for confirmation of critical actions it performs. This is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — Do not prompt for confirmation of critical <code class="command">yum</code> actions. If <code class="literal">assumeyes=1</code> is set, <code class="command">yum</code> behaves in the same way that the command line option <code class="option">-y</code> does.
+ </div></dd><dt class="varlistentry"><span class="term">cachedir=<code class="filename">/var/cache/yum/$basearch/$releasever</code> </span></dt><dd><div class="para">
+ This option specifies the directory where <span class="application"><strong>Yum</strong></span> should store its cache and database files. By default, <span class="application"><strong>Yum</strong></span>'s cache directory is <code class="filename">/var/cache/yum/$basearch/$releasever</code>. See <a class="xref" href="sec-Using_Yum_Variables.html" title="1.3.3. Using Yum Variables">Section 1.3.3, “Using Yum Variables”</a> for descriptions of the <code class="envar">$basearch</code> and <code class="envar">$releasever</code> <span class="application"><strong>Yum</strong></span> variables.
+ </div></dd><dt class="varlistentry"><span class="term">debuglevel=<em class="replaceable"><code>value</code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is an integer between <code class="constant">1</code> and <code class="constant">10</code>. Setting a higher <code class="literal">debuglevel</code> value causes <code class="command">yum</code> to display more detailed debugging output. <code class="literal">debuglevel=0</code> disables debugging output, while <code class="literal">debuglevel=2</code> is the default.
+ </div></dd><dt class="varlistentry"><span class="term">exactarch=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Do not take into account the exact architecture when updating packages.
+ </div><div class="para">
+ <code class="constant">1</code> — Consider the exact architecture when updating packages. With this setting, <code class="command">yum</code> will not install an i686 package to update an i386 package already installed on the system. This is the default.
+ </div></dd><dt class="varlistentry"><span class="term">exclude=<em class="replaceable"><code><package_name></code></em> [<span class="optional"><em class="replaceable"><code>more_package_names</code></em> </span>] </span></dt><dd><div class="para">
+ This option allows you to exclude packages by keyword during installation/updates. Listing multiple packages for exclusion can be accomplished by quoting a space-delimited list of packages. Shell globs using wildcards (for example, <code class="literal">*</code> and <code class="literal">?</code>) are allowed.
+ </div></dd><dt class="varlistentry"><span class="term">gpgcheck=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable GPG signature-checking on packages in all repositories, including local package installation.
+ </div><div class="para">
+ <code class="constant">1</code> — Enable GPG signature-checking on all packages in all repositories, including local package installation. <code class="literal">gpgcheck=1</code> is the default, and thus all packages' signatures are checked.
+ </div><div class="para">
+ If this option is set in the <code class="literal">[main]</code> section of the <code class="filename">/etc/yum.conf</code> file, it sets the GPG-checking rule for all repositories. However, you can also set <code class="literal">gpgcheck=</code> <em class="replaceable"><code><value></code></em> for individual repositories instead; i.e., you can enable GPG-checking on one repository while disabling it on another. Setting <code class="literal">gpgcheck=<em class="replaceable"><code><value></code></em> </code> for an individual repository in its correpsonding <code class="filename">.repo</code> file overrides the default if it is present in <code class="filename">/etc/yum.conf</code>. Refer to <a class="xref" href="s1-check-rpm-sig.html" title="3.3. Checking a Package's Signature">Section 3.3, “Checking a Package's Signature”</a> for further information on GPG signature-checking.
+ </div></dd><dt class="varlistentry"><span class="term">groupremove_leaf_only=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — <code class="command">yum</code> should <span class="emphasis"><em>not</em></span> check the dependencies of each package when removing a package group. With this setting, <code class="command">yum</code> removes all packages in a package group, regardless of whether those packages are required by other packages or groups. <code class="literal">groupremove_leaf_only=0</code> is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — <code class="command">yum</code> should check the dependencies of each package when removing a package group, and remove only those packages which are not not required by any other package or group.
+ </div><div class="para">
+ For more information on removing packages, refer to <a class="xref" href="sec-Removing.html#important-Smart_package_group_removal" title="Smart package group removal">Smart package group removal</a>.
+ </div></dd><dt class="varlistentry"><span class="term">installonlypkgs=<em class="replaceable"><code><space></code></em> <em class="replaceable"><code><separated></code></em> <em class="replaceable"><code><list></code></em> <em class="replaceable"><code><of></code></em> <em class="replaceable"><code><packages></code></em> </span></dt><dd><div class="para">
+ Here you can provide a space-separated list of packages which <code class="command">yum</code> can <span class="emphasis"><em>install</em></span>, but will never <span class="emphasis"><em>update</em></span>. Refer to <code class="command">man yum.conf</code> for the list of packages which are install-only by default. If you add the <code class="literal">installonlypkgs</code> directive to <code class="filename">/etc/yum.conf</code>, you should ensure that you list <span class="emphasis"><em>all</em></span> of the packages that should be install-only, including any of those listed under the <code class="literal">installonlypkgs</code> section of <code class="command">man yum.conf</code>. In particular, kernel packages should always be listed in <code class="literal">installonlypkgs</code> (as they are by default), and <code class="literal">installonly_limit</code> should always be set to a value greater than <code class="constant">2</code> so that a backup kernel is a
lways available in case the default one fails to boot. Refer to <a class="xref" href="sec-Configuring_Yum_and_Yum_Repositories.html#varentry-installonly_limit_value">installonly_limit=<em class="replaceable"><code><value></code></em> </a> for details on the <code class="literal">installonly_limit</code> directive.
+ </div></dd><dt class="varlistentry" id="varentry-installonly_limit_value"><span class="term">installonly_limit=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is an integer representing the maximum number of versions that can be installed simultaneously for any single package listed in the <code class="literal">installonlypkgs</code> directive. The defaults for the <code class="literal">installonlypkgs</code> directive include several different kernel packages, so be aware that changing the value of <code class="literal">installonly_limit</code> will also affect the maximum number of installed versions of any single kernel package. The default value listed in <code class="filename">/etc/yum.conf</code> is <code class="literal">installonly_limit=3</code>, and it is not recommended to decrease this value, particularly below <code class="constant">2</code>.
+ </div></dd><dt class="varlistentry"><span class="term">keepcache=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where value is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Do not retain the cache of headers and packages after a successful installation. This is the default.
+ </div><div class="para">
+ <code class="constant">1</code> — Retain the cache after a successful installation.
+ </div></dd><dt class="varlistentry"><span class="term">logfile=<code class="filename">/var/log/yum.log</code> </span></dt><dd><div class="para">
+ This option specifies where <code class="command">yum</code> should send its logging output. By default, <code class="command">yum</code> logs to <code class="filename">/var/log/yum.log</code>.
+ </div></dd><dt class="varlistentry"><span class="term">multilib_policy=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <strong class="userinput"><code>best</code></strong> — install the best-choice architecture for this system. For example, setting <code class="literal">multilib_policy=best</code> on an AMD64 system causes <code class="command">yum</code> to install 64-bit versions of all packages.
+ </div><div class="para">
+ <strong class="userinput"><code>all</code></strong> — always install every possible architecture for every package. For example, with <code class="literal">multilib_policy</code> set to <code class="literal">all</code> on an AMD64 system, <code class="command">yum</code> would install both the i586 and AMD64 versions of a package, if both were available.
+ </div></dd><dt class="varlistentry"><span class="term">obsoletes=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable <code class="command">yum</code>'s obsoletes processing logic when performing updates.
+ </div><div class="para">
+ <code class="constant">1</code> — Enable <code class="command">yum</code>'s obsoletes processing logic when performing updates. When one package declares in its spec file that it <em class="firstterm">obsoletes</em> another package, the latter package will be replaced by the former package when the former package is installed. Obsoletes are declared, for example, when a package is renamed. <code class="literal">obsoletes=1</code> the default.
+ </div></dd><dt class="varlistentry"><span class="term">plugins=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — Disable all <span class="application"><strong>Yum</strong></span> plugins globally.
+ </div><div class="important" title="Disabling plugins is not advised" id="important-Disabling_plugins_is_not_advised-main_options"><div class="admonition_header"><h2>Disabling plugins is not advised</h2></div><div class="admonition"><div class="para">
+ Disabling all plugins is not advised because certain plugins provide important <code class="command">Yum</code> services. In particular, <span class="application"><strong>rhnplugin</strong></span> enables connecting to <code class="systemitem">Red Hat Network</code>, and the security plugin allows system administrators to easily update the system with (sometimes critical) security updates. Disabling plugins globally is provided as a convenience option, and is generally only recommended when diagnosing a potential problem with <code class="command">Yum</code>.
+ </div></div></div><div class="para">
+ <code class="constant">1</code> — Enable all <span class="application"><strong>Yum</strong></span> plugins globally. With <code class="literal">plugins=1</code>, you can still disable a specific <span class="application"><strong>Yum</strong></span> plugin by setting <code class="literal">enabled=0</code> in that plugin's configuration file. Refer to <a class="xref" href="sec-Yum_Plugins.html" title="1.4. Yum Plugins">Section 1.4, “Yum Plugins”</a> for more information about various <span class="application"><strong>Yum</strong></span> plugins, or to <a class="xref" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins" title="1.4.1. Enabling, Configuring and Disabling Yum Plugins">Section 1.4.1, “Enabling, Configuring and Disabling Yum Plugins”</a> for further information on controlling plugins.
+ </div></dd><dt class="varlistentry"><span class="term">reposdir=<em class="replaceable"><code></absolute/path/to/directory/containing/repo/files></code></em> </span></dt><dd><div class="para">
+ This option allows you to specify a directory where <code class="filename">.repo</code> files are located. All <code class="filename">.repo</code> files contain repository information (similar to the [<em class="replaceable"><code>repository</code></em>] section(s) of <code class="filename">/etc/yum.conf</code>). <code class="command">yum</code> collects all repository information from <code class="filename">.repo</code> files and the [<em class="replaceable"><code>repository</code></em>] section of the <code class="filename">/etc/yum.conf</code> file to create a master list of repositories to use for transactions. Refer to <a class="xref" href="sec-Setting_repository_Options.html" title="1.3.2. Setting [repository] Options">Section 1.3.2, “Setting [repository] Options”</a> for more information about options you can use for both the [<em class="replaceable"><code>repository</code></em>] section and <code class="filename">.repo</code> files. If <code class="liter
al">reposdir</code> is not set, <code class="command">yum</code> uses the default directory <code class="filename">/etc/yum.repos.d/</code>.
+ </div></dd><dt class="varlistentry"><span class="term">retries=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is an integer <code class="constant">0</code> or greater. This value sets the number of times <code class="command">yum</code> should attempt to retrieve a file before returning an error. Setting this to <code class="constant">0</code> makes <code class="command">yum</code> retry forever. The default value is <code class="constant">10</code>.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Removing.html"><strong>Prev</strong>1.2.3. Removing</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Setting_repository_Options.html"><strong>Next</strong>1.3.2. Setting [repository] Options</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Connecting_to_a_Network_Automatically.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Connecting_to_a_Network_Automatically.html
new file mode 100644
index 0000000..31a5de6
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Connecting_to_a_Network_Automatically.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2.3. Connecting to a Network Automatically</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Interacting_with_NetworkManager.html" title="5.2. Interacting with NetworkManager" /><link rel="prev" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="5.2.2. Configuring New and Editing Existing Connections" /><link rel="next" href="sec-User_and_System_Connections.html" title="5.2.4. User and System Connections" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a ac
cesskey="p" href="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-User_and_System_Connections.html"><strong>Next</strong></a></li></ul><div class="section" title="5.2.3. Connecting to a Network Automatically" id="sec-Connecting_to_a_Network_Automatically"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Connecting_to_a_Network_Automatically">5.2.3. Connecting to a Network Automatically</h3></div></div></div><div class="para">
+ For any connection type you add or configure, you can choose whether you want <span class="application"><strong>NetworkManager</strong></span> to try to connect to that network automatically when it is available.
+ </div><div class="procedure" title="Procedure 5.1. Configuring NetworkManager to Connect to a Network Automatically When Detected" id="procedure-Configuring_NetworkManager_to_Connect_to_a_Network_Automatically_When_Detected"><h6>Procedure 5.1. Configuring NetworkManager to Connect to a Network Automatically When Detected</h6><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Right-click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area and click <span class="guilabel"><strong>Edit Connections</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> window appears.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Select the tab for the type of network connection you want to configure.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Select the specific connection that you want to configure and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ Check <span class="guilabel"><strong>Connect automatically</strong></span> to cause <span class="application"><strong>NetworkManager</strong></span> to auto-connect to the connection whenever <span class="application"><strong>NetworkManager</strong></span> detects that it is available. Uncheck the checkbox if you do not want <span class="application"><strong>NetworkManager</strong></span> to connect automatically. If the box is unchecked, you will have to select that connection manually in the <span class="application"><strong>NetworkManager</strong></span> applet's left-click menu to cause it to connect.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>Prev</strong>5.2.2. Configuring New and Editing Existing Conne...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-User_and_System_Connections.html"><strong>Next</strong>5.2.4. User and System Connections</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Creating_a_Yum_Repository.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Creating_a_Yum_Repository.html
new file mode 100644
index 0000000..990430e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Creating_a_Yum_Repository.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.4. Creating a Yum Repository</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="1.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Using_Yum_Variables.html" title="1.3.3. Using Yum Variables" /><link rel="next" href="sec-Yum_Plugins.html" title="1.4. Yum Plugins" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Yum_Variables.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="sec-Yum_Plugins.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.4. Creating a Yum Repository" id="sec-Creating_a_Yum_Repository"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Creating_a_Yum_Repository">1.3.4. Creating a Yum Repository</h3></div></div></div><a id="id454826" class="indexterm"></a><div class="para">
+ To set up a <span class="application"><strong>Yum</strong></span> repository, follow these steps:
+ </div><div class="procedure" title="Procedure 1.1. Setting Up a Yum repository" id="procedure-Setting_Up_a_Yum_repository"><h6>Procedure 1.1. Setting Up a <span class="application"><strong>Yum</strong></span> repository</h6><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Install the <code class="filename">createrepo</code> package:
+ </div><pre class="screen">~]# <code class="command">yum install createrepo</code>
+</pre></li><li class="step" title="Step 2"><div class="para">
+ Copy all of the packages into one directory, such as <code class="filename">/mnt/local_repo/</code>.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Run the <code class="command">createrepo --database</code> command on that directory:
+ </div><pre class="screen">~]# <code class="command">createrepo --database /mnt/local_repo</code>
+</pre><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Because RPM packages for Fedora 14 are compressed using the XZ lossless data compression format, and may also be signed using alternative (and stronger) hash algorithms such as SHA-256, it is not possible to run <code class="command">createrepo</code> on Fedora 5 to create the package metadata for Fedora 14 packages. The <code class="command">createrepo</code> command relies on <code class="command">rpm</code> to open and inspect the packages, and <code class="command">rpm</code> on Fedora 5 is not able to open the improved Fedora 14 RPM package format.
+ </div></div></div></li></ol></div><div class="para">
+ This will create the necessary metadata for your <span class="application"><strong>Yum</strong></span> repository, as well as the <span class="application"><strong>sqlite</strong></span> database for speeding up <code class="command">yum</code> operations.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Yum_Variables.html"><strong>Prev</strong>1.3.3. Using Yum Variables</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Yum_Plugins.html"><strong>Next</strong>1.4. Yum Plugins</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Displaying_Information_About_a_Module.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Displaying_Information_About_a_Module.html
new file mode 100644
index 0000000..ec80088
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Displaying_Information_About_a_Module.html
@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.2. Displaying Information About a Module</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="next" href="sec-Loading_a_Module.html" title="22.3. Loading a Module" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Working_with_Kernel_Modules.html"><stron
g>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Loading_a_Module.html"><strong>Next</strong></a></li></ul><div class="section" title="22.2. Displaying Information About a Module" id="sec-Displaying_Information_About_a_Module"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</h2></div></div></div><a id="id792340" class="indexterm"></a><a id="id792356" class="indexterm"></a><a id="id792376" class="indexterm"></a><div class="para">
+ You can display detailed information about a kernel module by running the <code class="command">modinfo <em class="replaceable"><code><module_name></code></em> </code> command.
+ </div><div class="note" title="Module names do not end in .ko" id="note-Module_names_do_not_end_in_.ko"><div class="admonition_header"><h2>Module names do not end in .ko</h2></div><div class="admonition"><div class="para">
+ When entering the name of a kernel module as an argument to one of the <span class="package">module-init-tools</span> utilities, do not append a <code class="filename">.ko</code> extension to the end of the name. Kernel module names do not have extensions: their corresponding files do.
+ </div></div></div><div class="para">
+ For example, to display information about the <code class="systemitem">e1000e</code> module, which is the Intel PRO/1000 network driver, run:
+ </div><div class="example" title="Example 22.1. Listing information about a kernel module with lsmod" id="ex-Listing_information_about_a_kernel_module_with_lsmod"><h6>Example 22.1. Listing information about a kernel module with lsmod</h6><div class="example-contents"><pre class="screen">~]# <code class="command">modinfo e1000e</code>
+filename: /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/net/e1000e/e1000e.ko
+version: 1.2.7-k2
+license: GPL
+description: Intel(R) PRO/1000 Network Driver
+author: Intel Corporation, <linux.nics at intel.com>
+srcversion: 93CB73D3995B501872B2982
+alias: pci:v00008086d00001503sv*sd*bc*sc*i*
+alias: pci:v00008086d00001502sv*sd*bc*sc*i*
+<em class="lineannotation"><span class="lineannotation">[some <code class="literal">alias</code> lines omitted]</span></em>
+alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
+depends:
+vermagic: 2.6.32-71.el6.x86_64 SMP mod_unload modversions
+parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
+parm: TxIntDelay:Transmit Interrupt Delay (array of int)
+parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
+parm: RxIntDelay:Receive Interrupt Delay (array of int)
+parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
+parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
+parm: IntMode:Interrupt Mode (array of int)
+parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
+parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
+parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to corrupted NVM] (array of int)
+parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)
+parm: EEE:Enable/disable on parts that support the feature (array of int)</pre></div></div><br class="example-break" /><div class="variablelist"><div class="para">
+ Here are descriptions of a few of the fields in <code class="command">modinfo</code> output:
+ </div><dl><dt class="varlistentry"><span class="term">filename</span></dt><dd><div class="para">
+ The absolute path to the <code class="filename">.ko</code> kernel object file. You can use <code class="command">modinfo -n</code> as a shorcut command for printing only the <code class="computeroutput">filename</code> field.
+ </div></dd><dt class="varlistentry"><span class="term">description</span></dt><dd><div class="para">
+ A short description of the module. You can use <code class="command">modinfo -d</code> as a shortcut command for printing only the description field.
+ </div></dd><dt class="varlistentry"><span class="term">alias</span></dt><dd><div class="para">
+ The <code class="computeroutput">alias</code> field appears as many times as there are aliases for a module, or is omitted entirely if there are none.
+ </div></dd><dt class="varlistentry"><span class="term">depends</span></dt><dd><div class="para">
+ This field contains a comma-separated list of all the modules this module depends on.
+ </div><div class="note" title="Note" id="note-Omitted_depends_field"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If a module has no dependencies, the <code class="computeroutput">depends</code> field may be omitted from the output.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">parm</span></dt><dd><div class="para">
+ Each <code class="computeroutput">parm</code> field presents one module parameter in the form <code class="computeroutput"><em class="replaceable"><code>parameter_name</code></em>:<em class="replaceable"><code>description</code></em></code>, where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="replaceable"><code>parameter_name</code></em> is the exact syntax you should use when using it as a module parameter on the command line, or in an option line in a <code class="filename">.conf</code> file in the <code class="filename">/etc/modprobe.d/</code> directory; and,
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>description</code></em> is a brief explanation of what the parameter does, along with an expectation for the type of value the parameter accepts (such as <span class="type">int</span>, <span class="type">unit</span> or <span class="type">array of int</span>) in parentheses.
+ </div></li></ul></div><div class="para">
+ You can list all parameters that the module supports by using the <code class="option">-p</code> option. However, because useful value type information is omitted from <code class="command">modinfo -p</code> output, it is more useful to run:
+ </div><pre class="screen">~]# <code class="command">modinfo e1000e |grep "^parm" |sort</code>
+parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
+parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)
+parm: EEE:Enable/disable on parts that support the feature (array of int)
+parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
+parm: IntMode:Interrupt Mode (array of int)
+parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
+parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
+parm: RxIntDelay:Receive Interrupt Delay (array of int)
+parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
+parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
+parm: TxIntDelay:Transmit Interrupt Delay (array of int)
+parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to corrupted NVM] (array of int)</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Working_with_Kernel_Modules.html"><strong>Prev</strong>Chapter 22. Working with Kernel Modules</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Loading_a_Module.html"><strong>Next</strong>22.3. Loading a Module</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Finding_Packages_with_Filters.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Finding_Packages_with_Filters.html
new file mode 100644
index 0000000..1cc744d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Finding_Packages_with_Filters.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.2. Finding Packages with Filters</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Using_Add_Remove_Software.html" title="2.2. Using Add/Remove Software" /><link rel="prev" href="sec-Using_Add_Remove_Software.html" title="2.2. Using Add/Remove Software" /><link rel="next" href="sec-Installing_and_Removing_Packages_and_Dependencies.html" title="2.2.3. Installing and Removing Packages (and Dependencies)" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" hr
ef="sec-Using_Add_Remove_Software.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.2. Finding Packages with Filters" id="sec-Finding_Packages_with_Filters"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Finding_Packages_with_Filters">2.2.2. Finding Packages with Filters</h3></div></div></div><a id="id456632" class="indexterm"></a><div class="para">
+ Once the software sources have been updated, it is often beneficial to apply some filters so that <span class="application"><strong>PackageKit</strong></span> retrieves the results of our <span class="guilabel"><strong>Find</strong></span> queries faster. This is especially helpful when performing many package searches. Four of the filters in the <span class="guimenu"><strong>Filters</strong></span> drop-down menu are used to split results by matching or not matching a single criterion. By default when <span class="application"><strong>PackageKit</strong></span> starts, these filters are all unapplied (<span class="guibutton"><strong>No filter</strong></span>), but once you do filter by one of them, that filter remains set until you either change it or close <span class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Because you are usually searching for available packages that are <span class="emphasis"><em>not</em></span> installed on the system, click <span class="guimenu"><strong>Filters</strong></span> → <span class="guimenuitem"><strong>Installed</strong></span> and select the <span class="guimenuitem"><strong>Only available</strong></span> radio button.
+ <a id="id456693" class="indexterm"></a>
+ <a id="id698300" class="indexterm"></a>
+ <a id="id698311" class="indexterm"></a>
+ <a id="id698327" class="indexterm"></a>
+ <a id="id698343" class="indexterm"></a>
+
+ </div><div class="figure" title="Figure 2.5. Filtering out already-installed packages" id="Graphical_Package_Management-filters-only_available"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-filters-only_available.png" align="middle" width="444" alt="Filtering out already-installed packages" /><div class="longdesc"><div class="para">
+ filtering out packages which are already installed
+ </div></div></div></div><h6>Figure 2.5. Filtering out already-installed packages</h6></div><br class="figure-break" /><div class="para">
+ <a id="id453385" class="indexterm"></a>
+ <a id="id453401" class="indexterm"></a>
+ <a id="id453416" class="indexterm"></a>
+ Also, unless we require development files such as C header files, we can filter for <span class="guimenu"><strong>Only end user files</strong></span> and, in doing so, filter out all of the <code class="filename"><em class="replaceable"><code><package_name></code></em>-devel</code> packages we are not interested in.
+ </div><div class="figure" title="Figure 2.6. Filtering out development packages from the list of Find results" id="fig-Graphical_Package_Management-filters-only_end_user"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-filters-only_end_user.png" align="middle" width="444" alt="Filtering out development packages from the list of Find results" /><div class="longdesc"><div class="para">
+ filtering out development packages from our results
+ </div></div></div></div><h6>Figure 2.6. Filtering out development packages from the list of Find results</h6></div><br class="figure-break" /><div class="para">
+ The two remaining filters with submenus are:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <span class="guisubmenu"><strong>Graphical</strong></span> <a id="id697167" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Narrows the search to either applications which provide a GUI interface or those that do not (<span class="guibutton"><strong>Only text</strong></span>). This filter is useful when browsing for GUI applications that perform a specific function.
+ </div></dd><dt class="varlistentry"><span class="term"> <span class="guisubmenu"><strong>Free</strong></span> <a id="id697207" class="indexterm"></a>
+ </span></dt><dd><div class="para">
+ Search for packages which are considered to be free software Refer to the <a href="https://fedoraproject.org/wiki/Licensing#SoftwareLicenses">Fedora Licensing List</a> for details on approved licenses.
+ </div></dd></dl></div><div class="para">
+ The remaining checkbox filters are always either checked or unchecked. They are:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <span class="guimenuitem"><strong>Hide subpackages</strong></span> </span></dt><dd><div class="para">
+ Checking the <span class="guimenuitem"><strong>Hide subpackages</strong></span> <a id="id849502" class="indexterm"></a>
+ checkbox filters out generally-uninteresting packages that are typically only dependencies of other packages that we want. For example, checking <span class="guimenuitem"><strong>Hide subpackages</strong></span> and searching for <code class="filename"><em class="replaceable"><code><package></code></em> </code> would cause the following related packages to be filtered out of the <span class="guibutton"><strong>Find</strong></span> results (if it exists):
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code><package></code></em>-devel</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code><package></code></em>-libs</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code><package></code></em>-libs-devel</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename"> <em class="replaceable"><code><package></code></em>-debuginfo</code>
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <span class="guimenuitem"><strong>Only newest items</strong></span> </span></dt><dd><div class="para">
+ Checking <span class="guimenuitem"><strong>Only newest items</strong></span> <a id="id841003" class="indexterm"></a>
+ filters out all older versions of the same package from the list of results, which is generally what we want.
+ </div><div class="important" title="Important: Using the Only newest items filter" id="important-Using_the_Only_newest_items_filter"><div class="admonition_header"><h2>Important: Using the Only newest items filter</h2></div><div class="admonition"><div class="para">
+ Checking <span class="guimenuitem"><strong>Only newest items</strong></span> filters out all but the most recent version of any package from the results list. This filter is often combined with the <span class="guimenuitem"><strong>Only available</strong></span> filter to search for the latest available versions of new (not installed) packages.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Only native packages</span></dt><dd><div class="para">
+ Checking the <span class="guimenuitem"><strong>Only native packages</strong></span> <a id="id520248" class="indexterm"></a>
+ box on a multilib system causes <span class="application"><strong>PackageKit</strong></span> to omit listing results for packages compiled for the architecture that runs in <span class="emphasis"><em>compatibility mode</em></span>. For example, enabling this filter on a 64-bit system with an AMD64 CPU would cause all packages built for the 32-bit x86 CPU architecture not to be shown in the list of results, even though those packages are able to run on an AMD64 machine. Packages which are architecture-agnostic (i.e. <em class="firstterm">noarch</em> packages such as <code class="filename">crontabs-1.10-32.1.el6.noarch.rpm</code>) are never filtered out by checking <span class="guimenuitem"><strong>Only native packages</strong></span>. This filter has no affect on non-multilib systems, such as x86 machines.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_Add_Remove_Software.html"><strong>Prev</strong>2.2. Using Add/Remove Software</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>Next</strong>2.2.3. Installing and Removing Packages (and Depe...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing.html
new file mode 100644
index 0000000..6041297
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing.html
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.2. Installing</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="1.2. Packages and Package Groups" /><link rel="prev" href="sec-Packages_and_Package_Groups.html" title="1.2. Packages and Package Groups" /><link rel="next" href="sec-Removing.html" title="1.2.3. Removing" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Packages_and_Package_Groups.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="sec-Removing.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.2. Installing" id="sec-Installing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Installing">1.2.2. Installing</h3></div></div></div><a id="id499834" class="indexterm"></a><a id="id499846" class="indexterm"></a><div class="para">
+ You can install a package and all of its non-installed dependencies by entering:
+ </div><pre class="screen">~]# <code class="command">yum install <em class="replaceable"><code><package_name></code></em> </code>
+</pre><div class="para">
+ You can install multiple packages simultaneously by appending their names as arguments: <code class="command">yum install <em class="replaceable"><code><package_name></code></em> [<span class="optional"><em class="replaceable"><code>more_names</code></em></span>] </code>.
+ </div><div class="para">
+ If you are installing packages on a <em class="firstterm">multilib</em> system, such as an AMD64 or Intel64 machine, you can specify the architecture of the package (as long as it's available in an enabled repository) by appending <em class="replaceable"><code>.arch</code></em> to the package name:
+ </div><pre class="screen">
+~]# <code class="command">yum install sqlite2.i586</code>
+</pre><div class="para">
+ You can use glob expressions to quickly install multiple similarly-named packages:
+ </div><pre class="screen">
+~]# <code class="command">yum install audacious-plugins-\*</code>
+</pre><div class="para">
+ In addition to package names and glob expressions, you can also provide file names to <code class="command">yum install</code>. If you know the name of the binary you want to install, but not its package name, you can give <code class="command">yum install</code> the path name:
+ </div><pre class="screen">~]# <code class="command">yum install /usr/sbin/named</code>
+</pre><div class="para">
+ <code class="command">yum</code> then searches through its package lists, finds the package which provides /usr/sbin/named, if any, and prompts you as to whether you want to install it.
+ </div><div class="para">
+ What if you know you want to install the package that contains the <code class="filename">named</code> binary, but don't know in which bin or sbin directory that file lives? In that situation, you can give <code class="command">yum provides</code> a glob expression:
+ </div><div class="example" title="Example 1.5. Finding which package owns a file and installing it" id="ex-Finding_which_package_owns_a_file_and_installing_it"><h6>Example 1.5. Finding which package owns a file and installing it</h6><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum provides "*bin/named"</code>
+Loaded plugins: presto, refresh-packagekit, security
+32:bind-9.6.1-0.3.b1.fc11.x86_64 : The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) server
+Repo : fedora
+Matched from:
+Filename : /usr/sbin/named
+~]# <code class="command">yum install bind</code>
+</pre></div></div><br class="example-break" /><div class="note" title="Note" id="note-Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ <code class="command">yum provides</code> is the same as <code class="command">yum whatprovides</code>.
+ </div></div></div><div class="note" title="Tip: yum provides/whatprovides and Glob Expressions" id="note-Tip-yum_provides_whatprovides_and_Glob_Expressions"><div class="admonition_header"><h2>Tip: yum provides/whatprovides and Glob Expressions</h2></div><div class="admonition"><div class="para">
+ <code class="command">yum provides "*/<file_name>"</code> is a common and useful trick to quickly find the package(s) that contain <file_name>.
+ </div></div></div><h4>Installing a Package Group</h4><a id="id842511" class="indexterm"></a><a id="id842523" class="indexterm"></a><div class="para">
+ A package group is similar to a package: it is not useful by itself, but installing one pulls a group of dependent packages that serve a common purpose. A package group has a name and a groupid. The <code class="command">yum grouplist -v</code> command lists the names of all package groups, and, next to each of them, their <em class="firstterm">groupid</em> in parentheses. The groupid is always the term in the last pair of parentheses, such as <code class="literal">kde-desktop</code> and <code class="literal">kde-software-development</code> in this example:
+ </div><div class="important" title="Not all packages used in examples may be available on RHN"><div class="admonition_header"><h2>Not all packages used in examples may be available on RHN</h2></div><div class="admonition"><div class="para">
+ Some of the software packages—or package groups—queried for and installed with <span class="application"><strong>Yum</strong></span> in this chapter may not be available from Red Hat Network. Their use in examples is purely to demonstrate <span class="application"><strong>Yum</strong></span>'s command usage.
+ </div><div class="para">
+ Note that obtaining and installing software packages from unverified or untrusted software sources other than Red Hat Network constitutes a potential security risk, and could lead to security, stability, compatibility maintainability issues.
+ </div></div></div><pre class="screen">
+~]# <code class="command">yum -v grouplist kde\*</code>
+KDE (K Desktop Environment) (kde-desktop)
+KDE Software Development (kde-software-development)
+</pre><div class="para">
+ You can install a package group by passing its full group name (without the groupid part) to <code class="command">groupinstall</code>:
+ </div><pre class="screen">
+~]# <code class="command">yum groupinstall "KDE (K Desktop Environment)"</code>
+</pre><div class="para">
+ You can also install by groupid:
+ </div><pre class="screen">
+~]# <code class="command">yum groupinstall kde-desktop</code>
+</pre><div class="para">
+ You can even pass the groupid (or quoted name) to the <code class="command">install</code> command if you prepend it with an <span class="keysym">@</span>-symbol (which tells <code class="command">yum</code> that you want to perform a <code class="command">groupinstall</code>):
+ </div><pre class="screen">
+~]# <code class="command">yum install @kde-desktop</code>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Packages_and_Package_Groups.html"><strong>Prev</strong>1.2. Packages and Package Groups</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Removing.html"><strong>Next</strong>1.2.3. Removing</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_More_Yum_Plugins.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_More_Yum_Plugins.html
new file mode 100644
index 0000000..8e338c3
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_More_Yum_Plugins.html
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.4.2. Installing More Yum Plugins</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Yum_Plugins.html" title="1.4. Yum Plugins" /><link rel="prev" href="sec-Yum_Plugins.html" title="1.4. Yum Plugins" /><link rel="next" href="sec-Plugin_Descriptions.html" title="1.4.3. Plugin Descriptions" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Yum_Plugins.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Plugin_Description
s.html"><strong>Next</strong></a></li></ul><div class="section" title="1.4.2. Installing More Yum Plugins" id="sec-Installing_More_Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Installing_More_Yum_Plugins">1.4.2. Installing More Yum Plugins</h3></div></div></div><div class="para">
+ <span class="application"><strong>Yum</strong></span> plugins usually adhere to the <code class="filename">yum-plugin-<em class="replaceable"><code><plugin_name></code></em> </code> package-naming convention, but not always: the package which provides the <span class="application"><strong>presto</strong></span> plugin is named <code class="filename">yum-presto</code>, for example. You can install a <span class="application"><strong>Yum</strong></span> plugin in the same way you install other packages:
+ </div><pre class="screen">
+~]# <code class="command">yum install yum-plugin-security</code>
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Yum_Plugins.html"><strong>Prev</strong>1.4. Yum Plugins</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Plugin_Descriptions.html"><strong>Next</strong>1.4.3. Plugin Descriptions</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_and_Removing_Package_Groups.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_and_Removing_Package_Groups.html
new file mode 100644
index 0000000..6c61411
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_and_Removing_Package_Groups.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.4. Installing and Removing Package Groups</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Using_Add_Remove_Software.html" title="2.2. Using Add/Remove Software" /><link rel="prev" href="sec-Installing_and_Removing_Packages_and_Dependencies.html" title="2.2.3. Installing and Removing Packages (and Dependencies)" /><link rel="next" href="sec-Viewing_the_Transaction_Log.html" title="2.2.5. Viewing the Transaction Log" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey=
"p" href="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Viewing_the_Transaction_Log.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.4. Installing and Removing Package Groups" id="sec-Installing_and_Removing_Package_Groups"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Installing_and_Removing_Package_Groups">2.2.4. Installing and Removing Package Groups</h3></div></div></div><a id="id837535" class="indexterm"></a><a id="id837547" class="indexterm"></a><a id="id837559" class="indexterm"></a><a id="id837570" class="indexterm"></a><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> also has the ability to install <span class="application"><strong>Yum</strong></span> package groups, which it calls <span class="guilabel"><strong>Package collections</strong></span>. Clicking on <span class="guilabel"><strong>Package collections</strong></span> in the top-left list of categories in the <span class="guilabel"><strong>Software Updates</strong></span> window allows us to scroll through and find the package group we want to install. In this case, we want to install Czech language support (the <span class="guilabel"><strong>Czech Support</strong></span> group). Checking the box and clicking <span class="guibutton"><strong>apply</strong></span> informs us how many <span class="emphasis"><em>additional</em></span> packages must be installed in order to fulfill the dependencies of the package group.
+ </div><div class="figure" title="Figure 2.9. Installing the Czech Support package group" id="fig-Graphical_Package_Management-installing_a_package_group"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-installing_a_package_group.png" align="middle" width="444" alt="Installing the Czech Support package group" /><div class="longdesc"><div class="para">
+ using PackageKit to install czech language support with PackageKit's add/remove software window
+ </div></div></div></div><h6>Figure 2.9. Installing the Czech Support package group</h6></div><br class="figure-break" /><div class="para">
+ Similarly, installed package groups can be uninstalled by selecting <span class="guilabel"><strong>Package collections</strong></span>, unchecking the appropriate checkbox, and applying.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_and_Removing_Packages_and_Dependencies.html"><strong>Prev</strong>2.2.3. Installing and Removing Packages (and Depe...</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Viewing_the_Transaction_Log.html"><strong>Next</strong>2.2.5. Viewing the Transaction Log</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.html
new file mode 100644
index 0000000..fd1475c
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_and_Removing_Packages_and_Dependencies.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.3. Installing and Removing Packages (and Dependencies)</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Using_Add_Remove_Software.html" title="2.2. Using Add/Remove Software" /><link rel="prev" href="sec-Finding_Packages_with_Filters.html" title="2.2.2. Finding Packages with Filters" /><link rel="next" href="sec-Installing_and_Removing_Package_Groups.html" title="2.2.4. Installing and Removing Package Groups" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Findin
g_Packages_with_Filters.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_and_Removing_Package_Groups.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.3. Installing and Removing Packages (and Dependencies)" id="sec-Installing_and_Removing_Packages_and_Dependencies"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Installing_and_Removing_Packages_and_Dependencies">2.2.3. Installing and Removing Packages (and Dependencies)</h3></div></div></div><a id="id520299" class="indexterm"></a><a id="id520311" class="indexterm"></a><div class="para">
+ With the two filters selected, <span class="guibutton"><strong>Only available</strong></span> and <span class="guibutton"><strong>Only end user files</strong></span>, search for the <span class="application"><strong>htop</strong></span> interactive process viewer and highlight the package. You now have access to some very useful information about it, including: a clickable link to the project homepage; the <span class="application"><strong>Yum</strong></span> package group it is found in, if any; the license of the package; a pointer to the GNOME menu location from where the application can be opened, if applicable (<span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>Htop</strong></span> in our case); and the size of the package, which is relevant when we download and install it.
+ </div><div class="figure" title="Figure 2.7. Viewing and installing a package with PackageKit's Add/Remove Software window" id="fig-Graphical_Package_Management-install"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-install.png" align="middle" width="444" alt="Viewing and installing a package with PackageKit's Add/Remove Software window" /><div class="longdesc"><div class="para">
+ Viewing and installing a package with PackageKit's Add/Remove Software window
+ </div></div></div></div><h6>Figure 2.7. Viewing and installing a package with PackageKit's Add/Remove Software window</h6></div><br class="figure-break" /><div class="para">
+ When the checkbox next to a package or group is checked, then that item is already installed on the system. Checking an unchecked box causes it to be <span class="emphasis"><em>marked</em></span> for installation, which only occurs when the <span class="guibutton"><strong>Apply</strong></span> button is clicked. In this way, you can search for and select multiple packages or package groups before performing the actual installation transactions. Additionally, you can remove installed packages by unchecking the checked box, and the removal will occur along with any pending installations when <span class="guibutton"><strong>Apply</strong></span> is pressed. Dependency resolution
+ <a id="id673540" class="indexterm"></a>
+ , which may add additional packages to be installed or removed, is performed after pressing <span class="guibutton"><strong>Apply</strong></span>. <span class="application"><strong>PackageKit</strong></span> will then display a window listing those additional packages to install or remove, and ask for confirmation to proceed.
+ </div><div class="para">
+ Check <span class="application"><strong>htop</strong></span> and click the <span class="guibutton"><strong>Apply</strong></span> button. You will then be prompted for the superuser password; enter it, and <span class="application"><strong>PackageKit</strong></span> will install <span class="application"><strong>htop</strong></span>. One nice feature of <span class="application"><strong>PackageKit</strong></span> is that, following installation, it sometimes presents you with a list of your newly-installed applications and offer you the choice of running them immediately. Alternatively, you will remember that finding a package and selecting it in the <span class="guilabel"><strong>Add/Remove Software</strong></span> window shows you the <span class="guilabel"><strong>Location</strong></span> of where in the GNOME menus its application shortcut is located, which is helpful when you want to run it.
+ </div><div class="para">
+ Once it is installed, you can run <code class="command">htop</code>, an colorful and enhanced version of the <code class="command">top</code> process viewer, by opening a shell prompt and entering:
+ </div><pre class="screen">~]$ <code class="command">htop</code>
+</pre><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-htop.png" align="middle" width="444" /><div class="caption"><div class="para">
+ Viewing processes with <span class="application"><strong>htop</strong></span>!
+ </div></div></div><div class="para">
+ <span class="application"><strong>htop</strong></span> is nifty, but we decide that <code class="command">top</code> is good enough for us and we want to uninstall it. Remembering that we need to change the <span class="guibutton"><strong>Only available</strong></span> filter we recently used to install it to <span class="guibutton"><strong>Only installed</strong></span> in <span class="guimenu"><strong>Filters</strong></span> → <span class="guimenuitem"><strong>Installed</strong></span>, we search for <span class="application"><strong>htop</strong></span> again and uncheck it. The program did not install any dependencies of its own; if it had, those would be automatically removed as well, as long as they were not also dependencies of any other packages still installed on our system.
+ </div><div class="warning" title="Warning: Removing a Package when Other Packages Depend On It" id="warning-PackageKit-Removing_a_Package_Without_Removing_Packages_Depending_on_It"><div class="admonition_header"><h2>Warning: Removing a Package when Other Packages Depend On It</h2></div><div class="admonition"><div class="para">
+ Although <span class="application"><strong>PackageKit</strong></span> automatically resolves dependencies during package installation and removal, it is unable to remove a package without also removing packages which depend on it. This type of operation can only be performed by <span class="application"><strong>RPM</strong></span>, is not advised, and can potentially leave your system in a non-functioning state or cause applications to misbehave and/or crash.
+ </div></div></div><div class="figure" title="Figure 2.8. Removing a package with PackageKit's Add/Remove Software window" id="fig-Graphical_Package_Management-removing_a_package"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-removing_a_package.png" align="middle" width="444" alt="Removing a package with PackageKit's Add/Remove Software window" /><div class="longdesc"><div class="para">
+ removing the htop package with packagekit's add/remove software window
+ </div></div></div></div><h6>Figure 2.8. Removing a package with PackageKit's Add/Remove Software window</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Finding_Packages_with_Filters.html"><strong>Prev</strong>2.2.2. Finding Packages with Filters</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_and_Removing_Package_Groups.html"><strong>Next</strong>2.2.4. Installing and Removing Package Groups</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_and_Upgrading.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_and_Upgrading.html
new file mode 100644
index 0000000..5299335
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Installing_and_Upgrading.html
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>3.2.2. Installing and Upgrading</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="s1-rpm-using.html" title="3.2. Using RPM" /><link rel="prev" href="s1-rpm-using.html" title="3.2. Using RPM" /><link rel="next" href="sec-Configuration_File_Changes.html" title="3.2.3. Configuration File Changes" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-using.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuration_Fil
e_Changes.html"><strong>Next</strong></a></li></ul><div class="section" title="3.2.2. Installing and Upgrading" id="sec-Installing_and_Upgrading"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Installing_and_Upgrading">3.2.2. Installing and Upgrading</h3></div></div></div><a id="id781470" class="indexterm"></a><a id="id781482" class="indexterm"></a><a id="id838441" class="indexterm"></a><a id="id690578" class="indexterm"></a><div class="para">
+ RPM packages typically have file names
+ <a id="id774662" class="indexterm"></a>
+ like <code class="filename">tree-1.5.3-2.fc14.x86_64.rpm</code>. The file name includes the package name (<code class="filename">tree</code>), version (<code class="filename">1.5.3</code>), release (<code class="filename">2</code>), operating system major version (<code class="filename">fc14</code>) and CPU architecture (<code class="filename">x86_64</code>).
+ </div><div class="para">
+ You can use <code class="command">rpm</code>'s <code class="option">-U</code> option to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ upgrade an existing but older package on the system to a newer version, or
+ </div></li><li class="listitem"><div class="para">
+ install the package even if an older version is not already installed.
+ </div></li></ul></div><div class="para">
+ That is, <code class="command">rpm -U <em class="replaceable"><code><rpm_file></code></em> </code> is able to perform the function of either <span class="emphasis"><em>upgrading</em></span> or <span class="emphasis"><em>installing</em></span> as is appropriate for the package.
+ </div><div class="para">
+ Assuming the <code class="filename">tree-1.5.3-2.fc14.x86_64.rpm</code> package is in the current directory, log in as root and type the following command at a shell prompt to either upgrade or install the <span class="package">tree</span> package as determined by <code class="command">rpm</code>:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh tree-1.5.3-2.fc14.x86_64.rpm</code>
+</pre><div class="note" title="Use -Uvh for nicely-formatted RPM installs" id="note-Use_-Uvh_for_nicely-formatted_RPM_installs"><div class="admonition_header"><h2>Use -Uvh for nicely-formatted RPM installs</h2></div><div class="admonition"><div class="para">
+ The <code class="option">-v</code> and <code class="option">-h</code> options (which are combined with <code class="option">-U</code>) cause <span class="application"><strong>rpm</strong></span> to print more verbose output and display a progress meter using hash signs.
+ </div></div></div><div class="para">
+ If the upgrade/installation is successful, the following output is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ 1:tree ########################################### [100%]</pre><div class="warning" title="Always use the -i (install) option to install new kernel packages!" id="warning-Always_use_the_-i_install_option_to_install_new_kernel_packages"><div class="admonition_header"><h2>Always use the -i (install) option to install new kernel packages!</h2></div><div class="admonition"><div class="para">
+ <code class="command">rpm</code> provides two different options for installing packages: the aforementioned <code class="option">-U</code> option (which historically stands for <span class="emphasis"><em>upgrade</em></span>), and the <code class="option">-i</code> option, historically standing for <span class="emphasis"><em>install</em></span>. Because the <code class="option">-U</code> option subsumes both install and upgrade functions, we recommend to use <code class="command">rpm -Uvh</code> with all packages <span class="emphasis"><em>except <span class="package">kernel</span> packages</em></span>.
+ </div><div class="para">
+ You should always use the <code class="option">-i</code> option to simply <span class="emphasis"><em>install</em></span> a new kernel package instead of upgrading it. This is because using the <code class="option">-U</code> option to upgrade a kernel package removes the previous (older) kernel package, which could render the system unable to boot if there is a problem with the new kernel. Therefore, use the <code class="command">rpm -i <em class="replaceable"><code><kernel_package></code></em> </code> command to install a new kernel <span class="emphasis"><em>without replacing any older <span class="package">kernel</span> packages</em></span>. For more information on installing <span class="package">kernel</span> packages, refer to <a class="xref" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 23. Manually Upgrading the Kernel">Chapter 23, <i>Manually Upgrading the Kernel</i></a>.
+ </div></div></div><div class="para">
+ The signature of a package is checked automatically when installing or upgrading a package. The signature confirms that the package was signed by an authorized party. For example, if the verification of the signature fails, an error message such as the following is displayed:
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc14.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD, key ID
+d22e77f2</pre><div class="para">
+ If it is a new, header-only, signature, an error message such as the following is displayed:
+ </div><pre class="screen">error: tree-1.5.2.2-4.fc14.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD,
+key ID d22e77f2</pre><div class="para">
+ If you do not have the appropriate key installed to verify the signature, the message contains the word <code class="computeroutput">NOKEY</code>:
+ </div><pre class="screen">warning: tree-1.5.2.2-4.fc14.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 57bbccba</pre><div class="para">
+ Refer to <a class="xref" href="s1-check-rpm-sig.html" title="3.3. Checking a Package's Signature">Section 3.3, “Checking a Package's Signature”</a> for more information on checking a package's signature.
+ </div><div class="section" title="3.2.2.1. Package Already Installed" id="s3-rpm-errors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-rpm-errors">3.2.2.1. Package Already Installed</h4></div></div></div><div class="para">
+ If a package of the same name and version is already installed
+ <a id="id832453" class="indexterm"></a>
+ <a id="id832465" class="indexterm"></a>
+ , the following output is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ package tree-1.5.3-2.fc14.x86_64 is already installed</pre><div class="para">
+ However, if you want to install the package anyway, you can use the <code class="command">--replacepkgs</code> option, which tells RPM to ignore the error:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --replacepkgs tree-1.5.3-2.fc14.x86_64.rpm</code>
+</pre><div class="para">
+ This option is helpful if files installed from the RPM were deleted or if you want the original configuration files from the RPM to be installed.
+ </div></div><div class="section" title="3.2.2.2. Conflicting Files" id="s3-rpm-conflicting-files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-rpm-conflicting-files">3.2.2.2. Conflicting Files</h4></div></div></div><a id="id455447" class="indexterm"></a><div class="para">
+ If you attempt to install a package that contains a file which has already been installed by another package
+ <a id="id519870" class="indexterm"></a>
+ <a id="id519882" class="indexterm"></a>
+ , the following is displayed:
+ </div><pre class="screen">Preparing... ##################################################
+ file /usr/bin/foobar from install of foo-1.0-1.fc14.x86_64 conflicts
+with file from package bar-3.1.1.fc14.x86_64</pre><div class="para">
+ To make RPM ignore this error, use the <code class="command">--replacefiles</code> option:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh --replacefiles foo-1.0-1.fc14.x86_64.rpm</code>
+</pre></div><div class="section" title="3.2.2.3. Unresolved Dependency" id="s3-rpm-unresolved-dependency"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-rpm-unresolved-dependency">3.2.2.3. Unresolved Dependency</h4></div></div></div><a id="id649415" class="indexterm"></a><a id="id649427" class="indexterm"></a><div class="para">
+ RPM packages may sometimes depend on other packages
+ <a id="id559839" class="indexterm"></a>
+ <a id="id559851" class="indexterm"></a>
+ , which means that they require other packages to be installed to run properly. If you try to install a package which has an unresolved dependency, output similar to the following is displayed:
+ </div><pre class="screen">error: Failed dependencies:
+ bar.so.3()(64bit) is needed by foo-1.0-1.fc14.x86_64</pre><div class="para">
+ If you are installing a package from the Fedora installation media, such as from a CD-ROM or DVD, the dependencies may be available. Find the suggested package(s) on the Fedora installation media or on one of the active Fedora mirrors and add it to the command:
+ </div><pre class="screen">
+<code class="command">rpm -Uvh foo-1.0-1.fc14.x86_64.rpm bar-3.1.1.fc14.x86_64.rpm</code>
+</pre><div class="para">
+ If installation of both packages is successful, output similar to the following is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ 1:foo ########################################### [ 50%]
+ 2:bar ########################################### [100%]</pre><div class="para">
+ You can try the <code class="option">--whatprovides</code> option to determine which package contains the required file.
+ </div><pre class="screen">
+<code class="command">rpm -q --whatprovides "bar.so.3"</code>
+</pre><div class="para">
+ If the package that contains <code class="filename">bar.so.3</code> is in the RPM database, the name of the package is displayed:
+ </div><pre class="screen">bar-3.1.1.fc14.i586.rpm</pre><div class="warning" title="Warning: Forcing Package Installation" id="warning-install-Warning-Forcing_Package_Installation"><div class="admonition_header"><h2>Warning: Forcing Package Installation</h2></div><div class="admonition"><div class="para">
+ Although we can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to install a package that gives us a <code class="computeroutput">Failed dependencies</code> error (using the <code class="option">--nodeps</code> option), this is <span class="emphasis"><em>not</em></span> recommended, and will usually result in the installed package failing to run. Installing or removing packages with <code class="command">rpm --nodeps</code> can cause applications to misbehave and/or crash, and can cause serious package management problems or, possibly, system failure. For these reasons, it is best to heed such warnings; the package manager—whether <span class="application"><strong>RPM</strong></span>, <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span>—shows us these warnings and suggests possible fixes because accounting for dependencies is critical. The <span class="application"><stron
g>Yum</strong></span> package manager can perform dependency resolution and fetch dependencies from online repositories, making it safer, easier and smarter than forcing <code class="command">rpm</code> to carry out actions without regard to resolving dependencies.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-using.html"><strong>Prev</strong>3.2. Using RPM</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuration_File_Changes.html"><strong>Next</strong>3.2.3. Configuration File Changes</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Interacting_with_NetworkManager.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Interacting_with_NetworkManager.html
new file mode 100644
index 0000000..01ca064
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Interacting_with_NetworkManager.html
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2. Interacting with NetworkManager</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Network_Configuration.html" title="Chapter 5. Network Configuration" /><link rel="prev" href="ch-Network_Configuration.html" title="Chapter 5. Network Configuration" /><link rel="next" href="sec-Configuring_New_and_Editing_Existing_Connections.html" title="5.2.2. Configuring New and Editing Existing Connections" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-N
etwork_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>Next</strong></a></li></ul><div class="section" title="5.2. Interacting with NetworkManager" id="sec-Interacting_with_NetworkManager"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Interacting_with_NetworkManager">5.2. Interacting with NetworkManager</h2></div></div></div><div class="para">
+ Users do not interact with the <span class="application"><strong>NetworkManager</strong></span> system service directly. Instead, you can perform network configuration tasks via <span class="application"><strong>NetworkManager</strong></span>'s Notification Area applet. The applet has multiple states that serve as visual indicators for the type of connection you are currently using. Hover the pointer over the applet icon for tooltip information on the current connection state.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-All_applet_states.png" align="middle" /><div class="caption"><div class="para">
+ NetworkManager applet states
+ </div></div></div><div class="para">
+ If you do not see the <span class="application"><strong>NetworkManager</strong></span> applet in the GNOME panel, and assuming that the <span class="application"><strong>NetworkManager</strong></span> package is installed on your system, you can start the applet by running the following command as a normal user (not root):
+ </div><pre class="screen">~]$ <code class="command">nm-applet &</code>
+</pre><div class="para">
+ After running this command, the applet appears in your Notification Area. You can ensure that the applet runs each time you log in by clicking <span class="guimenu"><strong>System</strong></span> → <span class="guisubmenu"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Startup Applications</strong></span> to open the <span class="guilabel"><strong>Startup Applications Preferences</strong></span> window. Then, select the <span class="guilabel"><strong>Startup Programs</strong></span> tab and check the box next to <span class="application"><strong>NetworkManager</strong></span>.
+ </div><div class="section" title="5.2.1. Connecting to a Network" id="sec-Connecting_to_a_Network"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Connecting_to_a_Network">5.2.1. Connecting to a Network</h3></div></div></div><div class="para">
+ When you left-click on the applet icon, you are presented with:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ a list of categorized networks you are currently connected to (such as <span class="guilabel"><strong>Wired</strong></span> and <span class="guilabel"><strong>Wireless</strong></span>);
+ </div></li><li class="listitem"><div class="para">
+ a list of all <span class="guilabel"><strong>Available Networks</strong></span> <span class="application"><strong>NetworkManager</strong></span> has detected;
+ </div></li><li class="listitem"><div class="para">
+ options for connecting to any configured Virtual Private Networks (VPNs); and,
+ </div></li><li class="listitem"><div class="para">
+ options for connecting to hidden or new wireless networks.
+ </div></li></ul></div><div class="para">
+ When many networks are available (as when there are many wireless access points in the area), the <span class="guilabel"><strong>More networks</strong></span> expandable menu entry appears. If you are connected to a network, its name is presented in bold typeface under its network type, such as <span class="guilabel"><strong>Wired</strong></span> or <span class="guilabel"><strong>Wireless</strong></span>.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-left-click_menu.png" align="middle" /><div class="caption"><div class="para">
+ The <span class="application"><strong>NetworkManager</strong></span> applet's left-click menu, showing all available and connected-to networks
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Network_Configuration.html"><strong>Prev</strong>Chapter 5. Network Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_New_and_Editing_Existing_Connections.html"><strong>Next</strong>5.2.2. Configuring New and Editing Existing Conne...</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Loading_a_Module.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Loading_a_Module.html
new file mode 100644
index 0000000..5e13936
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Loading_a_Module.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.3. Loading a Module</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Displaying_Information_About_a_Module.html" title="22.2. Displaying Information About a Module" /><link rel="next" href="sec-Unloading_a_Module.html" title="22.4. Unloading a Module" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Displaying_Informatio
n_About_a_Module.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Unloading_a_Module.html"><strong>Next</strong></a></li></ul><div class="section" title="22.3. Loading a Module" id="sec-Loading_a_Module"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Loading_a_Module">22.3. Loading a Module</h2></div></div></div><a id="id1770623" class="indexterm"></a><a id="id1770639" class="indexterm"></a><a id="id763579" class="indexterm"></a><div class="para">
+ To load a kernel module, run <code class="command">modprobe <em class="replaceable"><code><module_name></code></em> </code> as root. For example, to load the <code class="systemitem">wacom</code> module, run:
+ </div><pre class="screen">~]# <code class="command">modprobe wacom</code>
+</pre><a id="id763620" class="indexterm"></a><div class="para">
+ By default, <code class="command">modprobe</code> attempts to load the module from <code class="filename">/lib/modules/<em class="replaceable"><code><kernel_version></code></em>/kernel/drivers/</code>. In this directory, each type of module has its own subdirectory, such as <code class="filename">net/</code> and <code class="filename">scsi/</code>, for network and SCSI interface drivers respectively.
+ </div><div class="para">
+ Some modules have dependencies, which are other kernel modules that must be loaded before the module in question can be loaded. The <code class="command">modprobe</code> command always takes dependencies into account when performing operations. When you ask <code class="command">modprobe</code> to load a specific kernel module, it first examines the dependencies of that module, if there are any, and loads them if they are not already loaded into the kernel. <code class="command">modprobe</code> resolves dependencies recursively: it will load all dependencies of dependencies, and so on, if necessary, thus ensuring that all dependencies are always met.
+ </div><div class="para">
+ You can use the <code class="option">-v</code> (i.e. <code class="option">--verbose</code>) option to cause <code class="command">modprobe</code> to display detailed information about what it is doing, which may include loading module dependencies. Here's an example of loading the <code class="systemitem">Fibre Channel over Ethernet</code> module verbosely:
+ </div><div class="example" title="Example 22.2. modprobe -v shows module dependencies as they are loaded" id="ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded"><h6>Example 22.2. modprobe -v shows module dependencies as they are loaded</h6><div class="example-contents"><pre class="screen">~]# <code class="command">modprobe -v fcoe</code>
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_tgt.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/libfc/libfc.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko
+insmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</pre></div></div><br class="example-break" /><div class="para">
+ <a class="xref" href="sec-Loading_a_Module.html#ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded" title="Example 22.2. modprobe -v shows module dependencies as they are loaded">Example 22.2, “modprobe -v shows module dependencies as they are loaded”</a> shows that <code class="command">modprobe</code> loaded the <code class="systemitem">scsi_tgt</code>, <code class="systemitem">scsi_transport_fc</code>, <code class="systemitem">libfc</code> and <code class="systemitem">libfcoe</code> modules as dependencies before finally loading <code class="systemitem">fcoe</code>. Also note that <code class="command">modprobe</code> used the more <span class="quote">“<span class="quote">primitive</span>”</span> <code class="command">insmod</code> command to insert the modules into the running kernel.
+ </div><a id="id763790" class="indexterm"></a><a id="id763810" class="indexterm"></a><div class="important" title="Always use modprobe instead of insmod!" id="important-Always_use_modprobe_instead_of_insmod"><div class="admonition_header"><h2>Always use modprobe instead of insmod!</h2></div><div class="admonition"><div class="para">
+ Although the <code class="command">insmod</code> command can also be used to load kernel modules, it does not resolve dependencies. Because of this, you should <span class="emphasis"><em>always</em></span> load modules using <code class="command">modprobe</code> instead.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Displaying_Information_About_a_Module.html"><strong>Prev</strong>22.2. Displaying Information About a Module</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Unloading_a_Module.html"><strong>Next</strong>22.4. Unloading a Module</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-PackageKit_Architecture.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-PackageKit_Architecture.html
new file mode 100644
index 0000000..72588b5
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-PackageKit_Architecture.html
@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.3. PackageKit Architecture</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-PackageKit.html" title="Chapter 2. PackageKit" /><link rel="prev" href="sec-Viewing_the_Transaction_Log.html" title="2.2.5. Viewing the Transaction Log" /><link rel="next" href="ch-Graphical_Package_Management-sec-Additional_Resources.html" title="2.4. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Viewing_the_Transaction_Log.html"><stron
g>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Graphical_Package_Management-sec-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="2.3. PackageKit Architecture" id="sec-PackageKit_Architecture"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-PackageKit_Architecture">2.3. PackageKit Architecture</h2></div></div></div><a id="id741167" class="indexterm"></a><div class="para">
+ Red Hat provides the <span class="application"><strong>PackageKit</strong></span> suite of applications for viewing, updating, installing and uninstalling packages and package groups compatible with your system. Architecturally, <span class="application"><strong>PackageKit</strong></span> consists of several graphical front ends that communicate with the <code class="command">packagekitd</code> daemon back end, which communicates with a package manager-specific back end that utilizes <span class="application"><strong>Yum</strong></span> to perform the actual transactions, such as installing and removing packages, etc.
+ </div><div class="para">
+ <a class="xref" href="sec-PackageKit_Architecture.html#table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands" title="Table 2.1. PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands">Table 2.1, “PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands”</a> shows the name of the GUI window, how to start the window from the GNOME desktop or from the <span class="guilabel"><strong>Add/Remove Software</strong></span> window, and the name of the command line application that opens that window.
+ </div><div class="table" title="Table 2.1. PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands" id="table-PackageKit_GUI_Windows_Menu_Locations_and_Shell_Prompt_Commands"><h6>Table 2.1. PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands</h6><div class="table-contents"><table summary="PackageKit GUI Windows, Menu Locations, and Shell Prompt Commands" border="1"><colgroup><col align="left" width="25%" /><col align="left" width="25%" /><col align="left" width="25%" /><col align="left" width="25%" /></colgroup><thead><tr><th align="left">
+ Window Title
+ </th><th align="left">
+ Function
+ </th><th align="left">
+ How to Open
+ </th><th align="left">
+ Shell Command
+ </th></tr></thead><tbody><tr><td align="left">
+ Add/Remove Software
+ </td><td align="left">
+ Install, remove or view package info
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Add/Remove Software</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-application
+ </td></tr><tr><td align="left">
+ Software Update
+ </td><td align="left">
+ Perform package updates
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Software Update</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-update-viewer
+ </td></tr><tr><td align="left">
+ Software Sources
+ </td><td align="left">
+ Enable and disable <span class="application"><strong>Yum</strong></span> repositories
+ </td><td align="left">
+ <div class="para">
+ From <span class="guilabel"><strong>Add/Remove Software</strong></span>: <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Software sources</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-repo
+ </td></tr><tr><td align="left">
+ Software Log Viewer
+ </td><td align="left">
+ View the transaction log
+ </td><td align="left">
+ <div class="para">
+ From <span class="guilabel"><strong>Add/Remove Software</strong></span>: <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Software log</strong></span>
+ </div>
+
+ </td><td align="left">
+ gpk-log
+ </td></tr><tr><td align="left">
+ Software Update Preferences
+ </td><td align="left">
+ Set <span class="application"><strong>PackageKit</strong></span> preferences
+ </td><td align="left">
+ </td><td align="left">
+ gpk-prefs
+ </td></tr><tr><td align="left">
+ (Notification Area Alert)
+ </td><td align="left">
+ Alerts you when updates are available
+ </td><td align="left">
+ <div class="para">
+ From the GNOME panel: <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Preferences</strong></span> → <span class="guimenuitem"><strong>Startup Applications</strong></span>, <span class="guilabel"><strong>Startup Programs</strong></span> tab
+ </div>
+
+ </td><td align="left">
+ gpk-update-icon
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The <code class="command">packagekitd</code> daemon runs outside the user session and communicates with the various graphical front ends. The <code class="command">packagekitd</code> daemon<sup>[<a id="footnote-Daemons" href="#ftn.footnote-Daemons" class="footnote">2</a>]</sup> communicates via the <span class="application"><strong>DBus</strong></span> system message bus with another back end, which utilizes <span class="application"><strong>Yum</strong></span>'s Python API to perform queries and make changes to the sytem. On Linux systems other than Red Hat and Fedora, <code class="command">packagekitd</code> can communicate with other back ends that are able to utilize the native package manager for that system. This modular architecture provides the abstraction necessary for the graphical interfaces to work with many different package managers to perform essentially the same types of package management tasks. Learning how to use the <span class="application"><strong>Pa
ckageKit</strong></span> front ends means that you can use the same familiar graphical interface across many different Linux distributions, even when they utilize a native package manager other than <span class="application"><strong>Yum</strong></span>.
+ </div><div class="para">
+ In addition, <span class="application"><strong>PackageKit</strong></span>'s separation of concerns provides reliability in that a crash of one of the GUI windows—or even the user's X Window session—will not affect any package management tasks being supervised by the <code class="command">packagekitd</code> daemon, which runs outside of the user session.
+ </div><div class="para">
+ All of the front end graphical applications discussed in this chapter are provided by the <code class="filename">gnome-packagekit</code> package instead of by <span class="application"><strong>PackageKit</strong></span> and its dependencies. Users working in a KDE environment may prefer to install the <code class="filename">kpackagekit</code> package, which provides a KDE interface for <span class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Finally, <span class="application"><strong>PackageKit</strong></span> also comes with a console-based frontend called <code class="command">pkcon</code>.
+ </div><div class="footnotes"><br /><hr /><div class="footnote" id="footnote-Daemons"><p><sup>[<a id="ftn.footnote-Daemons" href="#footnote-Daemons" class="para">2</a>] </sup>
+ System daemons are typically long-running processes that provide services to the user or to other programs, and which are started, often at boot time, by special initialization scripts (often shortened to <span class="emphasis"><em>init scripts</em></span>). Daemons respond to the <code class="command">service</code> command and can be turned on or off permanently by using the <code class="command">chkconfig on</code> or <code class="command">chkconfig off</code>commands. They can typically be recognized by a <span class="quote">“<span class="quote"><span class="emphasis"><em>d</em></span> </span>”</span> appended to their name, such as the <code class="command">packagekitd</code> daemon. Refer to <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a> for information about system services.
+ </p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Viewing_the_Transaction_Log.html"><strong>Prev</strong>2.2.5. Viewing the Transaction Log</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Graphical_Package_Management-sec-Additional_Resources.html"><strong>Next</strong>2.4. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Packages_and_Package_Groups.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Packages_and_Package_Groups.html
new file mode 100644
index 0000000..2737198
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Packages_and_Package_Groups.html
@@ -0,0 +1,133 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2. Packages and Package Groups</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-yum.html" title="Chapter 1. Yum" /><link rel="prev" href="ch-yum.html" title="Chapter 1. Yum" /><link rel="next" href="sec-Installing.html" title="1.2.2. Installing" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-yum.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing.html"><strong>Next</strong></a></li></ul><div class="s
ection" title="1.2. Packages and Package Groups" id="sec-Packages_and_Package_Groups"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Packages_and_Package_Groups">1.2. Packages and Package Groups</h2></div></div></div><a id="id853372" class="indexterm"></a><a id="id853384" class="indexterm"></a><div class="section" title="1.2.1. Searching, Listing and Displaying Package Information" id="sec-Searching_Listing_and_Displaying_Package_Information"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Searching_Listing_and_Displaying_Package_Information">1.2.1. Searching, Listing and Displaying Package Information</h3></div></div></div><a id="id853406" class="indexterm"></a><a id="id853417" class="indexterm"></a><a id="id853429" class="indexterm"></a><a id="id853441" class="indexterm"></a><a id="id853453" class="indexterm"></a><a id="id495282" class="indexterm"></a><div class="para">
+ You can search all <span class="application"><strong>RPM</strong></span> package names, descriptions and summaries by using the <code class="command">yum search <em class="replaceable"><code><term></code></em> [<span class="optional"><em class="replaceable"><code>more_terms</code></em></span>] </code> command. <code class="command">yum</code> displays the list of matches for each term:
+ </div><pre class="screen">
+~]# <code class="command">yum search meld kompare</code>
+Loaded plugins: presto, refresh-packagekit, security
+=============================== Matched: kompare ===============================
+kdesdk.x86_64 : The KDE Software Development Kit (SDK)
+komparator.x86_64 : Kompare and merge two folders
+================================ Matched: meld =================================
+meld.noarch : Visual diff and merge tool
+python-meld3.x86_64 : An HTML/XML templating system for Python
+</pre><div class="para">
+ <a id="id495333" class="indexterm"></a>
+ <a id="id495349" class="indexterm"></a>
+ <code class="command">yum search</code> is useful for searching for packages you do not know the name of, but for which you know a related term.
+ </div><h4>Listing Packages</h4><div class="para">
+ <a id="id842134" class="indexterm"></a>
+ <a id="id842150" class="indexterm"></a>
+ <code class="command">yum list</code> and related commands provide information about packages, package groups, and repositories.
+ </div><div class="note" title="Tip: Filtering Results with Glob Expressions" id="note-Tip-Filtering_Results_with_Glob_Expressions"><div class="admonition_header"><h2>Tip: Filtering Results with Glob Expressions</h2></div><div class="admonition"><a id="id842178" class="indexterm"></a><a id="id842194" class="indexterm"></a><div class="para">
+ All of <span class="application"><strong>Yum</strong></span>'s various list commands allow you to filter the results by appending one or more <span class="emphasis"><em>glob expressions</em></span> as arguments. Glob expressions are normal strings of characters which contain one or more of the wildcard characters <code class="command">*</code> (which expands to match any character multiple times) and <code class="command">?</code> (which expands to match any one character). Be careful to escape both of these glob characters when passing them as arguments to a <code class="command">yum</code> command. If you do not, the bash shell will interpret the glob expressions as <span class="emphasis"><em>pathname expansions</em></span>, and potentially pass all files in the current directory that match the globs to <code class="command">yum</code>, which is not what you want. Instead, you want to pass the glob expressions themselves to <code class="command">yum</code>, which you
can do by either:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ escaping the wildcard characters
+ </div></li><li class="listitem"><div class="para">
+ double-quoting or single-quoting the entire glob expression.
+ </div></li></ul></div><div class="para">
+ The following examples show both methods:
+ </div><div class="example" title="Example 1.2. Filtering results using a single glob expression with two escaped wildcard characters" id="ex-Filtering_results_using_a_single_glob_expression_with_two_escaped_wildcards"><h6>Example 1.2. Filtering results using a single glob expression with two escaped wildcard characters</h6><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum list available gimp\*plugin\*</code>
+Loaded plugins: presto, refresh-packagekit, security
+Available Packages
+gimp-fourier-plugin.x86_64 0.3.2-3.fc11 fedora
+gimp-lqr-plugin.x86_64 0.6.1-2.fc11 updates
+</pre></div></div><br class="example-break" /><div class="example" title="Example 1.3. Filtering results using a double-quoted glob expression" id="ex-Filtering_results_using_a_double-quoted_glob_expression"><h6>Example 1.3. Filtering results using a double-quoted glob expression</h6><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum list installed "krb?-*"</code>
+Loaded plugins: presto, refresh-packagekit, security
+Installed Packages
+krb5-auth-dialog.x86_64 0.12-2.fc12 @fedora
+krb5-libs.x86_64 1.7-8.fc12 @fedora
+krb5-workstation.x86_64 1.7-8.fc12 @fedora
+</pre></div></div><br class="example-break" /></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yum list <em class="replaceable"><code><glob_expr></code></em> [<span class="optional"><em class="replaceable"><code>more_glob_exprs</code></em></span>] </code> — List information on installed and available packages matching all glob expressions.
+ </div><div class="example" title="Example 1.4. Listing all ABRT addons and plugins using glob expressions" id="ex-Listing_all_ABRT_addons_and_plugins_using_glob_expressions"><h6>Example 1.4. Listing all ABRT addons and plugins using glob expressions</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum list abrt-addon\* abrt-plugin\*</code>
+Loaded plugins: presto, refresh-packagekit, security
+Installed Packages
+abrt-addon-ccpp.x86_64 0.0.9-2.fc12 @fedora
+abrt-addon-kerneloops.x86_64 0.0.9-2.fc12 @fedora
+abrt-addon-python.x86_64 0.0.9-2.fc12 @fedora
+abrt-plugin-bugzilla.x86_64 0.0.9-2.fc12 @fedora
+abrt-plugin-kerneloopsreporter.x86_64 0.0.9-2.fc12 @fedora
+abrt-plugin-sqlite3.x86_64 0.0.9-2.fc12 @fedora
+Available Packages
+abrt-plugin-filetransfer.x86_64 0.0.9-2.fc12 fedora
+abrt-plugin-logger.x86_64 0.0.9-2.fc12 fedora
+abrt-plugin-mailx.x86_64 0.0.9-2.fc12 fedora
+abrt-plugin-runapp.x86_64 0.0.9-2.fc12 fedora
+abrt-plugin-sosreport.x86_64 0.0.9-2.fc12 fedora
+abrt-plugin-ticketuploader.x86_64 0.0.9-2.fc12 fedora</pre></div></div><br class="example-break" /></li></ul></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">yum list all</code> —
+ <a id="id821580" class="indexterm"></a>
+ <a id="id821596" class="indexterm"></a>
+ List all installed <span class="emphasis"><em>and</em></span> available packages.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum list installed</code> —
+ <a id="id461986" class="indexterm"></a>
+ <a id="id462001" class="indexterm"></a>
+ List all packages installed on your system. The rightmost column in the output lists the repository from which the package was retrieved.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum list available</code> —
+ <a id="id462030" class="indexterm"></a>
+ <a id="id462046" class="indexterm"></a>
+ List all available packages in all enabled repositories.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum grouplist</code> —
+ <a id="id462074" class="indexterm"></a>
+ <a id="id798683" class="indexterm"></a>
+ List all package groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">yum repolist</code> —
+ <a id="id798710" class="indexterm"></a>
+ <a id="id798726" class="indexterm"></a>
+ List the repository ID, name, and number of packages it provides for each <span class="emphasis"><em>enabled</em></span> repository.
+ </div></li></ul></div><h4>Displaying Package Info</h4><div class="para">
+ <code class="command">yum info <em class="replaceable"><code><package_name></code></em> [<span class="optional"><em class="replaceable"><code>more_names</code></em></span>] </code> <a id="id521644" class="indexterm"></a>
+ <a id="id521660" class="indexterm"></a>
+ displays information about one or more packages (glob expressions are valid here as well):
+ </div><pre class="screen">
+~]# <code class="command">yum info abrt</code>
+Loaded plugins: presto, refresh-packagekit, security
+Installed Packages
+Name : abrt
+Arch : x86_64
+Version : 0.0.9
+Release : 2.fc12
+Size : 525 k
+Repo : installed
+From repo : fedora
+Summary : Automatic bug detection and reporting tool
+URL : https://fedorahosted.org/abrt/
+License : GPLv2+
+Description: abrt is a tool to help users to detect defects in applications and
+ : to create bug reports that include all information required by the
+ : maintainer to hopefully resolve it. It uses a plugin system to extend
+ : its functionality.
+</pre><div class="para">
+ <a id="id521692" class="indexterm"></a>
+ <a id="id521708" class="indexterm"></a>
+ <code class="command">yum info <em class="replaceable"><code><package_name></code></em> </code> is similar to the <code class="command">rpm -q --info <em class="replaceable"><code><package_name></code></em> </code> command, but provides as additional information the ID of the <span class="application"><strong>Yum</strong></span> repository the RPM package is found in (look for the <span class="emphasis"><em>From repo:</em></span> line in the output).
+ </div><div class="para">
+ <code class="command">yumdb info <em class="replaceable"><code><package_name></code></em> [<span class="optional"><em class="replaceable"><code>more_names</code></em></span>] </code> can be used to query the <span class="application"><strong>Yum</strong></span> database for alternative and useful information about a package, including the checksum of the package (and algorithm used to produce it, such as SHA-256), the command given on the command line that was invoked to install the package (if any), and the reason that the package is installed on the system (where <code class="computeroutput">user</code> indicates it was installed by the user, and <code class="computeroutput">dep</code> means it was brought in as a dependency):
+ </div><pre class="screen">~]# <code class="command">yumdb info yum</code>
+yum-3.2.27-3.fc12.noarch
+ checksum_data = 8d7773ec28c954c69c053ea4bf61dec9fdea11a59c50a2c31d1aa2e24bc611d9
+ checksum_type = sha256
+ command_line = update
+ from_repo = updates
+ from_repo_revision = 1272392716
+ from_repo_timestamp = 1272414297
+ reason = user
+ releasever = 12</pre><div class="para">
+ See <code class="command">man yumdb</code> for more information on the <code class="command">yumdb</code> command.
+ </div><div class="para">
+ Finally, the <code class="command">yum history</code> command, which is new in Fedora 14, can be used to show a timeline of <span class="application"><strong>Yum</strong></span> transactions, the dates and times on when they occurred, the number of packages affected, whether transactions succeeded or were aborted, and if the RPM database was changed between transactions. Refer to the <code class="computeroutput">history</code> section of <code class="command">man yum</code> for details.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-yum.html"><strong>Prev</strong>Chapter 1. Yum</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing.html"><strong>Next</strong>1.2.2. Installing</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Persistent_Module_Loading.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Persistent_Module_Loading.html
new file mode 100644
index 0000000..49e94f2
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Persistent_Module_Loading.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.6. Persistent Module Loading</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Setting_Module_Parameters.html" title="22.5. Setting Module Parameters" /><link rel="next" href="sec-Specific_Kernel_Module_Capabilities.html" title="22.7. Specific Kernel Module Capabilities" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_Mod
ule_Parameters.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Specific_Kernel_Module_Capabilities.html"><strong>Next</strong></a></li></ul><div class="section" title="22.6. Persistent Module Loading" id="sec-Persistent_Module_Loading"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Persistent_Module_Loading">22.6. Persistent Module Loading</h2></div></div></div><a id="id843732" class="indexterm"></a><a id="id843748" class="indexterm"></a><div class="para">
+ As shown in <a class="xref" href="sec-Displaying_Information_About_a_Module.html#ex-Listing_information_about_a_kernel_module_with_lsmod" title="Example 22.1. Listing information about a kernel module with lsmod">Example 22.1, “Listing information about a kernel module with lsmod”</a>, many kernel modules are loaded automatically at boot time. You can specify additional modules to be loaded by creating a new <code class="filename"><em class="replaceable"><code><file_name></code></em>.modules</code> file in the <code class="filename">/etc/sysconfig/modules/</code> directory, where <em class="replaceable"><code><file_name></code></em> is any descriptive name of your choice. Your <code class="filename"><em class="replaceable"><code><file_name></code></em>.modules</code> files are treated by the system startup scripts as shell scripts, and as such should begin with an <em class="firstterm">interpreter directive</em> (also called a <span class="quote">
“<span class="quote">bang line</span>”</span>) as their first line:
+ </div><div class="example" title="Example 22.4. First line of a file_name.modules file" id="ex-First_line_of_a_file_name.modules_file"><h6>Example 22.4. First line of a <em class="replaceable"><code>file_name</code></em>.modules file</h6><div class="example-contents"><pre class="screen">#!/bin/sh</pre></div></div><br class="example-break" /><div class="para">
+ Additionally, the <code class="filename"><em class="replaceable"><code><file_name></code></em>.modules</code> file should be executable. You can make it executable by running:
+ </div><pre class="screen">modules]# <code class="command">chmod +x <em class="replaceable"><code><file_name></code></em>.modules</code>
+</pre><div class="para">
+ For example, the following <code class="filename">bluez-uinput.modules</code> script loads the <code class="systemitem">uinput</code> module:
+ </div><div class="example" title="Example 22.5. /etc/sysconfig/modules/bluez-uinput.modules" id="ex-bluez-uinput.modules"><h6>Example 22.5. /etc/sysconfig/modules/bluez-uinput.modules</h6><div class="example-contents"><pre class="programlisting"><span class="perl_Comment">#!/bin/sh</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+<span class="perl_Keyword">if</span><span class="perl_Reserved"> [</span> ! -c /dev/input/uinput<span class="perl_Reserved"> ]</span> ; <span class="perl_Keyword">then</span>
+ <span class="perl_Reserved">exec</span> /sbin/modprobe uinput <span class="perl_Operator">></span>/dev/null <span class="perl_Operator">2>&1</span>
+<span class="perl_Keyword">fi</span></pre><div class="para">
+ The <code class="literal">if</code>-conditional statement on the third line ensures that the <code class="filename">/dev/input/uinput</code> file does <span class="emphasis"><em>not</em></span> already exist (the <code class="literal">!</code> symbol negates the condition), and, if that is the case, loads the <code class="systemitem">uinput</code> module by calling <code class="command">exec /sbin/modprobe uinput</code>. Note that the <code class="systemitem">uinput</code> module creates the <code class="filename">/dev/input/uinput</code> file, so testing to see if that file exists serves as verification of whether the <code class="systemitem">uinput</code> module is loaded into the kernel.
+ </div><div class="para">
+ The following <code class="command">>/dev/null 2>&1</code> clause at the end of that line simply redirects any output to <code class="filename">/dev/null</code> so that the <code class="command">modprobe</code> command remains quiet.
+ </div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_Module_Parameters.html"><strong>Prev</strong>22.5. Setting Module Parameters</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Specific_Kernel_Module_Capabilities.html"><strong>Next</strong>22.7. Specific Kernel Module Capabilities</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Plugin_Descriptions.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Plugin_Descriptions.html
new file mode 100644
index 0000000..0a7b207
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Plugin_Descriptions.html
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.4.3. Plugin Descriptions</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Yum_Plugins.html" title="1.4. Yum Plugins" /><link rel="prev" href="sec-Installing_More_Yum_Plugins.html" title="1.4.2. Installing More Yum Plugins" /><link rel="next" href="sec-Additional_Resources.html" title="1.5. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_More_Yum_Plugins.html"><strong>Prev</strong></a></li><li class="n
ext"><a accesskey="n" href="sec-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" title="1.4.3. Plugin Descriptions" id="sec-Plugin_Descriptions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Plugin_Descriptions">1.4.3. Plugin Descriptions</h3></div></div></div><div class="para">
+ Here are descriptions of a few useful <span class="application"><strong>Yum</strong></span> plugins:
+ </div><h4>presto (yum-presto)</h4><a id="id585715" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>presto</strong></span> plugin adds support to <span class="application"><strong>Yum</strong></span> for downloading <em class="firstterm">delta RPM</em> packages, during updates, from repositories which have <span class="application"><strong>presto</strong></span> metadata enabled. Delta RPMs contain only the differences between the version of the package installed on the client requesting the RPM package and the updated version in the repository. Downloading a delta RPM is much quicker than downloading the entire updated package, and can speed up updates considerably. Once the delta RPMs are downloaded, they must be rebuilt (the difference applied to the currently-installed package to create the full updated package) on the installing machine, which takes CPU time. Using delta RPMs is therefore a tradeoff between time-to-download, which depends on the network connection, and time-to-rebuild, which is CPU-bound. Using the <span class
="application"><strong>presto</strong></span> plugin is recommended for fast machines and systems with slower network connections, while slower machines on very fast connections <span class="emphasis"><em>may</em></span> benefit more from downloading normal RPM packages, i.e. by disabling <span class="application"><strong>presto</strong></span>. The <span class="application"><strong>presto</strong></span> plugin is enabled by default.
+ </div><h4>protect-packages (yum-plugin-protect-packages)</h4><a id="id498069" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>protect-packages</strong></span> plugin prevents the <code class="filename">yum</code> package and all packages it depends on from being purposefully or accidentally removed. This simple scheme prevents many of the most important packages necessary for your system to run from being removed. In addition, you can list more packages, one per line, in the <code class="filename">/etc/sysconfig/protected-packages</code> file<sup>[<a id="footnote-Alternative_Locations_for_protect-packages_Lists" href="#ftn.footnote-Alternative_Locations_for_protect-packages_Lists" class="footnote">1</a>]</sup> (which you should create if it does not exist), and <span class="application"><strong>protect-packages</strong></span> will extend protection-from-removal to those packages as well. To temporarily override package protection, use the <code class="option">--override-protection</code> option with an applicable <code class="command">yum</code> command.
+ </div><h4>rhnplugin (yum-rhn-plugin)</h4><a id="id709300" class="indexterm"></a><a id="id709316" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>rhnplugin</strong></span> for <span class="application"><strong>Yum</strong></span> provides support for connecting to <code class="systemitem">Red Hat Network</code> (RHN). Systems registered with <code class="systemitem">RHN</code> are able to update and install packages from <code class="systemitem">Red Hat Network</code>.
+ </div><div class="para">
+ Refer to <code class="command">man rhnplugin</code> for more information.
+ </div><h4>refresh-packagekit (PackageKit-yum-plugin)</h4><a id="id709381" class="indexterm"></a><div class="para">
+ This plugin updates metadata for <span class="application"><strong>PackageKit</strong></span> whenever <span class="application"><strong>yum</strong></span> is run. The <span class="application"><strong>refresh-packagekit</strong></span> plugin is installed by default.
+ </div><h4>security (yum-plugin-security)</h4><a id="id477795" class="indexterm"></a><div class="para">
+ Discovering information about and applying security updates easily and often is important to all system administrators. For this reason <span class="application"><strong>Yum</strong></span> provides the <span class="application"><strong>security</strong></span> plugin, which extends <code class="command">yum</code> with a set of highly-useful security-related commands, subcommands and options.
+ </div><div class="para">
+ You can check for all security-related updates as follows:
+ </div><pre class="screen">
+~]# <code class="command">yum check-update --security</code>
+Loaded plugins: presto, refresh-packagekit, security
+Limiting package lists to security relevant ones
+Needed 3 of 7 packages, for security
+elinks.x86_64 0.12-0.13.pre3.fc11 fedora
+kernel.x86_64 2.6.30.8-64.fc11 fedora
+kernel-headers.x86_64 2.6.30.8-64.fc11 fedora</pre><div class="para">
+ You can then use either <code class="command">yum update --security</code> or <code class="command">yum update-minimal --security</code> to update those packages which are affected by security advisories. Both of these commands update all packages on the system for which a security advisiory has been issued. <code class="command">yum update-minimal --security</code> updates them to the latest packages which were released as part of a security advisory, while <code class="command">yum update --security</code> will update all packages affected by a security advisory <span class="emphasis"><em>to the latest version of that package available</em></span>.
+ </div><div class="para">
+ In other words, if:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ the <span class="package">kernel-2.6.30.8-16</span> package is installed on your system;
+ </div></li><li class="listitem"><div class="para">
+ the <span class="package">kernel-2.6.30.8-32</span> package was released as a security update;
+ </div></li><li class="listitem"><div class="para">
+ then <span class="package">kernel-2.6.30.8-64</span> was released as a bug fix update,
+ </div></li></ul></div><div class="para">
+ ...then <code class="command">yum update-minimal --security</code> will update you to <span class="package">kernel-2.6.30.8-32</span>, and <code class="command">yum update --security</code> will update you to <span class="package">kernel-2.6.30.8-64</span>. Conservative system administrators may want to use <code class="command">update-minimal</code> to reduce the risk incurred by updating packages as much as possible.
+ </div><div class="para">
+ Refer to <code class="command">man yum-security</code> for usage details and further explanation of the enhancements the <span class="application"><strong>security</strong></span> plugin adds to <code class="command">yum</code>.
+ </div><div class="footnotes"><br /><hr /><div class="footnote" id="footnote-Alternative_Locations_for_protect-packages_Lists"><p><sup>[<a id="ftn.footnote-Alternative_Locations_for_protect-packages_Lists" href="#footnote-Alternative_Locations_for_protect-packages_Lists" class="para">1</a>] </sup>
+ You can also place files with the extension <code class="filename">.list</code> in the <code class="filename">/etc/sysconfig/protected-packages.d/</code> directory (which you should create if it does not exist), and list packages—one per line—in these files. <span class="application"><strong>protect-packages</strong></span> will protect these too.
+ </p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_More_Yum_Plugins.html"><strong>Prev</strong>1.4.2. Installing More Yum Plugins</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Additional_Resources.html"><strong>Next</strong>1.5. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Removing.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Removing.html
new file mode 100644
index 0000000..b318f1d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Removing.html
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.2.3. Removing</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="1.2. Packages and Package Groups" /><link rel="prev" href="sec-Installing.html" title="1.2.2. Installing" /><link rel="next" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="1.3. Configuring Yum and Yum Repositories" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="sec-Configuring_Yum_and_Yum_Repositories.html"><strong>Next</strong></a></li></ul><div class="section" title="1.2.3. Removing" id="sec-Removing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Removing">1.2.3. Removing</h3></div></div></div><a id="id724108" class="indexterm"></a><a id="id724120" class="indexterm"></a><div class="para">
+ <code class="command">yum remove <package_name></code> <a id="id724138" class="indexterm"></a>
+ <a id="id793831" class="indexterm"></a>
+ uninstalls (removes in <span class="application"><strong>RPM</strong></span> and <span class="application"><strong>Yum</strong></span> terminology) the package, as well as any packages that depend on it. As when you install multiple packages, you can remove several at once by adding more package names to the command:
+ </div><pre class="screen">
+ <code class="command">yum remove foo bar baz</code>
+</pre><div class="para">
+ Similar to <code class="command">install</code>, <code class="command">remove</code> can take these arguments:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ package names
+ </div></li><li class="listitem"><div class="para">
+ glob expressions
+ </div></li><li class="listitem"><div class="para">
+ file lists
+ </div></li><li class="listitem"><div class="para">
+ package provides
+ </div></li></ul></div>
+
+ </div><div class="warning" title="Warning: Removing a Package when Other Packages Depend On It" id="warning-WarningRemoving_a_Package_when_Other_Packages_Depend_On_It"><div class="admonition_header"><h2>Warning: Removing a Package when Other Packages Depend On It</h2></div><div class="admonition"><div class="para">
+ <span class="application"><strong>Yum</strong></span> is not able to remove a package without also removing packages which depend on it. This type of operation can only be performed by <span class="application"><strong>RPM</strong></span>, is not advised, and can potentially leave your system in a non-functioning state or cause applications to misbehave and/or crash. For further information, refer to <a class="xref" href="s2-rpm-uninstalling.html" title="3.2.4. Uninstalling">Section 3.2.4, “Uninstalling”</a> in the <span class="application"><strong>RPM</strong></span> chapter.
+ </div></div></div><h4>Removing a Package Group</h4><div class="para">
+ You can remove a package group using syntax congruent with the <code class="command">install</code> syntax.
+ </div><div class="example" title="Example 1.6. Alternative but equivalent ways of removing a package group" id="ex-Alternative_but_equivalent_ways_of_removing_a_package_group"><h6>Example 1.6. Alternative but equivalent ways of removing a package group</h6><div class="example-contents"><pre class="screen">
+~]# <code class="command">yum groupremove "KDE (K Desktop Environment)"</code>
+~]# <code class="command">yum groupremove kde-desktop</code>
+~]# <code class="command">yum remove @kde-desktop</code>
+</pre></div></div><br class="example-break" /><div class="important" title="Smart package group removal" id="important-Smart_package_group_removal"><div class="admonition_header"><h2>Smart package group removal</h2></div><div class="admonition"><a id="id715613" class="indexterm"></a><a id="id715625" class="indexterm"></a><div class="para">
+ When you tell <span class="application"><strong>yum</strong></span> to remove a package group, it will remove every package in that group, even if those packages are members of other package groups or dependencies of other installed packages. However, you can instruct <code class="command">yum</code> to remove only those packages which are not required by any other packages or groups by adding the <code class="option">groupremove_leaf_only=1</code> directive to the <code class="literal">[main]</code> section of the <code class="filename">/etc/yum.conf</code> configuration file. For more information on this directive, refer to <a class="xref" href="sec-Configuring_Yum_and_Yum_Repositories.html#sec-Setting_main_Options" title="1.3.1. Setting [main] Options">Section 1.3.1, “Setting [main] Options”</a>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing.html"><strong>Prev</strong>1.2.2. Installing</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Yum_and_Yum_Repositories.html"><strong>Next</strong>1.3. Configuring Yum and Yum Repositories</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Setting_Module_Parameters.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Setting_Module_Parameters.html
new file mode 100644
index 0000000..167cb0e
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Setting_Module_Parameters.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.5. Setting Module Parameters</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Unloading_a_Module.html" title="22.4. Unloading a Module" /><link rel="next" href="sec-Persistent_Module_Loading.html" title="22.6. Persistent Module Loading" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Unloading_a_Module.html"><strong>Prev</strong
></a></li><li class="next"><a accesskey="n" href="sec-Persistent_Module_Loading.html"><strong>Next</strong></a></li></ul><div class="section" title="22.5. Setting Module Parameters" id="sec-Setting_Module_Parameters"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Setting_Module_Parameters">22.5. Setting Module Parameters</h2></div></div></div><a id="id677175" class="indexterm"></a><a id="id677187" class="indexterm"></a><div class="para">
+ Like the kernel itself, modules can also take parameters that change their behavior. Most of the time, the default ones work well, but occasionally it is necessary or desirable to set custom parameters for a module. Because parameters cannot be dynamically set for a module that is already loaded into a running kernel, there are two different methods for setting them.
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ You can unload all dependencies of the module you want to set parameters for, unload the module using <code class="command">modprobe -r</code>, and then load it with <code class="command">modprobe</code> along with a list of customized parameters. This method is often used when the module does not have many dependencies, or to test different combinations of parameters without making them persistent, and is the method covered in this section.
+ </div></li><li class="listitem"><div class="para">
+ Alternatively, you can list the new parameters in an existing or newly-created file in the <code class="filename">/etc/modprobe.d/</code> directory. This method makes the module parameters persistent by ensuring that they are set each time the module is loaded, such as after every reboot or <code class="command">modprobe</code> command. This method is covered in <a class="xref" href="sec-Persistent_Module_Loading.html" title="22.6. Persistent Module Loading">Section 22.6, “Persistent Module Loading”</a>, though the following information is a prerequisite.
+ </div></li></ol></div><div class="para">
+ You can use <code class="command">modprobe</code> to load a kernel module with custom parameters using the following command line format:
+ </div><div class="example" title="Example 22.3. Supplying optional parameters when loading a kernel module" id="ex-Supplying_optional_parameters_when_loading_a_kernel_module"><h6>Example 22.3. Supplying optional parameters when loading a kernel module</h6><div class="example-contents"><pre class="screen">~]# <code class="command">modprobe <em class="replaceable"><code><module_name></code></em> [<span class="optional"><em class="replaceable"><code>parameter</code></em>=<em class="replaceable"><code>value</code></em></span>] </code>
+</pre></div></div><br class="example-break" /><div class="para">
+ Here are some things to be aware of when loading a module with custom parameters on the command line:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ You can enter multiple parameters and values by separating them with spaces.
+ </div></li><li class="listitem"><div class="para">
+ Some module parameters expect a list of comma-separated values as their argument. When entering the list of values, do <span class="emphasis"><em>not</em></span> insert a space after each comma, or <code class="command">modprobe</code> will incorrectly interpret the values following spaces as additional parameters.
+ </div></li><li class="listitem"><div class="para">
+ The <code class="command">modprobe</code> command silently succeeds with an exit status of <code class="constant">0</code> if:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ it successfully loads the module, <span class="emphasis"><em>or</em></span>
+ </div></li><li class="listitem"><div class="para">
+ the module is <span class="emphasis"><em>already</em></span> loaded into the kernel.
+ </div></li></ul></div><div class="para">
+ Thus, you must ensure that the module is not already loaded before attempting to load it with custom parameters. The <code class="command">modprobe</code> command does not automatically reload the module, or alert you that it is already loaded.
+ </div></li></ul></div><div class="para">
+ Here are the recommended steps for setting custom parameters and then loading a kernel module. This procedure illustrates the steps using the <code class="systemitem">e1000e</code> module, which is the network driver for Intel PRO/1000 network adapters, as an example:
+ </div><div class="procedure" title="Procedure 22.1. Loading a Kernel Module with Custom Parameters" id="proc-Loading_a_Kernel_Module_with_Custom_Parameters"><h6>Procedure 22.1. Loading a Kernel Module with Custom Parameters</h6><ol class="1"><li class="step" title="Step 1" id="proc-step1-Loading_a_Kernel_Module_with_Custom_Parameters"><div class="para">
+ First, ensure the module is not already loaded into the kernel:
+ </div><pre class="screen">~]# <code class="command">lsmod |grep e1000e</code>
+~]# </pre><div class="para">
+ Output indicates that the module is already loaded into the kernel, in which case you must first unload it before proceeding. Refer to <a class="xref" href="sec-Unloading_a_Module.html" title="22.4. Unloading a Module">Section 22.4, “Unloading a Module”</a> for instructions on safely unloading it.
+ </div></li><li class="step" title="Step 2" id="proc-step2-Loading_a_Kernel_Module_with_Custom_Parameters"><div class="para">
+ Load the module and list all custom parameters after the module name. For example, if you wanted to load the Intel PRO/1000 network driver with the interrupt throttle rate set to 3000 interrupts per second for the first, second and third instances of the driver, and Energy Efficient Ethernet (EEE) turned on<sup>[<a id="footnote-Energy_Efficient_Ethernet" href="#ftn.footnote-Energy_Efficient_Ethernet" class="footnote">4</a>]</sup> , you would run, as root:
+ </div><pre class="screen">~]# <code class="command">modprobe e1000e InterruptThrottleRate=3000,3000,3000 EEE=1</code>
+</pre><div class="para">
+ This example illustrates passing multiple valued to a single parameter by separating them with commas and omitting any spaces between them.
+ </div></li></ol></div><div class="footnotes"><br /><hr /><div class="footnote" id="footnote-Energy_Efficient_Ethernet"><p><sup>[<a id="ftn.footnote-Energy_Efficient_Ethernet" href="#footnote-Energy_Efficient_Ethernet" class="para">4</a>] </sup>
+ Despite what the example might imply, Energy Efficient Ethernet is turned on by default in the <code class="systemitem">e1000e</code> driver.
+ </p></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Unloading_a_Module.html"><strong>Prev</strong>22.4. Unloading a Module</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Persistent_Module_Loading.html"><strong>Next</strong>22.6. Persistent Module Loading</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Setting_repository_Options.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Setting_repository_Options.html
new file mode 100644
index 0000000..7eda4a0
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Setting_repository_Options.html
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.2. Setting [repository] Options</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="1.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="1.3. Configuring Yum and Yum Repositories" /><link rel="next" href="sec-Using_Yum_Variables.html" title="1.3.3. Using Yum Variables" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configurin
g_Yum_and_Yum_Repositories.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_Yum_Variables.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.2. Setting [repository] Options" id="sec-Setting_repository_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Setting_repository_Options">1.3.2. Setting [repository] Options</h3></div></div></div><a id="id611856" class="indexterm"></a><div class="para">
+ You can define individual <span class="application"><strong>Yum</strong></span> repositories by adding [<em class="replaceable"><code>repository</code></em>] sections (where <em class="replaceable"><code>repository</code></em> is a unique repository ID, such as [<em class="replaceable"><code>my_personal_repo</code></em>]) to <code class="filename">/etc/yum.conf</code> or to <code class="filename">.repo</code> files in the <code class="filename">/etc/yum.repos.d/</code>directory. All <code class="filename">.repo</code> files in <code class="filename">/etc/yum.repos.d/</code>are read by <code class="command">yum</code>; best practice is to define your repositories here instead of in <code class="filename">/etc/yum.conf</code>. You can create new, custom <code class="filename">.repo</code> files in this directory, add [<em class="replaceable"><code>repository</code></em>] sections to those files, and the next time you run a <code class="command">yum</code> command, it will
take all newly-added repositories into account.
+ </div><div class="para">
+ Here is a (bare-minimum) example of the form a <code class="filename">.repo</code> file should take:
+ </div><pre class="screen">
+[repository_ID]
+name=A Repository Name
+baseurl=http://path/to/repo or ftp://path/to/repo or file://path/to/local/repo
+</pre><div class="para">
+ Every [<em class="replaceable"><code>repository</code></em>] section must contain the following minimum parts:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> [<em class="replaceable"><code>repository_ID</code></em>] </span></dt><dd><div class="para">
+ The repository ID is a unique, one-word (no spaces; underscores are allowed) string of characters (enclosed by brackets) that serves as a repository identifier.
+ </div></dd><dt class="varlistentry"><span class="term">name=<em class="replaceable"><code><My Repository Name></code></em> </span></dt><dd><div class="para">
+ This is a human-readable string describing the repository.
+ </div></dd><dt class="varlistentry"><span class="term">baseurl=http://path/to/repo, ftp://path/to/repo, file://path/to/local/repo</span></dt><dd><div class="para">
+ This is a URL to the directory where the repodata directory of a repository is located. Usually this URL is an HTTP link, such as:
+ </div><pre class="screen">baseurl=http://path/to/repo/releases/$releasever/server/$basearch/os/</pre><div class="para">
+ <span class="application"><strong>Yum</strong></span> always expands the <code class="envar">$releasever</code>, <code class="envar">$arch</code> and <code class="envar">$basearch</code> variables in URLs. See the following section for explanations of all <span class="application"><strong>Yum</strong></span> variables: <a class="xref" href="sec-Using_Yum_Variables.html" title="1.3.3. Using Yum Variables">Section 1.3.3, “Using Yum Variables”</a>.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If the repository is available over FTP, use: ftp://path/to/repo
+ </div></li><li class="listitem"><div class="para">
+ If the repository is local to the machine, use file://path/to/local/repo
+ </div></li><li class="listitem"><div class="para">
+ If a specific online repository requires basic HTTP authentication, you can specify your username and password in the <code class="literal">http://path/to/repo</code> by prepending it as <code class="command">username:password at link</code>. For example, if a repository on http://www.example.com/repo/ requires a username of "user" and a password of "password", then the <code class="literal">baseurl</code> link could be specified as:
+ </div><pre class="screen">baseurl=http://<strong class="userinput"><code>user</code></strong>:<strong class="userinput"><code>password</code></strong>@www.example.com/repo/</pre></li></ul></div></dd></dl></div><div class="para">
+ The following is another useful [<em class="replaceable"><code>repository</code></em>] directive:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">enabled=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="para">
+ <code class="constant">0</code> — do not include this repository as a package source when performing updates and installs. This is an easy way of quickly turning repositories on and off, which is useful when you desire a single package from a repository that you do not want to enable for updates or installs.
+ </div><div class="para">
+ <code class="constant">1</code> — include this repository as a package source.
+ </div><div class="para">
+ Turning repositories on and off can also be performed quickly by passing either the <code class="option">--enablerepo=<<em class="replaceable"><code>repo_name</code></em>></code> or <code class="option">--disablerepo=<<em class="replaceable"><code>repo_name</code></em>></code> option to <code class="command">yum</code>, or easily through <span class="application"><strong>PackageKit</strong></span>'s <span class="guilabel"><strong>Add/Remove Software</strong></span> window.
+ </div></dd></dl></div><div class="para">
+ Many more [<em class="replaceable"><code>repository</code></em>] options exist. Refer to the <code class="literal">[repository] OPTIONS</code> section of <code class="command">man yum.conf</code> for the exhaustive list and descriptions for each.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_Yum_and_Yum_Repositories.html"><strong>Prev</strong>1.3. Configuring Yum and Yum Repositories</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_Yum_Variables.html"><strong>Next</strong>1.3.3. Using Yum Variables</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Specific_Kernel_Module_Capabilities.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Specific_Kernel_Module_Capabilities.html
new file mode 100644
index 0000000..12b9650
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Specific_Kernel_Module_Capabilities.html
@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.7. Specific Kernel Module Capabilities</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Persistent_Module_Loading.html" title="22.6. Persistent Module Loading" /><link rel="next" href="sec-Using_Channel_Bonding.html" title="22.7.2. Using Channel Bonding" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Persistent_Module_Loading.html"><stro
ng>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_Channel_Bonding.html"><strong>Next</strong></a></li></ul><div class="section" title="22.7. Specific Kernel Module Capabilities" id="sec-Specific_Kernel_Module_Capabilities"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Specific_Kernel_Module_Capabilities">22.7. Specific Kernel Module Capabilities</h2></div></div></div><div class="para">
+ This section explains how to enable specific kernel capabilities using various kernel modules.
+ </div><div class="section" title="22.7.1. Using Multiple Ethernet Cards" id="sec-Using_Multiple_Ethernet_Cards"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Using_Multiple_Ethernet_Cards">22.7.1. Using Multiple Ethernet Cards</h3></div></div></div><a id="id465785" class="indexterm"></a><div class="para">
+ It is possible to use multiple Ethernet cards on a single machine. For each card there must be an <code class="command">alias</code> and, possibly, <code class="command">options</code> lines for each card in a user-created <code class="filename"><em class="replaceable"><code><module_name></code></em>.conf</code> file in the <code class="filename">/etc/modprobe.d/</code> directory.
+ </div><div class="para">
+ For additional information about using multiple Ethernet cards, refer to the <em class="citetitle">Linux Ethernet-HOWTO</em> online at <a href="http://www.redhat.com/mirrors/LDP/HOWTO/Ethernet-HOWTO.html">http://www.redhat.com/mirrors/LDP/HOWTO/Ethernet-HOWTO.html</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Persistent_Module_Loading.html"><strong>Prev</strong>22.6. Persistent Module Loading</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_Channel_Bonding.html"><strong>Next</strong>22.7.2. Using Channel Bonding</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Unloading_a_Module.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Unloading_a_Module.html
new file mode 100644
index 0000000..9965f71
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Unloading_a_Module.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.4. Unloading a Module</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Loading_a_Module.html" title="22.3. Loading a Module" /><link rel="next" href="sec-Setting_Module_Parameters.html" title="22.5. Setting Module Parameters" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Loading_a_Module.html"><strong>Prev</strong></a><
/li><li class="next"><a accesskey="n" href="sec-Setting_Module_Parameters.html"><strong>Next</strong></a></li></ul><div class="section" title="22.4. Unloading a Module" id="sec-Unloading_a_Module"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Unloading_a_Module">22.4. Unloading a Module</h2></div></div></div><a id="id481888" class="indexterm"></a><a id="id481900" class="indexterm"></a><a id="id481920" class="indexterm"></a><div class="para">
+ You can unload a kernel module by running <code class="command">modprobe -r <em class="replaceable"><code><module_name></code></em> </code> as root. For example, assuming that the <code class="systemitem">wacom</code> module is already loaded into the kernel, you can unload it by running:
+ </div><pre class="screen">~]# <code class="command">modprobe -r wacom</code>
+</pre><div class="para">
+ However, this command will fail if a process is using:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ the <code class="systemitem">wacom</code> module,
+ </div></li><li class="listitem"><div class="para">
+ a module that <code class="systemitem">wacom</code> directly depends on, or,
+ </div></li><li class="listitem"><div class="para">
+ any module that <code class="systemitem">wacom</code>—through the dependency tree—depends on indirectly.
+ </div></li></ul></div><div class="para">
+ Refer to <a class="xref" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules" title="22.1. Listing Currently-Loaded Modules">Section 22.1, “Listing Currently-Loaded Modules”</a> for more information about using <code class="command">lsmod</code> to obtain the names of the modules which are preventing you from unloading a certain module.
+ </div><div class="para">
+ For example, if you want to unload the <code class="systemitem">firewire_ohci</code> module because (because you believe there is a bug in it that is affecting system stability, for example), your terminal session might look similar to this:
+ </div><pre class="screen">~]# <code class="command">modinfo -F depends firewire_ohci</code>
+depends: firewire-core
+~]# <code class="command">modinfo -F depends firewire_core</code>
+depends: crc-itu-t
+~]# <code class="command">modinfo -F depends crc-itu-t</code>
+depends:</pre><div class="para">
+ You have figured out the dependency tree (which does not branch in this example) for the loaded Firewire modules: <code class="systemitem">firewire_ohci</code> depends on <code class="systemitem">firewire_core</code>, which itself depends on <code class="systemitem">crc-itu-t</code>.
+ </div><div class="para">
+ You can unload <code class="systemitem">firewire_ohci</code> using the <code class="command">modprobe -v -r <em class="replaceable"><code><module_name></code></em> </code> command, where <code class="option">-r</code> is short for <code class="option">--remove</code> and <code class="option">-v</code> for <code class="option">--verbose</code>:
+ </div><pre class="screen">~]# <code class="command">modprobe -r -v firewire_ohci</code>
+rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/firewire/firewire-ohci.ko
+rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/firewire/firewire-core.ko
+rmmod /lib/modules/2.6.32-71.el6.x86_64/kernel/lib/crc-itu-t.ko</pre><div class="para">
+ The output shows that modules are unloaded in the reverse order that they are loaded, given that no proceses depend on any of the modules being unloaded.
+ </div><a id="id677109" class="indexterm"></a><a id="id677129" class="indexterm"></a><div class="important" title="Do not use rmmod directly!" id="important-Do_not_use_rmmod_directly"><div class="admonition_header"><h2>Do not use rmmod directly!</h2></div><div class="admonition"><div class="para">
+ Although the <code class="command">rmmod</code> command can be used to unload kernel modules, it is recommended to use <code class="command">modprobe -r</code> instead.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Loading_a_Module.html"><strong>Prev</strong>22.3. Loading a Module</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Setting_Module_Parameters.html"><strong>Next</strong>22.5. Setting Module Parameters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-User_and_System_Connections.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-User_and_System_Connections.html
new file mode 100644
index 0000000..c45bd17
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-User_and_System_Connections.html
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>5.2.4. User and System Connections</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Interacting_with_NetworkManager.html" title="5.2. Interacting with NetworkManager" /><link rel="prev" href="sec-Connecting_to_a_Network_Automatically.html" title="5.2.3. Connecting to a Network Automatically" /><link rel="next" href="sec-Configuring_Connection_Settings.html" title="5.3. Configuring Connection Settings" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href
="sec-Connecting_to_a_Network_Automatically.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Connection_Settings.html"><strong>Next</strong></a></li></ul><div class="section" title="5.2.4. User and System Connections" id="sec-User_and_System_Connections"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-User_and_System_Connections">5.2.4. User and System Connections</h3></div></div></div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> connections are always either <span class="emphasis"><em>user connections</em></span> or <span class="emphasis"><em>system connections</em></span>. Depending on the system-specific policy that the administrator has configured, users may need root privileges to create and modify system connections. <span class="application"><strong>NetworkManager</strong></span>'s default policy enables users to create and modify user connections, but requires them to have root privileges to add, modify or delete system connections.
+ </div><div class="para">
+ User connections are so-called because they are specific to the user who creates them. In contrast to system connections, whose configurations are stored under the <code class="filename">/etc/sysconfig/network-scripts/</code> directory (mainly in <code class="filename">ifcfg-<em class="replaceable"><code><network_type></code></em> </code> interface configuration files), user connection settings are stored in the GConf configuration database and the GNOME keyring, and are only available during login sessions for the user who created them. Thus, logging out of the desktop session causes user-specific connections to become unavailable.
+ </div><div class="note" title="Tip: Increase security by making VPN connections user-specific" id="note-Tip-Increase_security_by_making_VPN_connections_user-specific"><div class="admonition_header"><h2>Tip: Increase security by making VPN connections user-specific</h2></div><div class="admonition"><div class="para">
+ Because <span class="application"><strong>NetworkManager</strong></span> uses the GConf and GNOME keyring applications to store user connection settings, and because these settings are specific to your desktop session, it is highly recommended to configure your personal VPN connections as user connections. If you do so, other non-root users on the system cannot view or access these connections in any way.
+ </div></div></div><div class="para">
+ System connections, on the other hand, become available at boot time and can be used by other users on the system without first logging in to a desktop session.
+ </div><div class="para">
+ <span class="application"><strong>NetworkManager</strong></span> can quickly and conveniently convert user to system connections and vice versa. Converting a user connection to a system connection causes <span class="application"><strong>NetworkManager</strong></span> to create the relevant interface configuration files under the <code class="filename">/etc/sysconfig/network-scripts/</code> directory, and to delete the GConf settings from the user's session. Conversely, converting a system to a user-specific connection causes <span class="application"><strong>NetworkManager</strong></span> to remove the system-wide configuration files and create the corresponding GConf/GNOME keyring settings.
+ </div><div class="mediaobject" align="center"><img src="images/Network_Configuration-NM-Available_to_all_users.png" align="middle" /><div class="caption"><div class="para">
+ The <span class="guilabel"><strong>Available to all users</strong></span> checkbox controls whether connections are user-specific or system-wide
+ </div></div></div><div class="procedure" title="Procedure 5.2. Changing a Connection to be User-Specific instead of System-Wide, or Vice-Versa" id="procedure-Changing_a_Connection_to_be_User-Specific_instead_of_System-Wide_or_Vice-Versa"><h6>Procedure 5.2. Changing a Connection to be User-Specific instead of System-Wide, or Vice-Versa</h6><div class="note" title="Depending on the system's policy, root privileges may be required" id="note-Depending_on_the_systems_policy_root_privileges_may_be_required"><div class="admonition_header"><h2>Depending on the system's policy, root privileges may be required</h2></div><div class="admonition"><div class="para">
+ As discussed, you may need root privileges on the system in order to change whether a connection is user-specific or system-wide.
+ </div></div></div><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Right-click on the <span class="application"><strong>NetworkManager</strong></span> applet icon in the Notification Area and click <span class="guilabel"><strong>Edit Connections</strong></span>. The <span class="guilabel"><strong>Network Connections</strong></span> window appears.
+ </div></li><li class="step" title="Step 2"><div class="para">
+ Select the tab for the type of network connection you want to configure.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Select the specific connection that you want to configure and click <span class="guibutton"><strong>Edit</strong></span>.
+ </div></li><li class="step" title="Step 4"><div class="para">
+ Check the <span class="guilabel"><strong>Available to all users</strong></span> checkbox to ask <span class="application"><strong>NetworkManager</strong></span> to make the connection a system-wide connection. Depending on system policy, you may then be prompted for the root password by the <span class="application"><strong>PolicyKit</strong></span> application. If so, enter the root password to finalize the change.
+ </div><div class="para">
+ Conversely, uncheck the <span class="guilabel"><strong>Available to all users</strong></span> checkbox to make the connection user-specific.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Connecting_to_a_Network_Automatically.html"><strong>Prev</strong>5.2.3. Connecting to a Network Automatically</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_Connection_Settings.html"><strong>Next</strong>5.3. Configuring Connection Settings</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Using_Add_Remove_Software.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Using_Add_Remove_Software.html
new file mode 100644
index 0000000..ef778c6
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Using_Add_Remove_Software.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2. Using Add/Remove Software</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-PackageKit.html" title="Chapter 2. PackageKit" /><link rel="prev" href="ch-PackageKit.html" title="Chapter 2. PackageKit" /><link rel="next" href="sec-Finding_Packages_with_Filters.html" title="2.2.2. Finding Packages with Filters" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-PackageKit.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hr
ef="sec-Finding_Packages_with_Filters.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2. Using Add/Remove Software" id="sec-Using_Add_Remove_Software"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Using_Add_Remove_Software">2.2. Using Add/Remove Software</h2></div></div></div><a id="id696845" class="indexterm"></a><a id="id696857" class="indexterm"></a><div class="para">
+ <span class="application"><strong>PackageKit</strong></span>'s <span class="application"><strong>Software Update</strong></span> GUI window is a separate application from its <span class="guilabel"><strong>Add/Remove Software</strong></span> application, although the two have intuitively similar interfaces. To find and install a new package, on the GNOME panel click on <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Administration</strong></span> → <span class="guimenuitem"><strong>Add/Remove Software</strong></span>, or run the <code class="command">gpk-application</code> command at the shell prompt.
+ </div><div class="figure" title="Figure 2.4. PackageKit's Add/Remove Software window" id="fig-Graphical_Package_Management-add_remove_software"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-add_remove_software.png" align="middle" width="444" alt="PackageKit's Add/Remove Software window" /><div class="longdesc"><div class="para">
+ viewing packagekit's add/remove softvware window
+ </div></div></div></div><h6>Figure 2.4. PackageKit's Add/Remove Software window</h6></div><br class="figure-break" /><div class="section" title="2.2.1. Refreshing Software Sources (Yum Repositories)" id="sec-Refreshing_Software_Sources_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Refreshing_Software_Sources_Yum_Repositories">2.2.1. Refreshing Software Sources (Yum Repositories)</h3></div></div></div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> refers to <span class="application"><strong>Yum</strong></span> repositories as
+ <a id="id841935" class="indexterm"></a>
+ <a id="id841946" class="indexterm"></a>
+ software sources. It obtains all packages from enabled software sources. You can view the list of all <span class="emphasis"><em>configured</em></span> and unfiltered (see below) <span class="application"><strong>Yum</strong></span> repositories by opening <span class="guilabel"><strong>Add/Remove Software</strong></span> and clicking <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Software sources</strong></span>. The <span class="guilabel"><strong>Software Sources</strong></span> dialog shows the repository name, as written on the <code class="computeroutput">name=<em class="replaceable"><code><My Repository Name></code></em> </code> field of all [<em class="replaceable"><code>repository</code></em>] sections in the <code class="filename">/etc/yum.conf</code> configuration file, and in all <code class="filename"><em class="replaceable"><code>repository</code></em>.repo</code> files in the <code class="filename">/etc/yum.
repos.d/</code> directory.
+ </div><div class="para">
+ Entries which are checked in the <span class="guilabel"><strong>Enabled</strong></span> column indicate that the corresponding repository will be used to locate packages to satisfy all update and installation requests (including dependency resolution). The <span class="guilabel"><strong>Enabled</strong></span> column corresponds to the <code class="computeroutput">enabled=<em class="replaceable"><code><1 or 0></code></em> </code> field in [<em class="replaceable"><code>repository</code></em>] sections. Checking an unchecked box enables the Yum repository, and unchecking it disables it. Performing either function causes <span class="application"><strong>PolicyKit</strong></span> to prompt for superuser authentication to enable or disable the repository. <span class="application"><strong>PackageKit</strong></span> actually inserts the <code class="literal">enabled=<em class="replaceable"><code><1 or 0></code></em> </code> line into the correct [<em class="repla
ceable"><code>repository</code></em>] section if it does not exist, or changes the value if it does. This means that enabling or disabling a repository through the <span class="guilabel"><strong>Software Sources</strong></span> window causes that change to persist after closing the window or rebooting the system. The ability to quickly enable and disable repositories based on our needs is a highly-convenient feature of <span class="application"><strong>PackageKit</strong></span>.
+ </div><div class="para">
+ Note that it is not possible to add or remove <span class="application"><strong>Yum</strong></span> repositories through <span class="application"><strong>PackageKit</strong></span>.
+ </div><div class="note" title="Showing Source RPM, Test and Debuginfo Repositories" id="note-Showing_Source_RPM_and_Test_Repositories"><div class="admonition_header"><h2>Showing Source RPM, Test and Debuginfo Repositories</h2></div><div class="admonition"><div class="para">
+ Checking the box at the bottom of the <span class="guilabel"><strong>Software Sources</strong></span> window causes <span class="application"><strong>PackageKit</strong></span> to display source RPM, testing and debuginfo repositories as well. This box is unchecked by defaut.
+ </div></div></div><div class="para">
+ After enabling and/or disabling the correct <span class="application"><strong>Yum</strong></span> repositories, ensure that you have the latest list of available packages. Click on <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Refresh package lists</strong></span> and <span class="application"><strong>PackageKit</strong></span> will obtain the latest lists of packages from all enabled software sources, i.e. <span class="application"><strong>Yum</strong></span> repositories.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-PackageKit.html"><strong>Prev</strong>Chapter 2. PackageKit</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Finding_Packages_with_Filters.html"><strong>Next</strong>2.2.2. Finding Packages with Filters</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Using_Channel_Bonding.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Using_Channel_Bonding.html
new file mode 100644
index 0000000..9ec9d3b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Using_Channel_Bonding.html
@@ -0,0 +1,192 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.7.2. Using Channel Bonding</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Specific_Kernel_Module_Capabilities.html" title="22.7. Specific Kernel Module Capabilities" /><link rel="prev" href="sec-Specific_Kernel_Module_Capabilities.html" title="22.7. Specific Kernel Module Capabilities" /><link rel="next" href="s1-kernel-modules-additional-resources.html" title="22.8. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s
ec-Specific_Kernel_Module_Capabilities.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-kernel-modules-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" title="22.7.2. Using Channel Bonding" id="sec-Using_Channel_Bonding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Using_Channel_Bonding">22.7.2. Using Channel Bonding</h3></div></div></div><a id="id465849" class="indexterm"></a><a id="id465865" class="indexterm"></a><a id="id465877" class="indexterm"></a><a id="id465889" class="indexterm"></a><a id="id481494" class="indexterm"></a><div class="para">
+ Fedora allows administrators to bind NICs together into a single channel using the <code class="filename">bonding</code> kernel module and a special network interface, called a <em class="firstterm">channel bonding interface</em>. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy.
+ </div><a id="id481520" class="indexterm"></a><a id="id481532" class="indexterm"></a><div class="para">
+ To channel bond multiple network interfaces, the administrator must perform the following steps:
+ </div><div class="orderedlist"><ol><li class="listitem"><div class="para">
+ As root, create a new file named <code class="filename"><em class="replaceable"><code><bonding></code></em>.conf</code> in the <code class="filename">/etc/modprobe.d/</code> directory. Note that you can name this file anything you like as long as it ends with a <code class="filename">.conf</code> extension. Insert the following line in this new file:
+ </div><pre class="screen">alias bond<em class="replaceable"><code><N></code></em> bonding</pre><div class="para">
+ Replace <em class="replaceable"><code><N></code></em> with the interface number, such as <code class="command">0</code>. For each configured channel bonding interface, there must be a corresponding entry in your new <code class="filename">/etc/modprobe.d/<em class="replaceable"><code><bonding></code></em>.conf</code> file.
+ </div></li><li class="listitem"><div class="para">
+ Configure a channel bonding interface as outlined in <a class="xref" href="s2-networkscripts-interfaces-chan.html" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a>.
+ </div></li><li class="listitem"><div class="para">
+ To enhance performance, adjust available module options to ascertain what combination works best. Pay particular attention to the <code class="command">miimon</code> or <code class="command">arp_interval</code> and the <code class="command">arp_ip_target</code> parameters. Refer to <a class="xref" href="sec-Using_Channel_Bonding.html#s3-modules-bonding-directives" title="22.7.2.1. Bonding Module Directives">Section 22.7.2.1, “Bonding Module Directives”</a> for a list of available options and how to quickly determine the best ones for your bonded interface.
+ </div></li></ol></div><div class="section" title="22.7.2.1. Bonding Module Directives" id="s3-modules-bonding-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="s3-modules-bonding-directives">22.7.2.1. Bonding Module Directives</h4></div></div></div><a id="id481658" class="indexterm"></a><a id="id481674" class="indexterm"></a><a id="id481690" class="indexterm"></a><div class="para">
+ It is a good idea to test which channel bonding module parameters work best for your bonded interfaces before adding them to the <em class="parameter"><code>BONDING_OPTS="<em class="replaceable"><code><bonding parameters></code></em>"</code></em> directive in your bonding interface configuration file (<code class="filename">ifcfg-bond0</code> for example). Parameters to bonded interfaces can be configured without unloading (and reloading) the bonding module by manipulating files in the <code class="systemitem">sysfs</code> file system.
+ </div><div class="para">
+ <code class="systemitem">sysfs</code> is a virtual file system that represents kernel objects as directories, files and symbolic links. <code class="systemitem">sysfs</code> can be used to query for information about kernel objects, and can also manipulate those objects through the use of normal file system commands. The <code class="systemitem">sysfs</code> virtual file system has a line in <code class="filename">/etc/fstab</code>, and is mounted under the <code class="filename">/sys/</code> directory. All bonding interfaces can be configured dynamically by interacting with and manipulating files under the <code class="filename">/sys/class/net/</code> directory.
+ </div><div class="para">
+ After you have created a channel bonding interface file such as <code class="filename">ifcfg-bond0</code> and inserted <em class="parameter"><code>SLAVE=yes</code></em> and <em class="parameter"><code>MASTER=bond0</code></em> directives in the configuration files for each interface bonded to bond0 following the instructions in <a class="xref" href="s2-networkscripts-interfaces-chan.html" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a>, you can proceed to testing and determining the best parameters for your bonding interface.
+ </div><div class="para">
+ First, bring up the bond you created by running <code class="command">ifconfig <code class="option">bond<em class="replaceable"><code><N></code></em> </code> <code class="option">up</code> </code> as root:
+ </div><pre class="screen">~]# <code class="command">ifconfig bond0 up</code>
+</pre><div class="para">
+ If you have correctly created the <code class="filename">ifcfg-bond0</code> bonding interface file, you will be able to see <code class="computeroutput">bond0</code> listed in the output of running <code class="command">ifconfig</code> (without any options):
+ </div><pre class="screen">~]# <code class="command">ifconfig</code>
+bond0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
+ UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
+ RX packets:0 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:0
+ RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
+eth0 Link encap:Ethernet HWaddr 52:54:00:26:9E:F1
+ inet addr:192.168.122.251 Bcast:192.168.122.255 Mask:255.255.255.0
+ inet6 addr: fe80::5054:ff:fe26:9ef1/64 Scope:Link
+ UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
+ RX packets:207 errors:0 dropped:0 overruns:0 frame:0
+ TX packets:205 errors:0 dropped:0 overruns:0 carrier:0
+ collisions:0 txqueuelen:1000
+ RX bytes:70374 (68.7 KiB) TX bytes:25298 (24.7 KiB)
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em>
+</pre><div class="para">
+ To view all existing bonds, even if they are not up, run:
+ </div><pre class="screen">~]# <code class="command">cat /sys/class/net/bonding_masters</code>
+bond0</pre><div class="para">
+ You can configure each bond individually by manipulating the files located in the <code class="filename">/sys/class/net/bond<em class="replaceable"><code><N></code></em>/bonding/</code> directory. First, the bond you are configuring must be taken down:
+ </div><pre class="screen">~]# <code class="command">ifconfig bond0 down</code>
+</pre><div class="para">
+ As an example, to enable MII monitoring on bond0 with a 1 second interval, you could run (as root):
+ </div><pre class="screen">~]# <code class="command">echo 1000 > /sys/class/net/bond0/bonding/miimon</code>
+</pre><div class="para">
+ To configure bond0 for <em class="parameter"><code>balance-alb</code></em> mode, you could run either:
+ </div><pre class="screen">~]# <code class="command">echo 6 > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ ...or, using the name of the mode:
+ </div><pre class="screen">~]# <code class="command">echo balance-alb > /sys/class/net/bond0/bonding/mode</code>
+</pre><div class="para">
+ After configuring some options for the bond in question, you can bring it up and test it by running <code class="command">ifconfig bond<em class="replaceable"><code><N></code></em> <code class="option">up</code> </code>. If you decide to change the options, take the interface down, modify its parameters using <code class="systemitem">sysfs</code>, bring it back up, and re-test.
+ </div><div class="para">
+ Once you have determined the best set of parameters for your bond, add those parameters as a space-separated list to the <em class="parameter"><code>BONDING_OPTS=</code></em> directive of the <code class="filename">/etc/sysconfig/network-scripts/ifcfg-bond<em class="replaceable"><code><N></code></em> </code> file for the bonding interface you are configuring. Whenever that bond is brought up (for example, by the system during the boot sequence if the <em class="parameter"><code>ONBOOT=yes</code></em> directive is set), the bonding options specified in the <em class="parameter"><code>BONDING_OPTS</code></em> will take effect for that bond. For more information on configuring bonding interfaces (and <em class="parameter"><code>BONDING_OPTS</code></em>), refer to <a class="xref" href="s2-networkscripts-interfaces-chan.html" title="4.2.2. Channel Bonding Interfaces">Section 4.2.2, “Channel Bonding Interfaces”</a>.
+ </div><div class="para">
+ The following list provides the names of many of the more common channel bonding parameters, along with a descriptions of what they do. For more information, refer to the brief descriptions for each <code class="computeroutput">parm</code> in <code class="command">modinfo bonding</code> output, or the exhaustive descriptions in the <code class="filename">bonding.txt</code> file in the <span class="package">kernel-doc</span> package (see <a class="xref" href="s1-kernel-modules-additional-resources.html" title="22.8. Additional Resources">Section 22.8, “Additional Resources”</a>).
+ </div><div class="variablelist" title="Bonding Interface Parameters"><h6>Bonding Interface Parameters</h6><dl><dt class="varlistentry"><span class="term"> <code class="literal">arp_interval=<em class="replaceable"><code><time_in_milliseconds></code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how often ARP monitoring occurs.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div><div class="para">
+ If using this setting while in <code class="literal">mode=0</code> or <code class="literal">mode=1</code> (the two load-balancing modes), the network switch must be configured to distribute packets evenly across the NICs. For more information on how to accomplish this, refer to <code class="filename">/usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel_version></code></em>/Documentation/networking/bonding.txt</code>
+ </div><div class="para">
+ The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_ip_target=<em class="replaceable"><code><ip_address></code></em>[<span class="optional">,<em class="replaceable"><code><ip_address_2></code></em>,…<em class="replaceable"><code><ip_address_16></code></em></span>] </code> </span></dt><dd><div class="para">
+ Specifies the target IP address of ARP requests when the <code class="literal">arp_interval</code> parameter is enabled. Up to 16 IP addresses can be specified in a comma separated list.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">arp_validate=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ Validate source/distribution of ARP probes; default is <strong class="userinput"><code>none</code></strong>. Other valid values are <strong class="userinput"><code>active</code></strong>, <strong class="userinput"><code>backup</code></strong>, and <strong class="userinput"><code>all</code></strong>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">debug=<em class="replaceable"><code><number></code></em> </code> </span></dt><dd><div class="para">
+ Enables debug messages. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> — Debug messages are disabled. This is the default.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> — Debug messages are enabled.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">downdelay=<em class="replaceable"><code><time_in_milliseconds></code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait after link failure before disabling the link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term">lacp_rate=<em class="replaceable"><code><value></code></em> </span></dt><dd><div class="para">
+ Specifies the rate at which link partners should transmit LACPDU packets in 802.3ad mode. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>slow</code></strong> or <strong class="userinput"><code>0</code></strong> — Default setting. This specifies that partners should transmit LACPDUs every 30 seconds.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>fast</code></strong> or <strong class="userinput"><code>1</code></strong> — Specifies that partners should transmit LACPDUs every 1 second.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">miimon=<em class="replaceable"><code><time_in_milliseconds></code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how often MII link monitoring occurs. This is useful if high availability is required because MII is used to verify that the NIC is active. To verify that the driver for a particular NIC supports the MII tool, type the following command as root:
+ </div><pre class="screen">~]# <code class="command">ethtool <em class="replaceable"><code><interface_name></code></em> | grep "Link detected:"</code>
+</pre><div class="para">
+ In this command, replace <em class="replaceable"><code><interface_name</code></em>> with the name of the device interface, such as <strong class="userinput"><code>eth0</code></strong>, not the bond interface. If MII is supported, the command returns:
+ </div><pre class="screen">Link detected: yes</pre><div class="para">
+ If using a bonded interface for high availability, the module for each NIC must support MII. Setting the value to <strong class="userinput"><code>0</code></strong> (the default), turns this feature off. When configuring this setting, a good starting point for this parameter is <strong class="userinput"><code>100</code></strong>.
+ </div><div class="important" title="Important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ It is essential that both <code class="literal">arp_interval</code> and <code class="literal">arp_ip_target</code> parameters are specified, or, alternatively, the <code class="literal">miimon</code> parameter is specified. Failure to do so can cause degradation of network performance in the event that a link fails.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">mode=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ ...where <em class="replaceable"><code><value></code></em> is one of:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-rr</code></strong> or <strong class="userinput"><code>0</code></strong> — Sets a round-robin policy for fault tolerance and load balancing. Transmissions are received and sent out sequentially on each bonded slave interface beginning with the first one available.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>active-backup</code></strong> or <strong class="userinput"><code>1</code></strong> — Sets an active-backup policy for fault tolerance. Transmissions are received and sent out via the first available bonded slave interface. Another bonded slave interface is only used if the active bonded slave interface fails.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-xor</code></strong> or <strong class="userinput"><code>2</code></strong> — Sets an XOR (exclusive-or) policy for fault tolerance and load balancing. Using this method, the interface matches up the incoming request's MAC address with the MAC address for one of the slave NICs. Once this link is established, transmissions are sent out sequentially beginning with the first available interface.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>broadcast</code></strong> or <strong class="userinput"><code>3</code></strong> — Sets a broadcast policy for fault tolerance. All transmissions are sent on all slave interfaces.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>802.3ad</code></strong> or <strong class="userinput"><code>4</code></strong> — Sets an IEEE 802.3ad dynamic link aggregation policy. Creates aggregation groups that share the same speed and duplex settings. Transmits and receives on all slaves in the active aggregator. Requires a switch that is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-tlb</code></strong> or <strong class="userinput"><code>5</code></strong> — Sets a Transmit Load Balancing (TLB) policy for fault tolerance and load balancing. The outgoing traffic is distributed according to the current load on each slave interface. Incoming traffic is received by the current slave. If the receiving slave fails, another slave takes over the MAC address of the failed slave.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>balance-alb</code></strong> or <strong class="userinput"><code>6</code></strong> — Sets an Active Load Balancing (ALB) policy for fault tolerance and load balancing. Includes transmit and receive load balancing for IPV4 traffic. Receive load balancing is achieved through ARP negotiation.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">num_unsol_na=<em class="replaceable"><code><number></code></em> </code> </span></dt><dd><div class="para">
+ Specifies the number of unsolicited IPv6 Neighbor Advertisements to be issued after a failover event. One unsolicited NA is issued immediately after the failover.
+ </div><div class="para">
+ The valid range is <strong class="userinput"><code>0 - 255</code></strong>; the default value is <strong class="userinput"><code>1</code></strong>. This parameter affects only the active-backup mode.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary=<em class="replaceable"><code><interface_name></code></em> </code> </span></dt><dd><div class="para">
+ Specifies the interface name, such as <strong class="userinput"><code>eth0</code></strong>, of the primary device. The <code class="literal">primary</code> device is the first of the bonding interfaces to be used and is not abandoned unless it fails. This setting is particularly useful when one NIC in the bonding interface is faster and, therefore, able to handle a bigger load.
+ </div><div class="para">
+ This setting is only valid when the bonding interface is in <strong class="userinput"><code>active-backup</code></strong> mode. Refer to <code class="filename"> /usr/share/doc/kernel-doc-<em class="replaceable"><code><kernel-version></code></em>/Documentation/networking/bonding.txt</code> for more information.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">primary_reselect=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ Specifies the reselection policy for the primary slave. This affects how the primary slave is chosen to become the active slave when failure of the active slave or recovery of the primary slave occurs. This parameter is designed to prevent flip-flopping between the primary slave and other slaves. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>always</code></strong> or <strong class="userinput"><code>0</code></strong> (default) — The primary slave becomes the active slave whenever it comes back up.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>better</code></strong> or <strong class="userinput"><code>1</code></strong> — The primary slave becomes the active slave when it comes back up, if the speed and duplex of the primary slave is better than the speed and duplex of the current active slave.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>failure</code></strong> or <strong class="userinput"><code>2</code></strong> — The primary slave becomes the active slave only if the current active slave fails and the primary slave is up.
+ </div></li></ul></div><div class="para">
+ The <code class="literal">primary_reselect</code> setting is ignored in two cases:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ If no slaves are active, the first slave to recover is made the active slave.
+ </div></li><li class="listitem"><div class="para">
+ When initially enslaved, the primary slave is always made the active slave.
+ </div></li></ul></div><div class="para">
+ Changing the <code class="literal">primary_reselect</code> policy via <code class="systemitem">sysfs</code> will cause an immediate selection of the best active slave according to the new policy. This may or may not result in a change of the active slave, depending upon the circumstances
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">updelay=<em class="replaceable"><code><time_in_milliseconds></code></em> </code> </span></dt><dd><div class="para">
+ Specifies (in milliseconds) how long to wait before enabling a link. The value must be a multiple of the value specified in the <code class="literal">miimon</code> parameter. The value is set to <strong class="userinput"><code>0</code></strong> by default, which disables it.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="literal">use_carrier=<em class="replaceable"><code><number></code></em> </code> </span></dt><dd><div class="para">
+ Specifies whether or not <code class="literal">miimon</code> should use MII/ETHTOOL ioctls or <code class="function">netif_carrier_ok()</code> to determine the link state. The <code class="function">netif_carrier_ok()</code> function relies on the device driver to maintains its state with <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em> </code>; most device drivers support this function.
+ </div><div class="para">
+ The MII/ETHROOL ioctls tools utilize a deprecated calling sequence within the kernel. However, this is still configurable in case your device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em> </code>.
+ </div><div class="para">
+ Valid values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> — Default setting. Enables the use of <code class="function">netif_carrier_ok()</code>.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> — Enables the use of MII/ETHTOOL ioctls.
+ </div></li></ul></div><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ If the bonding interface insists that the link is up when it should not be, it is possible that your network device driver does not support <code class="literal">netif_carrier_<em class="replaceable"><code>on/off</code></em> </code>.
+ </div></div></div></dd><dt class="varlistentry"><span class="term"> <code class="literal">xmit_hash_policy=<em class="replaceable"><code><value></code></em> </code> </span></dt><dd><div class="para">
+ Selects the transmit hash policy used for slave selection in <strong class="userinput"><code>balance-xor</code></strong> and <strong class="userinput"><code>802.3ad</code></strong> modes. Possible values are:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <strong class="userinput"><code>0</code></strong> or <strong class="userinput"><code>layer2</code></strong> — Default setting. This parameter uses the XOR of hardware MAC addresses to generate the hash. The formula used is:
+ </div><pre class="screen">(<em class="replaceable"><code><source_MAC_address></code></em> XOR <em class="replaceable"><code><destination_MAC></code></em>) MODULO <em class="replaceable"><code><slave_count></code></em>
+</pre><div class="para">
+ This algorithhm will place all traffic to a particular network peer on the same slave, and is 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>1</code></strong> or <strong class="userinput"><code>layer3+4</code></strong> — Uses upper layer protocol information (when available) to generate the hash. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves.
+ </div><div class="para">
+ The formula for unfragmented TCP and UDP packets used is:
+ </div><pre class="screen">((<em class="replaceable"><code><source_port></code></em> XOR <em class="replaceable"><code><dest_port></code></em>) XOR
+ ((<em class="replaceable"><code><source_IP></code></em> XOR <em class="replaceable"><code><dest_IP></code></em>) AND <code class="constant">0xffff</code>)
+ MODULO <em class="replaceable"><code><slave_count></code></em>
+</pre><div class="para">
+ For fragmented TCP or UDP packets and all other IP protocol traffic, the source and destination port information is omitted. For non-IP traffic, the formula is the same as the <code class="command">layer2</code> transmit hash policy.
+ </div><div class="para">
+ This policy intends to mimic the behavior of certain switches; particularly, Cisco switches with PFC2 as well as some Foundry and IBM products.
+ </div><div class="para">
+ The algorithm used by this policy is not 802.3ad compliant.
+ </div></li><li class="listitem"><div class="para">
+ <strong class="userinput"><code>2</code></strong> or <strong class="userinput"><code>layer2+3</code></strong> — Uses a combination of layer2 and layer3 protocol information to generate the hash.
+ </div><div class="para">
+ Uses XOR of hardware MAC addresses and IP addresses to generate the hash. The formula is:
+ </div><pre class="screen">(((<em class="replaceable"><code><source_IP></code></em> XOR <em class="replaceable"><code><dest_IP></code></em>) AND <code class="constant">0xffff</code>) XOR
+ ( <em class="replaceable"><code><source_MAC></code></em> XOR <em class="replaceable"><code><destination_MAC></code></em> ))
+ MODULO <em class="replaceable"><code><slave_count></code></em>
+</pre><div class="para">
+ This algorithm will place all traffic to a particular network peer on the same slave. For non-IP traffic, the formula is the same as for the layer2 transmit hash policy.
+ </div><div class="para">
+ This policy is intended to provide a more balanced distribution of traffic than layer2 alone, especially in environments where a layer3 gateway device is required to reach most destinations.
+ </div><div class="para">
+ This algorithm is 802.3ad compliant.
+ </div></li></ul></div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Specific_Kernel_Module_Capabilities.html"><strong>Prev</strong>22.7. Specific Kernel Module Capabilities</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kernel-modules-additional-resources.html"><strong>Next</strong>22.8. Additional Resources</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Using_Yum_Variables.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Using_Yum_Variables.html
new file mode 100644
index 0000000..e6ed79a
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Using_Yum_Variables.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.3.3. Using Yum Variables</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="1.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Setting_repository_Options.html" title="1.3.2. Setting [repository] Options" /><link rel="next" href="sec-Creating_a_Yum_Repository.html" title="1.3.4. Creating a Yum Repository" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_reposi
tory_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_a_Yum_Repository.html"><strong>Next</strong></a></li></ul><div class="section" title="1.3.3. Using Yum Variables" id="sec-Using_Yum_Variables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Using_Yum_Variables">1.3.3. Using Yum Variables</h3></div></div></div><a id="id733792" class="indexterm"></a><div class="para">
+ You can use and reference the following variables in <code class="command">yum</code> commands and in all <span class="application"><strong>Yum</strong></span> configuration files (<code class="filename">/etc/yum.conf</code> and all <code class="filename">.repo</code> files in <code class="filename">/etc/yum.repos.d/</code>.
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="envar">$releasever</code> </span></dt><dd><div class="para">
+ You can use this variable to reference the release version of Fedora. <span class="application"><strong>Yum</strong></span> obtains the value of <code class="filename">$releasever</code> from the <code class="literal">distroverpkg=<value></code> line in the <code class="filename">/etc/yum.conf</code> configuration file. If there is no such line in <code class="filename">/etc/yum.conf</code>, then <code class="command">yum</code> infers the correct value by deriving the version number from the <code class="filename">redhat-release</code> package.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="envar">$arch</code> </span></dt><dd><div class="para">
+ You can use this variable to refer to the system's CPU architecture as returned when calling Python's <code class="methodname">os.uname()</code> function. Valid values for <code class="envar">$arch</code> include: <code class="literal">i586</code>, <code class="literal">i686</code> and <code class="literal">x86_64</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="envar">$basearch</code> </span></dt><dd><div class="para">
+ You can use <code class="envar">$basearch</code> to reference the base architecture of the system. For example, i686 and i586 machines both have a base architecture of <code class="literal">i386</code>, and AMD64 and Intel64 machines have a base architecture of <code class="literal">x86_64</code>.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="envar">$YUM0-9</code> </span></dt><dd><div class="para">
+ These ten variables are each replaced with the value of any shell environment variables with the same name. If one of these variables is referenced (in <code class="filename">/etc/yum.conf</code> for example) and a shell environment variable with the same name does not exist, then the configuration file variable is not replaced.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_repository_Options.html"><strong>Prev</strong>1.3.2. Setting [repository] Options</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Creating_a_Yum_Repository.html"><strong>Next</strong>1.3.4. Creating a Yum Repository</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
new file mode 100644
index 0000000..ed00e36
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>23.5. Verifying the Initial RAM Disk Image</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 23. Manually Upgrading the Kernel" /><link rel="prev" href="s1-kernel-perform-upgrade.html" title="23.4. Performing the Upgrade" /><link rel="next" href="s1-kernel-boot-loader.html" title="23.6. Verifying the Boot Loader" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-perform-upgrade.html"><strong>Prev</
strong></a></li><li class="next"><a accesskey="n" href="s1-kernel-boot-loader.html"><strong>Next</strong></a></li></ul><div class="section" title="23.5. Verifying the Initial RAM Disk Image" id="sec-Verifying_the_Initial_RAM_Disk_Image"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Verifying_the_Initial_RAM_Disk_Image">23.5. Verifying the Initial RAM Disk Image</h2></div></div></div><a id="id471016" class="indexterm"></a><div class="para">
+ The job of the initial RAM disk image is to preload the block device modules, such as for IDE, SCSI or RAID, so that the root file system, on which those modules normally reside, can then be accessed and mounted. On Fedora 14 systems, whenever a new kernel is installed using either the <span class="application"><strong>Yum</strong></span>, <span class="application"><strong>PackageKit</strong></span>, or <span class="application"><strong>RPM</strong></span> package manager, the <span class="application"><strong>Dracut</strong></span> utility is always called by the installation scripts to create an <em class="firstterm">initramfs</em> (initial RAM disk image).
+ </div><div class="para">
+ On all architectures other than <span class="trademark">IBM</span>® <span class="trademark">eServer</span>™ <span class="trademark">System i</span>™ (see <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html#bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i" title="23.5. Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i">Section 23.5, “Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i”</a>), you can create an <code class="systemitem">initramfs</code> by running the <code class="command">dracut</code> command. However, you usually don't need to create an <code class="systemitem">initramfs</code> manually: this step is automatically performed if the kernel and its associated packages are installed or upgraded from RPM packages distributed by The Fedora Project.
+ </div><div class="para">
+ You can verify that an <code class="systemitem">initramfs</code> corresponding to your current kernel version exists and is specified correctly in the <code class="filename">grub.conf</code> configuration file by following this procedure:
+ </div><div class="procedure" title="Procedure 23.1. Verifying the Initial RAM Disk Image" id="procedure-Verifying_the_Initial_RAM_Disk_Image"><h6>Procedure 23.1. Verifying the Initial RAM Disk Image</h6><ol class="1"><li class="step" title="Step 1"><div class="para">
+ As root, list the contents in the <code class="filename">/boot/</code> directory and find the kernel (<code class="filename">vmlinuz-<em class="replaceable"><code><kernel_version></code></em> </code>) and <code class="filename">initramfs-<em class="replaceable"><code><kernel_version></code></em> </code> with the latest (most recent) version number:
+ </div><div class="example" title="Example 23.1. Ensuring that the kernel and initramfs versions match" id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"><h6>Example 23.1. Ensuring that the kernel and initramfs versions match</h6><div class="example-contents"><pre class="screen">~]# <code class="command">ls /boot/</code>
+config-2.6.32.10-90.fc12.x86_64
+config-2.6.32.11-99.fc12.x86_64
+config-2.6.32.9-70.fc12.x86_64
+efi
+elf-memtest86+-4.00
+grub
+initramfs-2.6.32.10-90.fc12.x86_64.img
+initramfs-2.6.32.11-99.fc12.x86_64.img
+initramfs-2.6.32.9-70.fc12.x86_64.img
+lost+found
+memtest86+-4.00
+System.map-2.6.32.10-90.fc12.x86_64
+System.map-2.6.32.11-99.fc12.x86_64
+System.map-2.6.32.9-70.fc12.x86_64
+vmlinuz-2.6.32.10-90.fc12.x86_64
+vmlinuz-2.6.32.11-99.fc12.x86_64
+vmlinuz-2.6.32.9-70.fc12.x86_64</pre></div></div><br class="example-break" /><div class="para">
+ <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html#ex-Ensuring_that_the_kernel_and_initramfs_versions_match" title="Example 23.1. Ensuring that the kernel and initramfs versions match">Example 23.1, “Ensuring that the kernel and initramfs versions match”</a> shows that:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ we have three kernels installed (or, more correctly, three kernel files are present in <code class="filename">/boot/</code>),
+ </div></li><li class="listitem"><div class="para">
+ the latest kernel is <code class="filename">vmlinuz-2.6.32.10-90.fc12.x86_64</code>, and
+ </div></li><li class="listitem"><div class="para">
+ an <code class="systemitem">initramfs</code> file matching our kernel version, <code class="filename">initramfs-2.6.32.10-90.fc12.x86_64.img</code>, also exists.
+ </div></li></ul></div><div class="important" title="initrd files in the /boot directory are not the same as initramfs files" id="important-initrd_files_in_the__boot_directory_are_not_the_same_as_initramfs_files"><div class="admonition_header"><h2>initrd files in the /boot directory are not the same as initramfs files</h2></div><div class="admonition"><div class="para">
+ In the <code class="filename">/boot/</code> directory you may find several <code class="filename">initrd-<em class="replaceable"><code><version></code></em>kdump.img</code> files. These are special files created by the <span class="application"><strong>Kdump</strong></span> mechanism for kernel debugging purposes, are not used to boot the system, and can safely be ignored.
+ </div></div></div></li><li class="step" title="Step 2"><div class="para">
+ (Optional) If your <code class="filename">initramfs-<em class="replaceable"><code><kernel_version></code></em> </code> file does not match the version of the latest kernel in <code class="filename">/boot/</code>, or, in certain other situations, you may need to generate an <code class="filename">initramfs</code> file with the <span class="application"><strong>Dracut</strong></span> utility. Simply invoking <code class="command">dracut</code> as root without options causes it to generate an <code class="filename">initramfs</code> file in the <code class="filename">/boot/</code> directory for the latest kernel present in that directory:
+ </div><pre class="screen">~]# <code class="command">dracut</code>
+</pre><div class="para">
+ You must use the <code class="option">--force</code> option if you want <code class="command">dracut</code> to overwrite an existing <code class="filename">initramfs</code> (for example, if your <code class="filename">initramfs</code> has become corrupt). Otherwise <code class="command">dracut</code> will refuse to overwrite the existing <code class="filename">initramfs</code> file:
+ </div><pre class="screen">~]# <code class="command">dracut</code>
+Will not override existing initramfs (/boot/initramfs-2.6.32.11-99.fc12.x86_64.img) without --force</pre><div class="para">
+ You can create an initramfs in the current directory by calling <code class="command">dracut <em class="replaceable"><code><initramfs_name></code></em> <em class="replaceable"><code><kernel_version></code></em></code>:
+ </div><pre class="screen">~]# <code class="command">dracut "initramfs-$(uname -r).img" $(uname -r)</code>
+</pre><div class="para">
+ If you need to specify specific kernel modules to be preloaded, add the names of those modules (minus any file name suffixes such as <code class="filename">.ko</code>) inside the parentheses of the <code class="computeroutput">add_dracutmodules="<em class="replaceable"><code><module></code></em> [<span class="optional"><em class="replaceable"><code><more_modules></code></em></span>]"</code> directive of the <code class="filename">/etc/dracut.conf</code> configuration file. You can list the file contents of an <code class="filename">initramfs</code> image file created by dracut by using the <code class="command">lsinitrd <em class="replaceable"><code><initramfs_file></code></em> </code> command:
+ </div><pre class="screen">~]# <code class="command">lsinitrd initramfs-2.6.32.11-99.fc12.x86_64.img</code>
+initramfs-2.6.32.11-99.fc12.x86_64.img:
+========================================================================
+drwxr-xr-x 23 root root 0 Apr 12 05:41 .
+drwxr-xr-x 2 root root 0 Apr 12 05:41 mount
+-rwxr-xr-x 1 root root 934 Jan 15 14:07 mount/99mount-root.sh
+-rwxr-xr-x 1 root root 230 Jan 15 14:07 mount/10resume.sh
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em>
+</pre><div class="para">
+ Refer to <code class="command">man dracut</code> and <code class="command">man dracut.conf</code> for more information on options and usage.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ Examine the <code class="filename">grub.conf</code> configuration file in the <code class="filename">/boot/grub/</code> directory to ensure that an <code class="computeroutput">initrd <code class="filename">initramfs-<em class="replaceable"><code><kernel_version></code></em>.img</code> </code> exists for the kernel version you are booting. Refer to <a class="xref" href="s1-kernel-boot-loader.html" title="23.6. Verifying the Boot Loader">Section 23.6, “Verifying the Boot Loader”</a> for more information.
+ </div></li></ol></div><h3>Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i</h3><a id="id501304" class="indexterm"></a><div class="para">
+ On IBM eSeries System i machines, the initial RAM disk and kernel files are combined into a single file, which is created with the <code class="command">addRamDisk</code> command. This step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by The Fedora Project; thus, it does not need to be executed manually. To verify that it was created, use the command <code class="command">ls -l /boot/</code> to make sure the <code class="filename">/boot/vmlinitrd-<em class="replaceable"><code><kernel_version></code></em> </code> file already exists (the <code class="filename"><em class="replaceable"><code><kernel_version></code></em> </code> should match the version of the kernel just installed).
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-perform-upgrade.html"><strong>Prev</strong>23.4. Performing the Upgrade</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-kernel-boot-loader.html"><strong>Next</strong>23.6. Verifying the Boot Loader</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Viewing_the_Transaction_Log.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Viewing_the_Transaction_Log.html
new file mode 100644
index 0000000..50d4d7b
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Viewing_the_Transaction_Log.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2.2.5. Viewing the Transaction Log</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sec-Using_Add_Remove_Software.html" title="2.2. Using Add/Remove Software" /><link rel="prev" href="sec-Installing_and_Removing_Package_Groups.html" title="2.2.4. Installing and Removing Package Groups" /><link rel="next" href="sec-PackageKit_Architecture.html" title="2.3. PackageKit Architecture" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_and_Remov
ing_Package_Groups.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-PackageKit_Architecture.html"><strong>Next</strong></a></li></ul><div class="section" title="2.2.5. Viewing the Transaction Log" id="sec-Viewing_the_Transaction_Log"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Viewing_the_Transaction_Log">2.2.5. Viewing the Transaction Log</h3></div></div></div><div class="para">
+ <span class="application"><strong>PackageKit</strong></span> maintains a log of the transactions
+ <a id="id490096" class="indexterm"></a>
+ <a id="id490108" class="indexterm"></a>
+ that it performs. To view the log, from the <span class="guilabel"><strong>Add/Remove Software</strong></span> window, click <span class="guimenu"><strong>System</strong></span> → <span class="guimenuitem"><strong>Software log</strong></span>, or run the <code class="command">gpk-log</code> command at the shell prompt.
+ </div><div class="para">
+ The <span class="guilabel"><strong>Software Log Viewer</strong></span> shows the <span class="guilabel"><strong>Action</strong></span>, such as <em class="replaceable"><code>Updated System</code></em> or <em class="replaceable"><code>Installed Packages</code></em>, the <span class="guilabel"><strong>Date</strong></span> on which that action was performed, the <span class="guilabel"><strong>Username</strong></span> of the user who performed the action, and the front end <span class="guilabel"><strong>Application</strong></span> the user used (such as <em class="replaceable"><code>Update Icon</code></em>, or <em class="replaceable"><code>kpackagekit</code></em>). The <span class="guilabel"><strong>Details</strong></span> column provides the types of the transactions, such as <em class="replaceable"><code>Updated</code></em>, <em class="replaceable"><code>Installed</code></em> or <em class="replaceable"><code>Removed</code></em>, as well as the list of packages the transact
ions were performed on.
+ </div><div class="figure" title="Figure 2.10. Viewing the log of package management transactions with the Software Log Viewer" id="fig-Graphical_Package_Management-Software_Log_Viewer"><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/Graphical_Package_Management-Software_Log_Viewer.png" align="middle" width="444" alt="Viewing the log of package management transactions with the Software Log Viewer" /><div class="longdesc"><div class="para">
+ viewing the log of package management transactions with packagekit's loftware log viewer window
+ </div></div></div></div><h6>Figure 2.10. Viewing the log of package management transactions with the Software Log Viewer</h6></div><br class="figure-break" /><div class="para">
+ Typing the name of a package in the top text entry field filters the list of transactions to those which affected that package.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_and_Removing_Package_Groups.html"><strong>Prev</strong>2.2.4. Installing and Removing Package Groups</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-PackageKit_Architecture.html"><strong>Next</strong>2.3. PackageKit Architecture</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Yum_Plugins.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Yum_Plugins.html
new file mode 100644
index 0000000..0d5b379
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sec-Yum_Plugins.html
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>1.4. Yum Plugins</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-yum.html" title="Chapter 1. Yum" /><link rel="prev" href="sec-Creating_a_Yum_Repository.html" title="1.3.4. Creating a Yum Repository" /><link rel="next" href="sec-Installing_More_Yum_Plugins.html" title="1.4.2. Installing More Yum Plugins" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Creating_a_Yum_Repository.html"><strong>Prev</strong></a></li><li class="n
ext"><a accesskey="n" href="sec-Installing_More_Yum_Plugins.html"><strong>Next</strong></a></li></ul><div class="section" title="1.4. Yum Plugins" id="sec-Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sec-Yum_Plugins">1.4. Yum Plugins</h2></div></div></div><a id="id463404" class="indexterm"></a><div class="para">
+ <span class="application"><strong>Yum</strong></span> provides plugins that extend and enhance its operations. Certain plugins are installed by default. <span class="application"><strong>Yum</strong></span> always informs you which plugins, if any, are loaded and active whenever you call any <code class="command">yum</code> command:
+ </div><pre class="screen">
+~]# <code class="command">yum info yum</code>
+Loaded plugins: presto, refresh-packagekit, security
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em>
+</pre><div class="para">
+ Note that the plugin names which follow <code class="command">Loaded plugins</code> are the names you can provide to the <code class="option">--disableplugins=<em class="replaceable"><code><plugin_name></code></em> </code> option.
+ </div><div class="section" title="1.4.1. Enabling, Configuring and Disabling Yum Plugins" id="sec-Enabling_Configuring_and_Disabling_Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sec-Enabling_Configuring_and_Disabling_Yum_Plugins">1.4.1. Enabling, Configuring and Disabling Yum Plugins</h3></div></div></div><a id="id768280" class="indexterm"></a><a id="id768292" class="indexterm"></a><a id="id768304" class="indexterm"></a><div class="para">
+ To enable <span class="application"><strong>Yum</strong></span> plugins, ensure that a line beginning with <code class="command">plugins=</code> is present in the <code class="literal">[main]</code> section of <code class="filename">/etc/yum.conf</code>, and that its value is set to <code class="constant">1</code>:
+ </div><pre class="screen">
+plugins=1
+</pre><div class="para">
+ You can disable all plugins by changing this line to <code class="command">plugins=0</code>.
+ </div><div class="important" title="Disabling plugins is not advised" id="important-Disabling_plugins_is_not_advised-plugins"><div class="admonition_header"><h2>Disabling plugins is not advised</h2></div><div class="admonition"><div class="para">
+ Disabling all plugins is not advised because certain plugins provide important <code class="command">Yum</code> services. In particular, <span class="application"><strong>rhnplugin</strong></span> enables connecting to <code class="systemitem">Red Hat Network</code>, and the security plugin allows system administrators to easily update the system with (sometimes critical) security updates. Disabling plugins globally is provided as a convenience option, and is generally only recommended when diagnosing a potential problem with <code class="command">Yum</code>.
+ </div></div></div><div class="para">
+ Every installed plugin has its own configuration file in the <code class="filename">/etc/yum/pluginconf.d/</code> directory. You can set plugin-specific options in these files. For example, here is the <span class="application"><strong>security</strong></span> plugin's <code class="filename">security.conf</code> configuration file:
+ </div><div class="example" title="Example 1.7. A minimal Yum plugin configuration file" id="ex-A_minimal_Yum_plugin_configuration_file"><h6>Example 1.7. A minimal <span class="application">Yum</span> plugin configuration file</h6><div class="example-contents"><pre class="screen">
+[main]
+enabled=1
+</pre></div></div><br class="example-break" /><div class="para">
+ Plugin configuration files always contain a <code class="literal">[main]</code> section (similar to <span class="application"><strong>Yum</strong></span>'s <code class="filename">/etc/yum.conf</code> file) in which there is (or you can place if it is missing) an <code class="literal">enabled=</code> option that controls whether the plugin is enabled when you run <code class="command">yum</code> commands.
+ </div><div class="para">
+ If you disable all plugins by setting <code class="command">enabled=0</code> in <code class="filename">/etc/yum.conf</code>, then all plugins are disabled regardless of whether they are enabled in their individual configuration files.
+ </div><div class="para">
+ If you merely want to disable all <span class="application"><strong>Yum</strong></span> plugins for a single <code class="command">yum</code> command, use the <code class="option">--noplugins</code> option.
+ </div><div class="para">
+ If you simply want to disable one or more <span class="application"><strong>Yum</strong></span> plugins for a single <code class="command">yum</code> command, then you can add the <code class="option">--disableplugin=<plugin_name></code> option to the command:
+ </div><div class="example" title="Example 1.8. Disabling the presto plugin while running yum update" id="ex-Disabling_the_presto_plugin_while_running_yum_update"><h6>Example 1.8. Disabling the presto plugin while running yum update</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum update --disableplugin=presto</code>
+</pre></div></div><br class="example-break" /><div class="para">
+ The plugin names you provide to the <code class="option">--disableplugin=</code> option are the same names listed after the <code class="command">Loaded plugins:</code> line in the output of any <code class="command">yum</code> command. You can disable multiple plugins by separating their names with commas. In addition, you can match multiple similarly-named plugin names or simply shorten long ones by using glob expressions: <code class="option">--disableplugin=presto,refresh-pack*</code>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Creating_a_Yum_Repository.html"><strong>Prev</strong>1.3.4. Creating a Yum Repository</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sec-Installing_More_Yum_Plugins.html"><strong>Next</strong>1.4.2. Installing More Yum Plugins</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html
new file mode 100644
index 0000000..f74fd59
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-Configuring_a_Multihomed_DHCP_Server.html
@@ -0,0 +1,131 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>6.4. Configuring a Multihomed DHCP Server</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="ch-Dynamic_Host_Configuration_Protocol_DHCP.html" title="Chapter 6. Dynamic Host Configuration Protocol (DHCP)" /><link rel="prev" href="s1-dhcp-configuring-client.html" title="6.3. Configuring a DHCP Client" /><link rel="next" href="s1-dhcp_for_ipv6_dhcpv6.html" title="6.5. DHCP for IPv6 (DHCPv6)" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp-configuring-cl
ient.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-dhcp_for_ipv6_dhcpv6.html"><strong>Next</strong></a></li></ul><div class="section" title="6.4. Configuring a Multihomed DHCP Server" id="sect-Configuring_a_Multihomed_DHCP_Server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Configuring_a_Multihomed_DHCP_Server">6.4. Configuring a Multihomed DHCP Server</h2></div></div></div><a id="id469477" class="indexterm"></a><div class="para">
+ A multihomed DHCP server serves multiple networks, that is, multiple subnets. The examples in these sections detail how to configure a DHCP server to serve multiple networks, select which network interfaces to listen on, and how to define network settings for systems that move networks.
+ </div><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/sysconfig/dhcpd</code> and <code class="filename">/etc/dhcp/dhcpd.conf</code> files.
+ </div><div class="para">
+ The DHCP daemon listens on all network interfaces unless otherwise specified. Use the <code class="filename">/etc/sysconfig/dhcpd</code> file to specify which network interfaces the DHCP daemon listens on. The following <code class="filename">/etc/sysconfig/dhcpd</code> example specifies that the DHCP daemon listens on the <code class="filename">eth0</code> and <code class="filename">eth1</code> interfaces:
+ </div><pre class="screen">
+DHCPDARGS="eth0 eth1";
+</pre><div class="para">
+ If a system has three network interfaces cards -- <code class="filename">eth0</code>, <code class="filename">eth1</code>, and <code class="filename">eth2</code> -- and it is only desired that the DHCP daemon listens on <code class="filename">eth0</code>, then only specify <code class="computeroutput">eth0</code> in <code class="filename">/etc/sysconfig/dhcpd</code>:
+ </div><pre class="screen">
+DHCPDARGS="eth0";
+</pre><div class="para">
+ The following is a basic <code class="filename">/etc/dhcp/dhcpd.conf</code> file, for a server that has two network interfaces, <code class="filename">eth0</code> in a 10.0.0.0/24 network, and <code class="filename">eth1</code> in a 172.16.0.0/24 network. Multiple <code class="computeroutput">subnet</code> declarations allow different settings to be defined for multiple networks:
+ </div><pre class="screen">
+default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}
+</pre><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="computeroutput">subnet <em class="replaceable"><code>10.0.0.0</code></em> netmask <em class="replaceable"><code>255.255.255.0</code></em>;</code> </span></dt><dd><div class="para">
+ A <code class="computeroutput">subnet</code> declaration is required for every network your DHCP server is serving. Multiple subnets require multiple <code class="computeroutput">subnet</code> declarations. If the DHCP server does not have a network interface in a range of a <code class="computeroutput">subnet</code> declaration, the DHCP server does not serve that network.
+ </div><div class="para">
+ If there is only one <code class="computeroutput">subnet</code> declaration, and no network interfaces are in the range of that subnet, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="screen">
+dhcpd: No subnet declaration for eth0 (0.0.0.0).
+dhcpd: ** Ignoring requests on eth0. If this is not what
+dhcpd: you want, please write a subnet declaration
+dhcpd: in your dhcpd.conf file for the network segment
+dhcpd: to which interface eth1 is attached. **
+dhcpd:
+dhcpd:
+dhcpd: Not configured to listen on any interfaces!
+</pre></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">option subnet-mask <em class="replaceable"><code>255.255.255.0</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">option subnet-mask</code> option defines a subnet mask, and overrides the <code class="computeroutput">netmask</code> value in the <code class="computeroutput">subnet</code> declaration. In simple cases, the subnet and netmask values are the same.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">option routers <em class="replaceable"><code>10.0.0.1</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">option routers</code> option defines the default gateway for the subnet. This is required for systems to reach internal networks on a different subnet, as well as external networks.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">range <em class="replaceable"><code>10.0.0.5</code></em> <em class="replaceable"><code>10.0.0.15</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">range</code> option specifies the pool of available IP addresses. Systems are assigned an address from the range of specified IP addresses.
+ </div></dd></dl></div><div class="para">
+ For further information, refer to the <code class="computeroutput">dhcpd.conf(5)</code> man page.
+ </div><div class="warning" title="Alias Interfaces"><div class="admonition_header"><h2>Alias Interfaces</h2></div><div class="admonition"><div class="para">
+ Alias interfaces are not supported by DHCP. If an alias interface is the only interface, in the only subnet specified in <code class="filename">/etc/dhcp/dhcpd.conf</code>, the DHCP daemon fails to start.
+ </div></div></div><div class="section" title="6.4.1. Host Configuration" id="sect-dns_Host_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-dns_Host_Configuration">6.4.1. Host Configuration</h3></div></div></div><a id="id835481" class="indexterm"></a><div class="para">
+ Before making any changes, back up the existing <code class="filename">/etc/sysconfig/dhcpd</code> and <code class="filename">/etc/dhcp/dhcpd.conf</code> files.
+ </div><div class="formalpara"><h5 class="formalpara" id="id835507">Configuring a single system for multiple networks</h5>
+ The following <code class="filename">/etc/dhcp/dhcpd.conf</code> example creates two subnets, and configures an IP address for the same system, depending on which network it connects to:
+ </div><pre class="screen">
+default-lease-time <em class="replaceable"><code>600</code></em>;
+max-lease-time <em class="replaceable"><code>7200</code></em>;
+subnet 10.0.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 10.0.0.1;
+ range 10.0.0.5 10.0.0.15;
+}
+subnet 172.16.0.0 netmask 255.255.255.0 {
+ option subnet-mask 255.255.255.0;
+ option routers 172.16.0.1;
+ range 172.16.0.5 172.16.0.15;
+}
+host example0 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 10.0.0.20;
+}
+host example1 {
+ hardware ethernet 00:1A:6B:6A:2E:0B;
+ fixed-address 172.16.0.20;
+}
+</pre><div class="variablelist"><dl><dt class="varlistentry"><span class="term"> <code class="computeroutput">host <em class="replaceable"><code>example0</code></em> </code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">host</code> declaration defines specific parameters for a single system, such as an IP address. To configure specific parameters for multiple hosts, use multiple <code class="computeroutput">host</code> declarations.
+ </div><div class="para">
+ Most DHCP clients ignore the name in <code class="computeroutput">host</code> declarations, and as such, this name can anything, as long as it is unique to other <code class="computeroutput">host</code> declarations. To configure the same system for multiple networks, use a different name for each <code class="computeroutput">host</code> declaration, otherwise the DHCP daemon fails to start. Systems are identified by the <code class="computeroutput">hardware ethernet</code> option, not the name in the <code class="computeroutput">host</code> declaration.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">hardware ethernet <em class="replaceable"><code>00:1A:6B:6A:2E:0B</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">hardware ethernet</code> option identifies the system. To find this address, run the <code class="command">ip link</code> command.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="computeroutput">fixed-address <em class="replaceable"><code>10.0.0.20</code></em>;</code> </span></dt><dd><div class="para">
+ The <code class="computeroutput">fixed-address</code> option assigns a valid IP address to the system specified by the <code class="computeroutput">hardware ethernet</code> option. This address must be outside the IP address pool specified with the <code class="computeroutput">range</code> option.
+ </div></dd></dl></div><div class="para">
+ If <code class="computeroutput">option</code> statements do not end with a semicolon, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="screen">
+/etc/dhcp/dhcpd.conf line 20: semicolon expected.
+dhcpd: }
+dhcpd: ^
+dhcpd: /etc/dhcp/dhcpd.conf line 38: unexpected end of file
+dhcpd:
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting
+</pre><div class="formalpara"><h5 class="formalpara" id="id786799">Configuring systems with multiple network interfaces</h5>
+ The following <code class="computeroutput">host</code> declarations configure a single system, that has multiple network interfaces, so that each interface receives the same IP address. This configuration will not work if both network interfaces are connected to the same network at the same time:
+ </div><pre class="screen">
+host interface0 {
+ hardware ethernet 00:1a:6b:6a:2e:0b;
+ fixed-address 10.0.0.18;
+}
+host interface1 {
+ hardware ethernet 00:1A:6B:6A:27:3A;
+ fixed-address 10.0.0.18;
+}
+</pre><div class="para">
+ For this example, <code class="computeroutput">interface0</code> is the first network interface, and <code class="computeroutput">interface1</code> is the second interface. The different <code class="computeroutput">hardware ethernet</code> options identify each interface.
+ </div><div class="para">
+ If such a system connects to another network, add more <code class="computeroutput">host</code> declarations, remembering to:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ assign a valid <code class="computeroutput">fixed-address</code> for the network the host is connecting to.
+ </div></li><li class="listitem"><div class="para">
+ make the name in the <code class="computeroutput">host</code> declaration unique.
+ </div></li></ul></div><div class="para">
+ When a name given in a <code class="computeroutput">host</code> declaration is not unique, the DHCP daemon fails to start, and an error such as the following is logged to <code class="filename">/var/log/messages</code>:
+ </div><pre class="screen">
+dhcpd: /etc/dhcp/dhcpd.conf line 31: host interface0: already exists
+dhcpd: }
+dhcpd: ^
+dhcpd: Configuration file errors encountered -- exiting
+</pre><div class="para">
+ This error was caused by having multiple <code class="computeroutput">host interface0</code> declarations defined in <code class="filename">/etc/dhcp/dhcpd.conf</code>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-dhcp-configuring-client.html"><strong>Prev</strong>6.3. Configuring a DHCP Client</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="s1-dhcp_for_ipv6_dhcpv6.html"><strong>Next</strong>6.5. DHCP for IPv6 (DHCPv6)</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html
new file mode 100644
index 0000000..6db8332
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2.2. Network Time Protocol Setup</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html" title="13.2. Command Line Configuration" /><link rel="prev" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html" title="13.2. Command Line Configuration" /><link rel="next" href="ch-Keyboard_Configuration.html" title="Chapter 14. Keyboard Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a acc
esskey="p" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Keyboard_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="13.2.2. Network Time Protocol Setup" id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol">13.2.2. Network Time Protocol Setup</h3></div></div></div><a id="id703000" class="indexterm"></a><a id="id485815" class="indexterm"></a><a id="id485829" class="indexterm"></a><a id="id485845" class="indexterm"></a><div class="para">
+ As opposed to the manual setup described above, you can also synchronize the system clock with a remote server over the Network Time Protocol (<acronym class="acronym">NTP</acronym>). For the one-time synchronization only, use the <span class="application"><strong>ntpdate</strong></span> command:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Firstly, check whether the selected NTP server is accessible:
+ </div><pre class="screen">~]# <code class="command">ntpdate -q <em class="replaceable"><code>server_address</code></em></code></pre><div class="para">
+ For example:
+ </div><pre class="screen">~]# <code class="command">ntpdate -q 0.rhel.pool.ntp.org</code></pre></li><li class="step" title="Step 2"><div class="para">
+ When you find a satisfactory server, run the <span class="application"><strong>ntpdate</strong></span> command followed with on or more server addresses:
+ </div><pre class="screen">~]# <code class="command">ntpdate <em class="replaceable"><code>server_address...</code></em></code></pre><div class="para">
+ For instance:
+ </div><pre class="screen">~]# <code class="command">ntpdate 0.rhel.pool.ntp.org 1.rhel.pool.ntp.org</code></pre><div class="para">
+ Unless an error message is displayed, the system time should now be set. You can check the current by setting typing <code class="command">date</code> without any additional arguments as shown in <a class="xref" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html#sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time" title="13.2.1. Date and Time Setup">Section 13.2.1, “Date and Time Setup”</a>.
+ </div></li><li class="step" title="Step 3"><div class="para">
+ In most cases, these steps are sufficient. Only if you really need one or more system services to always use the correct time, enable running the <span class="application"><strong>ntpdate</strong></span> at boot time:
+ </div><pre class="screen">~]# <code class="command">chkconfig ntpdate on</code></pre><div class="para">
+ For more information about system services and their setup, see <a class="xref" href="ch-Controlling_Access_to_Services.html" title="Chapter 7. Controlling Access to Services">Chapter 7, <i>Controlling Access to Services</i></a>.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ If the synchronization with the time server at boot time keeps failing, i.e., you find a relevant error message in the <code class="filename">/var/log/boot.log</code> system log, try to add the following line to <code class="filename">/etc/sysconfig/network</code>:
+ </div><pre class="screen">NETWORKWAIT=1</pre></div></div></li></ol></div><a id="id762308" class="indexterm"></a><a id="id689808" class="indexterm"></a><a id="id689825" class="indexterm"></a><div class="para">
+ However, the more convenient way is to set the <span class="application"><strong>ntpd</strong></span> daemon to synchronize the time at boot time automatically:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ Open the NTP configuration file <code class="filename">/etc/ntp.conf</code> in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, or create a new one if it does not already exist:
+ </div><pre class="screen">~]# <code class="command">nano /etc/ntp.conf</code></pre></li><li class="step" title="Step 2"><div class="para">
+ Now add or edit the list of public NTP servers. If you are using Fedora 14, the file should already contain the following lines, but feel free to change or expand these according to your needs:
+ </div><pre class="screen">server 0.rhel.pool.ntp.org
+server 1.rhel.pool.ntp.org
+server 2.rhel.pool.ntp.org</pre><div class="note" title="Tip"><div class="admonition_header"><h2>Tip</h2></div><div class="admonition"><div class="para">
+ To speed the initial synchronization up, add the <code class="command">iburst</code> directive at the end of each server line:
+ </div><pre class="screen">server 0.rhel.pool.ntp.org iburst
+server 1.rhel.pool.ntp.org iburst
+server 2.rhel.pool.ntp.org iburst</pre></div></div></li><li class="step" title="Step 3"><div class="para">
+ Once you have the list of servers complete, in the same file, set the proper permissions, giving the unrestricted access to localhost only:
+ </div><pre class="screen">restrict default kod nomodify notrap nopeer noquery
+restrict -6 default kod nomodify notrap nopeer noquery
+restrict 127.0.0.1
+restrict -6 ::1</pre></li><li class="step" title="Step 4"><div class="para">
+ Save all changes, exit the editor, and restart the NTP daemon:
+ </div><pre class="screen">~]# <code class="command">service ntpd restart</code></pre></li><li class="step" title="Step 5"><div class="para">
+ Make sure that <code class="command">ntpd</code> daemon is started at boot time:
+ </div><pre class="screen">~]# <code class="command">chkconfig ntpd on</code></pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Date_and_Time_Configuration-Command_Line_Configuration.html"><strong>Prev</strong>13.2. Command Line Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-Keyboard_Configuration.html"><strong>Next</strong>Chapter 14. Keyboard Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration.html
new file mode 100644
index 0000000..1cc5b52
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-Date_and_Time_Configuration-Command_Line_Configuration.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>13.2. Command Line Configuration</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-Date_and_Time_Configuration.html" title="Chapter 13. Date and Time Configuration" /><link rel="prev" href="chap-Date_and_Time_Configuration.html" title="Chapter 13. Date and Time Configuration" /><link rel="next" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html" title="13.2.2. Network Time Protocol Setup" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class
="previous"><a accesskey="p" href="chap-Date_and_Time_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html"><strong>Next</strong></a></li></ul><div class="section" title="13.2. Command Line Configuration" id="sect-Date_and_Time_Configuration-Command_Line_Configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-Date_and_Time_Configuration-Command_Line_Configuration">13.2. Command Line Configuration</h2></div></div></div><div class="para">
+ In case your system does not have the <span class="application"><strong>Date/Time Properties</strong></span> tool installed, or the <span class="emphasis"><em>X Window Server</em></span> is not running, you will have to change the system date and time on the command line. Note that in order to perform actions described in this section, you have to be logged in as a superuser:
+ </div><pre class="screen">~]$ <code class="command">su -</code>
+Password:</pre><div class="section" title="13.2.1. Date and Time Setup" id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time">13.2.1. Date and Time Setup</h3></div></div></div><a id="id543038" class="indexterm"></a><a id="id543056" class="indexterm"></a><a id="id453260" class="indexterm"></a><div class="para">
+ The <code class="command">date</code> command allows the superuser to set the system date and time manually:
+ </div><div class="procedure"><ol class="1"><li class="step" title="Step 1"><div class="para">
+ <span class="emphasis"><em>Change the current date.</em></span> Type the command in the following form at a shell prompt, replacing the <em class="replaceable"><code>YYYY</code></em> with a four-digit year, <em class="replaceable"><code>MM</code></em> with a two-digit month, and <em class="replaceable"><code>DD</code></em> with a two-digit day of the month:
+ </div><pre class="screen">~]# <code class="command">date +%D -s <em class="replaceable"><code>YYYY-MM-DD</code></em></code></pre><div class="para">
+ For example, to set the date to 2 June 2010, type:
+ </div><pre class="screen">~]# <code class="command">date +%D -s 2010-06-02</code></pre></li><li class="step" title="Step 2"><div class="para">
+ <span class="emphasis"><em>Change the current time.</em></span> Use the following command, where <em class="replaceable"><code>HH</code></em> stands for an hour, <em class="replaceable"><code>MM</code></em> is a minute, and <em class="replaceable"><code>SS</code></em> is a second, all typed in a two-digit form:
+ </div><pre class="screen">~]# <code class="command">date +%T -s <em class="replaceable"><code>HH:MM:SS</code></em></code></pre><div class="para">
+ If your system clock is set to use <acronym class="acronym">UTC</acronym> (Coordinated Universal Time), add the following option:
+ </div><pre class="screen">~]# <code class="command">date +%T -s <em class="replaceable"><code>HH:MM:SS</code></em> -u</code></pre><div class="para">
+ For instance, to set the system clock to 11:26 PM using the <acronym class="acronym">UTC</acronym>, type:
+ </div><pre class="screen">~]# <code class="command">date +%T -s 23:26:00 -u</code></pre></li></ol></div><div class="para">
+ You can check your current settings by typing <code class="command">date</code> without any additional argument:
+ </div><div class="example" title="Example 13.1. Displaying the current date and time" id="ex-Date_and_Time_Configuration-Command_Line_Configuration-Date_and_Time"><h6>Example 13.1. Displaying the current date and time</h6><div class="example-contents"><pre class="screen">~]$ <code class="command">date</code>
+Wed Jun 2 11:58:48 CEST 2010</pre></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-Date_and_Time_Configuration.html"><strong>Prev</strong>Chapter 13. Date and Time Configuration</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="sect-Date_and_Time_Configuration-Command_Line_Configuration-Network_Time_Protocol.html"><strong>Next</strong>13.2.2. Network Time Protocol Setup</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-RedHat-We_Need_Feedback.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-RedHat-We_Need_Feedback.html
new file mode 100644
index 0000000..23eff14
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-RedHat-We_Need_Feedback.html
@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>2. We Need Feedback!</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="pr01.html" title="Preface" /><link rel="prev" href="pr01.html" title="Preface" /><link rel="next" href="Acknowledgements.html" title="3. Acknowledgements" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="Acknowledgements.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="se
ction" title="2. We Need Feedback!" id="sect-RedHat-We_Need_Feedback" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="sect-RedHat-We_Need_Feedback">2. We Need Feedback!</h2></div></div></div><a id="id648775" class="indexterm"></a><div class="para">
+ If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: <a href="http://bugzilla.redhat.com/">http://bugzilla.redhat.com/</a> against the product <span class="application"><strong>Fedora Documentation.</strong></span>
+ </div><div class="para">
+ When submitting a bug report, be sure to mention the manual's identifier: <em class="citetitle">deployment-guide</em> and version number: <code class="literal">14</code>.
+ </div><div class="para">
+ If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
+ </div><div class="section" title="2.1. Technical Review Requests"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="id834087">2.1. Technical Review Requests</h3></div></div></div><div class="para">
+ All review requests are classified into one of the following five categories:
+ </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">New Content</span></dt><dd><div class="para">
+ content documented for the first time — an entirely new feature, procedure, or concept. For example: "Section now describes the new procedure for creating bootable USB devices."
+ </div></dd><dt class="varlistentry"><span class="term">Correction</span></dt><dd><div class="para">
+ a factual error previously present in the text has been corrected. For example: "Section previously stated (incorrectly) that IPv4 and IPv6 were both supported; section now states that IPv6 has never been supported."
+ </div></dd><dt class="varlistentry"><span class="term">Clarification</span></dt><dd><div class="para">
+ material that was already factually correct but is now better explained. Clarifications are usually in response to reader feedback that the previous content was confusing or misleading in some way. For example: "Paths described in Example 1.2.3 now better reflect the directory structure of an actual installed system."
+ </div></dd><dt class="varlistentry"><span class="term">Obsoletion</span></dt><dd><div class="para">
+ a description of a feature or a procedure has been dropped. Material might be obsolete because of a feature that is no longer supported, a known issue that has been corrected, or hardware that is now obsolete. For example, "Section no longer describes how to update kernel modules using a floppy disk."
+ </div></dd><dt class="varlistentry"><span class="term">Verification</span></dt><dd><div class="para">
+ a request to check a fact, procedure, or whether material should be obsoleted. For example, "Section describes how to connect to a generic iSCSI storage device. Please verify this on your hardware" or "Section still describes how to update kernel modules using a LS-120 SuperDisk; please verify that we still need to tell readers about this obsolete hardware."
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01.html"><strong>Prev</strong>Preface</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="Acknowledgements.html"><strong>Next</strong>3. Acknowledgements</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html
new file mode 100644
index 0000000..1527f33
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.6. Setting Up Kerberos Authentication</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Configuring_Domains.html" title="8.2.5. Configuring Domains" /><link rel="next" href="chap-SSSD_User_Guide-Troubleshooting.html" title="8.2.7. Troubleshooting" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-
Configuring_Domains.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Troubleshooting.html"><strong>Next</strong></a></li></ul><div class="section" title="8.2.6. Setting Up Kerberos Authentication" id="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-SSSD_User_Guide-Configuring_Domains-Setting_up_Kerberos_Authentication">8.2.6. Setting Up Kerberos Authentication</h3></div></div></div><a id="id648675" class="indexterm"></a><div class="para">
+ In order to set up Kerberos authentication, you need to know the address of your <em class="firstterm">key distribution center</em> (KDC) and the Kerberos domain. The client configuration is then stored in the <code class="filename">/etc/sssd/sssd.conf</code> file.
+ </div><div class="para">
+ The Kerberos 5 authentication back end does not contain an identity provider and must be paired with one in order to function properly (for example, <code class="option">id_provider = ldap</code>). Some information required by the Kerberos 5 authentication back end must be supplied by the identity provider, such as the user's <em class="firstterm">Kerberos Principal Name</em> (UPN). The identity provider configuration should contain an entry to specify this UPN. Refer to the manual page for the applicable identity provider for details on how to configure the UPN.
+ </div><div class="para">
+ If the UPN is not available in the identity back end, SSSD will construct a UPN using the format <code class="systemitem">username at krb5_realm</code>.
+ </div><div class="para">
+ SSSD assumes that the Kerberos KDC is also a Kerberos kadmin server. However, it is very common for production environments to have multiple, read-only replicas of the KDC, but only a single kadmin server (because password changes and similar procedures are comparitively rare). To manage this type of configuration, you can use the <code class="option">krb5_kpasswd</code> option to specify where your password changing service is running, or if it is running on a non-default port. Refer to the <em class="citetitle">sssd-krb5(5)</em> manual page for more information about this and all Kerberos configuration options.
+ </div><div class="formalpara" id="form-SSSD_User_Guide-Setting_Up_Kerberos_Authentication-How_to_Set_up_Kerberos_Authentication"><h5 class="formalpara">How to Set Up Kerberos Authentication</h5>
+ Edit your <code class="filename">/etc/sssd/sssd.conf</code> file to reflect the following example:
+ </div><pre class="screen"># A domain with identities provided by LDAP and authentication by Kerberos
+[domain/KRBDOMAIN]
+enumerate = false
+id_provider = ldap
+chpass_provider = krb5
+ldap_uri = ldap://ldap.mydomain.org
+ldap_search_base = dc=mydomain,dc=org
+tls_reqcert = demand
+ldap_tls_cacert = /etc/pki/tls/certs/ca-bundle.crt
+
+auth_provider = krb5
+krb5_kdcip = 192.168.1.1
+krb5_realm = EXAMPLE.COM
+krb5_changepw_principal = kadmin/changepw
+krb5_ccachedir = /tmp
+krb5_ccname_template = FILE:%d/krb5cc_%U_XXXXXX
+krb5_auth_timeout = 15
+</pre><div class="para">
+ This example describes the minimum options that must be configured when using Kerberos authentication. Refer to the <em class="citetitle">sssd-krb5(5)</em> manual page for a full description of all the options that apply to configuring Kerberos authentication.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Configuring_Domains.html"><strong>Prev</strong>8.2.5. Configuring Domains</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Troubleshooting.html"><strong>Next</strong>8.2.7. Troubleshooting</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.html
new file mode 100644
index 0000000..2657248
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-SSSD_User_Guide-Introduction-SSSD_Features.html
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.2. SSSD Features</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System Security Services Daemon (SSSD)" /><link rel="next" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html" title="8.2.3. Setting Up SSSD" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SS
SD_User_Guide-Introduction.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html"><strong>Next</strong></a></li></ul><div class="section" title="8.2.2. SSSD Features" id="sect-SSSD_User_Guide-Introduction-SSSD_Features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-SSSD_User_Guide-Introduction-SSSD_Features">8.2.2. SSSD Features</h3></div></div></div><div class="section" title="8.2.2.1. Offline Authentication" id="sect-SSSD_User_Guide-SSSD_Features-Offline_Authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Offline_Authentication">8.2.2.1. Offline Authentication</h4></div></div></div><div class="para">
+ One of the primary benefits of SSSD is offline authentication. This solves the case of users having a separate corporate account and a local machine account because of the common requirement to implement a Virtual Private Network (<abbr class="abbrev">VPN</abbr>).
+ </div><div class="para">
+ SSSD can cache remote identities and authentication credentials. This means that you can still authenticate with these remote identities even when a machine is offline. In an SSSD system, you only need to manage one account.
+ </div></div><div class="section" title="8.2.2.2. Server Load Reduction" id="sect-SSSD_User_Guide-SSSD_Features-Server_Load_Reduction"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Server_Load_Reduction">8.2.2.2. Server Load Reduction</h4></div></div></div><div class="para">
+ The use of SSSD also helps to reduce the load on identification servers. For example, using <span class="package">nss_ldap</span>, every client application that needs to request user information opens its own connection to the LDAP server. Managing these multiple connections can lead to a heavy load on the LDAP server. In an SSSD system, only the SSSD Data Provider process actually communicates with the LDAP server, reducing the load to one connection per client system.
+ </div></div><div class="section" title="8.2.2.3. Support for Multiple Domains" id="sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Support_for_Multiple_Domains">8.2.2.3. Support for Multiple Domains</h4></div></div></div><a id="id480078" class="indexterm"></a><div class="para">
+ You can use SSSD to specify multiple domains of the same type. Compare this to an <code class="filename">nsswitch.conf</code> file configuration, with which you can only request user information from a single server of any particular type (LDAP, NIS, etc.). With SSSD, you can create multiple domains of the same, or of different types of identity provider.
+ </div><div class="para">
+ Beginning with version 0.6.0, SSSD maintains a separate database file for each domain. This means that each domain has its own cache, and in the event that problems occur and maintenance is necessary, it is very easy to purge the cache for a single domain, by stopping <code class="systemitem">sssd</code> and deleting the corresponding cache file. These cache files are stored in the <code class="filename">/var/lib/sss/db/</code> directory.
+ </div><div class="para">
+ All cache files are named according to the domain that they represent, for example <code class="filename">cache_<em class="replaceable"><code>DOMAINNAME</code></em>.ldb</code>.
+ </div><div class="formalpara"><h5 class="formalpara" id="id791543">Considerations Associated with Deleting Cache Files</h5><a id="id791535" class="indexterm"></a>
+ Deleting a domain's cache file can have some unexpected side effects. You should be aware of the following before you proceed:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Deleting the cache file also deletes all user data (both identification and cached credentials). Consequently, you should not proceed unless you are online and can authenticate with your username against the domain's servers, because offline authentication will fail.
+ </div></li><li class="listitem"><div class="para">
+ If you are online and change your configuration to reference a different identity provider, SSSD will recognize users from both providers until the cached entries from the original provider time out.
+ </div><div class="para">
+ To avoid this situation, you can either purge the cache or use a different domain name for the new provider (this is the recommended practice). Changing the domain name means that when you restart SSSD it will create a new cache file (with the new name) and the old file will be ignored.
+ </div></li></ul></div></div><div class="section" title="8.2.2.4. Support for LDAP Referrals"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="id791483">8.2.2.4. Support for LDAP Referrals</h4></div></div></div><div class="para">
+ SSSD supports two types of LDAP referrals: object-level referrals and subtree referrals. These referral types and the extent of SSSD support is outlined below.
+ </div><div class="section" title="8.2.2.4.1. Object-level Referrals"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id791471">8.2.2.4.1. Object-level Referrals</h5></div></div></div><div class="para">
+ SSSD provides full support for object-level referrals within the same LDAP server, correctly handling any differences in the distinguished name (DN) that might exist as part of the LDAP server referral configuration.
+ </div><div class="para">
+ SSSD provides partial support for object-level referrals between different LDAP servers, and requires that the full DN of an LDAP request be identical on each server. SSSD does not support referrals to different DN paths on other servers.
+ </div></div><div class="section" title="8.2.2.4.2. Subtree Referrals"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id468270">8.2.2.4.2. Subtree Referrals</h5></div></div></div><div class="para">
+ SSSD provides a similar level of support for subtree referrals as it does for object-level referrals. That is, it supports referrals to a changed DN on the local system or to an identical DN on a remote system. The difference with subtree referrals, however, is the ability to set up identical subtrees on each LDAP server and to then configure referrals between these subtrees.
+ </div></div><div class="section" title="8.2.2.4.3. Enabling LDAP Referrals"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id791406">8.2.2.4.3. Enabling LDAP Referrals</h5></div></div></div><div class="para">
+ To take advantage of the SSSD LDAP referral functionality, you need to set the <code class="option">ldap_referrals</code> option to <code class="literal">TRUE</code> in the LDAP domain configuration section of the <code class="filename">/etc/sssd/sssd.conf</code> file. This will enable anonymous access to the second LDAP server.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ SSSD only supports LDAP referrals when it is compiled with OpenLDAP version 2.4.13 or later.
+ </div></div></div></div></div><div class="section" title="8.2.2.5. Differentiating Like-named Users" id="sect-SSSD_User_Guide-SSSD_Features-Differentiating_Like_named_Users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Differentiating_Like_named_Users">8.2.2.5. Differentiating Like-named Users</h4></div></div></div><div class="para">
+ SSSD supports the differentiation of like-named users in different domains. For example, you can differentiate the user <code class="systemitem">kate</code> in the <code class="systemitem">ldap.example.com</code> domain from the user <code class="systemitem">kate</code> in the <code class="systemitem">ldap.myhome.com</code> domain. You can use SSSD to make requests using fully-qualified usernames. If you request information for <code class="systemitem">kate</code>, you will receive the information from whichever domain is listed first in the look-up order. If you request information for <code class="systemitem">kate at ldap.myhome.com</code>, however, you will receive the correct user information.
+ </div><div class="para">
+ SSSD also provides a <code class="option">filter_users</code> option, which you can use to exclude certain users from being fetched from the database. Refer to the <em class="citetitle">sssd.conf(5)</em> manual page for full details about this option.
+ </div></div><div class="section" title="8.2.2.6. Integration with IPA" id="sect-SSSD_User_Guide-SSSD_Features-Integration_with_IPA"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="sect-SSSD_User_Guide-SSSD_Features-Integration_with_IPA">8.2.2.6. Integration with IPA</h4></div></div></div><div class="para">
+ Beyond the offline authentication, multiple domain management and other features already described, SSSD is also designed to integrate with and enhance the functionality of IPA clients. In an environment with the latest version of IPA installed, SSSD provides additional functionality, including support for dynamic DNS updates, host-based access control, and password migration from an LDAP-only environment into the LDAP/Kerberos 5 environment employed by IPA.
+ </div><div class="section" title="8.2.2.6.1. Support for Dynamic DNS Updates"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title" id="id759490">8.2.2.6.1. Support for Dynamic DNS Updates</h5></div></div></div><div class="para">
+ Because the IP address of IPA clients can change, SSSD provides the ability to dynamically update the client's DNS entry on the IPA server. Using a combination of Kerberos and GSS-TSIG (Generic Security Service Algorithm for Secret Key Transaction), IPA can determine the identity of the host machine, authenticate it, and allow that machine to edit its own DNS record. These changes are then stored in the LDAP back end.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Using this authentication system means that each IPA client can only edit its own DNS record; it cannot edit the DNS record of any other client.
+ </div></div></div><div class="formalpara"><h5 class="formalpara" id="id759444">Setting up Dynamic DNS Updates</h5>
+ The SSSD configuration file provides two options used for setting up dynamic DNS updates: <code class="option">ipa_dyndns_update</code>, used to enable dynamic DNS updates; and <code class="option">ipa_dyndns_iface</code>, which specifies the interface whose IP address should be used for dynamic DNS updates.
+ </div><div class="para">
+ Refer to the <em class="citetitle">sssd-ipa</em> manual page for more information about these options, and how to configure dynamic DNS updates.
+ </div><div class="note" title="Note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Support for dynamic DNS updates is only available on IPA version 2 or later, and with DNS correctly configured.
+ </div></div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Introduction.html"><strong>Prev</strong>8.2. The System Security Services Daemon (SSSD)</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="chap-SSSD_User_Guide-Setting_Up_SSSD.html"><strong>Next</strong>8.2.3. Setting Up SSSD</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html
new file mode 100644
index 0000000..8bc2f2d
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format.html
@@ -0,0 +1,71 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>8.2.8. SSSD Configuration File Format</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="chap-SSSD_User_Guide-Introduction.html" title="8.2. The System Security Services Daemon (SSSD)" /><link rel="prev" href="chap-SSSD_User_Guide-Troubleshooting.html" title="8.2.7. Troubleshooting" /><link rel="next" href="ch-OpenSSH.html" title="Chapter 9. OpenSSH" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Troubleshooting.html"><strong>Prev</s
trong></a></li><li class="next"><a accesskey="n" href="ch-OpenSSH.html"><strong>Next</strong></a></li></ul><div class="section" title="8.2.8. SSSD Configuration File Format" id="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="sect-SSSD_User_Guide-SSSD_Example_Configuration_Files-SSSD_Configuration_File_Format">8.2.8. SSSD Configuration File Format</h3></div></div></div><div class="para">
+ The following listing describes the current version (Version 2) of the SSSD configuration file format.
+ </div><pre class="programlisting">[sssd]
+config_file_version = 2
+services = nss, pam
+domains = mybox.example.com, ldap.example.com, ipa.example.com, nis.example.com
+# sbus_timeout = 300
+
+[nss]
+nss_filter_groups = root
+nss_filter_users = root
+nss_entry_cache_timeout = 30
+nss_enum_cache_timeout = 30
+
+[domain/mybox.example.com]
+domain_type = local
+enumerate = true
+min_id = 1000
+# max_id = 2000
+
+local_default_shell = /bin/bash
+local_default_homedir = /home
+
+# Possible overrides
+# id_provider = local
+# auth_provider = local
+# authz_provider = local
+# passwd_provider = local
+
+[domain/ldap.example.com]
+domain_type = ldap
+server = ldap.example.com, ldap3.example.com, 10.0.0.2
+# ldap_uri = ldaps://ldap.example.com:9093
+# ldap_use_tls = ssl
+ldap_search_base = dc=ldap,dc=example,dc=com
+enumerate = false
+
+# Possible overrides
+# id_provider = ldap
+# id_server = ldap2.example.com
+# auth_provider = krb5
+# auth_server = krb5.example.com
+# krb5_realm = KRB5.EXAMPLE.COM
+
+[domain/ipa.example.com]
+domain_type = ipa
+server = ipa.example.com, ipa2.example.com
+enumerate = false
+
+# Possible overrides
+# id_provider = ldap
+# id_server = ldap2.example.com
+# auth_provider = krb5
+# auth_server = krb5.example.com
+# krb5_realm = KRB5.EXAMPLE.COM
+
+[domain/nis.example.com]
+id_provider = proxy
+proxy_lib = nis
+auth_provider = proxy
+proxy_auth_target = nis_pam_proxy
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="chap-SSSD_User_Guide-Troubleshooting.html"><strong>Prev</strong>8.2.7. Troubleshooting</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="ch-OpenSSH.html"><strong>Next</strong>Chapter 9. OpenSSH</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/html/Deployment_Guide/testing-upload-method.html b/public_html/en-US/Fedora/14/html/Deployment_Guide/testing-upload-method.html
new file mode 100644
index 0000000..fa1ad64
--- /dev/null
+++ b/public_html/en-US/Fedora/14/html/Deployment_Guide/testing-upload-method.html
@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.7.2. Testing the Upload Method</title><link rel="stylesheet" href="Common_Content/css/default.css" type="text/css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.3" /><meta name="package" content="Fedora-Deployment_Guide-14-en-US-1.0-59" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.14');
+
+ addID('Fedora.14.books');
+ addID('Fedora.14.Deployment_Guide');
+ </script><link rel="home" href="index.html" title="Deployment Guide" /><link rel="up" href="configuring-centralized-crash-collection.html" title="21.7. Configuring Centralized Crash Collection" /><link rel="prev" href="configuring-centralized-crash-collection.html" title="21.7. Configuring Centralized Crash Collection" /><link rel="next" href="pt-kernel-configuration.html" title="Part V. Kernel, Module and Driver Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a ac
cesskey="p" href="configuring-centralized-crash-collection.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pt-kernel-configuration.html"><strong>Next</strong></a></li></ul><div class="section" title="21.7.2. Testing the Upload Method" id="testing-upload-method"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="testing-upload-method">21.7.2. Testing the Upload Method</h3></div></div></div><div class="para">
+ Test your upload method from a client system to ensure that it works. For example, upload a file using the interactive <code class="systemitem">FTP</code> client:
+ </div><pre class="screen">
+~]$ ftp
+ftp> open SERVERNAME
+Name: USERNAME
+Password: PASSWORD
+ftp> cd /var/spool/abrt-upload
+250 Operation successful
+ftp> put TESTFILE
+ftp> quit
+</pre><div class="para">
+ Check whether <code class="filename">TESTFILE</code> appeared in the correct directory on the server system.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="configuring-centralized-crash-collection.html"><strong>Prev</strong>21.7. Configuring Centralized Crash Collection</a></li><li class="up"><a accesskey="u" href="#"><strong>Up</strong></a></li><li class="home"><a accesskey="h" href="index.html"><strong>Home</strong></a></li><li class="next"><a accesskey="n" href="pt-kernel-configuration.html"><strong>Next</strong>Part V. Kernel, Module and Driver Configuration</a></li></ul></body></html>
diff --git a/public_html/en-US/Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf b/public_html/en-US/Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf
new file mode 100644
index 0000000..42feb79
Binary files /dev/null and b/public_html/en-US/Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf differ
diff --git a/public_html/en-US/Site_Statistics.html b/public_html/en-US/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/en-US/Site_Statistics.html
+++ b/public_html/en-US/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/en-US/opds-Fedora.xml b/public_html/en-US/opds-Fedora.xml
index 35293cc..30d201f 100644
--- a/public_html/en-US/opds-Fedora.xml
+++ b/public_html/en-US/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>en-US</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
index 222a4ca..191f0d3 100644
--- a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Core.xml b/public_html/en-US/opds-Fedora_Core.xml
index bd3b6af..ce2f0bf 100644
--- a/public_html/en-US/opds-Fedora_Core.xml
+++ b/public_html/en-US/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Draft_Documentation.xml b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
index 7bf88ef..d567608 100644
--- a/public_html/en-US/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds.xml b/public_html/en-US/opds.xml
index 8ecffcd..d69e1b4 100644
--- a/public_html/en-US/opds.xml
+++ b/public_html/en-US/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/en-US/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/en-US/toc.html b/public_html/en-US/toc.html
index 14d73a2..538ae35 100644
--- a/public_html/en-US/toc.html
+++ b/public_html/en-US/toc.html
@@ -99,6 +99,15 @@
<a class="type" href="./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed">
+ <a class="type" href="Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='./Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types" onclick="work=0;">
+ <a class="type" href="./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed">
<a class="type" href="Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='./Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types" onclick="work=0;">
diff --git a/public_html/es-ES/Site_Statistics.html b/public_html/es-ES/Site_Statistics.html
index 83202fa..ac9fb94 100644
--- a/public_html/es-ES/Site_Statistics.html
+++ b/public_html/es-ES/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Idiomas totales: </b>42<br />
- <b>Paquetes totales: </b>626
+ <b>Paquetes totales: </b>627
</div>
</body>
</html>
diff --git a/public_html/es-ES/opds-Fedora.xml b/public_html/es-ES/opds-Fedora.xml
index 97db2a6..2c8b6aa 100644
--- a/public_html/es-ES/opds-Fedora.xml
+++ b/public_html/es-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>es-ES</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-es-ES.epub</id>
<!--author>
diff --git a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
index 18b826d..7210274 100644
--- a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Core.xml b/public_html/es-ES/opds-Fedora_Core.xml
index 973ab09..6221b79 100644
--- a/public_html/es-ES/opds-Fedora_Core.xml
+++ b/public_html/es-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
index b51b8ed..56887a0 100644
--- a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds.xml b/public_html/es-ES/opds.xml
index e268eb1..5c3662f 100644
--- a/public_html/es-ES/opds.xml
+++ b/public_html/es-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/es-ES/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/es-ES/toc.html b/public_html/es-ES/toc.html
index d5edacd..9495e26 100644
--- a/public_html/es-ES/toc.html
+++ b/public_html/es-ES/toc.html
@@ -147,6 +147,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
@@ -328,6 +337,15 @@
<a class="type" href="../en-US/./Fedora/13/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.13.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.13.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.13.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/13/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.13.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/fa-IR/Site_Statistics.html b/public_html/fa-IR/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/fa-IR/Site_Statistics.html
+++ b/public_html/fa-IR/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/fa-IR/opds-Fedora.xml b/public_html/fa-IR/opds-Fedora.xml
index 0f83c28..e63b989 100644
--- a/public_html/fa-IR/opds-Fedora.xml
+++ b/public_html/fa-IR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>fa-IR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
index 5f97d03..55b3ba4 100644
--- a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Contributor_Documentation.xml</id>
<title>مستندات مشارکت کننده فدورا</title>
<subtitle>مستندات مشارکت کننده فدورا</subtitle>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Core.xml b/public_html/fa-IR/opds-Fedora_Core.xml
index 16a3b1b..58a2f91 100644
--- a/public_html/fa-IR/opds-Fedora_Core.xml
+++ b/public_html/fa-IR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
index 15afcc4..f6506d3 100644
--- a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds.xml b/public_html/fa-IR/opds.xml
index 0b4919c..d01e812 100644
--- a/public_html/fa-IR/opds.xml
+++ b/public_html/fa-IR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fa-IR/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>مستندات مشارکت کننده فدورا</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/fa-IR/toc.html b/public_html/fa-IR/toc.html
index 858bfd2..45779ea 100644
--- a/public_html/fa-IR/toc.html
+++ b/public_html/fa-IR/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/fi-FI/Site_Statistics.html b/public_html/fi-FI/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/fi-FI/Site_Statistics.html
+++ b/public_html/fi-FI/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/fi-FI/opds-Fedora.xml b/public_html/fi-FI/opds-Fedora.xml
index 66fe165..c14fa60 100644
--- a/public_html/fi-FI/opds-Fedora.xml
+++ b/public_html/fi-FI/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>fi-FI</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-fi-FI.epub</id>
<!--author>
diff --git a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
index 45d8ce6..17effcb 100644
--- a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Core.xml b/public_html/fi-FI/opds-Fedora_Core.xml
index 51c95ca..63ceef2 100644
--- a/public_html/fi-FI/opds-Fedora_Core.xml
+++ b/public_html/fi-FI/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
index 9d00fac..27e487f 100644
--- a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds.xml b/public_html/fi-FI/opds.xml
index 4f2d141..6fedd5e 100644
--- a/public_html/fi-FI/opds.xml
+++ b/public_html/fi-FI/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fi-FI/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/fi-FI/toc.html b/public_html/fi-FI/toc.html
index 2464775..ae7e6a6 100644
--- a/public_html/fi-FI/toc.html
+++ b/public_html/fi-FI/toc.html
@@ -111,6 +111,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/fr-FR/Site_Statistics.html b/public_html/fr-FR/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/fr-FR/Site_Statistics.html
+++ b/public_html/fr-FR/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/fr-FR/opds-Fedora.xml b/public_html/fr-FR/opds-Fedora.xml
index c883cb9..f7c3d09 100644
--- a/public_html/fr-FR/opds-Fedora.xml
+++ b/public_html/fr-FR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>fr-FR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
index 821e8fb..4639ef6 100644
--- a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Core.xml b/public_html/fr-FR/opds-Fedora_Core.xml
index 0d7fb67..b3aa1b0 100644
--- a/public_html/fr-FR/opds-Fedora_Core.xml
+++ b/public_html/fr-FR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
index b2fed72..cb84235 100644
--- a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds.xml b/public_html/fr-FR/opds.xml
index 5b67335..8772cc4 100644
--- a/public_html/fr-FR/opds.xml
+++ b/public_html/fr-FR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fr-FR/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/fr-FR/toc.html b/public_html/fr-FR/toc.html
index e18cd58..55192d6 100644
--- a/public_html/fr-FR/toc.html
+++ b/public_html/fr-FR/toc.html
@@ -111,6 +111,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/gu-IN/Site_Statistics.html b/public_html/gu-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/gu-IN/Site_Statistics.html
+++ b/public_html/gu-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/gu-IN/opds-Fedora.xml b/public_html/gu-IN/opds-Fedora.xml
index 17ad584..73514b9 100644
--- a/public_html/gu-IN/opds-Fedora.xml
+++ b/public_html/gu-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>gu-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
index 8e8036f..7fd8806 100644
--- a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Core.xml b/public_html/gu-IN/opds-Fedora_Core.xml
index 7cbdc78..e95d506 100644
--- a/public_html/gu-IN/opds-Fedora_Core.xml
+++ b/public_html/gu-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
index 0de16ff..7dc6f12 100644
--- a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds.xml b/public_html/gu-IN/opds.xml
index d4d02d6..17e76c8 100644
--- a/public_html/gu-IN/opds.xml
+++ b/public_html/gu-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/gu-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/gu-IN/toc.html b/public_html/gu-IN/toc.html
index 7a16eb2..593b4ee 100644
--- a/public_html/gu-IN/toc.html
+++ b/public_html/gu-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/he-IL/Site_Statistics.html b/public_html/he-IL/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/he-IL/Site_Statistics.html
+++ b/public_html/he-IL/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/he-IL/opds-Fedora.xml b/public_html/he-IL/opds-Fedora.xml
index f6c4d68..4de8a39 100644
--- a/public_html/he-IL/opds-Fedora.xml
+++ b/public_html/he-IL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>he-IL</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
index 29672e3..b898d97 100644
--- a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Core.xml b/public_html/he-IL/opds-Fedora_Core.xml
index a415b07..87cc8d2 100644
--- a/public_html/he-IL/opds-Fedora_Core.xml
+++ b/public_html/he-IL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
index 616a8ed..d85fc95 100644
--- a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds.xml b/public_html/he-IL/opds.xml
index e6e09ac..6f40cbf 100644
--- a/public_html/he-IL/opds.xml
+++ b/public_html/he-IL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/he-IL/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/he-IL/toc.html b/public_html/he-IL/toc.html
index f0be512..f667295 100644
--- a/public_html/he-IL/toc.html
+++ b/public_html/he-IL/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/hi-IN/Site_Statistics.html b/public_html/hi-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/hi-IN/Site_Statistics.html
+++ b/public_html/hi-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/hi-IN/opds-Fedora.xml b/public_html/hi-IN/opds-Fedora.xml
index 8feeea9..8962c6a 100644
--- a/public_html/hi-IN/opds-Fedora.xml
+++ b/public_html/hi-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>hi-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
index 3761370..0f9653d 100644
--- a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Core.xml b/public_html/hi-IN/opds-Fedora_Core.xml
index 4059b6c..07fa0fb 100644
--- a/public_html/hi-IN/opds-Fedora_Core.xml
+++ b/public_html/hi-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
index ffd40df..83d9744 100644
--- a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds.xml b/public_html/hi-IN/opds.xml
index d8a3ead..0c52b66 100644
--- a/public_html/hi-IN/opds.xml
+++ b/public_html/hi-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/hi-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/hi-IN/toc.html b/public_html/hi-IN/toc.html
index 9f80736..ae52243 100644
--- a/public_html/hi-IN/toc.html
+++ b/public_html/hi-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/hu-HU/Site_Statistics.html b/public_html/hu-HU/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/hu-HU/Site_Statistics.html
+++ b/public_html/hu-HU/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/hu-HU/opds-Fedora.xml b/public_html/hu-HU/opds-Fedora.xml
index 3b56eda..19034ba 100644
--- a/public_html/hu-HU/opds-Fedora.xml
+++ b/public_html/hu-HU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>hu-HU</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
index e586c4e..db3f608 100644
--- a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Core.xml b/public_html/hu-HU/opds-Fedora_Core.xml
index 14cd1cd..81d5399 100644
--- a/public_html/hu-HU/opds-Fedora_Core.xml
+++ b/public_html/hu-HU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
index 77210f1..7c8201a 100644
--- a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds.xml b/public_html/hu-HU/opds.xml
index 5839008..a9e36ba 100644
--- a/public_html/hu-HU/opds.xml
+++ b/public_html/hu-HU/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/hu-HU/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/hu-HU/toc.html b/public_html/hu-HU/toc.html
index ec89a90..276f24d 100644
--- a/public_html/hu-HU/toc.html
+++ b/public_html/hu-HU/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/id-ID/Site_Statistics.html b/public_html/id-ID/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/id-ID/Site_Statistics.html
+++ b/public_html/id-ID/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/id-ID/opds-Fedora.xml b/public_html/id-ID/opds-Fedora.xml
index 3c9e997..69e6052 100644
--- a/public_html/id-ID/opds-Fedora.xml
+++ b/public_html/id-ID/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>id-ID</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
index 43c48a7..0f4698f 100644
--- a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Core.xml b/public_html/id-ID/opds-Fedora_Core.xml
index 6f2328c..740f8aa 100644
--- a/public_html/id-ID/opds-Fedora_Core.xml
+++ b/public_html/id-ID/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
index 55ed36d..7b81786 100644
--- a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds.xml b/public_html/id-ID/opds.xml
index a33062d..6feb661 100644
--- a/public_html/id-ID/opds.xml
+++ b/public_html/id-ID/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/id-ID/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/id-ID/toc.html b/public_html/id-ID/toc.html
index 09e8a41..74075d9 100644
--- a/public_html/id-ID/toc.html
+++ b/public_html/id-ID/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/it-IT/Site_Statistics.html b/public_html/it-IT/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/it-IT/Site_Statistics.html
+++ b/public_html/it-IT/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/it-IT/opds-Fedora.xml b/public_html/it-IT/opds-Fedora.xml
index d1ba0e1..f11da2e 100644
--- a/public_html/it-IT/opds-Fedora.xml
+++ b/public_html/it-IT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>it-IT</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-it-IT.epub</id>
<!--author>
diff --git a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
index 6c15245..2efe2d3 100644
--- a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Core.xml b/public_html/it-IT/opds-Fedora_Core.xml
index 12cc39f..e150bfc 100644
--- a/public_html/it-IT/opds-Fedora_Core.xml
+++ b/public_html/it-IT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
index b4d37c8..6990865 100644
--- a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds.xml b/public_html/it-IT/opds.xml
index 08f3905..853b6bd 100644
--- a/public_html/it-IT/opds.xml
+++ b/public_html/it-IT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/it-IT/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/it-IT/toc.html b/public_html/it-IT/toc.html
index b5cc4c0..295fd18 100644
--- a/public_html/it-IT/toc.html
+++ b/public_html/it-IT/toc.html
@@ -138,6 +138,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ja-JP/Site_Statistics.html b/public_html/ja-JP/Site_Statistics.html
index c3792a0..6d03264 100644
--- a/public_html/ja-JP/Site_Statistics.html
+++ b/public_html/ja-JP/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>言語数の合計: </b>42<br />
- <b>パッケージ数の合計: </b>626
+ <b>パッケージ数の合計: </b>627
</div>
</body>
</html>
diff --git a/public_html/ja-JP/opds-Fedora.xml b/public_html/ja-JP/opds-Fedora.xml
index 0b7bbe4..47c8775 100644
--- a/public_html/ja-JP/opds-Fedora.xml
+++ b/public_html/ja-JP/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>ja-JP</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live イメージ</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-ja-JP.epub</id>
<!--author>
diff --git a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
index 90ff638..155ee25 100644
--- a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora コントリビュータ用ドキュメント</title>
<subtitle>Fedora コントリビュータ用ドキュメント</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Core.xml b/public_html/ja-JP/opds-Fedora_Core.xml
index edebfaf..5ccc812 100644
--- a/public_html/ja-JP/opds-Fedora_Core.xml
+++ b/public_html/ja-JP/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
index b3a4713..65aceda 100644
--- a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds.xml b/public_html/ja-JP/opds.xml
index fb17a07..393e966 100644
--- a/public_html/ja-JP/opds.xml
+++ b/public_html/ja-JP/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ja-JP/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora コントリビュータ用ドキュメント</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ja-JP/toc.html b/public_html/ja-JP/toc.html
index f8b4a14..29a6dab 100644
--- a/public_html/ja-JP/toc.html
+++ b/public_html/ja-JP/toc.html
@@ -120,6 +120,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/kn-IN/Site_Statistics.html b/public_html/kn-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/kn-IN/Site_Statistics.html
+++ b/public_html/kn-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/kn-IN/opds-Fedora.xml b/public_html/kn-IN/opds-Fedora.xml
index bb90ee6..091e485 100644
--- a/public_html/kn-IN/opds-Fedora.xml
+++ b/public_html/kn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>kn-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
index 88d3d2a..0510588 100644
--- a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Core.xml b/public_html/kn-IN/opds-Fedora_Core.xml
index 988d87a..50b6681 100644
--- a/public_html/kn-IN/opds-Fedora_Core.xml
+++ b/public_html/kn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
index 9c57d03..8083580 100644
--- a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds.xml b/public_html/kn-IN/opds.xml
index 1ac00af..cdc0477 100644
--- a/public_html/kn-IN/opds.xml
+++ b/public_html/kn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/kn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/kn-IN/toc.html b/public_html/kn-IN/toc.html
index 2292d24..7fe3c06 100644
--- a/public_html/kn-IN/toc.html
+++ b/public_html/kn-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ko-KR/Site_Statistics.html b/public_html/ko-KR/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/ko-KR/Site_Statistics.html
+++ b/public_html/ko-KR/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/ko-KR/opds-Fedora.xml b/public_html/ko-KR/opds-Fedora.xml
index 7dd1736..747cd83 100644
--- a/public_html/ko-KR/opds-Fedora.xml
+++ b/public_html/ko-KR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>ko-KR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
index 5fe6c84..5305b19 100644
--- a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Core.xml b/public_html/ko-KR/opds-Fedora_Core.xml
index 63e94e5..99f8c3b 100644
--- a/public_html/ko-KR/opds-Fedora_Core.xml
+++ b/public_html/ko-KR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
index ad22d51..d8fd707 100644
--- a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds.xml b/public_html/ko-KR/opds.xml
index b6133b2..7dd27a2 100644
--- a/public_html/ko-KR/opds.xml
+++ b/public_html/ko-KR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ko-KR/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ko-KR/toc.html b/public_html/ko-KR/toc.html
index 70b7516..4a20a13 100644
--- a/public_html/ko-KR/toc.html
+++ b/public_html/ko-KR/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ml-IN/Site_Statistics.html b/public_html/ml-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/ml-IN/Site_Statistics.html
+++ b/public_html/ml-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/ml-IN/opds-Fedora.xml b/public_html/ml-IN/opds-Fedora.xml
index 3bedced..5281ef5 100644
--- a/public_html/ml-IN/opds-Fedora.xml
+++ b/public_html/ml-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>ml-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
index 52e8fcb..47f5f39 100644
--- a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Core.xml b/public_html/ml-IN/opds-Fedora_Core.xml
index 218bacd..1af06d9 100644
--- a/public_html/ml-IN/opds-Fedora_Core.xml
+++ b/public_html/ml-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
index ed1d89f..7be79df 100644
--- a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds.xml b/public_html/ml-IN/opds.xml
index 97ce18a..33601d1 100644
--- a/public_html/ml-IN/opds.xml
+++ b/public_html/ml-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ml-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ml-IN/toc.html b/public_html/ml-IN/toc.html
index 0821e1d..40f4b04 100644
--- a/public_html/ml-IN/toc.html
+++ b/public_html/ml-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/mr-IN/Site_Statistics.html b/public_html/mr-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/mr-IN/Site_Statistics.html
+++ b/public_html/mr-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/mr-IN/opds-Fedora.xml b/public_html/mr-IN/opds-Fedora.xml
index 02b78c1..cb4018f 100644
--- a/public_html/mr-IN/opds-Fedora.xml
+++ b/public_html/mr-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>mr-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
index c52f6db..9fe7053 100644
--- a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Core.xml b/public_html/mr-IN/opds-Fedora_Core.xml
index e3c7ffd..acf6b08 100644
--- a/public_html/mr-IN/opds-Fedora_Core.xml
+++ b/public_html/mr-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
index 0ca43d8..e3f4d6a 100644
--- a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds.xml b/public_html/mr-IN/opds.xml
index 7170b0c..cb43853 100644
--- a/public_html/mr-IN/opds.xml
+++ b/public_html/mr-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/mr-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/mr-IN/toc.html b/public_html/mr-IN/toc.html
index 2418e24..98a8835 100644
--- a/public_html/mr-IN/toc.html
+++ b/public_html/mr-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/nb-NO/Site_Statistics.html b/public_html/nb-NO/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/nb-NO/Site_Statistics.html
+++ b/public_html/nb-NO/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/nb-NO/opds-Fedora.xml b/public_html/nb-NO/opds-Fedora.xml
index 74b2781..749d107 100644
--- a/public_html/nb-NO/opds-Fedora.xml
+++ b/public_html/nb-NO/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>nb-NO</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
index 10102e6..98cb88a 100644
--- a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Core.xml b/public_html/nb-NO/opds-Fedora_Core.xml
index f526104..91395aa 100644
--- a/public_html/nb-NO/opds-Fedora_Core.xml
+++ b/public_html/nb-NO/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
index 5bfd37e..475b254 100644
--- a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds.xml b/public_html/nb-NO/opds.xml
index 7d261cc..2b5634b 100644
--- a/public_html/nb-NO/opds.xml
+++ b/public_html/nb-NO/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/nb-NO/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/nb-NO/toc.html b/public_html/nb-NO/toc.html
index d390ca3..7c80e41 100644
--- a/public_html/nb-NO/toc.html
+++ b/public_html/nb-NO/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/nl-NL/Site_Statistics.html b/public_html/nl-NL/Site_Statistics.html
index 3fc39d3..4c14a67 100644
--- a/public_html/nl-NL/Site_Statistics.html
+++ b/public_html/nl-NL/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Totaal talen: </b>42<br />
- <b>Totaal pakketten: </b>626
+ <b>Totaal pakketten: </b>627
</div>
</body>
</html>
diff --git a/public_html/nl-NL/opds-Fedora.xml b/public_html/nl-NL/opds-Fedora.xml
index a99382c..0124f29 100644
--- a/public_html/nl-NL/opds-Fedora.xml
+++ b/public_html/nl-NL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>nl-NL</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-nl-NL.epub</id>
<!--author>
diff --git a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
index fb1aee1..f265019 100644
--- a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Core.xml b/public_html/nl-NL/opds-Fedora_Core.xml
index be5bb26..59bfc9d 100644
--- a/public_html/nl-NL/opds-Fedora_Core.xml
+++ b/public_html/nl-NL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
index 9ea1972..2b82b2c 100644
--- a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds.xml b/public_html/nl-NL/opds.xml
index 4be9551..3aefb18 100644
--- a/public_html/nl-NL/opds.xml
+++ b/public_html/nl-NL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/nl-NL/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/nl-NL/toc.html b/public_html/nl-NL/toc.html
index 9fe405d..77f7994 100644
--- a/public_html/nl-NL/toc.html
+++ b/public_html/nl-NL/toc.html
@@ -156,6 +156,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Musicians_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Musicians_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Musicians_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Musicians_Guide/index.html'"><span class="book">Musicians Guide</span></a>
<div id='Fedora.14.Musicians_Guide.types' class="types hidden" onclick="work=0;">
@@ -319,6 +328,15 @@
<a class="type" href="../en-US/./Fedora/13/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.13.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/13/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.13.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/13/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/13/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/13/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/13/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/13/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/13/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.13.Musicians_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.13.Musicians_Guide.types');">
<a class="type" href="../en-US/Fedora/13/html/Musicians_Guide/index.html" onclick="window.top.location='../en-US/Fedora/13/html/Musicians_Guide/index.html'"><span class="book">Musicians Guide</span></a>
<div id='Fedora.13.Musicians_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/opds.xml b/public_html/opds.xml
index 56e0f0c..506f13c 100644
--- a/public_html/opds.xml
+++ b/public_html/opds.xml
@@ -7,7 +7,7 @@
<link rel="start" href="http://docs.fedoraproject.org/opds.xml" type="application/atom+xml;type=feed;profile=opds-catalog"/>
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<title>Fedora Documentation</title>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
@@ -16,7 +16,7 @@
<entry>
<title>অসমীয়া</title>
<id>as-IN/opds.xml</id>
- <updated>2010-11-14T23:21:04</updated>
+ <updated>2010-11-14T23:46:05</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="as-IN/opds.xml"/>
@@ -24,7 +24,7 @@
<entry>
<title>български</title>
<id>bg-BG/opds.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bg-BG/opds.xml"/>
@@ -32,7 +32,7 @@
<entry>
<title>বাংলা</title>
<id>bn-IN/opds.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bn-IN/opds.xml"/>
@@ -40,7 +40,7 @@
<entry>
<title>Bosanski</title>
<id>bs-BA/opds.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bs-BA/opds.xml"/>
@@ -48,7 +48,7 @@
<entry>
<title>Català</title>
<id>ca-ES/opds.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ca-ES/opds.xml"/>
@@ -56,7 +56,7 @@
<entry>
<title>Čeština</title>
<id>cs-CZ/opds.xml</id>
- <updated>2010-11-14T23:21:05</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="cs-CZ/opds.xml"/>
@@ -64,7 +64,7 @@
<entry>
<title>Dansk</title>
<id>da-DK/opds.xml</id>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="da-DK/opds.xml"/>
@@ -72,7 +72,7 @@
<entry>
<title>Deutsch</title>
<id>de-DE/opds.xml</id>
- <updated>2010-11-14T23:21:06</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="de-DE/opds.xml"/>
@@ -80,7 +80,7 @@
<entry>
<title>Ελληνικά</title>
<id>el-GR/opds.xml</id>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="el-GR/opds.xml"/>
@@ -88,7 +88,7 @@
<entry>
<title>English</title>
<id>en-US/opds.xml</id>
- <updated>2010-11-14T23:21:07</updated>
+ <updated>2010-11-14T23:46:06</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="en-US/opds.xml"/>
@@ -96,7 +96,7 @@
<entry>
<title>Español</title>
<id>es-ES/opds.xml</id>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="es-ES/opds.xml"/>
@@ -104,7 +104,7 @@
<entry>
<title>فارسی</title>
<id>fa-IR/opds.xml</id>
- <updated>2010-11-14T23:21:08</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fa-IR/opds.xml"/>
@@ -112,7 +112,7 @@
<entry>
<title>Suomi</title>
<id>fi-FI/opds.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fi-FI/opds.xml"/>
@@ -120,7 +120,7 @@
<entry>
<title>Français</title>
<id>fr-FR/opds.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fr-FR/opds.xml"/>
@@ -128,7 +128,7 @@
<entry>
<title>ગુજરાતી</title>
<id>gu-IN/opds.xml</id>
- <updated>2010-11-14T23:21:09</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="gu-IN/opds.xml"/>
@@ -136,7 +136,7 @@
<entry>
<title>עברית</title>
<id>he-IL/opds.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="he-IL/opds.xml"/>
@@ -144,7 +144,7 @@
<entry>
<title>हिन्दी</title>
<id>hi-IN/opds.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hi-IN/opds.xml"/>
@@ -152,7 +152,7 @@
<entry>
<title>Magyar</title>
<id>hu-HU/opds.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hu-HU/opds.xml"/>
@@ -160,7 +160,7 @@
<entry>
<title>Indonesia</title>
<id>id-ID/opds.xml</id>
- <updated>2010-11-14T23:21:10</updated>
+ <updated>2010-11-14T23:46:07</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="id-ID/opds.xml"/>
@@ -168,7 +168,7 @@
<entry>
<title>Italiano</title>
<id>it-IT/opds.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="it-IT/opds.xml"/>
@@ -176,7 +176,7 @@
<entry>
<title>日本語</title>
<id>ja-JP/opds.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ja-JP/opds.xml"/>
@@ -184,7 +184,7 @@
<entry>
<title>ಕನ್ನಡ</title>
<id>kn-IN/opds.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="kn-IN/opds.xml"/>
@@ -192,7 +192,7 @@
<entry>
<title>한국어</title>
<id>ko-KR/opds.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ko-KR/opds.xml"/>
@@ -200,7 +200,7 @@
<entry>
<title>മലയാളം</title>
<id>ml-IN/opds.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ml-IN/opds.xml"/>
@@ -208,7 +208,7 @@
<entry>
<title>मराठी</title>
<id>mr-IN/opds.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="mr-IN/opds.xml"/>
@@ -216,7 +216,7 @@
<entry>
<title>Norsk (bokmål)</title>
<id>nb-NO/opds.xml</id>
- <updated>2010-11-14T23:21:11</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nb-NO/opds.xml"/>
@@ -224,7 +224,7 @@
<entry>
<title>Nederlands</title>
<id>nl-NL/opds.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nl-NL/opds.xml"/>
@@ -232,7 +232,7 @@
<entry>
<title>ଓଡ଼ିଆ</title>
<id>or-IN/opds.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="or-IN/opds.xml"/>
@@ -240,7 +240,7 @@
<entry>
<title>ਪੰਜਾਬੀ</title>
<id>pa-IN/opds.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pa-IN/opds.xml"/>
@@ -248,7 +248,7 @@
<entry>
<title>Polski</title>
<id>pl-PL/opds.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pl-PL/opds.xml"/>
@@ -256,7 +256,7 @@
<entry>
<title>Português Brasileiro</title>
<id>pt-BR/opds.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-BR/opds.xml"/>
@@ -264,7 +264,7 @@
<entry>
<title>Português</title>
<id>pt-PT/opds.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-PT/opds.xml"/>
@@ -272,7 +272,7 @@
<entry>
<title>Русский</title>
<id>ru-RU/opds.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ru-RU/opds.xml"/>
@@ -280,7 +280,7 @@
<entry>
<title>Slovenščina</title>
<id>sk-SK/opds.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sk-SK/opds.xml"/>
@@ -288,7 +288,7 @@
<entry>
<title>Srpski (latinica)</title>
<id>sr-Latn-RS/opds.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-Latn-RS/opds.xml"/>
@@ -296,7 +296,7 @@
<entry>
<title>Српски</title>
<id>sr-RS/opds.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-RS/opds.xml"/>
@@ -304,7 +304,7 @@
<entry>
<title>Svenska</title>
<id>sv-SE/opds.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sv-SE/opds.xml"/>
@@ -312,7 +312,7 @@
<entry>
<title>தமிழ்</title>
<id>ta-IN/opds.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ta-IN/opds.xml"/>
@@ -320,7 +320,7 @@
<entry>
<title>తెలుగు</title>
<id>te-IN/opds.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="te-IN/opds.xml"/>
@@ -328,7 +328,7 @@
<entry>
<title>Українська</title>
<id>uk-UA/opds.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="uk-UA/opds.xml"/>
@@ -336,7 +336,7 @@
<entry>
<title>简体中文</title>
<id>zh-CN/opds.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-CN/opds.xml"/>
@@ -344,7 +344,7 @@
<entry>
<title>繁體中文</title>
<id>zh-TW/opds.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-TW/opds.xml"/>
diff --git a/public_html/or-IN/Site_Statistics.html b/public_html/or-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/or-IN/Site_Statistics.html
+++ b/public_html/or-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/or-IN/opds-Fedora.xml b/public_html/or-IN/opds-Fedora.xml
index deff020..36a8efe 100644
--- a/public_html/or-IN/opds-Fedora.xml
+++ b/public_html/or-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>or-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
index ea0a895..11a6cc4 100644
--- a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Core.xml b/public_html/or-IN/opds-Fedora_Core.xml
index d8b8ff9..d33a50a 100644
--- a/public_html/or-IN/opds-Fedora_Core.xml
+++ b/public_html/or-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
index aed42fe..a3ccc8b 100644
--- a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds.xml b/public_html/or-IN/opds.xml
index 562f9da..8231734 100644
--- a/public_html/or-IN/opds.xml
+++ b/public_html/or-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/or-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/or-IN/toc.html b/public_html/or-IN/toc.html
index 57183f6..f4269cb 100644
--- a/public_html/or-IN/toc.html
+++ b/public_html/or-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/pa-IN/Site_Statistics.html b/public_html/pa-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/pa-IN/Site_Statistics.html
+++ b/public_html/pa-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/pa-IN/opds-Fedora.xml b/public_html/pa-IN/opds-Fedora.xml
index 05a0475..49579d4 100644
--- a/public_html/pa-IN/opds-Fedora.xml
+++ b/public_html/pa-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:08</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>pa-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
index d55c1f9..c61cb98 100644
--- a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Core.xml b/public_html/pa-IN/opds-Fedora_Core.xml
index 6ff3805..75981f2 100644
--- a/public_html/pa-IN/opds-Fedora_Core.xml
+++ b/public_html/pa-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
index 9eccbc1..1ae5e79 100644
--- a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds.xml b/public_html/pa-IN/opds.xml
index 1f130d1..691fe6d 100644
--- a/public_html/pa-IN/opds.xml
+++ b/public_html/pa-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pa-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pa-IN/toc.html b/public_html/pa-IN/toc.html
index 8c2ad0c..991ba41 100644
--- a/public_html/pa-IN/toc.html
+++ b/public_html/pa-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/pl-PL/Site_Statistics.html b/public_html/pl-PL/Site_Statistics.html
index 01ccde2..c878466 100644
--- a/public_html/pl-PL/Site_Statistics.html
+++ b/public_html/pl-PL/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Razem języków: </b>42<br />
- <b>Razem pakietów: </b>626
+ <b>Razem pakietów: </b>627
</div>
</body>
</html>
diff --git a/public_html/pl-PL/opds-Fedora.xml b/public_html/pl-PL/opds-Fedora.xml
index 4a92209..585cfb9 100644
--- a/public_html/pl-PL/opds-Fedora.xml
+++ b/public_html/pl-PL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>pl-PL</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-pl-PL.epub</id>
<!--author>
diff --git a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
index 54b49fb..c5898ec 100644
--- a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Dokumentacja dla współtwórców Fedory</title>
<subtitle>Dokumentacja dla współtwórców Fedory</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Core.xml b/public_html/pl-PL/opds-Fedora_Core.xml
index 0503d3e..08f59ec 100644
--- a/public_html/pl-PL/opds-Fedora_Core.xml
+++ b/public_html/pl-PL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
index 2189315..40e6557 100644
--- a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds.xml b/public_html/pl-PL/opds.xml
index e207d18..76b05fc 100644
--- a/public_html/pl-PL/opds.xml
+++ b/public_html/pl-PL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pl-PL/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Dokumentacja dla współtwórców Fedory</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pl-PL/toc.html b/public_html/pl-PL/toc.html
index 05386ac..8d113dc 100644
--- a/public_html/pl-PL/toc.html
+++ b/public_html/pl-PL/toc.html
@@ -120,6 +120,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/pt-BR/Site_Statistics.html b/public_html/pt-BR/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/pt-BR/Site_Statistics.html
+++ b/public_html/pt-BR/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/pt-BR/opds-Fedora.xml b/public_html/pt-BR/opds-Fedora.xml
index a79ef59..43ba3fa 100644
--- a/public_html/pt-BR/opds-Fedora.xml
+++ b/public_html/pt-BR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>pt-BR</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
index 5a40d60..641eef9 100644
--- a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Core.xml b/public_html/pt-BR/opds-Fedora_Core.xml
index 0ea039a..49e7b90 100644
--- a/public_html/pt-BR/opds-Fedora_Core.xml
+++ b/public_html/pt-BR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
index 457774e..1eaa9f5 100644
--- a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds.xml b/public_html/pt-BR/opds.xml
index f1d2c71..56a9e72 100644
--- a/public_html/pt-BR/opds.xml
+++ b/public_html/pt-BR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pt-BR/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:12</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pt-BR/toc.html b/public_html/pt-BR/toc.html
index a1cd772..37b469a 100644
--- a/public_html/pt-BR/toc.html
+++ b/public_html/pt-BR/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/pt-PT/Site_Statistics.html b/public_html/pt-PT/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/pt-PT/Site_Statistics.html
+++ b/public_html/pt-PT/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/pt-PT/opds-Fedora.xml b/public_html/pt-PT/opds-Fedora.xml
index c41a518..6013c0c 100644
--- a/public_html/pt-PT/opds-Fedora.xml
+++ b/public_html/pt-PT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>pt-PT</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-pt-PT.epub</id>
<!--author>
diff --git a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
index ab48e7b..ba5818d 100644
--- a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Core.xml b/public_html/pt-PT/opds-Fedora_Core.xml
index 7dee4e9..c7b0cea 100644
--- a/public_html/pt-PT/opds-Fedora_Core.xml
+++ b/public_html/pt-PT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
index 29e0301..a17eabf 100644
--- a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds.xml b/public_html/pt-PT/opds.xml
index 9376c9e..17d04ab 100644
--- a/public_html/pt-PT/opds.xml
+++ b/public_html/pt-PT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pt-PT/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/pt-PT/toc.html b/public_html/pt-PT/toc.html
index 2c03bbf..00170f4 100644
--- a/public_html/pt-PT/toc.html
+++ b/public_html/pt-PT/toc.html
@@ -111,6 +111,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ru-RU/Site_Statistics.html b/public_html/ru-RU/Site_Statistics.html
index 4fb6815..adb2c09 100644
--- a/public_html/ru-RU/Site_Statistics.html
+++ b/public_html/ru-RU/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Всего языков: </b>42<br />
- <b>Всего пакетов: </b>626
+ <b>Всего пакетов: </b>627
</div>
</body>
</html>
diff --git a/public_html/ru-RU/opds-Fedora.xml b/public_html/ru-RU/opds-Fedora.xml
index 170dbae..bfd7762 100644
--- a/public_html/ru-RU/opds-Fedora.xml
+++ b/public_html/ru-RU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>ru-RU</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-ru-RU.epub</id>
<!--author>
diff --git a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
index ffe64c1..bc1ed6b 100644
--- a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Core.xml b/public_html/ru-RU/opds-Fedora_Core.xml
index cc7ec8b..bdc87cf 100644
--- a/public_html/ru-RU/opds-Fedora_Core.xml
+++ b/public_html/ru-RU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
index 5cdf39a..1ef89b0 100644
--- a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds.xml b/public_html/ru-RU/opds.xml
index 3036794..9695ff5 100644
--- a/public_html/ru-RU/opds.xml
+++ b/public_html/ru-RU/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ru-RU/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ru-RU/toc.html b/public_html/ru-RU/toc.html
index 26debfd..8453e9c 100644
--- a/public_html/ru-RU/toc.html
+++ b/public_html/ru-RU/toc.html
@@ -120,6 +120,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/sk-SK/Site_Statistics.html b/public_html/sk-SK/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/sk-SK/Site_Statistics.html
+++ b/public_html/sk-SK/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/sk-SK/opds-Fedora.xml b/public_html/sk-SK/opds-Fedora.xml
index 9b43d0c..d9a9f4a 100644
--- a/public_html/sk-SK/opds-Fedora.xml
+++ b/public_html/sk-SK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>sk-SK</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
index ae7bbf2..8050957 100644
--- a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Core.xml b/public_html/sk-SK/opds-Fedora_Core.xml
index a99b488..0ef8263 100644
--- a/public_html/sk-SK/opds-Fedora_Core.xml
+++ b/public_html/sk-SK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
index 45ffb34..36505c4 100644
--- a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds.xml b/public_html/sk-SK/opds.xml
index 0d7847b..9e7b853 100644
--- a/public_html/sk-SK/opds.xml
+++ b/public_html/sk-SK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sk-SK/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sk-SK/toc.html b/public_html/sk-SK/toc.html
index 37a565d..acbc256 100644
--- a/public_html/sk-SK/toc.html
+++ b/public_html/sk-SK/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/sr-Latn-RS/Site_Statistics.html b/public_html/sr-Latn-RS/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/sr-Latn-RS/Site_Statistics.html
+++ b/public_html/sr-Latn-RS/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/sr-Latn-RS/opds-Fedora.xml b/public_html/sr-Latn-RS/opds-Fedora.xml
index 940f36a..f1f1e46 100644
--- a/public_html/sr-Latn-RS/opds-Fedora.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>sr-Latn-RS</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
index 53d9c04..bbbca72 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Core.xml b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
index 99dab9a..9bdefe1 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
index 1d91451..3b3388b 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds.xml b/public_html/sr-Latn-RS/opds.xml
index cd82e27..a829cf3 100644
--- a/public_html/sr-Latn-RS/opds.xml
+++ b/public_html/sr-Latn-RS/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sr-Latn-RS/toc.html b/public_html/sr-Latn-RS/toc.html
index 93536de..e3a6a57 100644
--- a/public_html/sr-Latn-RS/toc.html
+++ b/public_html/sr-Latn-RS/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/sr-RS/Site_Statistics.html b/public_html/sr-RS/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/sr-RS/Site_Statistics.html
+++ b/public_html/sr-RS/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/sr-RS/opds-Fedora.xml b/public_html/sr-RS/opds-Fedora.xml
index 579eef9..ab544fe 100644
--- a/public_html/sr-RS/opds-Fedora.xml
+++ b/public_html/sr-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>sr-RS</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
index 166b639..b4b97bf 100644
--- a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Core.xml b/public_html/sr-RS/opds-Fedora_Core.xml
index ee15ff1..d0f5ce9 100644
--- a/public_html/sr-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
index cce01e3..de4096b 100644
--- a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds.xml b/public_html/sr-RS/opds.xml
index 892e72a..6a956b3 100644
--- a/public_html/sr-RS/opds.xml
+++ b/public_html/sr-RS/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sr-RS/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sr-RS/toc.html b/public_html/sr-RS/toc.html
index c85760b..7c5508c 100644
--- a/public_html/sr-RS/toc.html
+++ b/public_html/sr-RS/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/sv-SE/Site_Statistics.html b/public_html/sv-SE/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/sv-SE/Site_Statistics.html
+++ b/public_html/sv-SE/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/sv-SE/opds-Fedora.xml b/public_html/sv-SE/opds-Fedora.xml
index 515b3a6..6f38131 100644
--- a/public_html/sv-SE/opds-Fedora.xml
+++ b/public_html/sv-SE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>sv-SE</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-sv-SE.epub</id>
<!--author>
diff --git a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
index 18d5931..82209a1 100644
--- a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Core.xml b/public_html/sv-SE/opds-Fedora_Core.xml
index 51b79f2..2ccf031 100644
--- a/public_html/sv-SE/opds-Fedora_Core.xml
+++ b/public_html/sv-SE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
index 19a4edc..0c89a93 100644
--- a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds.xml b/public_html/sv-SE/opds.xml
index 1f22657..a0c0cb5 100644
--- a/public_html/sv-SE/opds.xml
+++ b/public_html/sv-SE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sv-SE/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/sv-SE/toc.html b/public_html/sv-SE/toc.html
index 7f96bb6..b59a554 100644
--- a/public_html/sv-SE/toc.html
+++ b/public_html/sv-SE/toc.html
@@ -120,6 +120,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/ta-IN/Site_Statistics.html b/public_html/ta-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/ta-IN/Site_Statistics.html
+++ b/public_html/ta-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/ta-IN/opds-Fedora.xml b/public_html/ta-IN/opds-Fedora.xml
index 12166c8..1eb9b1e 100644
--- a/public_html/ta-IN/opds-Fedora.xml
+++ b/public_html/ta-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>ta-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
index 61bf762..42df4be 100644
--- a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Core.xml b/public_html/ta-IN/opds-Fedora_Core.xml
index b88f3b6..af23d97 100644
--- a/public_html/ta-IN/opds-Fedora_Core.xml
+++ b/public_html/ta-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
index 45b6e49..ca41841 100644
--- a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds.xml b/public_html/ta-IN/opds.xml
index 7b85a8f..3279a91 100644
--- a/public_html/ta-IN/opds.xml
+++ b/public_html/ta-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ta-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:09</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/ta-IN/toc.html b/public_html/ta-IN/toc.html
index 3dc08fd..3a597f4 100644
--- a/public_html/ta-IN/toc.html
+++ b/public_html/ta-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/te-IN/Site_Statistics.html b/public_html/te-IN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/te-IN/Site_Statistics.html
+++ b/public_html/te-IN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/te-IN/opds-Fedora.xml b/public_html/te-IN/opds-Fedora.xml
index 3ac8cc9..e3ab619 100644
--- a/public_html/te-IN/opds-Fedora.xml
+++ b/public_html/te-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>te-IN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
index 5595008..1e9c0e9 100644
--- a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Core.xml b/public_html/te-IN/opds-Fedora_Core.xml
index d15e4b4..9e2014c 100644
--- a/public_html/te-IN/opds-Fedora_Core.xml
+++ b/public_html/te-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
index d147188..5e7e168 100644
--- a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds.xml b/public_html/te-IN/opds.xml
index 77b58da..75d440d 100644
--- a/public_html/te-IN/opds.xml
+++ b/public_html/te-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/te-IN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:13</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/te-IN/toc.html b/public_html/te-IN/toc.html
index 7add637..c8d4cbc 100644
--- a/public_html/te-IN/toc.html
+++ b/public_html/te-IN/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/toc.html b/public_html/toc.html
index 091145d..eaf59c0 100644
--- a/public_html/toc.html
+++ b/public_html/toc.html
@@ -1248,6 +1248,21 @@
</div>
<div class="book">
+ <span id="Deployment_Guide" class="book">Deployment Guide</span>
+ <div class="types">
+
+ <a class="type" href="./en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">epub</a>
+
+ <a class="type" href="./en-US/Fedora/14/html/Deployment_Guide/index.html">html</a>
+
+ <a class="type" href="./en-US/Fedora/14/html-single/Deployment_Guide/index.html">html-single</a>
+
+ <a class="type" href="./en-US/Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf">pdf</a>
+
+ </div>
+ </div>
+
+ <div class="book">
<span id="Fedora_Live_Images" class="book">Fedora Live Images</span>
<div class="types">
diff --git a/public_html/uk-UA/Site_Statistics.html b/public_html/uk-UA/Site_Statistics.html
index 17eae86..2562264 100644
--- a/public_html/uk-UA/Site_Statistics.html
+++ b/public_html/uk-UA/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Загалом мов: </b>42<br />
- <b>Загалом пакунків: </b>626
+ <b>Загалом пакунків: </b>627
</div>
</body>
</html>
diff --git a/public_html/uk-UA/opds-Fedora.xml b/public_html/uk-UA/opds-Fedora.xml
index cf39701..bf7361d 100644
--- a/public_html/uk-UA/opds-Fedora.xml
+++ b/public_html/uk-UA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>uk-UA</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-uk-UA.epub</id>
<!--author>
diff --git a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
index 2907969..3fd3180 100644
--- a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Contributor_Documentation.xml</id>
<title>Документація для учасника розробки Fedora</title>
<subtitle>Документація для учасника розробки Fedora</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Core.xml b/public_html/uk-UA/opds-Fedora_Core.xml
index afae448..fc11ffb 100644
--- a/public_html/uk-UA/opds-Fedora_Core.xml
+++ b/public_html/uk-UA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
index 8d4eaed..530d82b 100644
--- a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds.xml b/public_html/uk-UA/opds.xml
index 6d8aa22..a5c35f4 100644
--- a/public_html/uk-UA/opds.xml
+++ b/public_html/uk-UA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/uk-UA/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Документація для учасника розробки Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/uk-UA/toc.html b/public_html/uk-UA/toc.html
index 147ea81..73e0144 100644
--- a/public_html/uk-UA/toc.html
+++ b/public_html/uk-UA/toc.html
@@ -129,6 +129,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Amateur_Radio_Guide/Fedora-14-Amateur_Radio_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/zh-CN/Site_Statistics.html b/public_html/zh-CN/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/zh-CN/Site_Statistics.html
+++ b/public_html/zh-CN/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/zh-CN/opds-Fedora.xml b/public_html/zh-CN/opds-Fedora.xml
index f662171..54eead3 100644
--- a/public_html/zh-CN/opds-Fedora.xml
+++ b/public_html/zh-CN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>zh-CN</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-zh-CN.epub</id>
<!--author>
diff --git a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
index df3fdd6..d650601 100644
--- a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Core.xml b/public_html/zh-CN/opds-Fedora_Core.xml
index ab031ea..3bfe460 100644
--- a/public_html/zh-CN/opds-Fedora_Core.xml
+++ b/public_html/zh-CN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
index cc1b354..d92b4b5 100644
--- a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds.xml b/public_html/zh-CN/opds.xml
index 5d4b4cc..c600130 100644
--- a/public_html/zh-CN/opds.xml
+++ b/public_html/zh-CN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/zh-CN/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/zh-CN/toc.html b/public_html/zh-CN/toc.html
index 18b7e9f..45cbfe6 100644
--- a/public_html/zh-CN/toc.html
+++ b/public_html/zh-CN/toc.html
@@ -111,6 +111,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Installation_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Installation_Guide.types');">
<a class="type" href="../en-US/Fedora/14/html/Installation_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Installation_Guide/index.html'"><span class="book">Installation Guide</span></a>
<div id='Fedora.14.Installation_Guide.types' class="types hidden" onclick="work=0;">
diff --git a/public_html/zh-TW/Site_Statistics.html b/public_html/zh-TW/Site_Statistics.html
index 92d0107..cfeb0ce 100644
--- a/public_html/zh-TW/Site_Statistics.html
+++ b/public_html/zh-TW/Site_Statistics.html
@@ -28,7 +28,7 @@
<td>4</td>
<td>27</td>
<td>15</td>
- <td>85</td>
+ <td>86</td>
</tr>
<tr>
@@ -403,7 +403,7 @@
</table>
<div class="totals">
<b>Total Languages: </b>42<br />
- <b>Total Packages: </b>626
+ <b>Total Packages: </b>627
</div>
</body>
</html>
diff --git a/public_html/zh-TW/opds-Fedora.xml b/public_html/zh-TW/opds-Fedora.xml
index a48c58d..8769e03 100644
--- a/public_html/zh-TW/opds-Fedora.xml
+++ b/public_html/zh-TW/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
@@ -70,6 +70,25 @@
<!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
</entry>
<entry>
+ <title>Deployment Guide</title>
+ <id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub</id>
+ <!--author>
+ <name></name>
+ <uri></uri>
+ </author-->
+ <updated>2010-11-14</updated>
+ <dc:language>zh-TW</dc:language>
+ <category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
+ <!--dc:issued></dc:issued-->
+ <summary>Deployment, configuration and administration of Fedora 14
+</summary>
+ <content type="text">The Deployment Guide documents relevant information regarding the deployment, configuration and administration of Fedora 14.</content>
+ <link type="application/epub+zip" rel="http://opds-spec.org/acquisition" href="http://docs.fedoraproject.org/en-US/Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub">
+ <dc:format>application/epub+zip</dc:format>
+ </link>
+ <!--link type="application/atom+xml;type=entry" href="" rel="alternate" title="Full entry"/-->
+ </entry>
+ <entry>
<title>Fedora Live Images</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/14/epub/Fedora_Live_Images/Fedora-14-Fedora_Live_Images-en-US.epub</id>
<!--author>
diff --git a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
index 5abf4a9..c80ad62 100644
--- a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Core.xml b/public_html/zh-TW/opds-Fedora_Core.xml
index c53baff..cde763b 100644
--- a/public_html/zh-TW/opds-Fedora_Core.xml
+++ b/public_html/zh-TW/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
index ad07a3c..9dcc12a 100644
--- a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds.xml b/public_html/zh-TW/opds.xml
index 52e441b..34c0a9f 100644
--- a/public_html/zh-TW/opds.xml
+++ b/public_html/zh-TW/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/zh-TW/opds.xml</id>
<title>Product List</title>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora/opds-Fedora.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2010-11-14T23:21:14</updated>
+ <updated>2010-11-14T23:46:10</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
diff --git a/public_html/zh-TW/toc.html b/public_html/zh-TW/toc.html
index 73c1ee5..15ad2c7 100644
--- a/public_html/zh-TW/toc.html
+++ b/public_html/zh-TW/toc.html
@@ -102,6 +102,15 @@
<a class="type" href="../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Burning_ISO_images_to_disc/Fedora-14-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
+ <div id='Fedora.14.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.14.Deployment_Guide.types');">
+ <a class="type" href="../en-US/Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Deployment_Guide/index.html'"><span class="book">Deployment Guide</span></a>
+ <div id='Fedora.14.Deployment_Guide.types' class="types hidden" onclick="work=0;">
+ <a class="type" href="../en-US/./Fedora/14/epub/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.epub" >epub</a>
+ <a class="type" href="../en-US/./Fedora/14/html/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html/Deployment_Guide/index.html';return false;">html</a>
+ <a class="type" href="../en-US/./Fedora/14/html-single/Deployment_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/14/html-single/Deployment_Guide/index.html';return false;">html-single</a>
+ <a class="type" href="../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/14/pdf/Deployment_Guide/Fedora-14-Deployment_Guide-en-US.pdf';return false;">pdf</a>
+ </div>
+ </div>
<div id='Fedora.14.Fedora_Live_Images' class="book collapsed" onclick="toggle(event, 'Fedora.14.Fedora_Live_Images.types');">
<a class="type" href="../en-US/Fedora/14/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/Fedora/14/html/Fedora_Live_Images/index.html'"><span class="book">Fedora Live Images</span></a>
<div id='Fedora.14.Fedora_Live_Images.types' class="types hidden" onclick="work=0;">
More information about the docs-commits
mailing list